
From marcelo@it.uc3m.es  Tue Sep  1 00:26:12 2009
Return-Path: <marcelo@it.uc3m.es>
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 CFC5428C3D1 for <behave@core3.amsl.com>; Tue,  1 Sep 2009 00:26:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.571
X-Spam-Level: 
X-Spam-Status: No, score=-6.571 tagged_above=-999 required=5 tests=[AWL=0.028,  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 FHhE0R0BsMGG for <behave@core3.amsl.com>; Tue,  1 Sep 2009 00:26:12 -0700 (PDT)
Received: from smtp02.uc3m.es (smtp02.uc3m.es [163.117.176.132]) by core3.amsl.com (Postfix) with ESMTP id A875728C320 for <behave@ietf.org>; Tue,  1 Sep 2009 00:26:11 -0700 (PDT)
Received: from marcelo-bagnulos-macbook-pro.local (wlap005.it.uc3m.es [163.117.139.108]) by smtp02.uc3m.es (Postfix) with ESMTP id 331666C17C0; Tue,  1 Sep 2009 09:26:22 +0200 (CEST)
Message-ID: <4A9CCC9E.7090202@it.uc3m.es>
Date: Tue, 01 Sep 2009 09:26:22 +0200
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
User-Agent: Thunderbird 2.0.0.22 (Macintosh/20090605)
MIME-Version: 1.0
To: Dave Thaler <dthaler@microsoft.com>
References: <2991246A29623A4082EB2B06A2B891A41B7C3D85A9@EUSAACMS0703.eamcs.ericsson.se>	<200908280743.18009.simon.perreault@viagenie.ca>	<2991246A29623A4082EB2B06A2B891A41B7C42ED53@EUSAACMS0703.eamcs.ericsson.se>	<200908281141.28240.simon.perreault@viagenie.ca>	<1d38a3350908282033t67bf8824of7fcfb48f8efe280@mail.gmail.com> <4A98E244.1060605@it.uc3m.es> <E4561B14EE2A3E4E9D478EBFB5416E1B1C29A4@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <E4561B14EE2A3E4E9D478EBFB5416E1B1C29A4@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-TM-AS-Product-Ver: IMSS-7.0.0.3116-5.6.0.1016-16860.003
Cc: Hui Deng <denghui02@gmail.com>, Wassim Haddad <wassim.haddad@ericsson.com>, "behave@ietf.org" <behave@ietf.org>
Subject: Re: [BEHAVE] NAT64 and MIPv6
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/mail-archive/web/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>
X-List-Received-Date: Tue, 01 Sep 2009 07:26:12 -0000

Dave Thaler escribió:
>> -----Original Message-----
>> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On
>> Behalf Of marcelo bagnulo braun
>> Sent: Saturday, August 29, 2009 1:10 AM
>> To: Hui Deng
>> Cc: Wassim Haddad; behave@ietf.org
>> Subject: Re: [BEHAVE] NAT64 and MIPv6
>>
>> Hui Deng escribió:
>>     
>>> I am doubting that NAT64 doesn't change the host,
>>> how it learn translator prefix?
>>>
>>>       
>> the host behind a nat64 doesn't need to learn the prefix for the basic
>> support i.e. to support basic applications (such as any application
>> that
>> works through nat today) and to support a validating stub resolver.
>>     
>                            ^^^^^^^^^^^^^^^^^^^^^^^^^^^
> I think there's a typo above.  I think you meant to say it doesn't
> need to learn the prefix to support a non-validating security-aware
> stub resolver (which is what Windows 7 supports, BTW).
>   

right,
also that it needs to learn the prefix to support a validating stub 
resolver.

Regards, marcelo

> -Dave
>
>   
>> Regards, marcelo
>>
>>     
>>> -Hui
>>>
>>> 2009/8/28 Simon Perreault <simon.perreault@viagenie.ca>:
>>>
>>>       
>>>> On Friday 28 August 2009 11:31:34 Wassim Haddad wrote:
>>>>
>>>>         
>>>>> NAT64 doesn't assume anything about the host, while
>>>>> PNAT64 assumes that the host implements PNAT64.
>>>>>
>>>>> => Your comment does not help solve/avoid the problem!
>>>>>
>>>>>           
>>>> My apologies. Here's something more constructive:
>>>>
>>>> It is pointless to try to solve the problem you pointed out by
>>>>         
>> changing the
>>     
>>>> networking stack in hosts. If this is done, then the major driver
>>>>         
>> for NAT64
>>     
>>>> goes away, and there is a plethora of solutions that become
>>>>         
>> possible.
>>     
>>>> Therefore, it is better to ask this question: is it possible to fix
>>>>         
>> the NAT64
>>     
>>>> box (and/or DNS64) so that the problem you pointed out is solved?
>>>>
>>>> Simon
>>>> --
>>>> DNS64 open-source   --> http://ecdysis.viagenie.ca
>>>> STUN/TURN server    --> http://numb.viagenie.ca
>>>> vCard 4.0           --> http://www.vcarddav.org
>>>>
>>>>
>>>>
>>>>         
>>> _______________________________________________
>>> 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 marcelo@it.uc3m.es  Tue Sep  1 01:54:05 2009
Return-Path: <marcelo@it.uc3m.es>
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 EA34828C619 for <behave@core3.amsl.com>; Tue,  1 Sep 2009 01:54:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.572
X-Spam-Level: 
X-Spam-Status: No, score=-6.572 tagged_above=-999 required=5 tests=[AWL=0.027,  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 bV2x0XaQKRNn for <behave@core3.amsl.com>; Tue,  1 Sep 2009 01:54:05 -0700 (PDT)
Received: from smtp02.uc3m.es (smtp02.uc3m.es [163.117.176.132]) by core3.amsl.com (Postfix) with ESMTP id 1190328C60C for <behave@ietf.org>; Tue,  1 Sep 2009 01:54:04 -0700 (PDT)
Received: from marcelo-bagnulos-macbook-pro.local (wlap005.it.uc3m.es [163.117.139.108]) by smtp02.uc3m.es (Postfix) with ESMTP id 8B2226BAC49; Tue,  1 Sep 2009 10:54:16 +0200 (CEST)
Message-ID: <4A9CE138.4040100@it.uc3m.es>
Date: Tue, 01 Sep 2009 10:54:16 +0200
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
User-Agent: Thunderbird 2.0.0.22 (Macintosh/20090605)
MIME-Version: 1.0
To: Hesham Soliman <hesham@elevatemobile.com>
References: <C6C2E1CF.F19E%hesham@elevatemobile.com>
In-Reply-To: <C6C2E1CF.F19E%hesham@elevatemobile.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-TM-AS-Product-Ver: IMSS-7.0.0.3116-5.6.0.1016-16860.003
Cc: Cameron Byrne <cb.list6@gmail.com>, Wassim Haddad <wmhaddad@gmail.com>, "behave@ietf.org" <behave@ietf.org>, Dave Thaler <dthaler@microsoft.com>, Wassim Haddad <wassim.haddad@ericsson.com>
Subject: Re: [BEHAVE] NAT64 and MIPv6
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/mail-archive/web/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>
X-List-Received-Date: Tue, 01 Sep 2009 08:54:06 -0000

Hesham Soliman escribió:
>
>
> => Please read my text above, I didn't suggest host changes. First we need
> to acknowledge an issue then figure out what to do about it.
>   
I certainly agree that we need to ack the issues and i think it is also 
important to document them, so people are aware of the limitations of 
the tools they are using.
In the case of NAT64, when used in conjunction with DNS64, we have some 
scenarios where it will present some issues.


The case that Wassim has pointed out is certainly one of them.

The case is:

MN is in an IPv6 only visited network with DNS64/NAT64 services
The home network is also IPv6 only and is providing DNS64/NAT64 services.

They prefix used in the two DNS64/NAT64 are different
 In particular, it should be noted that in case both networks use the WK 
prefix (which is the default prefix for the NAT64/DNS64) the problem 
does _not_ occur.

So, in case the MN is using the BT mode and using the DNS server from 
the visited network, then the communication will fail.

So, the possible ways to deal with this are:
- use the WK prefix (which is the default prefix) or,
- use the dns server of the home network, or
- implement dns64 in stub resolver mode in the MN

We can think of other configurations that will present problems, namely:

- Any situation where the host is using the dns server that is provided 
by a different entity than the one providing nat64 services. For 
example, if the host is using a remote dns server, which is not 
uncommon. The solutions for this one are similar tot he one for the case 
of MIP.

- A configuration where there is a recursive resolver sitting behind the 
dns64. In this case, the recursive resolver will query directly to the 
authoritative servers, so it won't receive the synthetic RR. (this is 
part of the issue that is being disucssed in the thread about what to do 
with the additional section info). the solution here seems to involve 
making the recursive resolver dns64 aware.

So, i agree that it makes sense to document the limitations of the 
proposed tools and describe ways to handle the limitations. I am not 
sure what is the best place to do this though. Probably the NAT64 and 
the DNS64 documents could be a good fit. Some part could also be 
included in the prefix document. another option would be to write a 
separate document. thoughts?

Regards, marcelo




From remi.despres@free.fr  Tue Sep  1 03:40:42 2009
Return-Path: <remi.despres@free.fr>
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 0AEFE28C2B1 for <behave@core3.amsl.com>; Tue,  1 Sep 2009 03:40:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.53
X-Spam-Level: 
X-Spam-Status: No, score=-1.53 tagged_above=-999 required=5 tests=[AWL=-0.180,  BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_62=0.6, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WPycRpFFBV-X for <behave@core3.amsl.com>; Tue,  1 Sep 2009 03:40:41 -0700 (PDT)
Received: from smtp6-g21.free.fr (smtp6-g21.free.fr [212.27.42.6]) by core3.amsl.com (Postfix) with ESMTP id D83433A6A57 for <behave@ietf.org>; Tue,  1 Sep 2009 03:40:39 -0700 (PDT)
Received: from smtp6-g21.free.fr (localhost [127.0.0.1]) by smtp6-g21.free.fr (Postfix) with ESMTP id F0CF8E08163; Tue,  1 Sep 2009 12:40:46 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by smtp6-g21.free.fr (Postfix) with ESMTP id E2665E080DF; Tue,  1 Sep 2009 12:40:43 +0200 (CEST)
Mime-Version: 1.0 (Apple Message framework v753.1)
Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed
Message-Id: <095E4E4E-F4F5-4FFD-95D5-4D6C05608124@free.fr>
Content-Transfer-Encoding: quoted-printable
From: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
Date: Tue, 1 Sep 2009 12:40:37 +0200
To: Dave Thaler <dthaler@windows.microsoft.com>
X-Mailer: Apple Mail (2.753.1)
Cc: Behave WG <behave@ietf.org>, Xing Li <xing@cernet.edu.cn>, Fred Baker <fred@cisco.com>
Subject: [BEHAVE] IPv4-only and IPv6-only definitions
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/mail-archive/web/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>
X-List-Received-Date: Tue, 01 Sep 2009 10:40:42 -0000

Dave,

I also also think that the current definition of IPv6-only needs more =20=

work.

Here is an approach which, in my understanding, would improve the =20
situation.
(Whereas you introduced "connected", as an adjective for =20
applications, it introduces "connections", and more precisely =20
connection "endpoints" as objects that can be IPv6-only at one end =20
and IPv4-only at the other end.)


1. The definition would become(in substance):
"IPvX-only endpoint: In a connection that traverses an IPv6/IPv4 =20
translator, the endpoint that works in IPvX. Reasons for this may be =20
that: (1) its application is IPvX-only (not IPvY capable); (2) its =20
node is IPvX-only (not IPvY-enabled); (3) if the endpoint is =20
connection initiator, all known addresses of the other endpoint are =20
IPvX (and translatable to IPvY); if the endpoint is connection =20
acceptor, all of its addresses known by other endpoint are IPvY =20
(translatable to IPvX)."

2. In the text, IPv6-only entities that contain connection endpoints =20
("systems", "devices", "equipment", "nodes") would be renamed "IPv6-=20
only endpoints".

Regards,
RD


Le 1 sept. 09 =E0 00:54, Dave Thaler a =E9crit :

> "IPv6-only" is an adjective and can be used to describe a network,
> a host, or an application.
>
> The text in the framework doc says:
>    IPv6-only:  An IPv6-only implementation, in this context, comprises
>       an IPv6 enabled end system stack plus routing in the =20
> network.  It
>       implies that two application instances are capable of
>       communicating using IPv6, but not IPv4 - they have an IPv6 =20
> stack,
>       addresses, and network support including routing in IPv6, but =20=

> some
>       element is missing that prevents communication with IPv4 hosts.
>
> One problem with the above is that it confuses whether it's an =20
> adjective,
> or a term "IPv6-only implementation" or an "IPv6-only end system" or
> an "IPv6-only application"
> ...
> I think people would expect that an IP-version agnostic application =20=

> would be "IPv4-capable" but not necessarily "IPv4-connected".






From hesham@elevatemobile.com  Tue Sep  1 05:51:41 2009
Return-Path: <hesham@elevatemobile.com>
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 283183A6FBC for <behave@core3.amsl.com>; Tue,  1 Sep 2009 05:51:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.203
X-Spam-Level: 
X-Spam-Status: No, score=-1.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XaqSJ-UFoYg6 for <behave@core3.amsl.com>; Tue,  1 Sep 2009 05:51:40 -0700 (PDT)
Received: from smtp-2.servers.netregistry.net (smtp.netregistry.net [202.124.241.204]) by core3.amsl.com (Postfix) with ESMTP id 7C86B3A6FBF for <behave@ietf.org>; Tue,  1 Sep 2009 05:48:15 -0700 (PDT)
Received: from [203.219.211.243] (helo=[192.168.0.3]) by smtp-2.servers.netregistry.net protocol: esmtpa (Exim 4.63 #1 (Debian)) id 1MiSmd-0005vI-99; Tue, 01 Sep 2009 22:48:23 +1000
User-Agent: Microsoft-Entourage/12.20.0.090605
Date: Tue, 01 Sep 2009 22:48:11 +1000
From: Hesham Soliman <hesham@elevatemobile.com>
To: marcelo bagnulo braun <marcelo@it.uc3m.es>
Message-ID: <C6C3552B.F1C0%hesham@elevatemobile.com>
Thread-Topic: [BEHAVE] NAT64 and MIPv6
Thread-Index: AcorAnZo9kzMBnoy8EycW3PNJWvRpA==
In-Reply-To: <4A9CE138.4040100@it.uc3m.es>
Mime-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
X-Authenticated-User: hesham@elevatemobile.com
Cc: Cameron Byrne <cb.list6@gmail.com>, Wassim Haddad <wmhaddad@gmail.com>, "behave@ietf.org" <behave@ietf.org>, Dave Thaler <dthaler@microsoft.com>, Wassim Haddad <wassim.haddad@ericsson.com>
Subject: Re: [BEHAVE] NAT64 and MIPv6
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/mail-archive/web/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>
X-List-Received-Date: Tue, 01 Sep 2009 12:51:41 -0000

On 1/09/09 6:54 PM, "marcelo bagnulo braun" <marcelo@it.uc3m.es> wrote:

> Hesham Soliman escribi=F3:
>>=20
>>=20
>> =3D> Please read my text above, I didn't suggest host changes. First we ne=
ed
>> to acknowledge an issue then figure out what to do about it.
>>  =20
> I certainly agree that we need to ack the issues and i think it is also
> important to document them, so people are aware of the limitations of
> the tools they are using.
> In the case of NAT64, when used in conjunction with DNS64, we have some
> scenarios where it will present some issues.
>=20
>=20
> The case that Wassim has pointed out is certainly one of them.
>=20
> The case is:
>=20
> MN is in an IPv6 only visited network with DNS64/NAT64 services
> The home network is also IPv6 only and is providing DNS64/NAT64 services.
>=20
> They prefix used in the two DNS64/NAT64 are different
>  In particular, it should be noted that in case both networks use the WK
> prefix (which is the default prefix for the NAT64/DNS64) the problem
> does _not_ occur.
>=20
> So, in case the MN is using the BT mode and using the DNS server from
> the visited network, then the communication will fail.
>=20
> So, the possible ways to deal with this are:
> - use the WK prefix (which is the default prefix) or,
> - use the dns server of the home network, or
> - implement dns64 in stub resolver mode in the MN
>=20
> We can think of other configurations that will present problems, namely:
>=20
> - Any situation where the host is using the dns server that is provided
> by a different entity than the one providing nat64 services. For
> example, if the host is using a remote dns server, which is not
> uncommon. The solutions for this one are similar tot he one for the case
> of MIP.
>=20
> - A configuration where there is a recursive resolver sitting behind the
> dns64. In this case, the recursive resolver will query directly to the
> authoritative servers, so it won't receive the synthetic RR. (this is
> part of the issue that is being disucssed in the thread about what to do
> with the additional section info). the solution here seems to involve
> making the recursive resolver dns64 aware.
>=20
> So, i agree that it makes sense to document the limitations of the
> proposed tools and describe ways to handle the limitations. I am not
> sure what is the best place to do this though. Probably the NAT64 and
> the DNS64 documents could be a good fit. Some part could also be
> included in the prefix document. another option would be to write a
> separate document. thoughts?

=3D> I like the idea of having the limitations of the proposal in the same
document. I think it provides the read with a complete picture and it's
generally good practice to do that.

Hesham

>=20
> Regards, marcelo
>=20
>=20
>=20
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave



From marcelo@it.uc3m.es  Tue Sep  1 06:44:14 2009
Return-Path: <marcelo@it.uc3m.es>
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 52EE23A6880 for <behave@core3.amsl.com>; Tue,  1 Sep 2009 06:44:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.573
X-Spam-Level: 
X-Spam-Status: No, score=-6.573 tagged_above=-999 required=5 tests=[AWL=0.026,  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 ViKUo1QL1KPw for <behave@core3.amsl.com>; Tue,  1 Sep 2009 06:44:13 -0700 (PDT)
Received: from smtp02.uc3m.es (smtp02.uc3m.es [163.117.176.132]) by core3.amsl.com (Postfix) with ESMTP id 248F63A6840 for <behave@ietf.org>; Tue,  1 Sep 2009 06:44:12 -0700 (PDT)
Received: from marcelo-bagnulos-macbook-pro.local (wlap005.it.uc3m.es [163.117.139.108]) by smtp02.uc3m.es (Postfix) with ESMTP id F38166C1970; Tue,  1 Sep 2009 15:44:24 +0200 (CEST)
Message-ID: <4A9D2538.1090306@it.uc3m.es>
Date: Tue, 01 Sep 2009 15:44:24 +0200
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
User-Agent: Thunderbird 2.0.0.22 (Macintosh/20090605)
MIME-Version: 1.0
To: Hesham Soliman <hesham@elevatemobile.com>
References: <C6C3552B.F1C0%hesham@elevatemobile.com>
In-Reply-To: <C6C3552B.F1C0%hesham@elevatemobile.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-TM-AS-Product-Ver: IMSS-7.0.0.3116-5.6.0.1016-16860.007
Cc: Cameron Byrne <cb.list6@gmail.com>, Wassim Haddad <wmhaddad@gmail.com>, "behave@ietf.org" <behave@ietf.org>, Dave Thaler <dthaler@microsoft.com>, Wassim Haddad <wassim.haddad@ericsson.com>
Subject: Re: [BEHAVE] NAT64 and MIPv6
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/mail-archive/web/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>
X-List-Received-Date: Tue, 01 Sep 2009 13:44:14 -0000

Hesham Soliman escribió:
>
> On 1/09/09 6:54 PM, "marcelo bagnulo braun" <marcelo@it.uc3m.es> wrote:
>
>   
>> Hesham Soliman escribió:
>>     
>>> => Please read my text above, I didn't suggest host changes. First we need
>>> to acknowledge an issue then figure out what to do about it.
>>>   
>>>       
>> I certainly agree that we need to ack the issues and i think it is also
>> important to document them, so people are aware of the limitations of
>> the tools they are using.
>> In the case of NAT64, when used in conjunction with DNS64, we have some
>> scenarios where it will present some issues.
>>
>>
>> The case that Wassim has pointed out is certainly one of them.
>>
>> The case is:
>>
>> MN is in an IPv6 only visited network with DNS64/NAT64 services
>> The home network is also IPv6 only and is providing DNS64/NAT64 services.
>>
>> They prefix used in the two DNS64/NAT64 are different
>>  In particular, it should be noted that in case both networks use the WK
>> prefix (which is the default prefix for the NAT64/DNS64) the problem
>> does _not_ occur.
>>
>> So, in case the MN is using the BT mode and using the DNS server from
>> the visited network, then the communication will fail.
>>
>> So, the possible ways to deal with this are:
>> - use the WK prefix (which is the default prefix) or,
>> - use the dns server of the home network, or
>> - implement dns64 in stub resolver mode in the MN
>>
>> We can think of other configurations that will present problems, namely:
>>
>> - Any situation where the host is using the dns server that is provided
>> by a different entity than the one providing nat64 services. For
>> example, if the host is using a remote dns server, which is not
>> uncommon. The solutions for this one are similar tot he one for the case
>> of MIP.
>>
>> - A configuration where there is a recursive resolver sitting behind the
>> dns64. In this case, the recursive resolver will query directly to the
>> authoritative servers, so it won't receive the synthetic RR. (this is
>> part of the issue that is being disucssed in the thread about what to do
>> with the additional section info). the solution here seems to involve
>> making the recursive resolver dns64 aware.
>>
>> So, i agree that it makes sense to document the limitations of the
>> proposed tools and describe ways to handle the limitations. I am not
>> sure what is the best place to do this though. Probably the NAT64 and
>> the DNS64 documents could be a good fit. Some part could also be
>> included in the prefix document. another option would be to write a
>> separate document. thoughts?
>>     
>
> => I like the idea of having the limitations of the proposal in the same
> document. I think it provides the read with a complete picture and it's
> generally good practice to do that.
>   

right, the problem is that there are 4 documents related to the 
mechanisms involved int he problem, the dns64 one, the nat64 one, the 
doc defining the prefixes, and the framework document....
> Hesham
>
>   
>> Regards, marcelo
>>
>>
>>
>> _______________________________________________
>> Behave mailing list
>> Behave@ietf.org
>> https://www.ietf.org/mailman/listinfo/behave
>>     
>
>
>
>   


From cb.list6@gmail.com  Tue Sep  1 07:12:14 2009
Return-Path: <cb.list6@gmail.com>
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 7D26D28C432 for <behave@core3.amsl.com>; Tue,  1 Sep 2009 07:12:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.556
X-Spam-Level: 
X-Spam-Status: No, score=-2.556 tagged_above=-999 required=5 tests=[AWL=0.043,  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 i0KxHGfxQwpU for <behave@core3.amsl.com>; Tue,  1 Sep 2009 07:12:13 -0700 (PDT)
Received: from mail-pz0-f173.google.com (mail-pz0-f173.google.com [209.85.222.173]) by core3.amsl.com (Postfix) with ESMTP id C78B328C43F for <behave@ietf.org>; Tue,  1 Sep 2009 07:12:13 -0700 (PDT)
Received: by pzk3 with SMTP id 3so13199pzk.20 for <behave@ietf.org>; Tue, 01 Sep 2009 07:12:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=DyYJNQgw8/qY72MasYbb1VoB0IcpAeZrM0fW34RgHqk=; b=ux3+AWDG6Aylx8rSnRcfC//RO8q1wf5CadCBWOpWIhhNTmrXWKaH2KemRy0AsUbymg H1ld42skPBJKloWcKb+YzzFUxriOaUhNMsLwrNHSDdUfd2OEVcTo5xiNlLNqEPHNTYAi VeaVXh7OTXeBneeh2GozmzRx3L39IyZ8N+8ug=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=xrzbqfJgc2HbXbVnhpp6XVdNc5L3+BjY40T1eUDYx6HJuAAWKZZ1Rb1X7DANsthkGG 8HBTBCncN/kOh5lOY2yq7ZnGUZGUhugeVTgKc7k8RNG15xcCLmD0DxXcjSQUYn0IDSDB eyWLweFaOypFT0Ms3lEKaJb/m7ILKIRw7DyP8=
MIME-Version: 1.0
Received: by 10.142.202.9 with SMTP id z9mr76502wff.34.1251814343822; Tue, 01  Sep 2009 07:12:23 -0700 (PDT)
In-Reply-To: <4A9D2538.1090306@it.uc3m.es>
References: <C6C3552B.F1C0%hesham@elevatemobile.com> <4A9D2538.1090306@it.uc3m.es>
Date: Tue, 1 Sep 2009 07:12:23 -0700
Message-ID: <bcff0fba0909010712h374a1506i39bbca5652443843@mail.gmail.com>
From: Cameron Byrne <cb.list6@gmail.com>
To: marcelo bagnulo braun <marcelo@it.uc3m.es>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Wassim Haddad <wassim.haddad@ericsson.com>, Wassim Haddad <wmhaddad@gmail.com>, "behave@ietf.org" <behave@ietf.org>, Dave Thaler <dthaler@microsoft.com>, Hesham Soliman <hesham@elevatemobile.com>
Subject: Re: [BEHAVE] NAT64 and MIPv6
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/mail-archive/web/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>
X-List-Received-Date: Tue, 01 Sep 2009 14:12:14 -0000

> right, the problem is that there are 4 documents related to the mechanisms
> involved int he problem, the dns64 one, the nat64 one, the doc defining the
> prefixes, and the framework document....
>>

That said, is the best and most general solution to not make a
statement about MIPv6, but to state that DNS64, NAT64, and prefix64
all must be configured and managed as a single system.  Attempting to
mix different elements from different management domains may result in
unexpected behavior.   This is an operational assumption that i have
had, but it may be best to codify it here so that there is no more
confusion.

From cb.list6@gmail.com  Tue Sep  1 07:25:53 2009
Return-Path: <cb.list6@gmail.com>
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 0D50E3A67FB for <behave@core3.amsl.com>; Tue,  1 Sep 2009 07:25:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.561
X-Spam-Level: 
X-Spam-Status: No, score=-2.561 tagged_above=-999 required=5 tests=[AWL=0.038,  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 H1XfmP7dISoi for <behave@core3.amsl.com>; Tue,  1 Sep 2009 07:25:52 -0700 (PDT)
Received: from mail-px0-f185.google.com (mail-px0-f185.google.com [209.85.216.185]) by core3.amsl.com (Postfix) with ESMTP id 1B30528C625 for <behave@ietf.org>; Tue,  1 Sep 2009 07:25:52 -0700 (PDT)
Received: by pxi15 with SMTP id 15so20589pxi.23 for <behave@ietf.org>; Tue, 01 Sep 2009 07:26:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=c22z0qHOHWDJT3MJW8XPgUHYJLCnneCUyL3F6qFVz3M=; b=Z+QQ4y0DMQezmegZHazx6mHsl8MKGZPVGutk0IT0P91PkxDkqO2Vm7aos9sNGNkIYo 9MJWrfrzLxcojOOxrbkmXM/0Ym+INy5xV/o6964D4CKFsRJszSKP2ITuejkfJ5lgOLz9 94ojuUjM4xAsEe284SO4C78I84+uQhA+Di66Y=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=Fv87+qem95+/RQpWvWDW3YKC9IPOYO583g//KtjjZ0F6ziooKyeQF1XMbmxTttg5lc 6cen09NIEdYcy0NwP/WsOvKEcela2bPTB08ZwT8oA5y8ac2WctWa8pMocSrRNZEmJvKs zFwCGn1GtKQ/mI52AEK7HeyCgcmmOnzlMKN5A=
MIME-Version: 1.0
Received: by 10.142.250.41 with SMTP id x41mr75757wfh.42.1251815160369; Tue,  01 Sep 2009 07:26:00 -0700 (PDT)
In-Reply-To: <C6C2E1CF.F19E%hesham@elevatemobile.com>
References: <bcff0fba0908312124k2b3f34c8s1b4ba868cafd9aff@mail.gmail.com> <C6C2E1CF.F19E%hesham@elevatemobile.com>
Date: Tue, 1 Sep 2009 07:26:00 -0700
Message-ID: <bcff0fba0909010726g7fa3f741yc42c88fdad8192c1@mail.gmail.com>
From: Cameron Byrne <cb.list6@gmail.com>
To: Hesham Soliman <hesham@elevatemobile.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Wassim Haddad <wmhaddad@gmail.com>, "behave@ietf.org" <behave@ietf.org>, Dave Thaler <dthaler@microsoft.com>, Wassim Haddad <wassim.haddad@ericsson.com>
Subject: Re: [BEHAVE] NAT64 and MIPv6
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/mail-archive/web/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>
X-List-Received-Date: Tue, 01 Sep 2009 14:25:53 -0000

> =3D> Hmm, I think linux, BSD =A0and Symbian are pretty major but I guess =
you
> disagree.
>

I don't disagree if the standard build supports it. My understanding
is that FreeBSD and Linux require a kernel patch to work with MIPv6,
in which case your scenario could read "your average kernel developer
at an IETF meeting tries to go to youtube ...."  :)  My ubuntu laptop
does not support MIPv6.

> =A0If a user would
>> like to have =A0MIPv6 work, they should conspire through non-technical
>> means to communicate using IPv6 (i know paying for v6 is a novel
>> idea), because that is the end-state the MIPv6 designers had in mind.
>> If we make the middle-box so smart, we will never get rid of it. =A0Or,
>> it will never be done.
>
> =3D> I have no idea what you're talking about or what you think MIPv6
> desginers conspired to do. The point is there is a problem that first nee=
d
> to be acknowledged instead of delving into irrelevant discussions.

I did spend a lot of time looking at this when Wassim first sent out
his text.  I concluded at that point that he must have assumed mixing
DNS64 and NAT64 across service providers or domains within a service
provider.  Today, this type of issue is a considered an end user
configuration error.  If i statically configure my laptop to use my
work's private DNS server and I go home and cannot get DNS to resolve,
it is a configuration issue, not a failure or DHCP or DNS.  This
thread mentions that MIPv6 does not make any statements regarding
where the DNS is hosted, that is a problem.  We can make the general
statement that DNS64, NAT64, and Prefix64 must be part of one
administrative domain to ensure proper operation.

>
>>
>> I want NAT64 in my network because it is a needed interim step, but i
>> don't want to stop the network evolution there. =A0I need IPv6
>> end-to-end to be realized (NAT64 does have an exit strategy), then
>> MIPv6 will work great (if your firewall does not break it).
>
> =3D> That's fine, but you can't force everyone in the world to be in lock=
 step
> with your vision so things that break existing protocols should be
> documented with a pointer on what IETF concensus is for the solution, or
> lack of.

Not forcing anything.  I am just putting forward my deployment
scenario.  I agree that we need to explicitly say that DNS64, NAT64,
and Prefix64 do not stand on their own.  They should be viewed as a
system under a single management domain.


>
> Hesham
>
>>
>> Cameron Byrne
>> Principal Engineer
>> T-Mobile USA
>
>
>

From hesham@elevatemobile.com  Tue Sep  1 07:46:18 2009
Return-Path: <hesham@elevatemobile.com>
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 43B7928C74E for <behave@core3.amsl.com>; Tue,  1 Sep 2009 07:46:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.203
X-Spam-Level: 
X-Spam-Status: No, score=-1.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zEXk5GQkJ+9X for <behave@core3.amsl.com>; Tue,  1 Sep 2009 07:46:17 -0700 (PDT)
Received: from smtp-1.servers.netregistry.net (smtp.netregistry.net [202.124.241.204]) by core3.amsl.com (Postfix) with ESMTP id 4B22128C73A for <behave@ietf.org>; Tue,  1 Sep 2009 07:46:16 -0700 (PDT)
Received: from [203.219.211.243] (helo=[192.168.0.3]) by smtp-1.servers.netregistry.net protocol: esmtpa (Exim 4.63 #1 (Debian)) id 1MiUcm-0004jZ-AY; Wed, 02 Sep 2009 00:46:20 +1000
User-Agent: Microsoft-Entourage/12.20.0.090605
Date: Wed, 02 Sep 2009 00:46:09 +1000
From: Hesham Soliman <hesham@elevatemobile.com>
To: Cameron Byrne <cb.list6@gmail.com>
Message-ID: <C6C370D1.F1CB%hesham@elevatemobile.com>
Thread-Topic: [BEHAVE] NAT64 and MIPv6
Thread-Index: AcorEvE6Eb38ox2pMUGOM5z9rHWDPA==
In-Reply-To: <bcff0fba0909010726g7fa3f741yc42c88fdad8192c1@mail.gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
X-Authenticated-User: hesham@elevatemobile.com
Cc: Wassim Haddad <wmhaddad@gmail.com>, "behave@ietf.org" <behave@ietf.org>, Dave Thaler <dthaler@microsoft.com>, Wassim Haddad <wassim.haddad@ericsson.com>
Subject: Re: [BEHAVE] NAT64 and MIPv6
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/mail-archive/web/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>
X-List-Received-Date: Tue, 01 Sep 2009 14:46:18 -0000

On 2/09/09 12:26 AM, "Cameron Byrne" <cb.list6@gmail.com> wrote:

>> =3D> Hmm, I think linux, BSD =A0and Symbian are pretty major but I guess you
>> disagree.
>>=20
>=20
> I don't disagree if the standard build supports it. My understanding
> is that FreeBSD and Linux require a kernel patch to work with MIPv6,
> in which case your scenario could read "your average kernel developer
> at an IETF meeting tries to go to youtube ...."  :)  My ubuntu laptop
> does not support MIPv6.

=3D> FreeBSD *does* come with MIPv6 in its standard distribution. Linux has a
separate module. As I'm sure you know, you don't need a kernel developer to
load a module, it can be done almost seamlessly to the user. But, this is
not the issue that behave cares about. Even if MIPv6 was not supported by
anybody today (which is not the case), it doesn't mean we just assume this
to be the case 2-4 years from now. Makes no sense.

>=20
>> =A0If a user would
>>> like to have =A0MIPv6 work, they should conspire through non-technical
>>> means to communicate using IPv6 (i know paying for v6 is a novel
>>> idea), because that is the end-state the MIPv6 designers had in mind.
>>> If we make the middle-box so smart, we will never get rid of it. =A0Or,
>>> it will never be done.
>>=20
>> =3D> I have no idea what you're talking about or what you think MIPv6
>> desginers conspired to do. The point is there is a problem that first ne=
ed
>> to be acknowledged instead of delving into irrelevant discussions.
>=20
> I did spend a lot of time looking at this when Wassim first sent out
> his text.  I concluded at that point that he must have assumed mixing
> DNS64 and NAT64 across service providers or domains within a service
> provider.  Today, this type of issue is a considered an end user
> configuration error.  If i statically configure my laptop to use my
> work's private DNS server and I go home and cannot get DNS to resolve,
> it is a configuration issue, not a failure or DHCP or DNS.

=3D> Yes but he's not suggesting doing anything statically, he's using a
standard mechanism developed by IETF.

  This
> thread mentions that MIPv6 does not make any statements regarding
> where the DNS is hosted, that is a problem.

=3D> It's a problem when you think about this scenario with NAT64 or when you
think about people storing local names in the DNS. Local names are a
separate issue and you do it at your own risk and there is usually
indicators for the user as to why something didn't resolve (e.g. I forgot t=
o
connect to the office). But the case here is simply a clash between two
solutions.=20

Hesham



From wassim.haddad@ericsson.com  Tue Sep  1 08:11:12 2009
Return-Path: <wassim.haddad@ericsson.com>
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 EF5F028C7D6 for <behave@core3.amsl.com>; Tue,  1 Sep 2009 08:11:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.569
X-Spam-Level: 
X-Spam-Status: No, score=-6.569 tagged_above=-999 required=5 tests=[AWL=0.030,  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 4B531zqNJsCb for <behave@core3.amsl.com>; Tue,  1 Sep 2009 08:11:12 -0700 (PDT)
Received: from imr2.ericy.com (imr2.ericy.com [198.24.6.3]) by core3.amsl.com (Postfix) with ESMTP id 0BA303A7084 for <behave@ietf.org>; Tue,  1 Sep 2009 08:10:04 -0700 (PDT)
Received: from eusrcmw751.eamcs.ericsson.se (eusrcmw751.exu.ericsson.se [138.85.77.51]) by imr2.ericy.com (8.13.1/8.13.1) with ESMTP id n81F9dQK013932; Tue, 1 Sep 2009 10:09:40 -0500
Received: from eusrcmw750.eamcs.ericsson.se ([138.85.77.50]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 1 Sep 2009 10:08:48 -0500
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 1 Sep 2009 10:08:48 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.20]) by eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) with mapi; Tue, 1 Sep 2009 11:08:47 -0400
From: Wassim Haddad <wassim.haddad@ericsson.com>
To: Hesham Soliman <hesham@elevatemobile.com>, marcelo bagnulo braun <marcelo@it.uc3m.es>
Date: Tue, 1 Sep 2009 11:06:55 -0400
Thread-Topic: [BEHAVE] NAT64 and MIPv6
Thread-Index: AcorAnZo9kzMBnoy8EycW3PNJWvRpAAE2Fm0
Message-ID: <2991246A29623A4082EB2B06A2B891A41B7C42ED5E@EUSAACMS0703.eamcs.ericsson.se>
References: <4A9CE138.4040100@it.uc3m.es>, <C6C3552B.F1C0%hesham@elevatemobile.com>
In-Reply-To: <C6C3552B.F1C0%hesham@elevatemobile.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 01 Sep 2009 15:08:48.0223 (UTC) FILETIME=[1B6306F0:01CA2B16]
Cc: Cameron Byrne <cb.list6@gmail.com>, Wassim Haddad <wassim.haddad@ericsson.com>, "behave@ietf.org" <behave@ietf.org>, Dave Thaler <dthaler@microsoft.com>
Subject: Re: [BEHAVE] NAT64 and MIPv6
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/mail-archive/web/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>
X-List-Received-Date: Tue, 01 Sep 2009 15:11:13 -0000

On 1/09/09 6:54 PM, "marcelo bagnulo braun" <marcelo@it.uc3m.es> wrote:

> Hesham Soliman escribi=F3:
>>
>>
>> =3D> Please read my text above, I didn't suggest host changes. First we =
need
>> to acknowledge an issue then figure out what to do about it.
>>
> I certainly agree that we need to ack the issues and i think it is also
> important to document them, so people are aware of the limitations of
> the tools they are using.
> In the case of NAT64, when used in conjunction with DNS64, we have some
> scenarios where it will present some issues.
>
>
> The case that Wassim has pointed out is certainly one of them.
>
> The case is:
>
> MN is in an IPv6 only visited network with DNS64/NAT64 services
> The home network is also IPv6 only and is providing DNS64/NAT64 services.
>
> They prefix used in the two DNS64/NAT64 are different
>  In particular, it should be noted that in case both networks use the WK
> prefix (which is the default prefix for the NAT64/DNS64) the problem
> does _not_ occur.
>
> So, in case the MN is using the BT mode and using the DNS server from
> the visited network, then the communication will fail.
>
> So, the possible ways to deal with this are:
> - use the WK prefix (which is the default prefix) or,
> - use the dns server of the home network, or
> - implement dns64 in stub resolver mode in the MN
>
> We can think of other configurations that will present problems, namely:
>
> - Any situation where the host is using the dns server that is provided
> by a different entity than the one providing nat64 services. For
> example, if the host is using a remote dns server, which is not
> uncommon. The solutions for this one are similar tot he one for the case
> of MIP.
>
> - A configuration where there is a recursive resolver sitting behind the
> dns64. In this case, the recursive resolver will query directly to the
> authoritative servers, so it won't receive the synthetic RR. (this is
> part of the issue that is being disucssed in the thread about what to do
> with the additional section info). the solution here seems to involve
> making the recursive resolver dns64 aware.
>
> So, i agree that it makes sense to document the limitations of the
> proposed tools and describe ways to handle the limitations. I am not
> sure what is the best place to do this though. Probably the NAT64 and
> the DNS64 documents could be a good fit. Some part could also be
> included in the prefix document. another option would be to write a
> separate document. thoughts?

=3D> I like the idea of having the limitations of the proposal in the same
document. I think it provides the read with a complete picture and it's
generally good practice to do that.


+1

Wassim H.


From dthaler@microsoft.com  Tue Sep  1 08:21:13 2009
Return-Path: <dthaler@microsoft.com>
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 B689D3A6D27 for <behave@core3.amsl.com>; Tue,  1 Sep 2009 08:21:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.442
X-Spam-Level: 
X-Spam-Status: No, score=-10.442 tagged_above=-999 required=5 tests=[AWL=0.157, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GS6Onp0yoP7p for <behave@core3.amsl.com>; Tue,  1 Sep 2009 08:21:13 -0700 (PDT)
Received: from smtp.microsoft.com (mail3.microsoft.com [131.107.115.214]) by core3.amsl.com (Postfix) with ESMTP id 0BF383A6964 for <behave@ietf.org>; Tue,  1 Sep 2009 08:21:13 -0700 (PDT)
Received: from TK5EX14HUBC102.redmond.corp.microsoft.com (157.54.7.154) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.2.176.0; Tue, 1 Sep 2009 08:21:26 -0700
Received: from TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com (157.54.71.68) by TK5EX14HUBC102.redmond.corp.microsoft.com (157.54.7.154) with Microsoft SMTP Server id 14.0.639.13; Tue, 1 Sep 2009 08:21:26 -0700
Received: from TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com ([169.254.3.25]) by TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.68]) with mapi; Tue, 1 Sep 2009 08:21:38 -0700
From: Dave Thaler <dthaler@microsoft.com>
To: Hesham Soliman <hesham@elevatemobile.com>, Wassim Haddad <wmhaddad@gmail.com>
Thread-Topic: [BEHAVE] NAT64 and MIPv6
Thread-Index: AQHKKHuIwEJcSog/t0mWiJZwt4jxx5C//1+AgAEYr4D//60LwIAAl/4A//+c3CCAAAvsuIAA2Jvw
Date: Tue, 1 Sep 2009 15:21:22 +0000
Message-ID: <E4561B14EE2A3E4E9D478EBFB5416E1B1C389D@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
References: <E4561B14EE2A3E4E9D478EBFB5416E1B1C3163@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <C6C2C322.F191%hesham@elevatemobile.com>
In-Reply-To: <C6C2C322.F191%hesham@elevatemobile.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Wassim Haddad <wassim.haddad@ericsson.com>, "behave@ietf.org" <behave@ietf.org>
Subject: Re: [BEHAVE] NAT64 and MIPv6
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/mail-archive/web/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>
X-List-Received-Date: Tue, 01 Sep 2009 15:21:13 -0000

Hesham writes:
> At the very least any solution should highlight this as a requirement for
> MNs because 3775 doesn't limit the DNS queries to the home DNS. But I
> don't
> know how to do that if the presence of a NAT is not known to the host.

I agree that 3775 is defective by not mentioning this,
since again the presence of a NAT does not introduce
this problem... it already breaks with private namespaces
and 3775 should have pointed out how to make DNS work.

-Dave

From dthaler@microsoft.com  Tue Sep  1 08:24:33 2009
Return-Path: <dthaler@microsoft.com>
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 0D7F728C172 for <behave@core3.amsl.com>; Tue,  1 Sep 2009 08:24:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.445
X-Spam-Level: 
X-Spam-Status: No, score=-10.445 tagged_above=-999 required=5 tests=[AWL=0.154, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6JYuLMVJkp4e for <behave@core3.amsl.com>; Tue,  1 Sep 2009 08:24:32 -0700 (PDT)
Received: from smtp.microsoft.com (mailb.microsoft.com [131.107.115.215]) by core3.amsl.com (Postfix) with ESMTP id 4C1F93A6DFC for <behave@ietf.org>; Tue,  1 Sep 2009 08:24:32 -0700 (PDT)
Received: from TK5EX14MLTC102.redmond.corp.microsoft.com (157.54.79.180) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.176.0; Tue, 1 Sep 2009 08:24:40 -0700
Received: from TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com (157.54.71.68) by TK5EX14MLTC102.redmond.corp.microsoft.com (157.54.79.180) with Microsoft SMTP Server id 14.0.639.13; Tue, 1 Sep 2009 08:24:39 -0700
Received: from TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com ([169.254.3.25]) by TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.68]) with mapi; Tue, 1 Sep 2009 08:24:51 -0700
From: Dave Thaler <dthaler@microsoft.com>
To: Dave Thaler <dthaler@microsoft.com>, Hesham Soliman <hesham@elevatemobile.com>, Wassim Haddad <wmhaddad@gmail.com>
Thread-Topic: [BEHAVE] NAT64 and MIPv6
Thread-Index: AQHKKHuIwEJcSog/t0mWiJZwt4jxx5C//1+AgAEYr4D//60LwIAAl/4A//+c3CCAAAvsuIAA2JvwgAAAnzA=
Date: Tue, 1 Sep 2009 15:24:36 +0000
Message-ID: <E4561B14EE2A3E4E9D478EBFB5416E1B1C3931@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
References: <E4561B14EE2A3E4E9D478EBFB5416E1B1C3163@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <C6C2C322.F191%hesham@elevatemobile.com> <E4561B14EE2A3E4E9D478EBFB5416E1B1C389D@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <E4561B14EE2A3E4E9D478EBFB5416E1B1C389D@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Wassim Haddad <wassim.haddad@ericsson.com>, "behave@ietf.org" <behave@ietf.org>
Subject: Re: [BEHAVE] NAT64 and MIPv6
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/mail-archive/web/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>
X-List-Received-Date: Tue, 01 Sep 2009 15:24:33 -0000

> -----Original Message-----
> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On Behalf
> Of Dave Thaler
> Sent: Tuesday, September 01, 2009 8:21 AM
> To: Hesham Soliman; Wassim Haddad
> Cc: Wassim Haddad; behave@ietf.org
> Subject: Re: [BEHAVE] NAT64 and MIPv6
>
> Hesham writes:
> > At the very least any solution should highlight this as a requirement
> for
> > MNs because 3775 doesn't limit the DNS queries to the home DNS. But I
> > don't
> > know how to do that if the presence of a NAT is not known to the host.
>
> I agree that 3775 is defective by not mentioning this,
> since again the presence of a NAT does not introduce
> this problem... it already breaks with private namespaces
> and 3775 should have pointed out how to make DNS work.

Another thing... I disagree that the NAT64 or DNS64
document should discuss this issue.  I believe it
belongs in a separate document that covers the issues
with mobile IP resulting from both private namespaces
and private address spaces.  It's not specific to
translation so it's arguably better done in a MIP
group rather than Behave, although Behave should certainly
review it.  That's what I'd recommend anyway.

-Dave

From cb.list6@gmail.com  Tue Sep  1 08:25:50 2009
Return-Path: <cb.list6@gmail.com>
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 D689228C172 for <behave@core3.amsl.com>; Tue,  1 Sep 2009 08:25:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.566
X-Spam-Level: 
X-Spam-Status: No, score=-2.566 tagged_above=-999 required=5 tests=[AWL=0.034,  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 9-YW9X9Du8IG for <behave@core3.amsl.com>; Tue,  1 Sep 2009 08:25:50 -0700 (PDT)
Received: from mail-pz0-f173.google.com (mail-pz0-f173.google.com [209.85.222.173]) by core3.amsl.com (Postfix) with ESMTP id 260533A6F11 for <behave@ietf.org>; Tue,  1 Sep 2009 08:25:50 -0700 (PDT)
Received: by pzk3 with SMTP id 3so66752pzk.20 for <behave@ietf.org>; Tue, 01 Sep 2009 08:26:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=19bCSSNq/JTZaODKxo5UcwBl2No7/ADXbVuJd7+NQC4=; b=GB/Shy+xHbyXTWoMXxY0nfeuF97d9X9Ds+6ZedxNhlPA14iDx7C9vCbW0UO7FTGrt7 Hn+I1825tWzlAKTofWWkbHGTsFuD6o0n7m8+yGk7g+8oPsiBSy5fCn0Xti1XjIsEVNt+ TPC/EuT/IDAbEKYHGMYW+kWBrNrVrf2IRAjzU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=vVRSFdvUT++7j7umw6JIEdNmqjb/yqKkOqRHjhge2e2gosE1L4AoFXKa0KPmxrbDCl Wlz5oE7UYbeKQwr9j4K+LON/uoYxFOt4azym1Hn+PTuYWBm38UIeu8TMjKvuKwGmxcsT m7msvgxu1Ue7kMHTnrvhaKuUhpfOTLSiOVcAU=
MIME-Version: 1.0
Received: by 10.142.3.38 with SMTP id 38mr76828wfc.111.1251818759152; Tue, 01  Sep 2009 08:25:59 -0700 (PDT)
In-Reply-To: <E4561B14EE2A3E4E9D478EBFB5416E1B1C3931@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
References: <E4561B14EE2A3E4E9D478EBFB5416E1B1C3163@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <C6C2C322.F191%hesham@elevatemobile.com> <E4561B14EE2A3E4E9D478EBFB5416E1B1C389D@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <E4561B14EE2A3E4E9D478EBFB5416E1B1C3931@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
Date: Tue, 1 Sep 2009 08:25:59 -0700
Message-ID: <bcff0fba0909010825i6c75e1bk9213d27234b66041@mail.gmail.com>
From: Cameron Byrne <cb.list6@gmail.com>
To: Dave Thaler <dthaler@microsoft.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Wassim Haddad <wassim.haddad@ericsson.com>, Wassim Haddad <wmhaddad@gmail.com>, "behave@ietf.org" <behave@ietf.org>, Hesham Soliman <hesham@elevatemobile.com>
Subject: Re: [BEHAVE] NAT64 and MIPv6
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/mail-archive/web/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>
X-List-Received-Date: Tue, 01 Sep 2009 15:25:51 -0000

> Another thing... I disagree that the NAT64 or DNS64
> document should discuss this issue. =A0I believe it
> belongs in a separate document that covers the issues
> with mobile IP resulting from both private namespaces
> and private address spaces. =A0It's not specific to
> translation so it's arguably better done in a MIP
> group rather than Behave, although Behave should certainly
> review it. =A0That's what I'd recommend anyway.

Agreed.

From wassim.haddad@ericsson.com  Tue Sep  1 09:15:23 2009
Return-Path: <wassim.haddad@ericsson.com>
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 9922328C7FA for <behave@core3.amsl.com>; Tue,  1 Sep 2009 09:15:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.572
X-Spam-Level: 
X-Spam-Status: No, score=-6.572 tagged_above=-999 required=5 tests=[AWL=0.027,  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 JrM0eyulo+O8 for <behave@core3.amsl.com>; Tue,  1 Sep 2009 09:15:22 -0700 (PDT)
Received: from imr2.ericy.com (imr2.ericy.com [198.24.6.3]) by core3.amsl.com (Postfix) with ESMTP id D7A6228C8BB for <behave@ietf.org>; Tue,  1 Sep 2009 09:14:44 -0700 (PDT)
Received: from eusrcmw750.eamcs.ericsson.se (eusrcmw750.exu.ericsson.se [138.85.77.50]) by imr2.ericy.com (8.13.1/8.13.1) with ESMTP id n81GEs3u011609; Tue, 1 Sep 2009 11:14:54 -0500
Received: from eusrcmw750.eamcs.ericsson.se ([138.85.77.53]) by eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 1 Sep 2009 11:13:56 -0500
Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) by eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 1 Sep 2009 11:13:56 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.20]) by eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) with mapi; Tue, 1 Sep 2009 12:13:55 -0400
From: Wassim Haddad <wassim.haddad@ericsson.com>
To: "dthaler@microsoft.com" <dthaler@microsoft.com>, "hesham@elevatemobile.com" <hesham@elevatemobile.com>
Date: Tue, 1 Sep 2009 12:13:54 -0400
Thread-Topic: [BEHAVE] NAT64 and MIPv6
Thread-Index: AQHKKHuIwEJcSog/t0mWiJZwt4jxx5C//1+AgAEYr4D//60LwIAAl/4A//+c3CCAAAvsuIAA2JvwgAAN9/A=
Message-ID: <2991246A29623A4082EB2B06A2B891A41B7C4591FD@EUSAACMS0703.eamcs.ericsson.se>
References: <E4561B14EE2A3E4E9D478EBFB5416E1B1C3163@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <C6C2C322.F191%hesham@elevatemobile.com> <E4561B14EE2A3E4E9D478EBFB5416E1B1C389D@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <E4561B14EE2A3E4E9D478EBFB5416E1B1C389D@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 01 Sep 2009 16:13:56.0023 (UTC) FILETIME=[349DFC70:01CA2B1F]
Cc: Wassim Haddad <wassim.haddad@ericsson.com>, "behave@ietf.org" <behave@ietf.org>
Subject: Re: [BEHAVE] NAT64 and MIPv6
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/mail-archive/web/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>
X-List-Received-Date: Tue, 01 Sep 2009 16:15:23 -0000

> At the very least any solution should highlight this as a requirement
> for MNs because 3775 doesn't limit the DNS queries to the home DNS.
> But I don't know how to do that if the presence of a NAT is not known
> to the host.

I agree that 3775 is defective by not mentioning this, since again the pres=
ence of a NAT does not introduce this problem... it already breaks with pri=
vate namespaces and 3775 should have pointed out how to make DNS work.

=3D> Just to clarify: you mean RFC 3775 is defective by not mentioning that=
 "the MN should NOT rely on the DNS in the foreign network when using MIPv6=
 (i.e., its home address). Instead, it should/must rely on the home DNS".

Is that correct?


Wassim H.


From dthaler@microsoft.com  Tue Sep  1 09:16:10 2009
Return-Path: <dthaler@microsoft.com>
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 6C6193A6B55 for <behave@core3.amsl.com>; Tue,  1 Sep 2009 09:16:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.447
X-Spam-Level: 
X-Spam-Status: No, score=-10.447 tagged_above=-999 required=5 tests=[AWL=0.152, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QCpts6uyH8jg for <behave@core3.amsl.com>; Tue,  1 Sep 2009 09:16:05 -0700 (PDT)
Received: from smtp.microsoft.com (mailc.microsoft.com [131.107.115.214]) by core3.amsl.com (Postfix) with ESMTP id 0B9FD3A7025 for <behave@ietf.org>; Tue,  1 Sep 2009 09:16:05 -0700 (PDT)
Received: from TK5EX14HUBC102.redmond.corp.microsoft.com (157.54.7.154) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.2.176.0; Tue, 1 Sep 2009 09:16:18 -0700
Received: from TK5EX14MLTW651.wingroup.windeploy.ntdev.microsoft.com (157.54.71.39) by TK5EX14HUBC102.redmond.corp.microsoft.com (157.54.7.154) with Microsoft SMTP Server id 14.0.639.13; Tue, 1 Sep 2009 09:16:18 -0700
Received: from TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com ([169.254.3.25]) by TK5EX14MLTW651.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.39]) with mapi; Tue, 1 Sep 2009 09:16:30 -0700
From: Dave Thaler <dthaler@microsoft.com>
To: Wassim Haddad <wassim.haddad@ericsson.com>, "hesham@elevatemobile.com" <hesham@elevatemobile.com>
Thread-Topic: [BEHAVE] NAT64 and MIPv6
Thread-Index: AQHKKHuIwEJcSog/t0mWiJZwt4jxx5C//1+AgAEYr4D//60LwIAAl/4A//+c3CCAAAvsuIAA2JvwgAAN9/CAAAGkEA==
Date: Tue, 1 Sep 2009 16:16:15 +0000
Message-ID: <E4561B14EE2A3E4E9D478EBFB5416E1B1C3AA8@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
References: <E4561B14EE2A3E4E9D478EBFB5416E1B1C3163@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <C6C2C322.F191%hesham@elevatemobile.com> <E4561B14EE2A3E4E9D478EBFB5416E1B1C389D@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <2991246A29623A4082EB2B06A2B891A41B7C4591FD@EUSAACMS0703.eamcs.ericsson.se>
In-Reply-To: <2991246A29623A4082EB2B06A2B891A41B7C4591FD@EUSAACMS0703.eamcs.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "behave@ietf.org" <behave@ietf.org>
Subject: Re: [BEHAVE] NAT64 and MIPv6
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/mail-archive/web/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>
X-List-Received-Date: Tue, 01 Sep 2009 16:16:10 -0000

Yes.

> -----Original Message-----
> From: Wassim Haddad [mailto:wassim.haddad@ericsson.com]
> Sent: Tuesday, September 01, 2009 9:14 AM
> To: Dave Thaler; hesham@elevatemobile.com
> Cc: behave@ietf.org; Wassim Haddad
> Subject: RE: [BEHAVE] NAT64 and MIPv6
>
> > At the very least any solution should highlight this as a requirement
> > for MNs because 3775 doesn't limit the DNS queries to the home DNS.
> > But I don't know how to do that if the presence of a NAT is not known
> > to the host.
>
> I agree that 3775 is defective by not mentioning this, since again the
> presence of a NAT does not introduce this problem... it already breaks
> with private namespaces and 3775 should have pointed out how to make DNS
> work.
>
> =3D> Just to clarify: you mean RFC 3775 is defective by not mentioning th=
at
> "the MN should NOT rely on the DNS in the foreign network when using MIPv=
6
> (i.e., its home address). Instead, it should/must rely on the home DNS".
>
> Is that correct?
>
>
> Wassim H.
>


From zhouboyj@gmail.com  Tue Sep  1 09:29:25 2009
Return-Path: <zhouboyj@gmail.com>
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 8697B28C6EF for <behave@core3.amsl.com>; Tue,  1 Sep 2009 09:29:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.921
X-Spam-Level: 
X-Spam-Status: No, score=-0.921 tagged_above=-999 required=5 tests=[AWL=-0.423, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, J_CHICKENPOX_19=0.6, J_CHICKENPOX_62=0.6, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AAJUV7sLGneV for <behave@core3.amsl.com>; Tue,  1 Sep 2009 09:29:24 -0700 (PDT)
Received: from mail-iw0-f200.google.com (mail-iw0-f200.google.com [209.85.223.200]) by core3.amsl.com (Postfix) with ESMTP id 595633A6EC5 for <behave@ietf.org>; Tue,  1 Sep 2009 09:29:24 -0700 (PDT)
Received: by iwn38 with SMTP id 38so51180iwn.29 for <behave@ietf.org>; Tue, 01 Sep 2009 09:29:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=HrxylIoparSU6kj0NLEH6o1Ww/YaO4ZenkC/GZUUF0o=; b=IU31Gspd/F2Srp6X24o+1pZP6eSTzgH2vDs7CClCggR/uIph/lo7LRrtaY0icW9sPz oWFrqVcc73tNIC9pXtUroZ4Omp6M11iKRg+QXFRGoO/rKN2ft9chpO+A8SkeywOu7vb+ QoGUo/oETX6FzuS2B1psgcXURmS8Wm55+z4rM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=kah27XwPXfCpybwQHuwQnXI6PVKQYhYC/OnXQA3NeWLckMn0IREGFxjC0e2YyfGDQy kilLFjdLL8IcV0hU3oRpE1IXjIfren64/QA725mLVDhCT/sGXf1MQDJTd44XcJibZds1 l1EmKcOF6Lil5gfh/DjEuuQtahhV0J1+/BI7s=
MIME-Version: 1.0
Received: by 10.231.122.162 with SMTP id l34mr7947792ibr.20.1251822571463;  Tue, 01 Sep 2009 09:29:31 -0700 (PDT)
In-Reply-To: <095E4E4E-F4F5-4FFD-95D5-4D6C05608124@free.fr>
References: <095E4E4E-F4F5-4FFD-95D5-4D6C05608124@free.fr>
Date: Wed, 2 Sep 2009 00:29:31 +0800
Message-ID: <36a593230909010929j14f04b09i8deb0237f412de32@mail.gmail.com>
From: bo zhou <zhouboyj@gmail.com>
To: =?ISO-8859-1?B?UultaSBEZXNwculz?= <remi.despres@free.fr>
Content-Type: multipart/alternative; boundary=0016e64608e4b1a63c047286a732
Cc: Xing Li <xing@cernet.edu.cn>, Behave WG <behave@ietf.org>, Fred Baker <fred@cisco.com>, Dave Thaler <dthaler@windows.microsoft.com>
Subject: Re: [BEHAVE] IPv4-only and IPv6-only definitions
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/mail-archive/web/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>
X-List-Received-Date: Tue, 01 Sep 2009 16:29:25 -0000

--0016e64608e4b1a63c047286a732
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Well,

I think the  IP endpoint shall be defined combining with four aspects:
a. the application type installed on the endpoint,
b.the IP family stack supported by the endpoint
c.the IP family routing assigned by a network
d.available IP family connectivity

If the IPvX only endpoint is only focus on 6/4 translation framework, I
agree with Remi that its connection traverses an IPv6/IPv4 translator.
However, in general, we need not define IPvX only endpoint traverses
translator.

Futrhermore, we can predict there should be some "endpoint" cannot easy to
define as IPvX/Y only endpoint. for example:
 IPv4-inherited IPv6 host comprises an IPv4/IPv6 enabled end system
dual-stack plus IPv6 routing in the network, IPv4/IPv6 applications
installed on the host. It implies two application instances with installed
IPv4/IPv6 applications are capable of communication using IPv6 =96 they hav=
e
IPv4/IPv6 dual-stack, network support including routing in IPv6, IPv4/IPv6
applications can communicate with IPv4/IPv6 hosts respectively.
   Regards,

Bo Zhou


On Tue, Sep 1, 2009 at 6:40 PM, R=E9mi Despr=E9s <remi.despres@free.fr> wro=
te:

> Dave,
>
> I also also think that the current definition of IPv6-only needs more wor=
k.
>
> Here is an approach which, in my understanding, would improve the
> situation.
> (Whereas you introduced "connected", as an adjective for applications, it
> introduces "connections", and more precisely connection "endpoints" as
> objects that can be IPv6-only at one end and IPv4-only at the other end.)
>
>
> 1. The definition would become(in substance):
> "IPvX-only endpoint: In a connection that traverses an IPv6/IPv4
> translator, the endpoint that works in IPvX. Reasons for this may be that=
:
> (1) its application is IPvX-only (not IPvY capable); (2) its node is
> IPvX-only (not IPvY-enabled); (3) if the endpoint is connection initiator=
,
> all known addresses of the other endpoint are IPvX (and translatable to
> IPvY); if the endpoint is connection acceptor, all of its addresses known=
 by
> other endpoint are IPvY (translatable to IPvX)."
>
> 2. In the text, IPv6-only entities that contain connection endpoints
> ("systems", "devices", "equipment", "nodes") would be renamed "IPv6-only
> endpoints".
>
> Regards,
> RD
>
>
> Le 1 sept. 09 =E0 00:54, Dave Thaler a =E9crit :
>
> "IPv6-only" is an adjective and can be used to describe a network,
>> a host, or an application.
>>
>> The text in the framework doc says:
>>   IPv6-only:  An IPv6-only implementation, in this context, comprises
>>      an IPv6 enabled end system stack plus routing in the network.  It
>>      implies that two application instances are capable of
>>      communicating using IPv6, but not IPv4 - they have an IPv6 stack,
>>      addresses, and network support including routing in IPv6, but some
>>      element is missing that prevents communication with IPv4 hosts.
>>
>> One problem with the above is that it confuses whether it's an adjective=
,
>> or a term "IPv6-only implementation" or an "IPv6-only end system" or
>> an "IPv6-only application"
>> ...
>> I think people would expect that an IP-version agnostic application woul=
d
>> be "IPv4-capable" but not necessarily "IPv4-connected".
>>
>
>
>
>
>
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>



--=20
Regards,

Bo Zhou
China Mobile

--0016e64608e4b1a63c047286a732
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div>Well,</div>
<div>=C2=A0</div>
<div>I=C2=A0think the=C2=A0 IP=C2=A0endpoint shall be defined combining wit=
h four aspects: <br>a. the application type installed on the endpoint, <br>=
b.the IP family stack supported by=C2=A0the endpoint=C2=A0<br>c.the IP fami=
ly routing assigned by a network <br>
d.available IP family connectivity </div>
<div>=C2=A0</div>
<div>If the IPvX only endpoint is only focus on 6/4 translation framework, =
I agree with Remi that its connection traverses an IPv6/IPv4 translator. Ho=
wever, in general, we need not define IPvX only endpoint traverses translat=
or.</div>

<div>=C2=A0</div>
<div>Futrhermore, we can predict<font color=3D"#000000"> there should be so=
me &quot;endpoint&quot; cannot easy to define as IPvX/Y only endpoint. for =
example:=C2=A0=C2=A0 </font></div>
<div>
<div class=3D"O1" style=3D"mso-line-spacing: &#39;100 30 0&#39;; mso-char-w=
rap: 1; mso-kinsoku-overflow: 1"><font color=3D"#000000"><font color=3D"#00=
0000"><font color=3D"#000000"><font color=3D"#000000"><font color=3D"#00000=
0"><font size=3D"2"><span lang=3D"EN-US" style=3D"FONT-SIZE: 12pt; COLOR: r=
ed; mso-fareast-font-family: =E5=AE=8B=E4=BD=93; mso-hansi-font-family: Ari=
al; mso-fareast-language: ZH-CN"><font color=3D"#000000" size=3D"2">IPv4-in=
herited IPv6 host</font></span><span lang=3D"EN-US" style=3D"FONT-SIZE: 12p=
t; mso-fareast-font-family: =E5=AE=8B=E4=BD=93; mso-hansi-font-family: Aria=
l; mso-fareast-language: ZH-CN"> </span></font></font><span lang=3D"EN-US" =
style=3D"FONT-SIZE: 12pt; COLOR: red; mso-fareast-font-family: =E5=AE=8B=E4=
=BD=93; mso-hansi-font-family: Arial; mso-fareast-language: ZH-CN"><font co=
lor=3D"#000000"><font size=3D"2">comprises an IPv4/IPv6 enabled</font> <fon=
t size=3D"2">end system dual-stack plus</font></font><font size=3D"2"> </fo=
nt></span></font><span lang=3D"EN-US" style=3D"FONT-SIZE: 12pt; COLOR: red;=
 mso-fareast-font-family: =E5=AE=8B=E4=BD=93; mso-hansi-font-family: Arial;=
 mso-fareast-language: ZH-CN"><font size=3D"2"><font color=3D"#000000">IPv6=
 routing</font> <font color=3D"#000000">in the network, IPv4/IPv6 applicati=
ons installed on the host. It implies two</font> </font></span></font><span=
 lang=3D"EN-US" style=3D"FONT-SIZE: 12pt; COLOR: red; mso-fareast-font-fami=
ly: =E5=AE=8B=E4=BD=93; mso-hansi-font-family: Arial; mso-fareast-language:=
 ZH-CN"><font size=3D"2"><font color=3D"#000000"><font color=3D"#000000"><f=
ont color=3D"#000000">application</font> </font>instances with installed IP=
v4/IPv6 applications are capable of communication</font> </font></span></fo=
nt><span lang=3D"EN-US" style=3D"FONT-SIZE: 12pt; COLOR: red; mso-fareast-f=
ont-family: =E5=AE=8B=E4=BD=93; mso-hansi-font-family: Arial; mso-fareast-l=
anguage: ZH-CN"><font size=3D"2"><font color=3D"#000000">using IPv6 =E2=80=
=93 they have IPv4/IPv6 dual-stack, network support including routing in IP=
v6,</font> </font></span></font><span lang=3D"EN-US" style=3D"FONT-SIZE: 12=
pt; COLOR: red; mso-fareast-font-family: =E5=AE=8B=E4=BD=93; mso-hansi-font=
-family: Arial; mso-fareast-language: ZH-CN"><font color=3D"#000000" size=
=3D"2">IPv4/IPv6 applications can communicate with IPv4/IPv6 hosts respecti=
vely.</font> </span></div>

<div class=3D"O" style=3D"mso-line-spacing: &#39;100 30 0&#39;; mso-char-wr=
ap: 1; mso-kinsoku-overflow: 1"><span style=3D"FONT-SIZE: 12pt; FONT-FAMILY=
: =E5=AE=8B=E4=BD=93; mso-fareast-font-family: =E5=AE=8B=E4=BD=93; mso-hans=
i-font-family: Arial"></span></div>

<div class=3D"O" style=3D"mso-line-spacing: &#39;100 50 0&#39;; mso-char-wr=
ap: 1; mso-kinsoku-overflow: 1"></div></div>
<div>
<div class=3D"O" style=3D"mso-line-spacing: &#39;100 30 0&#39;; mso-char-wr=
ap: 1; mso-kinsoku-overflow: 1"><span style=3D"FONT-SIZE: 12pt; FONT-FAMILY=
: =E5=AE=8B=E4=BD=93; mso-fareast-font-family: =E5=AE=8B=E4=BD=93; mso-hans=
i-font-family: Arial"></span></div>

<div class=3D"O" style=3D"mso-line-spacing: &#39;100 50 0&#39;; mso-char-wr=
ap: 1; mso-kinsoku-overflow: 1"></div></div>
<div>Regards,</div>
<div>=C2=A0</div>
<div>Bo Zhou</div>
<div><br>=C2=A0</div>
<div class=3D"gmail_quote">On Tue, Sep 1, 2009 at 6:40 PM, R=C3=A9mi Despr=
=C3=A9s <span dir=3D"ltr">&lt;<a href=3D"mailto:remi.despres@free.fr">remi.=
despres@free.fr</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Dave,<br><br>I also also think t=
hat the current definition of IPv6-only needs more work.<br><br>Here is an =
approach which, in my understanding, would improve the situation.<br>
(Whereas you introduced &quot;connected&quot;, as an adjective for applicat=
ions, it introduces &quot;connections&quot;, and more precisely connection =
&quot;endpoints&quot; as objects that can be IPv6-only at one end and IPv4-=
only at the other end.)<br>
<br><br>1. The definition would become(in substance):<br>&quot;IPvX-only en=
dpoint: In a connection that traverses an IPv6/IPv4 translator, the endpoin=
t that works in IPvX. Reasons for this may be that: (1) its application is =
IPvX-only (not IPvY capable); (2) its node is IPvX-only (not IPvY-enabled);=
 (3) if the endpoint is connection initiator, all known addresses of the ot=
her endpoint are IPvX (and translatable to IPvY); if the endpoint is connec=
tion acceptor, all of its addresses known by other endpoint are IPvY (trans=
latable to IPvX).&quot;<br>
<br>2. In the text, IPv6-only entities that contain connection endpoints (&=
quot;systems&quot;, &quot;devices&quot;, &quot;equipment&quot;, &quot;nodes=
&quot;) would be renamed &quot;IPv6-only endpoints&quot;.<br><br>Regards,<b=
r>
RD<br><br><br>Le 1 sept. 09 =C3=A0 00:54, Dave Thaler a =C3=A9crit :<br><br=
>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">&quot;IPv6-only&quot; is an adje=
ctive and can be used to describe a network,<br>a host, or an application.<=
br>
<br>The text in the framework doc says:<br>=C2=A0 IPv6-only: =C2=A0An IPv6-=
only implementation, in this context, comprises<br>=C2=A0 =C2=A0 =C2=A0an I=
Pv6 enabled end system stack plus routing in the network. =C2=A0It<br>=C2=
=A0 =C2=A0 =C2=A0implies that two application instances are capable of<br>
=C2=A0 =C2=A0 =C2=A0communicating using IPv6, but not IPv4 - they have an I=
Pv6 stack,<br>=C2=A0 =C2=A0 =C2=A0addresses, and network support including =
routing in IPv6, but some<br>=C2=A0 =C2=A0 =C2=A0element is missing that pr=
events communication with IPv4 hosts.<br>
<br>One problem with the above is that it confuses whether it&#39;s an adje=
ctive,<br>or a term &quot;IPv6-only implementation&quot; or an &quot;IPv6-o=
nly end system&quot; or<br>an &quot;IPv6-only application&quot;<br>...<br>
I think people would expect that an IP-version agnostic application would b=
e &quot;IPv4-capable&quot; but not necessarily &quot;IPv4-connected&quot;.<=
br></blockquote><br><br><br><br><br>_______________________________________=
________<br>
Behave mailing list<br><a href=3D"mailto:Behave@ietf.org" target=3D"_blank"=
>Behave@ietf.org</a><br><a href=3D"https://www.ietf.org/mailman/listinfo/be=
have" target=3D"_blank">https://www.ietf.org/mailman/listinfo/behave</a><br=
></blockquote>
</div><br><br clear=3D"all">
<div></div><br>-- <br>Regards,<br><br>Bo Zhou<br>China Mobile<br>

--0016e64608e4b1a63c047286a732--

From remi.despres@free.fr  Tue Sep  1 09:29:28 2009
Return-Path: <remi.despres@free.fr>
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 0F0DE28C7FB for <behave@core3.amsl.com>; Tue,  1 Sep 2009 09:29:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.82
X-Spam-Level: 
X-Spam-Status: No, score=-1.82 tagged_above=-999 required=5 tests=[AWL=0.129,  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 gOrhkP+pEu3f for <behave@core3.amsl.com>; Tue,  1 Sep 2009 09:29:27 -0700 (PDT)
Received: from smtp6-g21.free.fr (smtp6-g21.free.fr [212.27.42.6]) by core3.amsl.com (Postfix) with ESMTP id 0DA8B3A69ED for <behave@ietf.org>; Tue,  1 Sep 2009 09:29:25 -0700 (PDT)
Received: from smtp6-g21.free.fr (localhost [127.0.0.1]) by smtp6-g21.free.fr (Postfix) with ESMTP id 1EFE0E081DD; Tue,  1 Sep 2009 18:29:30 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by smtp6-g21.free.fr (Postfix) with ESMTP id 18734E08198; Tue,  1 Sep 2009 18:29:27 +0200 (CEST)
Mime-Version: 1.0 (Apple Message framework v753.1)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <0A5916B6-4B95-4818-B099-044701D4B659@free.fr>
Content-Transfer-Encoding: 7bit
From: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
Date: Tue, 1 Sep 2009 18:29:21 +0200
To: Christian Huitema <huitema@microsoft.com>
X-Mailer: Apple Mail (2.753.1)
Cc: Behave WG <behave@ietf.org>, Dave Thaler <dthaler@windows.microsoft.com>
Subject: [BEHAVE] draft-ietf-behave-address-format-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/mail-archive/web/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>
X-List-Received-Date: Tue, 01 Sep 2009 16:29:28 -0000

Christian,


1.
The draft says in its sec. 2.1.5.3:

    The use of a prefix length longer than 64 bits may affect the
    Interface Identifier format.  Specifically, [RFC4291] section 2.5.1
    requires that for all unicast addresses, except those that start  
with
    the binary value 000, Interface IDs are required to be 64 bits long
    and to be constructed in Modified EUI-64 format.  While any method
    can be used to construct a Modified EUI-64, the format requires the
    71st bit (the universal/local bit) to be set with specific meaning,
    and hence it is not available for use by an address format unless  
the
    prefix starts with binary 000.

Here is a text that, without changing the conclusion, would in my  
understanding better reflect points that were made.

[RFC4291] section 2.5.1 imposes that "for all unicast addresses,  
except those that start with the binary value 000, Interface IDs  
(IIDs) are required to be 64 bits long and to be constructed in  
Modified EUI-64 format". In the case of an IPv6 address used to  
represent an IPv4 host, its 64 lower bits are never used to identify  
an interface on an IPv6 link. These lower bits are therefore not  
concerned with the semantics of IIDs. The IID format requirement has  
no technical reason to apply. However, to avoid that a discussion  
involving interpretation of [RFC 4291 ]could delay progress of the  
present draft, where specified address formats are urgently needed,  
all formats defined here comply with the Modified EUI-64  
specification: the 71st bit of IPv6 addresses (the universal/local  
bit) has its meaning defined in [RFC 4291 ].

2.
To qualify IPv6 Addresses, what about replacing "Used to Represent  
IPv4 Hosts" (rather long), by "IPv4-mappable" (shorter, not used yet,  
reasonably intuitive)?


Regards,
RD 

From wassim.haddad@ericsson.com  Tue Sep  1 09:30:28 2009
Return-Path: <wassim.haddad@ericsson.com>
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 E0A143A6CE1 for <behave@core3.amsl.com>; Tue,  1 Sep 2009 09:30:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.574
X-Spam-Level: 
X-Spam-Status: No, score=-6.574 tagged_above=-999 required=5 tests=[AWL=0.025,  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 cskgWIuKfOEf for <behave@core3.amsl.com>; Tue,  1 Sep 2009 09:30:28 -0700 (PDT)
Received: from imr1.ericy.com (imr1.ericy.com [198.24.6.9]) by core3.amsl.com (Postfix) with ESMTP id E83953A69ED for <behave@ietf.org>; Tue,  1 Sep 2009 09:30:27 -0700 (PDT)
Received: from eusrcmw750.eamcs.ericsson.se (eusrcmw750.exu.ericsson.se [138.85.77.50]) by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id n81GUYKo032495; Tue, 1 Sep 2009 11:30:38 -0500
Received: from eusrcmw751.eamcs.ericsson.se ([138.85.77.51]) by eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 1 Sep 2009 11:30:10 -0500
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 1 Sep 2009 11:30:10 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.20]) by eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) with mapi; Tue, 1 Sep 2009 12:30:09 -0400
From: Wassim Haddad <wassim.haddad@ericsson.com>
To: "dthaler@microsoft.com" <dthaler@microsoft.com>, "hesham@elevatemobile.com" <hesham@elevatemobile.com>
Date: Tue, 1 Sep 2009 12:30:09 -0400
Thread-Topic: [BEHAVE] NAT64 and MIPv6
Thread-Index: AQHKKHuIwEJcSog/t0mWiJZwt4jxx5C//1+AgAEYr4D//60LwIAAl/4A//+c3CCAAAvsuIAA2JvwgAAN9/CAAAGkEIAAAD/w
Message-ID: <2991246A29623A4082EB2B06A2B891A41B7C459216@EUSAACMS0703.eamcs.ericsson.se>
References: <E4561B14EE2A3E4E9D478EBFB5416E1B1C3163@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <C6C2C322.F191%hesham@elevatemobile.com> <E4561B14EE2A3E4E9D478EBFB5416E1B1C389D@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <2991246A29623A4082EB2B06A2B891A41B7C4591FD@EUSAACMS0703.eamcs.ericsson.se> <E4561B14EE2A3E4E9D478EBFB5416E1B1C3AA8@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <E4561B14EE2A3E4E9D478EBFB5416E1B1C3AA8@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 01 Sep 2009 16:30:10.0400 (UTC) FILETIME=[79641E00:01CA2B21]
Cc: Wassim Haddad <wassim.haddad@ericsson.com>, "behave@ietf.org" <behave@ietf.org>
Subject: Re: [BEHAVE] NAT64 and MIPv6
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/mail-archive/web/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>
X-List-Received-Date: Tue, 01 Sep 2009 16:30:29 -0000

Yes.

=3D> OK. This also means:

"When the MN reboots in the foreign network, then it should/must rely on th=
e foreign=20
DNS in order to be able to communicate with its HA (i.e., turn on MIPv6)".=
=20


Thanks!
Wassim H.


> -----Original Message-----
> From: Wassim Haddad [mailto:wassim.haddad@ericsson.com]
> Sent: Tuesday, September 01, 2009 9:14 AM
> To: Dave Thaler; hesham@elevatemobile.com
> Cc: behave@ietf.org; Wassim Haddad
> Subject: RE: [BEHAVE] NAT64 and MIPv6
>
> > At the very least any solution should highlight this as a=20
> > requirement for MNs because 3775 doesn't limit the DNS queries to the h=
ome DNS.
> > But I don't know how to do that if the presence of a NAT is not=20
> > known to the host.
>
> I agree that 3775 is defective by not mentioning this, since again the=20
> presence of a NAT does not introduce this problem... it already breaks=20
> with private namespaces and 3775 should have pointed out how to make=20
> DNS work.
>
> =3D> Just to clarify: you mean RFC 3775 is defective by not mentioning=20
> that "the MN should NOT rely on the DNS in the foreign network when=20
> using MIPv6 (i.e., its home address). Instead, it should/must rely on the=
 home DNS".
>
> Is that correct?
>
>
> Wassim H.
>

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

From zhouboyj@gmail.com  Tue Sep  1 09:33:47 2009
Return-Path: <zhouboyj@gmail.com>
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 C4B6928C791 for <behave@core3.amsl.com>; Tue,  1 Sep 2009 09:33:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.029
X-Spam-Level: 
X-Spam-Status: No, score=-1.029 tagged_above=-999 required=5 tests=[AWL=-0.231, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, J_CHICKENPOX_19=0.6, J_CHICKENPOX_62=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 luQQ-Vv-m4RZ for <behave@core3.amsl.com>; Tue,  1 Sep 2009 09:33:46 -0700 (PDT)
Received: from mail-iw0-f200.google.com (mail-iw0-f200.google.com [209.85.223.200]) by core3.amsl.com (Postfix) with ESMTP id 996063A6C92 for <behave@ietf.org>; Tue,  1 Sep 2009 09:33:46 -0700 (PDT)
Received: by iwn38 with SMTP id 38so53082iwn.29 for <behave@ietf.org>; Tue, 01 Sep 2009 09:33:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=yNeBzu2A8TgU3yh8PfQEYoDDp4H4KgM3lhePLeTi10w=; b=laQZspDcXb4SODumD+lZeqxqIqcahMNEK/cfDmiaYN7JJnhWkuWz3GrklYCiD/hSwl gLFvek4pViv/E3JeApgq8pGBGwKvvQrglbvI5vE8UkNXoT5xsfc1pF8au1jxN95aNCmg /w9Ape8LDpvSf2tncKTN5gIoYB0M13OfWSOdo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=iOZ45fl9hGTJtL9oEt6GPVMlgSqCrstIng7WvMHUeuLgLrwTzqZoz/Cr9lLtlDlU/o pMG/O/PASDpry7xkJZm4TsBNAMXWUUEw0msYXuCSWUhioxq6T9Kt7o7dDUHXbYEWuJfS 7GvIvggf27Q5TImLK7Wb/XWOoumYbLA8D6nxs=
MIME-Version: 1.0
Received: by 10.231.121.69 with SMTP id g5mr7901275ibr.44.1251822836000; Tue,  01 Sep 2009 09:33:56 -0700 (PDT)
In-Reply-To: <36a593230909010929j14f04b09i8deb0237f412de32@mail.gmail.com>
References: <095E4E4E-F4F5-4FFD-95D5-4D6C05608124@free.fr> <36a593230909010929j14f04b09i8deb0237f412de32@mail.gmail.com>
Date: Wed, 2 Sep 2009 00:33:55 +0800
Message-ID: <36a593230909010933u657b573dgb56e59273dc9ce82@mail.gmail.com>
From: bo zhou <zhouboyj@gmail.com>
To: dthaler@microsoft.com
Content-Type: multipart/alternative; boundary=0016e644cd96762874047286b704
Cc: Xing Li <xing@cernet.edu.cn>, Behave WG <behave@ietf.org>, Fred Baker <fred@cisco.com>
Subject: Re: [BEHAVE] IPv4-only and IPv6-only definitions
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/mail-archive/web/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>
X-List-Received-Date: Tue, 01 Sep 2009 16:33:47 -0000

--0016e644cd96762874047286b704
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi Dave,

I just find the previous discussion used a wrong email address of you, so I
modify it, Hope you can receive it now.

Regards,

Bo Zhou

On Wed, Sep 2, 2009 at 12:29 AM, bo zhou <zhouboyj@gmail.com> wrote:

> Well,
>
> I think the  IP endpoint shall be defined combining with four aspects:
> a. the application type installed on the endpoint,
> b.the IP family stack supported by the endpoint
> c.the IP family routing assigned by a network
> d.available IP family connectivity
>
> If the IPvX only endpoint is only focus on 6/4 translation framework, I
> agree with Remi that its connection traverses an IPv6/IPv4 translator.
> However, in general, we need not define IPvX only endpoint traverses
> translator.
>
> Futrhermore, we can predict there should be some "endpoint" cannot easy t=
o
> define as IPvX/Y only endpoint. for example:
>  IPv4-inherited IPv6 host comprises an IPv4/IPv6 enabled end system
> dual-stack plus IPv6 routing in the network, IPv4/IPv6 applications
> installed on the host. It implies two application instances with installe=
d
> IPv4/IPv6 applications are capable of communication using IPv6 =96 they h=
ave
> IPv4/IPv6 dual-stack, network support including routing in IPv6, IPv4/IPv=
6
> applications can communicate with IPv4/IPv6 hosts respectively.
>    Regards,
>
> Bo Zhou
>
>
> On Tue, Sep 1, 2009 at 6:40 PM, R=E9mi Despr=E9s <remi.despres@free.fr> w=
rote:
>
>> Dave,
>>
>> I also also think that the current definition of IPv6-only needs more
>> work.
>>
>> Here is an approach which, in my understanding, would improve the
>> situation.
>> (Whereas you introduced "connected", as an adjective for applications, i=
t
>> introduces "connections", and more precisely connection "endpoints" as
>> objects that can be IPv6-only at one end and IPv4-only at the other end.=
)
>>
>>
>> 1. The definition would become(in substance):
>> "IPvX-only endpoint: In a connection that traverses an IPv6/IPv4
>> translator, the endpoint that works in IPvX. Reasons for this may be tha=
t:
>> (1) its application is IPvX-only (not IPvY capable); (2) its node is
>> IPvX-only (not IPvY-enabled); (3) if the endpoint is connection initiato=
r,
>> all known addresses of the other endpoint are IPvX (and translatable to
>> IPvY); if the endpoint is connection acceptor, all of its addresses know=
n by
>> other endpoint are IPvY (translatable to IPvX)."
>>
>> 2. In the text, IPv6-only entities that contain connection endpoints
>> ("systems", "devices", "equipment", "nodes") would be renamed "IPv6-only
>> endpoints".
>>
>> Regards,
>> RD
>>
>>
>> Le 1 sept. 09 =E0 00:54, Dave Thaler a =E9crit :
>>
>> "IPv6-only" is an adjective and can be used to describe a network,
>>> a host, or an application.
>>>
>>> The text in the framework doc says:
>>>   IPv6-only:  An IPv6-only implementation, in this context, comprises
>>>      an IPv6 enabled end system stack plus routing in the network.  It
>>>      implies that two application instances are capable of
>>>      communicating using IPv6, but not IPv4 - they have an IPv6 stack,
>>>      addresses, and network support including routing in IPv6, but some
>>>      element is missing that prevents communication with IPv4 hosts.
>>>
>>> One problem with the above is that it confuses whether it's an adjectiv=
e,
>>> or a term "IPv6-only implementation" or an "IPv6-only end system" or
>>> an "IPv6-only application"
>>> ...
>>> I think people would expect that an IP-version agnostic application wou=
ld
>>> be "IPv4-capable" but not necessarily "IPv4-connected".
>>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> Behave mailing list
>> Behave@ietf.org
>> https://www.ietf.org/mailman/listinfo/behave
>>
>
>
>
> --
> Regards,
>
> Bo Zhou
> China Mobile
>



--=20
Regards,

Bo Zhou
China Mobile

--0016e644cd96762874047286b704
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div>Hi Dave,</div>
<div>=A0</div>
<div>I just find the previous discussion used a wrong email address of you,=
 so I modify it, Hope you can receive it now.</div>
<div>=A0</div>
<div>Regards,</div>
<div>=A0</div>
<div>Bo Zhou<br><br></div>
<div class=3D"gmail_quote">On Wed, Sep 2, 2009 at 12:29 AM, bo zhou <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:zhouboyj@gmail.com">zhouboyj@gmail.com</a>=
&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>Well,</div>
<div>=A0</div>
<div>I=A0think the=A0 IP=A0endpoint shall be defined combining with four as=
pects: <br>a. the application type installed on the endpoint, <br>b.the IP =
family stack supported by=A0the endpoint=A0<br>c.the IP family routing assi=
gned by a network <br>
d.available IP family connectivity </div>
<div>=A0</div>
<div>If the IPvX only endpoint is only focus on 6/4 translation framework, =
I agree with Remi that its connection traverses an IPv6/IPv4 translator. Ho=
wever, in general, we need not define IPvX only endpoint traverses translat=
or.</div>

<div>=A0</div>
<div>Futrhermore, we can predict<font color=3D"#000000"> there should be so=
me &quot;endpoint&quot; cannot easy to define as IPvX/Y only endpoint. for =
example:=A0=A0 </font></div>
<div>
<div><font color=3D"#000000"><font color=3D"#000000"><font color=3D"#000000=
"><font color=3D"#000000"><font color=3D"#000000"><font size=3D"2"><span la=
ng=3D"EN-US" style=3D"FONT-SIZE: 12pt; COLOR: red"><font color=3D"#000000" =
size=3D"2">IPv4-inherited IPv6 host</font></span><span lang=3D"EN-US" style=
=3D"FONT-SIZE: 12pt"> </span></font></font><span lang=3D"EN-US" style=3D"FO=
NT-SIZE: 12pt; COLOR: red"><font color=3D"#000000"><font size=3D"2">compris=
es an IPv4/IPv6 enabled</font> <font size=3D"2">end system dual-stack plus<=
/font></font><font size=3D"2"> </font></span></font><span lang=3D"EN-US" st=
yle=3D"FONT-SIZE: 12pt; COLOR: red"><font size=3D"2"><font color=3D"#000000=
">IPv6 routing</font> <font color=3D"#000000">in the network, IPv4/IPv6 app=
lications installed on the host. It implies two</font> </font></span></font=
><span lang=3D"EN-US" style=3D"FONT-SIZE: 12pt; COLOR: red"><font size=3D"2=
"><font color=3D"#000000"><font color=3D"#000000"><font color=3D"#000000">a=
pplication</font> </font>instances with installed IPv4/IPv6 applications ar=
e capable of communication</font> </font></span></font><span lang=3D"EN-US"=
 style=3D"FONT-SIZE: 12pt; COLOR: red"><font size=3D"2"><font color=3D"#000=
000">using IPv6 =96 they have IPv4/IPv6 dual-stack, network support includi=
ng routing in IPv6,</font> </font></span></font><span lang=3D"EN-US" style=
=3D"FONT-SIZE: 12pt; COLOR: red"><font color=3D"#000000" size=3D"2">IPv4/IP=
v6 applications can communicate with IPv4/IPv6 hosts respectively.</font> <=
/span></div>

<div><span style=3D"FONT-SIZE: 12pt"></span></div>
<div></div></div>
<div>
<div><span style=3D"FONT-SIZE: 12pt"></span></div>
<div></div></div>
<div>Regards,</div>
<div>=A0</div>
<div>Bo Zhou</div>
<div>
<div></div>
<div class=3D"h5">
<div><br>=A0</div>
<div class=3D"gmail_quote">On Tue, Sep 1, 2009 at 6:40 PM, R=E9mi Despr=E9s=
 <span dir=3D"ltr">&lt;<a href=3D"mailto:remi.despres@free.fr" target=3D"_b=
lank">remi.despres@free.fr</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Dave,<br><br>I also also think t=
hat the current definition of IPv6-only needs more work.<br><br>Here is an =
approach which, in my understanding, would improve the situation.<br>
(Whereas you introduced &quot;connected&quot;, as an adjective for applicat=
ions, it introduces &quot;connections&quot;, and more precisely connection =
&quot;endpoints&quot; as objects that can be IPv6-only at one end and IPv4-=
only at the other end.)<br>
<br><br>1. The definition would become(in substance):<br>&quot;IPvX-only en=
dpoint: In a connection that traverses an IPv6/IPv4 translator, the endpoin=
t that works in IPvX. Reasons for this may be that: (1) its application is =
IPvX-only (not IPvY capable); (2) its node is IPvX-only (not IPvY-enabled);=
 (3) if the endpoint is connection initiator, all known addresses of the ot=
her endpoint are IPvX (and translatable to IPvY); if the endpoint is connec=
tion acceptor, all of its addresses known by other endpoint are IPvY (trans=
latable to IPvX).&quot;<br>
<br>2. In the text, IPv6-only entities that contain connection endpoints (&=
quot;systems&quot;, &quot;devices&quot;, &quot;equipment&quot;, &quot;nodes=
&quot;) would be renamed &quot;IPv6-only endpoints&quot;.<br><br>Regards,<b=
r>
RD<br><br><br>Le 1 sept. 09 =E0 00:54, Dave Thaler a =E9crit :<br><br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">&quot;IPv6-only&quot; is an adje=
ctive and can be used to describe a network,<br>a host, or an application.<=
br>
<br>The text in the framework doc says:<br>=A0 IPv6-only: =A0An IPv6-only i=
mplementation, in this context, comprises<br>=A0 =A0 =A0an IPv6 enabled end=
 system stack plus routing in the network. =A0It<br>=A0 =A0 =A0implies that=
 two application instances are capable of<br>
=A0 =A0 =A0communicating using IPv6, but not IPv4 - they have an IPv6 stack=
,<br>=A0 =A0 =A0addresses, and network support including routing in IPv6, b=
ut some<br>=A0 =A0 =A0element is missing that prevents communication with I=
Pv4 hosts.<br>
<br>One problem with the above is that it confuses whether it&#39;s an adje=
ctive,<br>or a term &quot;IPv6-only implementation&quot; or an &quot;IPv6-o=
nly end system&quot; or<br>an &quot;IPv6-only application&quot;<br>...<br>
I think people would expect that an IP-version agnostic application would b=
e &quot;IPv4-capable&quot; but not necessarily &quot;IPv4-connected&quot;.<=
br></blockquote><br><br><br><br><br>_______________________________________=
________<br>
Behave mailing list<br><a href=3D"mailto:Behave@ietf.org" target=3D"_blank"=
>Behave@ietf.org</a><br><a href=3D"https://www.ietf.org/mailman/listinfo/be=
have" target=3D"_blank">https://www.ietf.org/mailman/listinfo/behave</a><br=
></blockquote>
</div><br><br clear=3D"all">
<div></div><br></div></div><font color=3D"#888888">-- <br>Regards,<br><br>B=
o Zhou<br>China Mobile<br></font></blockquote></div><br><br clear=3D"all">
<div></div><br>-- <br>Regards,<br><br>Bo Zhou<br>China Mobile<br>

--0016e644cd96762874047286b704--

From dthaler@microsoft.com  Tue Sep  1 10:12:29 2009
Return-Path: <dthaler@microsoft.com>
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 EE77F28C88B for <behave@core3.amsl.com>; Tue,  1 Sep 2009 10:12:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.3
X-Spam-Level: 
X-Spam-Status: No, score=-10.3 tagged_above=-999 required=5 tests=[AWL=-0.001,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5m+hdk0sQQ4h for <behave@core3.amsl.com>; Tue,  1 Sep 2009 10:12:29 -0700 (PDT)
Received: from smtp.microsoft.com (maila.microsoft.com [131.107.115.212]) by core3.amsl.com (Postfix) with ESMTP id 8D0DF28C860 for <behave@ietf.org>; Tue,  1 Sep 2009 10:11:34 -0700 (PDT)
Received: from TK5EX14MLTC102.redmond.corp.microsoft.com (157.54.79.180) by TK5-EXGWY-E801.partners.extranet.microsoft.com (10.251.56.50) with Microsoft SMTP Server (TLS) id 8.2.176.0; Tue, 1 Sep 2009 10:11:47 -0700
Received: from TK5EX14MLTW651.wingroup.windeploy.ntdev.microsoft.com (157.54.71.39) by TK5EX14MLTC102.redmond.corp.microsoft.com (157.54.79.180) with Microsoft SMTP Server id 14.0.639.13; Tue, 1 Sep 2009 10:11:47 -0700
Received: from TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com ([169.254.3.25]) by TK5EX14MLTW651.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.39]) with mapi; Tue, 1 Sep 2009 10:11:58 -0700
From: Dave Thaler <dthaler@microsoft.com>
To: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
Thread-Topic: [BEHAVE] draft-ietf-behave-address-format-00
Thread-Index: AQHKKyGF59k2cg/pOEScJAj9QALQOZDB9yyw
Date: Tue, 1 Sep 2009 17:11:44 +0000
Message-ID: <E4561B14EE2A3E4E9D478EBFB5416E1B1C4ECE@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
References: <0A5916B6-4B95-4818-B099-044701D4B659@free.fr>
In-Reply-To: <0A5916B6-4B95-4818-B099-044701D4B659@free.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] draft-ietf-behave-address-format-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/mail-archive/web/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>
X-List-Received-Date: Tue, 01 Sep 2009 17:12:30 -0000

R=E9mi Despr=E9s wrote:
> To qualify IPv6 Addresses, what about replacing "Used to Represent
> IPv4 Hosts" (rather long), by "IPv4-mappable" (shorter, not used yet,
> reasonably intuitive)?

In my presentation at the WG meeting I used, as SIIT did:

"IPv4-mappED" (past tense, meaning the mapping already happened
   in order to get an IPv6 address) for addresses used to
   represent IPv4 hosts

"IPv4-translatABLE" (future tense, meaning the mapping
   has not yet happened, when you have an IPv6 address)
   for addresses assigned to IPv6 hosts

Of course the last term only applies to translation not
encapsulation, and Softwires folk wanted the doc to
cover both.  So I suppose "IPv4-mappable" could be
used for addresses assigned to IPv6 hosts.

(Just pointing this out because you suggested
IPv4-mappable be used for addresses used to
represent IPv4 hosts, which is backwards.)

-Dave

From maxpassion@gmail.com  Tue Sep  1 10:32:40 2009
Return-Path: <maxpassion@gmail.com>
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 E5AA928C90A for <behave@core3.amsl.com>; Tue,  1 Sep 2009 10:32:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.079
X-Spam-Level: 
X-Spam-Status: No, score=-2.079 tagged_above=-999 required=5 tests=[AWL=0.520,  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 oWFS7Id04txj for <behave@core3.amsl.com>; Tue,  1 Sep 2009 10:32:40 -0700 (PDT)
Received: from mail-vw0-f177.google.com (mail-vw0-f177.google.com [209.85.212.177]) by core3.amsl.com (Postfix) with ESMTP id 9B3DB28C911 for <behave@ietf.org>; Tue,  1 Sep 2009 10:32:31 -0700 (PDT)
Received: by vws7 with SMTP id 7so205668vws.29 for <behave@ietf.org>; Tue, 01 Sep 2009 10:32:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=9K3skwf22Iv1jYBk0UJG4scpaTaR++sFNHTdxXhmdcs=; b=T2rmgK2S1CGR2+IJK0DSPnC3hp+Qidw/Y5VsdtzEPfAgTHl6w8Mte+kbgqesAT2i95 1rWQiCOX4MTfh9AHmkzSt0hKm8kUzRd8iv8TokqQWG1rac4aaYyAgTLVPLd+OgDYpVXV SQfER3N3CvnFA86OBwmzgbnshg3H1AD2jBnxA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=O9FfhqV9TK9kR2f37TXpzkHdutCmnPfPWKgPxbRYQMkeq3AObSSjI6OaS/zDPhbm5R Y3FVBJHEbrOq+I90tagjyXGilVf8MO8fI92DLkVslOnkdi558aPG26R3GxOWKKloYb14 6adlrovRUWyrEShCPE7dphffSE7v6JGvbNdMk=
MIME-Version: 1.0
Received: by 10.220.88.201 with SMTP id b9mr9151155vcm.106.1251826333500; Tue,  01 Sep 2009 10:32:13 -0700 (PDT)
In-Reply-To: <2991246A29623A4082EB2B06A2B891A41B7C458E91@EUSAACMS0703.eamcs.ericsson.se>
References: <2991246A29623A4082EB2B06A2B891A41B7C3D85A9@EUSAACMS0703.eamcs.ericsson.se> <25e1aaa40908310956m6f638a4x32dca4039b63b21d@mail.gmail.com> <2991246A29623A4082EB2B06A2B891A41B7C458E91@EUSAACMS0703.eamcs.ericsson.se>
Date: Wed, 2 Sep 2009 01:32:11 +0800
Message-ID: <25e1aaa40909011032t7f76e318i5b815a1d08995464@mail.gmail.com>
From: liu dapeng <maxpassion@gmail.com>
To: Wassim Haddad <wassim.haddad@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "behave@ietf.org" <behave@ietf.org>
Subject: Re: [BEHAVE] NAT64 and MIPv6
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/mail-archive/web/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>
X-List-Received-Date: Tue, 01 Sep 2009 17:32:41 -0000

Thanks Wassim,

2009/9/1, Wassim Haddad <wassim.haddad@ericsson.com>:
> Hi,
>
> I am wondering where does the HA locate?   it locate in the IPv6
> network or in the IPv4 network?
>
> => the home network is an IPv6 network which has its own NAT64 and DNS64.
> Did I answer your question?

Then you mean the HA is located in the IPv6 netowrk if I understood it
correctly, right?

BR,
Dapeng Liu
>
> Regards,
>
> Wassim H.
>

From maxpassion@gmail.com  Tue Sep  1 10:35:39 2009
Return-Path: <maxpassion@gmail.com>
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 E61D228C8CD for <behave@core3.amsl.com>; Tue,  1 Sep 2009 10:35:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[AWL=0.502,  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 5XDz9KhT8VWn for <behave@core3.amsl.com>; Tue,  1 Sep 2009 10:35:39 -0700 (PDT)
Received: from mail-vw0-f177.google.com (mail-vw0-f177.google.com [209.85.212.177]) by core3.amsl.com (Postfix) with ESMTP id B57F43A7053 for <behave@ietf.org>; Tue,  1 Sep 2009 10:35:38 -0700 (PDT)
Received: by vws7 with SMTP id 7so208741vws.29 for <behave@ietf.org>; Tue, 01 Sep 2009 10:35:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=4qaVdfboY70Qi2eWY64lnAuqxWJp3bD7s/Ey9ezyFTc=; b=AgDPqDUDOTp7P0zwfzQZClWVDWYb7ux2p3e+RNpYbxyDSfDkkWjr2L0jjTOk8KhJiZ u2iLHr7Wp3kgbUdklEwp/JV9jS+DLRMCyHywuSgfoELRp3J5rsyZDSUuzgJLDKSQ7hYF Va8yYEiLLTE1Z3LMHhk54HOilxgzPWT3xxm78=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=YYaEMxRQ04Q1VeWQb8Fkzeao4RNpdusQP3Af8LJsB+b0RrLybotyq0CPADeJN9FXSK LUlRVqjzYVTr+ehCkVpfkn5GqDQceepxBMx9YX/wEjZFt4Ilz7PJo74Lp3kQbLs0M+bH +t4N/bQV6g+6Nqkiuf4tfZZPEvReJcxlk49Mc=
MIME-Version: 1.0
Received: by 10.220.108.102 with SMTP id e38mr8916761vcp.71.1251826547270;  Tue, 01 Sep 2009 10:35:47 -0700 (PDT)
In-Reply-To: <4A9C32D3.80106@it.uc3m.es>
References: <2991246A29623A4082EB2B06A2B891A41B7C3D85A9@EUSAACMS0703.eamcs.ericsson.se> <4A9799AC.8050109@it.uc3m.es> <2991246A29623A4082EB2B06A2B891A41B7C42ED57@EUSAACMS0703.eamcs.ericsson.se> <4A9C32D3.80106@it.uc3m.es>
Date: Wed, 2 Sep 2009 01:35:46 +0800
Message-ID: <25e1aaa40909011035t10239d69yebf422730a4bc00a@mail.gmail.com>
From: liu dapeng <maxpassion@gmail.com>
To: marcelo bagnulo braun <marcelo@it.uc3m.es>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Wassim Haddad <wassim.haddad@ericsson.com>, "behave@ietf.org" <behave@ietf.org>
Subject: Re: [BEHAVE] NAT64 and MIPv6
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/mail-archive/web/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>
X-List-Received-Date: Tue, 01 Sep 2009 17:35:40 -0000

2009/9/1, marcelo bagnulo braun <marcelo@it.uc3m.es>:
> Wassim Haddad escribi=F3:
>> Hi Marcelo,
>>
>> Thanks for the notes. Please see mine inline.
>>
>>
>>> I understand that the first point being made in the draft is that RO
>>> mode doesn't work through NAT64. I certainly agree with that and this
>>> was identified RFC 4966.
>>>
>>
>> =3D> OK
>>
>>
>>> During the requirement discussion, the input from the mobility communit=
y
>>> was that the support for the RO mode in nat64 was not critical and that
>>> it was acceptable to fall back to BT mode in case there is a NAT64 alon=
g
>>> the path. I am not sure if you agree with that.
>>>
>>
>> =3D> I don't think we have much choices here. The CN is an IPv4 node onl=
y so
>> it does not understand RO mode...
>>
>>
>>> In case you don't, it would be possible to overcome this by having the
>>> NAT64
>>> to terminate the RO procedure (i.e. that the NAT64 replies the RR
>>> signalling
>>> so that the path is optimized to the nat64, sicne it cannot be optimize=
d
>>> to the
>>>
>> CN).
>>
>> =3D> I see no problem with that. It should work fine if a MN starts a
>> session with a
>> CN while at home then moves to a foreign network (equipped with NAT64),
>> tries
>> RR and fails then stays with the BT mode.
>>
>>
>>> I think it would be possible to define the nat64 extensions needed for
>>> that.
>>>
>>
>> =3D> Agree.
>>
>>
>>> Then in your draft, you state that:
>>>
>>> In this case, the
>>> MN tunnels first its data packets to its HA without having them being
>>> intercepted by the foreign NAT64.  However, after reaching the HA,
>>> the data packets will most likely be dropped at some point.  This is
>>> due to the presence of the foreign NAT64 IPv6 prefix in the CN's IPv6
>>> address.
>>>
>>
>> I am not sure i understand that part. Are you saying that in case the MN
>> decides to move to RO mode things won't work anymore or are you saying
>> that data packets will be lost in BT mode?
>>
>> =3D> First, am sorry for a possible confusion! But you cut the first par=
t of
>> the
>> text! :)
>> What I meant is that when the MN moves to a foreign network and decides =
to
>>
>> initiate a new session with a v4 CN then:
>>
>> a) we can forget about RO mode here BUT this is not the problem.
>> b) the MN will try to reach the CN via BT mode but even in this case, it
>> will
>> ultimately fail because the packet won't reach the home NAT64 in order t=
o
>> get
>> translated (as it is using a different prefix).
>>
>
> ah!
> i think i understand what you mean.
>
> If the MN uses the dns64 from the visited network and the NAT64 from the
> home networks, things may break (if the WK prefix is not used)
Hi marcelo,

You mean WKP prfix?

BR,
Dapeng Liu

> please note that this is not a problem only in mip. for instance, if you
> are connected to the IETF network but you still use the DNS server at
> you work, then if there is a nat64 in the ietf meeting wifi, it would
> fail in the same way (this is actually the reverse situation, you are
> using the local nat64 and the remot dns64)
>
> The point is that you need to use the dns64 (i.e. the dns server) of the
> network that is running the nat64.
>
> Now, there are several ways to address this problem if you use the LIR
> prefix
>
> either you configure the MN to use the dns server from the home network,
> either you use the dns64 in stub resolver mode (i.e. in the MN)
>
>>
>>> If you are saying that the RO mode doesn't work, i agree with you as i
>>> mentioned above. If you are saying that data packets are lost in BT mod=
e
>>> (when RO mode is not used at all), that i don't understnad the scenario=
,
>>> and i would appreciate a figure to understand it better.
>>>
>>
>> =3D> Hope the above helps?
>>
>
> It does, if what i understood is correct
>
> As you say in the draft, NAT64 is a NAT, so we shouldn't be surprised if
> somethings break.
> This seems to be one of these cases.
>
> Maybe it would be important to explain this limitation in some of the
> the documents, not sure where though... suggestions?
>
> Regards, marcelo
>
>>
>> Regards,
>>
>> Wassim H.
>>
>>
>>
>
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>

From wassim.haddad@ericsson.com  Tue Sep  1 10:49:03 2009
Return-Path: <wassim.haddad@ericsson.com>
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 72DAE28C8E5 for <behave@core3.amsl.com>; Tue,  1 Sep 2009 10:49:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.576
X-Spam-Level: 
X-Spam-Status: No, score=-6.576 tagged_above=-999 required=5 tests=[AWL=0.023,  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 fDo7N-PL8Q0W for <behave@core3.amsl.com>; Tue,  1 Sep 2009 10:49:02 -0700 (PDT)
Received: from imr1.ericy.com (imr1.ericy.com [198.24.6.9]) by core3.amsl.com (Postfix) with ESMTP id 8E3BB3A7033 for <behave@ietf.org>; Tue,  1 Sep 2009 10:49:02 -0700 (PDT)
Received: from eusrcmw750.eamcs.ericsson.se (eusrcmw750.exu.ericsson.se [138.85.77.50]) by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id n81HnE5q021914; Tue, 1 Sep 2009 12:49:15 -0500
Received: from eusrcmw751.eamcs.ericsson.se ([138.85.77.51]) by eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 1 Sep 2009 12:48:46 -0500
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 1 Sep 2009 12:48:45 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.20]) by eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) with mapi; Tue, 1 Sep 2009 13:48:45 -0400
From: Wassim Haddad <wassim.haddad@ericsson.com>
To: "maxpassion@gmail.com" <maxpassion@gmail.com>
Date: Tue, 1 Sep 2009 13:48:43 -0400
Thread-Topic: [BEHAVE] NAT64 and MIPv6
Thread-Index: AcorKk2QB+P27WhwTNmND8RVRwdnRgAAeC9g
Message-ID: <2991246A29623A4082EB2B06A2B891A41B7C4942F9@EUSAACMS0703.eamcs.ericsson.se>
References: <2991246A29623A4082EB2B06A2B891A41B7C3D85A9@EUSAACMS0703.eamcs.ericsson.se> <25e1aaa40908310956m6f638a4x32dca4039b63b21d@mail.gmail.com> <2991246A29623A4082EB2B06A2B891A41B7C458E91@EUSAACMS0703.eamcs.ericsson.se> <25e1aaa40909011032t7f76e318i5b815a1d08995464@mail.gmail.com>
In-Reply-To: <25e1aaa40909011032t7f76e318i5b815a1d08995464@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 01 Sep 2009 17:48:45.0935 (UTC) FILETIME=[7411A7F0:01CA2B2C]
Cc: Wassim Haddad <wassim.haddad@ericsson.com>, "behave@ietf.org" <behave@ietf.org>
Subject: Re: [BEHAVE] NAT64 and MIPv6
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/mail-archive/web/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>
X-List-Received-Date: Tue, 01 Sep 2009 17:49:03 -0000

Hi,

-----Original Message-----
From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On Behalf Of=
 liu dapeng
Sent: Tuesday, September 01, 2009 11:32 AM
To: Wassim Haddad
Cc: behave@ietf.org
Subject: Re: [BEHAVE] NAT64 and MIPv6

> I am wondering where does the HA locate?   it locate in the IPv6
> network or in the IPv4 network?
>
> =3D> the home network is an IPv6 network which has its own NAT64 and DNS6=
4.
> Did I answer your question?

Then you mean the HA is located in the IPv6 netowrk

=3D> Which has its own NAT64 and DNS64.

if I understood it correctly, right?

=3D> That's correct.


Regards,

Wassim H.

From marcelo@it.uc3m.es  Tue Sep  1 11:12:22 2009
Return-Path: <marcelo@it.uc3m.es>
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 8F9383A6A4C for <behave@core3.amsl.com>; Tue,  1 Sep 2009 11:12:22 -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 4XREh58KXjwo for <behave@core3.amsl.com>; Tue,  1 Sep 2009 11:12:21 -0700 (PDT)
Received: from smtp03.uc3m.es (smtp03.uc3m.es [163.117.176.133]) by core3.amsl.com (Postfix) with ESMTP id 480C03A69ED for <behave@ietf.org>; Tue,  1 Sep 2009 11:12:20 -0700 (PDT)
Received: from marcelo-bagnulos-macbook-pro.local (203.pool85-53-144.dynamic.orange.es [85.53.144.203]) by smtp03.uc3m.es (Postfix) with ESMTP id 399D672D4F4; Tue,  1 Sep 2009 20:12:32 +0200 (CEST)
Message-ID: <4A9D640F.6040007@it.uc3m.es>
Date: Tue, 01 Sep 2009 20:12:31 +0200
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
User-Agent: Thunderbird 2.0.0.22 (Macintosh/20090605)
MIME-Version: 1.0
To: Cameron Byrne <cb.list6@gmail.com>
References: <C6C3552B.F1C0%hesham@elevatemobile.com>	 <4A9D2538.1090306@it.uc3m.es> <bcff0fba0909010712h374a1506i39bbca5652443843@mail.gmail.com>
In-Reply-To: <bcff0fba0909010712h374a1506i39bbca5652443843@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-TM-AS-Product-Ver: IMSS-7.0.0.3116-5.6.0.1016-16860.007
Cc: Wassim Haddad <wassim.haddad@ericsson.com>, Wassim Haddad <wmhaddad@gmail.com>, "behave@ietf.org" <behave@ietf.org>, Dave Thaler <dthaler@microsoft.com>, Hesham Soliman <hesham@elevatemobile.com>
Subject: Re: [BEHAVE] NAT64 and MIPv6
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/mail-archive/web/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>
X-List-Received-Date: Tue, 01 Sep 2009 18:12:22 -0000

Cameron Byrne escribió:
>> right, the problem is that there are 4 documents related to the mechanisms
>> involved int he problem, the dns64 one, the nat64 one, the doc defining the
>> prefixes, and the framework document....
>>     
>
> That said, is the best and most general solution to not make a
> statement about MIPv6, but to state that DNS64, NAT64, and prefix64
> all must be configured and managed as a single system.

mmm, the must is a bit too strong i think
if the WK prefix is being used, the dns64 and the nat64 can be in 
different admin domains and everything works just fine

>   Attempting to
> mix different elements from different management domains may result in
> unexpected behavior.   This is an operational assumption that i have
> had, but it may be best to codify it here so that there is no more
> confusion.
>   

i think the assumption is lighter than that i.e. that the nat64 and the 
dns64 use the same prefix, which in the LIR prefix is likely to be true 
in the case of a single admin domain, but in the WK prefix case is broader


From charliep@wichorus.com  Tue Sep  1 11:12:49 2009
Return-Path: <charliep@wichorus.com>
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 891A93A6B99 for <behave@core3.amsl.com>; Tue,  1 Sep 2009 11:12:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.98
X-Spam-Level: 
X-Spam-Status: No, score=-1.98 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zrJYlHdE+-79 for <behave@core3.amsl.com>; Tue,  1 Sep 2009 11:12:48 -0700 (PDT)
Received: from elasmtp-kukur.atl.sa.earthlink.net (elasmtp-kukur.atl.sa.earthlink.net [209.86.89.65]) by core3.amsl.com (Postfix) with ESMTP id AC05A3A6AF5 for <behave@ietf.org>; Tue,  1 Sep 2009 11:12:48 -0700 (PDT)
Received: from [12.204.153.98] (helo=[10.166.254.52]) by elasmtp-kukur.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <charliep@wichorus.com>) id 1MiXqm-0005sm-8i; Tue, 01 Sep 2009 14:13:00 -0400
Message-ID: <4A9D6424.2010007@wichorus.com>
Date: Tue, 01 Sep 2009 11:12:52 -0700
From: "Charles E. Perkins" <charliep@wichorus.com>
Organization: WiChorus Inc.
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Dave Thaler <dthaler@microsoft.com>
References: <E4561B14EE2A3E4E9D478EBFB5416E1B1C3163@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>	<C6C2C322.F191%hesham@elevatemobile.com>	<E4561B14EE2A3E4E9D478EBFB5416E1B1C389D@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>	<2991246A29623A4082EB2B06A2B891A41B7C4591FD@EUSAACMS0703.eamcs.ericsson.se> <E4561B14EE2A3E4E9D478EBFB5416E1B1C3AA8@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <E4561B14EE2A3E4E9D478EBFB5416E1B1C3AA8@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956abb457f1b4332f52d7d85bb3a977fc6ccc090480835e2d0c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 12.204.153.98
Cc: Wassim Haddad <wassim.haddad@ericsson.com>, "behave@ietf.org" <behave@ietf.org>, "hesham@elevatemobile.com" <hesham@elevatemobile.com>
Subject: Re: [BEHAVE] NAT64 and MIPv6
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/mail-archive/web/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>
X-List-Received-Date: Tue, 01 Sep 2009 18:12:49 -0000

Hello folks,

I disagree that this represents a defect in RFC 3775.
Mobile IPv6 is a network-layer protocol, and does not
depend in any way on DNS for its operation.

Now if, in the future, all IETF documents are required to
include a "Incompatible IP Address Domains Considerations"
section -- then in that case, I would agree that this problem
would then require a remedy in RFC 3775bisbisbisbis...

On the other hand, I would not oppose an appendix
describing the pitfalls.

On the third hand (or is that a foot?) any such discussion
about defects in Mobile IPv6 deserves to have at least
some visibility in the [mext] working group.  Doesn't
seem quite right for [behave] to quickly adopt a consensus
position without even asking about it in [mext].

Does someone want to contribute a problem report
against RFC 3775 on this issue?

Regards,
Charlie P.


Dave Thaler wrote:
> Yes.
>
>   
>> -----Original Message-----
>> From: Wassim Haddad [mailto:wassim.haddad@ericsson.com]
>> Sent: Tuesday, September 01, 2009 9:14 AM
>> To: Dave Thaler; hesham@elevatemobile.com
>> Cc: behave@ietf.org; Wassim Haddad
>> Subject: RE: [BEHAVE] NAT64 and MIPv6
>>
>>     
>>> At the very least any solution should highlight this as a requirement
>>> for MNs because 3775 doesn't limit the DNS queries to the home DNS.
>>> But I don't know how to do that if the presence of a NAT is not known
>>> to the host.
>>>       
>> I agree that 3775 is defective by not mentioning this, since again the
>> presence of a NAT does not introduce this problem... it already breaks
>> with private namespaces and 3775 should have pointed out how to make DNS
>> work.
>>
>> => Just to clarify: you mean RFC 3775 is defective by not mentioning that
>> "the MN should NOT rely on the DNS in the foreign network when using MIPv6
>> (i.e., its home address). Instead, it should/must rely on the home DNS".
>>
>> Is that correct?
>>
>>
>> Wassim H.
>>
>>     
>
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>   


From maxpassion@gmail.com  Tue Sep  1 11:20:06 2009
Return-Path: <maxpassion@gmail.com>
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 7ABEB3A7071 for <behave@core3.amsl.com>; Tue,  1 Sep 2009 11:20:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.113
X-Spam-Level: 
X-Spam-Status: No, score=-2.113 tagged_above=-999 required=5 tests=[AWL=0.486,  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 Wk0mA6OLH540 for <behave@core3.amsl.com>; Tue,  1 Sep 2009 11:20:05 -0700 (PDT)
Received: from mail-vw0-f177.google.com (mail-vw0-f177.google.com [209.85.212.177]) by core3.amsl.com (Postfix) with ESMTP id 94F5B3A6B99 for <behave@ietf.org>; Tue,  1 Sep 2009 11:20:05 -0700 (PDT)
Received: by vws7 with SMTP id 7so246957vws.29 for <behave@ietf.org>; Tue, 01 Sep 2009 11:20:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=cg7TV9cpdj4LwZOCa6hBSYM7w6CAhf5v/+khtTyB3gU=; b=OkHt9IJWdyLcVE0mc7FsJ9+RCgZzKcx+RkmSfHfPTXRtxDt40LtiBcA+KTIrcySEA+ b93swqfmfsB2fvRuEOEZbJdppr6Htj0oIChaMVlz27XROOvC1xr4iDboWlAxXccn0Ijn IkasExrvNQx15pc6uT6cVqCjdwx6jbnUoV3Dc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=J7SBh+jBVu7i6VAK8LZOG62gtcKxEJAp17gE3gk37PlLH5VfHW0d39/zN+oyvQnJLZ kNTr0i2NR6xh56+5+6dYJbRLlSR/mwHl1MbwbhgqbdxLXb4oD7HGZiAj4EfsPi1WL8AB fIEKaJWxc9k4AGqCIjg06Y5h5iMEbUAz+223Q=
MIME-Version: 1.0
Received: by 10.220.70.73 with SMTP id c9mr9147526vcj.33.1251829213739; Tue,  01 Sep 2009 11:20:13 -0700 (PDT)
In-Reply-To: <2991246A29623A4082EB2B06A2B891A41B7C4942F9@EUSAACMS0703.eamcs.ericsson.se>
References: <2991246A29623A4082EB2B06A2B891A41B7C3D85A9@EUSAACMS0703.eamcs.ericsson.se> <25e1aaa40908310956m6f638a4x32dca4039b63b21d@mail.gmail.com> <2991246A29623A4082EB2B06A2B891A41B7C458E91@EUSAACMS0703.eamcs.ericsson.se> <25e1aaa40909011032t7f76e318i5b815a1d08995464@mail.gmail.com> <2991246A29623A4082EB2B06A2B891A41B7C4942F9@EUSAACMS0703.eamcs.ericsson.se>
Date: Wed, 2 Sep 2009 02:20:13 +0800
Message-ID: <25e1aaa40909011120vd5d1830l108ed46c49f719@mail.gmail.com>
From: liu dapeng <maxpassion@gmail.com>
To: Wassim Haddad <wassim.haddad@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "behave@ietf.org" <behave@ietf.org>
Subject: Re: [BEHAVE] NAT64 and MIPv6
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/mail-archive/web/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>
X-List-Received-Date: Tue, 01 Sep 2009 18:20:06 -0000

Hi Wassim,

2009/9/2, Wassim Haddad <wassim.haddad@ericsson.com>:
> Hi,
>
> -----Original Message-----
> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On Behalf Of
> liu dapeng
> Sent: Tuesday, September 01, 2009 11:32 AM
> To: Wassim Haddad
> Cc: behave@ietf.org
> Subject: Re: [BEHAVE] NAT64 and MIPv6
>
>> I am wondering where does the HA locate?   it locate in the IPv6
>> network or in the IPv4 network?
>>
>> => the home network is an IPv6 network which has its own NAT64 and DNS64.
>> Did I answer your question?
>
> Then you mean the HA is located in the IPv6 netowrk
>
> => Which has its own NAT64 and DNS64.
>
> if I understood it correctly, right?
>
> => That's correct.

Do you consider the scenario that the HA is located in the IPv4
network that behind NAT64 which may be DSMIP case?

Best Regards,
Dapeng Liu


>
> Regards,
>
> Wassim H.
>

From marcelo@it.uc3m.es  Tue Sep  1 11:21:08 2009
Return-Path: <marcelo@it.uc3m.es>
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 1E7B83A706C for <behave@core3.amsl.com>; Tue,  1 Sep 2009 11:21:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.506
X-Spam-Level: 
X-Spam-Status: No, score=-6.506 tagged_above=-999 required=5 tests=[AWL=0.093,  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 1THNkezax-Ph for <behave@core3.amsl.com>; Tue,  1 Sep 2009 11:21:07 -0700 (PDT)
Received: from smtp03.uc3m.es (smtp03.uc3m.es [163.117.176.133]) by core3.amsl.com (Postfix) with ESMTP id C9BA23A6A82 for <behave@ietf.org>; Tue,  1 Sep 2009 11:21:06 -0700 (PDT)
Received: from marcelo-bagnulos-macbook-pro.local (203.pool85-53-144.dynamic.orange.es [85.53.144.203]) by smtp03.uc3m.es (Postfix) with ESMTP id 7FC107F26F6; Tue,  1 Sep 2009 20:21:17 +0200 (CEST)
Message-ID: <4A9D661C.1030604@it.uc3m.es>
Date: Tue, 01 Sep 2009 20:21:16 +0200
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
User-Agent: Thunderbird 2.0.0.22 (Macintosh/20090605)
MIME-Version: 1.0
To: liu dapeng <maxpassion@gmail.com>
References: <2991246A29623A4082EB2B06A2B891A41B7C3D85A9@EUSAACMS0703.eamcs.ericsson.se>	 <4A9799AC.8050109@it.uc3m.es>	 <2991246A29623A4082EB2B06A2B891A41B7C42ED57@EUSAACMS0703.eamcs.ericsson.se>	 <4A9C32D3.80106@it.uc3m.es> <25e1aaa40909011035t10239d69yebf422730a4bc00a@mail.gmail.com>
In-Reply-To: <25e1aaa40909011035t10239d69yebf422730a4bc00a@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-TM-AS-Product-Ver: IMSS-7.0.0.3116-5.6.0.1016-16860.007
Cc: Wassim Haddad <wassim.haddad@ericsson.com>, "behave@ietf.org" <behave@ietf.org>
Subject: Re: [BEHAVE] NAT64 and MIPv6
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/mail-archive/web/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>
X-List-Received-Date: Tue, 01 Sep 2009 18:21:08 -0000

liu dapeng escribió:
> 2009/9/1, marcelo bagnulo braun <marcelo@it.uc3m.es>:
>   
>> Wassim Haddad escribió:
>>     
>>> Hi Marcelo,
>>>
>>> Thanks for the notes. Please see mine inline.
>>>
>>>
>>>       
>>>> I understand that the first point being made in the draft is that RO
>>>> mode doesn't work through NAT64. I certainly agree with that and this
>>>> was identified RFC 4966.
>>>>
>>>>         
>>> => OK
>>>
>>>
>>>       
>>>> During the requirement discussion, the input from the mobility community
>>>> was that the support for the RO mode in nat64 was not critical and that
>>>> it was acceptable to fall back to BT mode in case there is a NAT64 along
>>>> the path. I am not sure if you agree with that.
>>>>
>>>>         
>>> => I don't think we have much choices here. The CN is an IPv4 node only so
>>> it does not understand RO mode...
>>>
>>>
>>>       
>>>> In case you don't, it would be possible to overcome this by having the
>>>> NAT64
>>>> to terminate the RO procedure (i.e. that the NAT64 replies the RR
>>>> signalling
>>>> so that the path is optimized to the nat64, sicne it cannot be optimized
>>>> to the
>>>>
>>>>         
>>> CN).
>>>
>>> => I see no problem with that. It should work fine if a MN starts a
>>> session with a
>>> CN while at home then moves to a foreign network (equipped with NAT64),
>>> tries
>>> RR and fails then stays with the BT mode.
>>>
>>>
>>>       
>>>> I think it would be possible to define the nat64 extensions needed for
>>>> that.
>>>>
>>>>         
>>> => Agree.
>>>
>>>
>>>       
>>>> Then in your draft, you state that:
>>>>
>>>> In this case, the
>>>> MN tunnels first its data packets to its HA without having them being
>>>> intercepted by the foreign NAT64.  However, after reaching the HA,
>>>> the data packets will most likely be dropped at some point.  This is
>>>> due to the presence of the foreign NAT64 IPv6 prefix in the CN's IPv6
>>>> address.
>>>>
>>>>         
>>> I am not sure i understand that part. Are you saying that in case the MN
>>> decides to move to RO mode things won't work anymore or are you saying
>>> that data packets will be lost in BT mode?
>>>
>>> => First, am sorry for a possible confusion! But you cut the first part of
>>> the
>>> text! :)
>>> What I meant is that when the MN moves to a foreign network and decides to
>>>
>>> initiate a new session with a v4 CN then:
>>>
>>> a) we can forget about RO mode here BUT this is not the problem.
>>> b) the MN will try to reach the CN via BT mode but even in this case, it
>>> will
>>> ultimately fail because the packet won't reach the home NAT64 in order to
>>> get
>>> translated (as it is using a different prefix).
>>>
>>>       
>> ah!
>> i think i understand what you mean.
>>
>> If the MN uses the dns64 from the visited network and the NAT64 from the
>> home networks, things may break (if the WK prefix is not used)
>>     
> Hi marcelo,
>
> You mean WKP prfix?
>   

i mean the WK prefix
> BR,
> Dapeng Liu
>
>   
>> please note that this is not a problem only in mip. for instance, if you
>> are connected to the IETF network but you still use the DNS server at
>> you work, then if there is a nat64 in the ietf meeting wifi, it would
>> fail in the same way (this is actually the reverse situation, you are
>> using the local nat64 and the remot dns64)
>>
>> The point is that you need to use the dns64 (i.e. the dns server) of the
>> network that is running the nat64.
>>
>> Now, there are several ways to address this problem if you use the LIR
>> prefix
>>
>> either you configure the MN to use the dns server from the home network,
>> either you use the dns64 in stub resolver mode (i.e. in the MN)
>>
>>     
>>>> If you are saying that the RO mode doesn't work, i agree with you as i
>>>> mentioned above. If you are saying that data packets are lost in BT mode
>>>> (when RO mode is not used at all), that i don't understnad the scenario,
>>>> and i would appreciate a figure to understand it better.
>>>>
>>>>         
>>> => Hope the above helps?
>>>
>>>       
>> It does, if what i understood is correct
>>
>> As you say in the draft, NAT64 is a NAT, so we shouldn't be surprised if
>> somethings break.
>> This seems to be one of these cases.
>>
>> Maybe it would be important to explain this limitation in some of the
>> the documents, not sure where though... suggestions?
>>
>> Regards, marcelo
>>
>>     
>>> Regards,
>>>
>>> Wassim H.
>>>
>>>
>>>
>>>       
>> _______________________________________________
>> Behave mailing list
>> Behave@ietf.org
>> https://www.ietf.org/mailman/listinfo/behave
>>
>>     
>
>   


From dthaler@microsoft.com  Tue Sep  1 11:30:13 2009
Return-Path: <dthaler@microsoft.com>
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 ECB4E3A7075 for <behave@core3.amsl.com>; Tue,  1 Sep 2009 11:30:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.45
X-Spam-Level: 
X-Spam-Status: No, score=-10.45 tagged_above=-999 required=5 tests=[AWL=0.149,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ty+bQs5fLSf7 for <behave@core3.amsl.com>; Tue,  1 Sep 2009 11:30:09 -0700 (PDT)
Received: from smtp.microsoft.com (mailb.microsoft.com [131.107.115.215]) by core3.amsl.com (Postfix) with ESMTP id 17A9128C8EA for <behave@ietf.org>; Tue,  1 Sep 2009 11:30:09 -0700 (PDT)
Received: from TK5EX14HUBC101.redmond.corp.microsoft.com (157.54.7.153) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.176.0; Tue, 1 Sep 2009 11:30:21 -0700
Received: from TK5EX14MLTW651.wingroup.windeploy.ntdev.microsoft.com (157.54.71.39) by TK5EX14HUBC101.redmond.corp.microsoft.com (157.54.7.153) with Microsoft SMTP Server id 14.0.639.13; Tue, 1 Sep 2009 11:30:21 -0700
Received: from TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com ([169.254.3.25]) by TK5EX14MLTW651.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.39]) with mapi; Tue, 1 Sep 2009 11:30:33 -0700
From: Dave Thaler <dthaler@microsoft.com>
To: "Charles E. Perkins" <charliep@wichorus.com>
Thread-Topic: [BEHAVE] NAT64 and MIPv6
Thread-Index: AQHKKHuIwEJcSog/t0mWiJZwt4jxx5C//1+AgAEYr4D//60LwIAAl/4A//+c3CCAAAvsuIAA2JvwgAAN9/CAAAGkEIAAlfAA//+OJTA=
Date: Tue, 1 Sep 2009 18:30:18 +0000
Message-ID: <E4561B14EE2A3E4E9D478EBFB5416E1B1C50A4@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
References: <E4561B14EE2A3E4E9D478EBFB5416E1B1C3163@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <C6C2C322.F191%hesham@elevatemobile.com> <E4561B14EE2A3E4E9D478EBFB5416E1B1C389D@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <2991246A29623A4082EB2B06A2B891A41B7C4591FD@EUSAACMS0703.eamcs.ericsson.se> <E4561B14EE2A3E4E9D478EBFB5416E1B1C3AA8@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <4A9D6424.2010007@wichorus.com>
In-Reply-To: <4A9D6424.2010007@wichorus.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Wassim Haddad <wassim.haddad@ericsson.com>, "behave@ietf.org" <behave@ietf.org>, "hesham@elevatemobile.com" <hesham@elevatemobile.com>
Subject: Re: [BEHAVE] NAT64 and MIPv6
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/mail-archive/web/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>
X-List-Received-Date: Tue, 01 Sep 2009 18:30:13 -0000

> -----Original Message-----
> From: Charles E. Perkins [mailto:charliep@wichorus.com]
> Sent: Tuesday, September 01, 2009 11:13 AM
> To: Dave Thaler
> Cc: Wassim Haddad; hesham@elevatemobile.com; behave@ietf.org
> Subject: Re: [BEHAVE] NAT64 and MIPv6
>
>
> Hello folks,
>
> I disagree that this represents a defect in RFC 3775.
> Mobile IPv6 is a network-layer protocol, and does not
> depend in any way on DNS for its operation.

IPv6 is a network-layer protocol and does not depend
in any way on upper-layer protocols for its operation,
but RFC 2460 contains section 8 "upper-layer protocol issues".

> Now if, in the future, all IETF documents are required to
> include a "Incompatible IP Address Domains Considerations"
> section -- then in that case, I would agree that this problem
> would then require a remedy in RFC 3775bisbisbisbis...
>
> On the other hand, I would not oppose an appendix
> describing the pitfalls.

That's along the lines of what I was referring to yes.

> On the third hand (or is that a foot?) any such discussion
> about defects in Mobile IPv6 deserves to have at least
> some visibility in the [mext] working group.  Doesn't
> seem quite right for [behave] to quickly adopt a consensus
> position without even asking about it in [mext].

I don't know why you're referring to a [behave]
consensus position.  I already stated in the thread
that such a document belongs in a MIP related WG not
in Behave.  Perhaps you missed that.

-Dave

From cb.list6@gmail.com  Tue Sep  1 11:35:04 2009
Return-Path: <cb.list6@gmail.com>
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 CF6FC28C934 for <behave@core3.amsl.com>; Tue,  1 Sep 2009 11:35:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.569
X-Spam-Level: 
X-Spam-Status: No, score=-2.569 tagged_above=-999 required=5 tests=[AWL=0.030,  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 WxCPMlwZYAsM for <behave@core3.amsl.com>; Tue,  1 Sep 2009 11:35:02 -0700 (PDT)
Received: from mail-yw0-f174.google.com (mail-yw0-f174.google.com [209.85.211.174]) by core3.amsl.com (Postfix) with ESMTP id 5995C28C93A for <behave@ietf.org>; Tue,  1 Sep 2009 11:32:04 -0700 (PDT)
Received: by ywh4 with SMTP id 4so298695ywh.17 for <behave@ietf.org>; Tue, 01 Sep 2009 11:32:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=oMUs2bl5W/525YVjOoo2812WtnMcchV+Ot4yAQcZkPk=; b=dRSOVT33qKiQ10ATaDsRfdc9IWuFNZi1Iur99kPYIEyJWCx0dmSvUNR5JKcBCzaJJa iSgUQ3OTneqeu93x49vJHsYrDbC0gbVxuX2DZYf8ej80HqIsQdZoEqMUJMtjEber50yv z4PctfaV19ngxWmeZa68wYVHg1Z+1V0EeDeYk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=gAjTx+zArxEITzl+2k/KUFjP4ZpdUOrWiFXmBCzDcDoiWtzPy+wRK7Irv6CYvnt1WU sxb98cNRpPvG2BjVdkYoQ4T/W/1t/mtuRvQuotVn+poe9bQSrEdhWaLHThWmv1FZ5uJ5 QcM1K74Eqnx4FA2YzntWp7O90QfAtqhIhCizU=
MIME-Version: 1.0
Received: by 10.151.28.10 with SMTP id f10mr10907103ybj.323.1251829934121;  Tue, 01 Sep 2009 11:32:14 -0700 (PDT)
In-Reply-To: <4A9D640F.6040007@it.uc3m.es>
References: <C6C3552B.F1C0%hesham@elevatemobile.com> <4A9D2538.1090306@it.uc3m.es> <bcff0fba0909010712h374a1506i39bbca5652443843@mail.gmail.com> <4A9D640F.6040007@it.uc3m.es>
Date: Tue, 1 Sep 2009 11:32:13 -0700
Message-ID: <bcff0fba0909011132gb2180e0q66ad51bc9281d87a@mail.gmail.com>
From: Cameron Byrne <cb.list6@gmail.com>
To: marcelo bagnulo braun <marcelo@it.uc3m.es>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Wassim Haddad <wassim.haddad@ericsson.com>, Wassim Haddad <wmhaddad@gmail.com>, "behave@ietf.org" <behave@ietf.org>, Dave Thaler <dthaler@microsoft.com>, Hesham Soliman <hesham@elevatemobile.com>
Subject: Re: [BEHAVE] NAT64 and MIPv6
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/mail-archive/web/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>
X-List-Received-Date: Tue, 01 Sep 2009 18:35:04 -0000

On Tue, Sep 1, 2009 at 11:12 AM, marcelo bagnulo
braun<marcelo@it.uc3m.es> wrote:
> Cameron Byrne escribi=F3:
>>>
>>> right, the problem is that there are 4 documents related to the
>>> mechanisms
>>> involved int he problem, the dns64 one, the nat64 one, the doc defining
>>> the
>>> prefixes, and the framework document....
>>>
>>
>> That said, is the best and most general solution to not make a
>> statement about MIPv6, but to state that DNS64, NAT64, and prefix64
>> all must be configured and managed as a single system.
>
> mmm, the must is a bit too strong i think

I have know issues with making the language weaker.

> if the WK prefix is being used, the dns64 and the nat64 can be in differe=
nt
> admin domains and everything works just fine

For my deployment scenario, i don't think the WK prefix is a good
option so i don't like to to engineer around it.

draft-miyata-behave-prefix64-02 covers some of the issues, but i
believe this text should also have covered that the WK prefix does not
lend itself well to load balancing across many NAT64 systems.  I would
like my DNS64 system to hand out different prefix64 based on loading
and resiliency, even if the DNS64 can round-robin prefix64 it allows
me to scale the NAT64 state and connections per second across many
systems.   This may be off topic for this thread, but this is the
reasoning why i think WK prefix is weaker than just using LIR
addressing.

Cameron


>
>> =A0Attempting to
>> mix different elements from different management domains may result in
>> unexpected behavior. =A0 This is an operational assumption that i have
>> had, but it may be best to codify it here so that there is no more
>> confusion.
>>
>
> i think the assumption is lighter than that i.e. that the nat64 and the
> dns64 use the same prefix, which in the LIR prefix is likely to be true i=
n
> the case of a single admin domain, but in the WK prefix case is broader
>
>

From charliep@wichorus.com  Tue Sep  1 11:35:42 2009
Return-Path: <charliep@wichorus.com>
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 6E33B28C944 for <behave@core3.amsl.com>; Tue,  1 Sep 2009 11:35:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.98
X-Spam-Level: 
X-Spam-Status: No, score=-1.98 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YmSm8edPT1dw for <behave@core3.amsl.com>; Tue,  1 Sep 2009 11:35:38 -0700 (PDT)
Received: from elasmtp-mealy.atl.sa.earthlink.net (elasmtp-mealy.atl.sa.earthlink.net [209.86.89.69]) by core3.amsl.com (Postfix) with ESMTP id 59F1728C935 for <behave@ietf.org>; Tue,  1 Sep 2009 11:35:00 -0700 (PDT)
Received: from [12.204.153.98] (helo=[10.166.254.52]) by elasmtp-mealy.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <charliep@wichorus.com>) id 1MiYC5-0005No-RS; Tue, 01 Sep 2009 14:35:01 -0400
Message-ID: <4A9D6950.8020501@wichorus.com>
Date: Tue, 01 Sep 2009 11:34:56 -0700
From: "Charles E. Perkins" <charliep@wichorus.com>
Organization: WiChorus Inc.
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Dave Thaler <dthaler@microsoft.com>
References: <E4561B14EE2A3E4E9D478EBFB5416E1B1C3163@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>	<C6C2C322.F191%hesham@elevatemobile.com>	<E4561B14EE2A3E4E9D478EBFB5416E1B1C389D@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>	<2991246A29623A4082EB2B06A2B891A41B7C4591FD@EUSAACMS0703.eamcs.ericsson.se> <E4561B14EE2A3E4E9D478EBFB5416E1B1C3AA8@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <4A9D6424.2010007@wichorus.com> <E4561B14EE2A3E4E9D478EBFB5416E1B1C50A4@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <E4561B14EE2A3E4E9D478EBFB5416E1B1C50A4@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956abb457f1b4332f5299c0aaf95d0d083e9b11155c274e21be350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 12.204.153.98
Cc: "behave@ietf.org" <behave@ietf.org>
Subject: Re: [BEHAVE] NAT64 and MIPv6
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/mail-archive/web/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>
X-List-Received-Date: Tue, 01 Sep 2009 18:35:42 -0000

Hello Dave,

Yes, I did miss the email where you said that.
I thought I'd read through all thousand of them,
but now I see there are more :-)  And, my
suggestion of a [behave] consensus was
purely hypothetical and not based on any
formal position, but instead only on what
I had read from the previous emails.

Regards,
Charlie P.


Dave Thaler wrote:
>
>> On the third hand (or is that a foot?) any such discussion
>> about defects in Mobile IPv6 deserves to have at least
>> some visibility in the [mext] working group.  Doesn't
>> seem quite right for [behave] to quickly adopt a consensus
>> position without even asking about it in [mext].
>>     
>
> I don't know why you're referring to a [behave]
> consensus position.  I already stated in the thread
> that such a document belongs in a MIP related WG not
> in Behave.  Perhaps you missed that.
>
> -Dave
>   


From maxpassion@gmail.com  Tue Sep  1 11:47:12 2009
Return-Path: <maxpassion@gmail.com>
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 E9C4B28C93E for <behave@core3.amsl.com>; Tue,  1 Sep 2009 11:47:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.129
X-Spam-Level: 
X-Spam-Status: No, score=-2.129 tagged_above=-999 required=5 tests=[AWL=0.470,  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 FNPxVPw6MYeJ for <behave@core3.amsl.com>; Tue,  1 Sep 2009 11:47:12 -0700 (PDT)
Received: from mail-vw0-f177.google.com (mail-vw0-f177.google.com [209.85.212.177]) by core3.amsl.com (Postfix) with ESMTP id 15E5F3A6A6C for <behave@ietf.org>; Tue,  1 Sep 2009 11:47:09 -0700 (PDT)
Received: by vws7 with SMTP id 7so269032vws.29 for <behave@ietf.org>; Tue, 01 Sep 2009 11:47:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=2HV7ECnWYxNXQsyOyJW2yPqt5vnhcmDSPNtpakmZ09c=; b=K4mVPX7BMh0JeT1/Qm6wQZxcIgQX5tAIFmTkYMtzHNlNknXIespsbNn8N3lESeVjB8 kjOTsQ+UM0pZWf+3fw3j88efxvu9cbaF4LjRUQFmBTwtf6NlYcA6mKxuOW12GXI2efGM nla3usK7nUf/agZzvBGTdnpAEOAlk9ITWNdPc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=GmOqZIPN/EZojvdflq02QaC5WtHyteu0VOKtPRHTqMeNQaHLXiT0xk3Q2ADa7Bj+kM 8dZv0RCLdL6O0uFunO93wShneWWE6MaihznJIjvBv/hMMlghqC7nN0QBTwJkaLNbbatH oF9CNcX4sad2RT+arktOJpoduWmX6O1uvAJzw=
MIME-Version: 1.0
Received: by 10.220.107.227 with SMTP id c35mr9114907vcp.0.1251830414450; Tue,  01 Sep 2009 11:40:14 -0700 (PDT)
In-Reply-To: <4A9D661C.1030604@it.uc3m.es>
References: <2991246A29623A4082EB2B06A2B891A41B7C3D85A9@EUSAACMS0703.eamcs.ericsson.se> <4A9799AC.8050109@it.uc3m.es> <2991246A29623A4082EB2B06A2B891A41B7C42ED57@EUSAACMS0703.eamcs.ericsson.se> <4A9C32D3.80106@it.uc3m.es> <25e1aaa40909011035t10239d69yebf422730a4bc00a@mail.gmail.com> <4A9D661C.1030604@it.uc3m.es>
Date: Wed, 2 Sep 2009 02:40:14 +0800
Message-ID: <25e1aaa40909011140i96f7ee7ma698b7b16ba5fbb@mail.gmail.com>
From: liu dapeng <maxpassion@gmail.com>
To: marcelo bagnulo braun <marcelo@it.uc3m.es>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Wassim Haddad <wassim.haddad@ericsson.com>, "behave@ietf.org" <behave@ietf.org>
Subject: Re: [BEHAVE] NAT64 and MIPv6
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/mail-archive/web/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>
X-List-Received-Date: Tue, 01 Sep 2009 18:47:13 -0000

2009/9/2, marcelo bagnulo braun <marcelo@it.uc3m.es>:
>
>
>
> liu dapeng escribi=F3:
>> 2009/9/1, marcelo bagnulo braun <marcelo@it.uc3m.es>:
>>
>>> Wassim Haddad escribi=F3:
>>>
>>>> Hi Marcelo,
>>>>
>>>> Thanks for the notes. Please see mine inline.
>>>>
>>>>
>>>>
>>>>> I understand that the first point being made in the draft is that RO
>>>>> mode doesn't work through NAT64. I certainly agree with that and this
>>>>> was identified RFC 4966.
>>>>>
>>>>>
>>>> =3D> OK
>>>>
>>>>
>>>>
>>>>> During the requirement discussion, the input from the mobility
>>>>> community
>>>>> was that the support for the RO mode in nat64 was not critical and th=
at
>>>>> it was acceptable to fall back to BT mode in case there is a NAT64
>>>>> along
>>>>> the path. I am not sure if you agree with that.
>>>>>
>>>>>
>>>> =3D> I don't think we have much choices here. The CN is an IPv4 node o=
nly
>>>> so
>>>> it does not understand RO mode...
>>>>
>>>>
>>>>
>>>>> In case you don't, it would be possible to overcome this by having th=
e
>>>>> NAT64
>>>>> to terminate the RO procedure (i.e. that the NAT64 replies the RR
>>>>> signalling
>>>>> so that the path is optimized to the nat64, sicne it cannot be
>>>>> optimized
>>>>> to the
>>>>>
>>>>>
>>>> CN).
>>>>
>>>> =3D> I see no problem with that. It should work fine if a MN starts a
>>>> session with a
>>>> CN while at home then moves to a foreign network (equipped with NAT64)=
,
>>>> tries
>>>> RR and fails then stays with the BT mode.
>>>>
>>>>
>>>>
>>>>> I think it would be possible to define the nat64 extensions needed fo=
r
>>>>> that.
>>>>>
>>>>>
>>>> =3D> Agree.
>>>>
>>>>
>>>>
>>>>> Then in your draft, you state that:
>>>>>
>>>>> In this case, the
>>>>> MN tunnels first its data packets to its HA without having them being
>>>>> intercepted by the foreign NAT64.  However, after reaching the HA,
>>>>> the data packets will most likely be dropped at some point.  This is
>>>>> due to the presence of the foreign NAT64 IPv6 prefix in the CN's IPv6
>>>>> address.
>>>>>
>>>>>
>>>> I am not sure i understand that part. Are you saying that in case the =
MN
>>>> decides to move to RO mode things won't work anymore or are you saying
>>>> that data packets will be lost in BT mode?
>>>>
>>>> =3D> First, am sorry for a possible confusion! But you cut the first p=
art
>>>> of
>>>> the
>>>> text! :)
>>>> What I meant is that when the MN moves to a foreign network and decide=
s
>>>> to
>>>>
>>>> initiate a new session with a v4 CN then:
>>>>
>>>> a) we can forget about RO mode here BUT this is not the problem.
>>>> b) the MN will try to reach the CN via BT mode but even in this case, =
it
>>>> will
>>>> ultimately fail because the packet won't reach the home NAT64 in order
>>>> to
>>>> get
>>>> translated (as it is using a different prefix).
>>>>
>>>>
>>> ah!
>>> i think i understand what you mean.
>>>
>>> If the MN uses the dns64 from the visited network and the NAT64 from th=
e
>>> home networks, things may break (if the WK prefix is not used)
>>>
>> Hi marcelo,
>>
>> You mean WKP prfix?
>>
>
> i mean the WK prefix

thanks marcelo, I think we mean the same thing here:)




>> BR,
>> Dapeng Liu
>>
>>
>>> please note that this is not a problem only in mip. for instance, if yo=
u
>>> are connected to the IETF network but you still use the DNS server at
>>> you work, then if there is a nat64 in the ietf meeting wifi, it would
>>> fail in the same way (this is actually the reverse situation, you are
>>> using the local nat64 and the remot dns64)
>>>
>>> The point is that you need to use the dns64 (i.e. the dns server) of th=
e
>>> network that is running the nat64.
>>>
>>> Now, there are several ways to address this problem if you use the LIR
>>> prefix
>>>
>>> either you configure the MN to use the dns server from the home network=
,
>>> either you use the dns64 in stub resolver mode (i.e. in the MN)
>>>
>>>
>>>>> If you are saying that the RO mode doesn't work, i agree with you as =
i
>>>>> mentioned above. If you are saying that data packets are lost in BT
>>>>> mode
>>>>> (when RO mode is not used at all), that i don't understnad the
>>>>> scenario,
>>>>> and i would appreciate a figure to understand it better.
>>>>>
>>>>>
>>>> =3D> Hope the above helps?
>>>>
>>>>
>>> It does, if what i understood is correct
>>>
>>> As you say in the draft, NAT64 is a NAT, so we shouldn't be surprised i=
f
>>> somethings break.
>>> This seems to be one of these cases.
>>>
>>> Maybe it would be important to explain this limitation in some of the
>>> the documents, not sure where though... suggestions?
>>>
>>> Regards, marcelo
>>>
>>>
>>>> Regards,
>>>>
>>>> Wassim H.
>>>>
>>>>
>>>>
>>>>
>>> _______________________________________________
>>> Behave mailing list
>>> Behave@ietf.org
>>> https://www.ietf.org/mailman/listinfo/behave
>>>
>>>
>>
>>
>
>

From rpenno@juniper.net  Tue Sep  1 11:49:31 2009
Return-Path: <rpenno@juniper.net>
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 EB9DE3A7076 for <behave@core3.amsl.com>; Tue,  1 Sep 2009 11:49:31 -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 qQ8Vgm00FBGi for <behave@core3.amsl.com>; Tue,  1 Sep 2009 11:49:30 -0700 (PDT)
Received: from exprod7og120.obsmtp.com (exprod7og120.obsmtp.com [64.18.2.18]) by core3.amsl.com (Postfix) with ESMTP id 42CD23A7073 for <behave@ietf.org>; Tue,  1 Sep 2009 11:49:27 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob120.postini.com ([64.18.6.12]) with SMTP ID DSNKSp1svS9ynF08dR5BHgptutvylQ2dXP5g@postini.com; Tue, 01 Sep 2009 11:49:44 PDT
Received: from p-emfe01-wf.jnpr.net (172.28.145.24) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.1.375.2; Tue, 1 Sep 2009 11:47:57 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe01-wf.jnpr.net ([fe80::d0d1:653d:5b91:a123%11]) with mapi; Tue, 1 Sep 2009 14:47:57 -0400
From: Reinaldo Penno <rpenno@juniper.net>
To: Dan Wing <dwing@cisco.com>, marcelo bagnulo braun <marcelo@it.uc3m.es>
Date: Tue, 1 Sep 2009 14:47:55 -0400
Thread-Topic: NAT64 and TCP processing (was Re: [BEHAVE] Comments todraft-ietf-behave-v6v4-xlate-stateful-01.txt)
Thread-Index: AcoFHpFlgJpcPdYdRO6zyzbH45axGgAY79wwCWyZqWU=
Message-ID: <C6C2BA6B.36875%rpenno@juniper.net>
In-Reply-To: <128401ca0583$480210b0$c4f0200a@cisco.com>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Behave WG <behave@ietf.org>
Subject: [BEHAVE] NAT64 and TCP processing (was Re: Comments todraft-ietf-behave-v6v4-xlate-stateful-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/mail-archive/web/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>
X-List-Received-Date: Tue, 01 Sep 2009 18:49:32 -0000

Hello,

I read the paper reference by Dan below and the number of TCP connections
that end with TCP RST is significant.

> Martin Arlitt, Carey Williamson, "An Analysis of TCP Reset Behaviour on t=
he
> Internet", October, 2004,
> http://pages.cpsc.ucalgary.ca/~carey/papers/2005/TCP-Resets.pdf

Also, there is this draft which is categorized as standards track and talks
about the many issues related to TCP window attacks and most of the
mitigations discussed require TCP sequence tracking.

http://www.ietf.org/id/draft-ietf-tcpm-tcpsecure-11.txt

The issues found here are not exclusive of NAT64, NAT44 would suffer the
same problems. But most NAT44 implementations today already track sequence
numbers whether due to security concerns or ALGs.

Thanks,

Reinaldo

On 7/15/09 12:34 PM, "Dan Wing" <dwing@cisco.com> wrote:

>=20
>=20
>> -----Original Message-----
>> From: behave-bounces@ietf.org
>> [mailto:behave-bounces@ietf.org] On Behalf Of marcelo bagnulo braun
>> Sent: Wednesday, July 15, 2009 12:31 AM
>> To: Reinaldo Penno
>> Cc: Behave WG
>> Subject: Re: [BEHAVE] Comments
>> todraft-ietf-behave-v6v4-xlate-stateful-01.txt
>>=20
>> Reinaldo Penno escribi=F3:
>>>=20
>>> On 7/14/09 9:30 AM, "marcelo bagnulo braun"
>> <marcelo@it.uc3m.es> wrote:
>>>=20
>>> =20
>>>> Reinaldo Penno escribi=F3:
>>>>   =20
>>>>> Hello,
>>>>>=20
>>>>> we should include how to handle TCP RSTs as well. Host
>> implementations and
>>>>> NATs might remove the tcpb (or binding) as soon as a RST
>> is received (as
>>>>> long as seq number checking passes).
>>>>>=20
>>>>>     =20
>>>> but that would imply to keep track of all the seq # for
>> all the data
>>>> packets for each of the flows....
>>>> I don't think i would like to go there.
>>>>=20
>>>> In order to handle the RST packets, actually, i had
>> thought of that and
>>>> i included in the state machines, but it seems i forgot to
>> include in
>>>> the text...
>>>>=20
>>>> I think a RST coming from the Internet part should be
>> ignored, cause as
>>>> you say may be an attack, but i think that if the rst
>> packet comes from
>>>> the network side (the network that runs the nat64) then it
>> should be
>>>> honnoured.
>>>>   =20
>>>=20
>>> After the connection is established, and the v4 side sends
>> a RST to end the
>>> connection and we do not honor it we will have hanging TCP
>> bindings. This is
>>> exactly what we were trying to avoid by being diligent on following
>>> FINs/ACKs and having timeouts.
>>=20
>> right, i guess the question is how often this happens.
>=20
> Martin Arlitt, Carey Williamson, "An Analysis of TCP Reset Behaviour on t=
he
> Internet", October, 2004,
> http://pages.cpsc.ucalgary.ca/~carey/papers/2005/TCP-Resets.pdf
>=20
> -d
>=20
>> I like Iljitshc suggestion of reducing the lifetime of the
>> binding when
>> a RST is seen, what do you think about that?
>>=20
>>> A TCP connection ended by RST is reused pretty quickly and
>> the issue I see
>>> if we do not honor valid TCP RST it is that we can end up
>> reusing a old
>>> binding and all kinds of problems can exist.
>>> =20
>>=20
>> I fail to see any problem here. I mean, if the new connection
>> uses the
>> same 5 tuple, then the state can be reused wihtout problem and if it
>> doesn't, then a new binding will be created, what is the problem that
>> you see?
>>> On the other hand, spoofed TCP packets can end the
>> connection and there are
>>> specific seq checks needed (different from connecting state
>> from established
>>> state).
>>>=20
>>> =20
>>=20
>> right, this is my concern
>>=20
>>>> what do you think?
>>>>   =20
>>>=20
>>> =20
>>>>> Here, I think checking seq numbers is important for
>> security sake, specially
>>>>> in the case of TCP RSTs.
>>>>>=20
>>>>> As far as ICMP response to unsolicited SYNs which we
>> discussed before I
>>>>> suggest the following amendment to your text
>>>>>=20
>>>>> From
>>>>>=20
>>>>> "      If the destination transport address contained in
>> the incoming V4
>>>>>       SYN is not in use in the TCP BIB, then the packet
>> is discarded and
>>>>>       an ICMP Port Unreachable error (Type 3, Code 3) is
>> sent back to
>>>>>       the source of the v4 SYN.  The state remains
>> unchanged in CLOSED"
>>>>>=20
>>>>> To
>>>>>=20
>>>>> "      If the destination transport address contained in
>> the incoming V4
>>>>>       SYN is not in use in the TCP BIB, then the packet
>> is discarded and
>>>>>       an ICMP Port Unreachable error (Type 3, Code 3) is
>> sent back to
>>>>>       the source of the v4 SYN unless REQ-4a of RFC5382
>> applies.  The state
>>>>>       remains unchanged in CLOSED"
>>>>>=20
>>>>>=20
>>>>>     =20
>>>> right
>>>>=20
>>>> thanks, marcelo
>>>>=20
>>>>=20
>>>>   =20
>>>>> Thanks,
>>>>>=20
>>>>> Reinaldo
>>>>>=20
>>>>>=20
>>>>> On 7/11/09 1:52 AM, "marcelo bagnulo braun"
>> <marcelo@it.uc3m.es> wrote:
>>>>>=20
>>>>>=20
>>>>>     =20
>>>>>> Hi,
>>>>>>=20
>>>>>> We have posted a new version of the NAT64 draft.
>>>>>>=20
>>>>>> As discussed lately in the ml, we are using the FINs and
>> the SYNs to
>>>>>> close and establish the TCP session state in the NAT.
>>>>>>=20
>>>>>> The document still needs quite some work, but if people
>> can take a quick
>>>>>> look and let us know if the overall direction is ok, it
>> would be great.
>>>>>>=20
>>>>>> Thanks, marcelo
>>>>>>=20
>>>>>>=20
>>>>>> -------- Mensaje original --------
>>>>>> Asunto:         [BEHAVE] I-D
>>>>>> Action:draft-ietf-behave-v6v4-xlate-stateful-01.txt
>>>>>> Fecha:  Sat, 11 Jul 2009 01:45:01 -0700 (PDT)
>>>>>> De:     Internet-Drafts@ietf.org
>>>>>> Para:   i-d-announce@ietf.org
>>>>>> CC:     behave@ietf.org
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>> 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.
>>>>>>=20
>>>>>>=20
>>>>>>         Title           : NAT64: Network Address and
>> Protocol Translation
>>>>>> from
>>>>>> IPv6 Clients to IPv4 Servers
>>>>>>         Author(s)       : M. Bagnulo, et al.
>>>>>>         Filename        :
>> draft-ietf-behave-v6v4-xlate-stateful-01.txt
>>>>>>         Pages           : 35
>>>>>>         Date            : 2009-07-11
>>>>>>=20
>>>>>> NAT64 is a mechanism for translating IPv6 packets to
>> IPv4 packets and
>>>>>> vice-versa.  DNS64 is a mechanism for synthesizing AAAA
>> records from
>>>>>> A records.  These two mechanisms together enable client-server
>>>>>> communication between an IPv6-only client and an
>> IPv4-only server,
>>>>>> without requiring any changes to either the IPv6 or the
>> IPv4 node,
>>>>>> for the class of applications that work through NATs.  They also
>>>>>> enable peer-to-peer communication between an IPv4 and an
>> IPv6 node,
>>>>>> where the communication can be initiated by either end using
>>>>>> existing, NAT-traversing, peer-to-peer communication techniques.
>>>>>> This document specifies NAT64, and gives suggestions on how they
>>>>>> should be deployed.
>>>>>>=20
>>>>>> A URL for this Internet-Draft is:
>>>>>>=20
>> http://www.ietf.org/internet-drafts/draft-ietf-behave-v6v4-xla
>> te-stateful-01
>>>>>> .t
>>>>>> xt
>>>>>>=20
>>>>>> Internet-Drafts are also available by anonymous FTP at:
>>>>>> ftp://ftp.ietf.org/internet-drafts/
>>>>>>=20
>>>>>> Below is the data which will enable a MIME compliant mail reader
>>>>>> implementation to automatically retrieve the ASCII version of the
>>>>>> Internet-Draft.
>>>>>>=20
>>>>>>=20
>>>>>>  =20
>>>>>>       =20
>>>>>=20
>>>>>     =20
>>>=20
>>>=20
>>> =20
>>=20
>> _______________________________________________
>> Behave mailing list
>> Behave@ietf.org
>> https://www.ietf.org/mailman/listinfo/behave
>=20


From wassim.haddad@ericsson.com  Tue Sep  1 12:38:13 2009
Return-Path: <wassim.haddad@ericsson.com>
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 16C933A6CCF for <behave@core3.amsl.com>; Tue,  1 Sep 2009 12:38:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.578
X-Spam-Level: 
X-Spam-Status: No, score=-6.578 tagged_above=-999 required=5 tests=[AWL=0.021,  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 nGpQ0fLb29AY for <behave@core3.amsl.com>; Tue,  1 Sep 2009 12:38:12 -0700 (PDT)
Received: from imr2.ericy.com (imr2.ericy.com [198.24.6.3]) by core3.amsl.com (Postfix) with ESMTP id 5C4FC3A6910 for <behave@ietf.org>; Tue,  1 Sep 2009 12:36:46 -0700 (PDT)
Received: from eusrcmw751.eamcs.ericsson.se (eusrcmw751.exu.ericsson.se [138.85.77.51]) by imr2.ericy.com (8.13.1/8.13.1) with ESMTP id n81Jaa4W002674; Tue, 1 Sep 2009 14:36:36 -0500
Received: from eusrcmw750.eamcs.ericsson.se ([138.85.77.50]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 1 Sep 2009 14:35:55 -0500
Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 1 Sep 2009 14:35:54 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.20]) by eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) with mapi; Tue, 1 Sep 2009 15:35:54 -0400
From: Wassim Haddad <wassim.haddad@ericsson.com>
To: "maxpassion@gmail.com" <maxpassion@gmail.com>
Date: Tue, 1 Sep 2009 15:35:52 -0400
Thread-Topic: [BEHAVE] NAT64 and MIPv6
Thread-Index: AcorMNvmlxSGRZTQTgWdavyaqQ9AvAACSE5g
Message-ID: <2991246A29623A4082EB2B06A2B891A41B7C494396@EUSAACMS0703.eamcs.ericsson.se>
References: <2991246A29623A4082EB2B06A2B891A41B7C3D85A9@EUSAACMS0703.eamcs.ericsson.se> <25e1aaa40908310956m6f638a4x32dca4039b63b21d@mail.gmail.com> <2991246A29623A4082EB2B06A2B891A41B7C458E91@EUSAACMS0703.eamcs.ericsson.se> <25e1aaa40909011032t7f76e318i5b815a1d08995464@mail.gmail.com> <2991246A29623A4082EB2B06A2B891A41B7C4942F9@EUSAACMS0703.eamcs.ericsson.se> <25e1aaa40909011120vd5d1830l108ed46c49f719@mail.gmail.com>
In-Reply-To: <25e1aaa40909011120vd5d1830l108ed46c49f719@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 01 Sep 2009 19:35:54.0665 (UTC) FILETIME=[6BE40190:01CA2B3B]
Cc: Wassim Haddad <wassim.haddad@ericsson.com>, "behave@ietf.org" <behave@ietf.org>
Subject: Re: [BEHAVE] NAT64 and MIPv6
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/mail-archive/web/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>
X-List-Received-Date: Tue, 01 Sep 2009 19:38:13 -0000

Hi,=20

>> =3D> the home network is an IPv6 network which has its own NAT64 and DNS=
64.
>> Did I answer your question?
>
> Then you mean the HA is located in the IPv6 netowrk
>
> =3D> Which has its own NAT64 and DNS64.
>
> if I understood it correctly, right?
>
> =3D> That's correct.

Do you consider the scenario that the HA is located in the IPv4 network tha=
t behind NAT64 which may be DSMIP case?

=3D> No actually, I did not consider this one. Can you explain more about i=
t and where you see the problem?


Regards,

Wassim H.

From wassim.haddad@ericsson.com  Tue Sep  1 14:42:48 2009
Return-Path: <wassim.haddad@ericsson.com>
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 E20D23A6948 for <behave@core3.amsl.com>; Tue,  1 Sep 2009 14:42:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.579
X-Spam-Level: 
X-Spam-Status: No, score=-6.579 tagged_above=-999 required=5 tests=[AWL=0.020,  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 pJqz+VIF8G+p for <behave@core3.amsl.com>; Tue,  1 Sep 2009 14:42:47 -0700 (PDT)
Received: from imr1.ericy.com (imr1.ericy.com [198.24.6.9]) by core3.amsl.com (Postfix) with ESMTP id D6EE83A677C for <behave@ietf.org>; Tue,  1 Sep 2009 14:42:46 -0700 (PDT)
Received: from eusrcmw751.eamcs.ericsson.se (eusrcmw751.exu.ericsson.se [138.85.77.51]) by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id n81Lgvp5005779; Tue, 1 Sep 2009 16:42:57 -0500
Received: from eusrcmw751.eamcs.ericsson.se ([138.85.77.56]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 1 Sep 2009 16:42:49 -0500
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 1 Sep 2009 16:42:49 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.20]) by eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) with mapi; Tue, 1 Sep 2009 17:42:48 -0400
From: Wassim Haddad <wassim.haddad@ericsson.com>
To: "charliep@wichorus.com" <charliep@wichorus.com>, "dthaler@microsoft.com" <dthaler@microsoft.com>
Date: Tue, 1 Sep 2009 17:42:47 -0400
Thread-Topic: [BEHAVE] NAT64 and MIPv6
Thread-Index: AcorMyAQUJMZemg+QGiqASwANdDwSAAGFVaA
Message-ID: <2991246A29623A4082EB2B06A2B891A41B7C49444D@EUSAACMS0703.eamcs.ericsson.se>
References: <E4561B14EE2A3E4E9D478EBFB5416E1B1C3163@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <C6C2C322.F191%hesham@elevatemobile.com> <E4561B14EE2A3E4E9D478EBFB5416E1B1C389D@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <2991246A29623A4082EB2B06A2B891A41B7C4591FD@EUSAACMS0703.eamcs.ericsson.se> <E4561B14EE2A3E4E9D478EBFB5416E1B1C3AA8@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <4A9D6424.2010007@wichorus.com> <E4561B14EE2A3E4E9D478EBFB5416E1B1C50A4@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <4A9D6950.8020501@wichorus.com>
In-Reply-To: <4A9D6950.8020501@wichorus.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 01 Sep 2009 21:42:49.0427 (UTC) FILETIME=[26A47A30:01CA2B4D]
Cc: Wassim Haddad <wassim.haddad@ericsson.com>, "behave@ietf.org" <behave@ietf.org>
Subject: Re: [BEHAVE] NAT64 and MIPv6
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/mail-archive/web/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>
X-List-Received-Date: Tue, 01 Sep 2009 21:42:48 -0000

Hi Charles,

AFAIK, there is no consensus nor an attempt to build consensus within Behav=
e WG. There was a
comment from Dave about MIPv6 which I tried to clarify with him in my previ=
ous email in the
form of a "text".

Personally, I am not in favor of limiting MIPv6 to work only in such config=
uration.


Regards,

Wassim H.


-----Original Message-----
From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On Behalf Of=
 Charles E. Perkins
Sent: Tuesday, September 01, 2009 12:35 PM
To: Dave Thaler
Cc: behave@ietf.org
Subject: Re: [BEHAVE] NAT64 and MIPv6


Hello Dave,

Yes, I did miss the email where you said that.
I thought I'd read through all thousand of them, but now I see there are mo=
re :-)  And, my suggestion of a [behave] consensus was purely hypothetical =
and not based on any formal position, but instead only on what I had read f=
rom the previous emails.

Regards,
Charlie P.


Dave Thaler wrote:
>
>> On the third hand (or is that a foot?) any such discussion about
>> defects in Mobile IPv6 deserves to have at least some visibility in
>> the [mext] working group.  Doesn't seem quite right for [behave] to
>> quickly adopt a consensus position without even asking about it in
>> [mext].
>>
>
> I don't know why you're referring to a [behave] consensus position.  I
> already stated in the thread that such a document belongs in a MIP
> related WG not in Behave.  Perhaps you missed that.
>
> -Dave
>

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

From xing@cernet.edu.cn  Tue Sep  1 21:05:58 2009
Return-Path: <xing@cernet.edu.cn>
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 BB0EF3A6A27 for <behave@core3.amsl.com>; Tue,  1 Sep 2009 21:05:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.628
X-Spam-Level: 
X-Spam-Status: No, score=0.628 tagged_above=-999 required=5 tests=[AWL=0.531,  BAYES_00=-2.599, FH_HAS_XAIMC=2.696]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3av28foAS-9M for <behave@core3.amsl.com>; Tue,  1 Sep 2009 21:05:58 -0700 (PDT)
Received: from cernet.edu.cn (sea.net.edu.cn [202.112.3.66]) by core3.amsl.com (Postfix) with SMTP id 5EF553A6830 for <behave@ietf.org>; Tue,  1 Sep 2009 21:05:56 -0700 (PDT)
Received: from [59.66.24.75]([59.66.24.75]) by cernet.edu.cn(AIMC 3.2.0.0) with SMTP id jm04a9e17e8; Wed, 02 Sep 2009 12:04:46 +0800
Message-ID: <4A9DEED0.3040407@cernet.edu.cn>
Date: Wed, 02 Sep 2009 12:04:32 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Dave Thaler <dthaler@microsoft.com>
References: <E4561B14EE2A3E4E9D478EBFB5416E1B1C3163@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>	<C6C2C322.F191%hesham@elevatemobile.com>	<E4561B14EE2A3E4E9D478EBFB5416E1B1C389D@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <E4561B14EE2A3E4E9D478EBFB5416E1B1C3931@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <E4561B14EE2A3E4E9D478EBFB5416E1B1C3931@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-AIMC-AUTH: xing
X-AIMC-MAILFROM: xing@cernet.edu.cn
X-AIMC-Msg-ID: 2V2FhiWB
Cc: Wassim Haddad <wassim.haddad@ericsson.com>, Wassim Haddad <wmhaddad@gmail.com>, "behave@ietf.org" <behave@ietf.org>, Hesham Soliman <hesham@elevatemobile.com>
Subject: Re: [BEHAVE] NAT64 and MIPv6
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/mail-archive/web/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>
X-List-Received-Date: Wed, 02 Sep 2009 04:05:58 -0000

Dave Thaler 写道:
>> -----Original Message-----
>> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On Behalf
>> Of Dave Thaler
>> Sent: Tuesday, September 01, 2009 8:21 AM
>> To: Hesham Soliman; Wassim Haddad
>> Cc: Wassim Haddad; behave@ietf.org
>> Subject: Re: [BEHAVE] NAT64 and MIPv6
>>
>> Hesham writes:
>>     
>>> At the very least any solution should highlight this as a requirement
>>>       
>> for
>>     
>>> MNs because 3775 doesn't limit the DNS queries to the home DNS. But I
>>> don't
>>> know how to do that if the presence of a NAT is not known to the host.
>>>       
>> I agree that 3775 is defective by not mentioning this,
>> since again the presence of a NAT does not introduce
>> this problem... it already breaks with private namespaces
>> and 3775 should have pointed out how to make DNS work.
>>     
>
> Another thing... I disagree that the NAT64 or DNS64
> document should discuss this issue.  I believe it
> belongs in a separate document that covers the issues
> with mobile IP resulting from both private namespaces
> and private address spaces.  It's not specific to
> translation so it's arguably better done in a MIP
> group rather than Behave, although Behave should certainly
> review it.  That's what I'd recommend anyway.
>   

I think this should be the way to move forward. xing

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


From remi.despres@free.fr  Wed Sep  2 03:20:16 2009
Return-Path: <remi.despres@free.fr>
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 1F81D3A67A4 for <behave@core3.amsl.com>; Wed,  2 Sep 2009 03:20:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.826
X-Spam-Level: 
X-Spam-Status: No, score=-1.826 tagged_above=-999 required=5 tests=[AWL=0.123,  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 mkQ8Ce4fRXg6 for <behave@core3.amsl.com>; Wed,  2 Sep 2009 03:20:15 -0700 (PDT)
Received: from smtp6-g21.free.fr (smtp6-g21.free.fr [212.27.42.6]) by core3.amsl.com (Postfix) with ESMTP id DCE6228C3F1 for <behave@ietf.org>; Wed,  2 Sep 2009 03:19:24 -0700 (PDT)
Received: from smtp6-g21.free.fr (localhost [127.0.0.1]) by smtp6-g21.free.fr (Postfix) with ESMTP id A52F0E0813F; Wed,  2 Sep 2009 12:17:05 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by smtp6-g21.free.fr (Postfix) with ESMTP id A6C81E08133; Wed,  2 Sep 2009 12:17:02 +0200 (CEST)
In-Reply-To: <E4561B14EE2A3E4E9D478EBFB5416E1B1C4ECE@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
References: <0A5916B6-4B95-4818-B099-044701D4B659@free.fr> <E4561B14EE2A3E4E9D478EBFB5416E1B1C4ECE@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
Mime-Version: 1.0 (Apple Message framework v753.1)
Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed
Message-Id: <8514A943-FAC0-46DE-8218-CE938837CEE3@free.fr>
Content-Transfer-Encoding: quoted-printable
From: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
Date: Wed, 2 Sep 2009 12:17:01 +0200
To: Dave Thaler <dthaler@microsoft.com>
X-Mailer: Apple Mail (2.753.1)
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] draft-ietf-behave-address-format-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/mail-archive/web/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>
X-List-Received-Date: Wed, 02 Sep 2009 10:20:16 -0000

Dave,

I should have explained more the rationale for "IPv4-mappable" (I did =20=

know and understood the words you used in your presentation).

In a given translator, the IPv6 address used to represent an IPv4 =20
host and the IPv4 address of this can be mapped both ways.
This IPv6 address can therefore be viewed as mappable to the IPv4 =20
address as well mappable from it.
When it traverses the translator, the destination becomes the result =20
of a mapping from the mappable address to the mapped address.

As you rightly decided, "IPv4-mapped" couldn't be a generic term for =20
addresses "used to represent IPv4 hosts" because it is linked to a =20
specific format.

Now, IPv4-mappable has two properties:
- it isn't reserved for a specific format
- because of the reversibility, its semantic is not less adequate =20
than that of IPv4-mapped.

Actually, IPv6 addresses that exist before any traversal of an IPv6/=20
IPv4 translator, like addresses used to represent IPv4 hosts, would =20
be more intuitively called mappable than a mapped. (A minor point I =20
would agree, but still a point IMHO)

Does this make sense, or do I still miss something?.

Regards,
RD

Le 1 sept. 09 =E0 19:11, Dave Thaler a =E9crit :

> R=E9mi Despr=E9s wrote:
>> To qualify IPv6 Addresses, what about replacing "Used to Represent
>> IPv4 Hosts" (rather long), by "IPv4-mappable" (shorter, not used yet,
>> reasonably intuitive)?
>
> In my presentation at the WG meeting I used, as SIIT did:
>
> "IPv4-mappED" (past tense, meaning the mapping already happened
>    in order to get an IPv6 address) for addresses used to
>    represent IPv4 hosts
>
> "IPv4-translatABLE" (future tense, meaning the mapping
>    has not yet happened, when you have an IPv6 address)
>    for addresses assigned to IPv6 hosts
>
> Of course the last term only applies to translation not
> encapsulation, and Softwires folk wanted the doc to
> cover both.  So I suppose "IPv4-mappable" could be
> used for addresses assigned to IPv6 hosts.
>
> (Just pointing this out because you suggested
> IPv4-mappable be used for addresses used to
> represent IPv4 hosts, which is backwards.)
>
> -Dave


From root@core3.amsl.com  Wed Sep  2 08:00:02 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: behave@ietf.org
Delivered-To: behave@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 22E2C3A6C67; Wed,  2 Sep 2009 08:00:01 -0700 (PDT)
From: IESG Secretary <iesg-secretary@ietf.org>
To: ietf-announce@ietf.org
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20090902150002.22E2C3A6C67@core3.amsl.com>
Date: Wed,  2 Sep 2009 08:00:02 -0700 (PDT)
Cc: behave@ietf.org
Subject: [BEHAVE] BEHAVE interim teleconference calls
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/mail-archive/web/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>
X-List-Received-Date: Wed, 02 Sep 2009 15:00:02 -0000

As announced at the Stockholm IETF's BEHAVE meeting, BEHAVE will be using
WebEx and PSTN conferencing for the following interim meetings
to discuss 6/4 translation and advance those documents:

Wednesday, September 16, 7am-9am Pacific Time
Wednesday, October 21, 7am-9am Pacific Time

Per http://www.ietf.org/meeting/cutoff-dates.html#76, the cut-off
for revised I-Ds is October 26.

Agendas WebEx URL and PSTN dial-in information will be published
on BEHAVE's wiki at http://trac.tools.ietf.org/wg/behave/trac/wiki

From maxpassion@gmail.com  Wed Sep  2 11:33:06 2009
Return-Path: <maxpassion@gmail.com>
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 8DD6328C165 for <behave@core3.amsl.com>; Wed,  2 Sep 2009 11:33:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.144
X-Spam-Level: 
X-Spam-Status: No, score=-2.144 tagged_above=-999 required=5 tests=[AWL=0.455,  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 Vr8JtlFKVyZg for <behave@core3.amsl.com>; Wed,  2 Sep 2009 11:33:05 -0700 (PDT)
Received: from mail-vw0-f177.google.com (mail-vw0-f177.google.com [209.85.212.177]) by core3.amsl.com (Postfix) with ESMTP id 0466028C192 for <behave@ietf.org>; Wed,  2 Sep 2009 11:32:25 -0700 (PDT)
Received: by vws7 with SMTP id 7so967430vws.29 for <behave@ietf.org>; Wed, 02 Sep 2009 11:31:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=pqHtpGPZ9BGSiyBZdWrpuRce1FVTba64nKLIiMOFvmI=; b=t8RENm9Si/CZHwByp9VrKPoAJeybhvljHbt9K5yCoICsBh23ubsLST5l0L68JND4vW MdfqHi5HU2/OCZAekZY7QHz32UPfg7zEe2dtcmhVXuQgUBAp8jeObcB5u7m2gUkia39x ouq9DQw8DyqMnBQWzGaa6hVUDqN6kepM0iFYs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=JObk1PAmuobr+iZ0L5toDW1P1kt0T9meWi6gbEc5VFPX1lTduDi9fIrps/7SDyiGH8 JawudKnra5G3auuUcDV9wE3N+7SZOjMNzuYOpNGvUqetesBdpcAhCRgWyAyZPeOypC+8 r6+PO4wEHT6X41W0tjwn52bIeWaDGfh03Uqso=
MIME-Version: 1.0
Received: by 10.220.107.227 with SMTP id c35mr197073vcp.0.1251916312647; Wed,  02 Sep 2009 11:31:52 -0700 (PDT)
In-Reply-To: <2991246A29623A4082EB2B06A2B891A41B7C494396@EUSAACMS0703.eamcs.ericsson.se>
References: <2991246A29623A4082EB2B06A2B891A41B7C3D85A9@EUSAACMS0703.eamcs.ericsson.se> <25e1aaa40908310956m6f638a4x32dca4039b63b21d@mail.gmail.com> <2991246A29623A4082EB2B06A2B891A41B7C458E91@EUSAACMS0703.eamcs.ericsson.se> <25e1aaa40909011032t7f76e318i5b815a1d08995464@mail.gmail.com> <2991246A29623A4082EB2B06A2B891A41B7C4942F9@EUSAACMS0703.eamcs.ericsson.se> <25e1aaa40909011120vd5d1830l108ed46c49f719@mail.gmail.com> <2991246A29623A4082EB2B06A2B891A41B7C494396@EUSAACMS0703.eamcs.ericsson.se>
Date: Thu, 3 Sep 2009 02:31:51 +0800
Message-ID: <25e1aaa40909021131h683a7ddara6aea85cb6c6ebe0@mail.gmail.com>
From: liu dapeng <maxpassion@gmail.com>
To: Wassim Haddad <wassim.haddad@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "behave@ietf.org" <behave@ietf.org>
Subject: Re: [BEHAVE] NAT64 and MIPv6
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/mail-archive/web/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>
X-List-Received-Date: Wed, 02 Sep 2009 18:33:06 -0000

2009/9/2, Wassim Haddad <wassim.haddad@ericsson.com>:
> Hi,
>
>>> => the home network is an IPv6 network which has its own NAT64 and DNS64.
>>> Did I answer your question?
>>
>> Then you mean the HA is located in the IPv6 netowrk
>>
>> => Which has its own NAT64 and DNS64.
>>
>> if I understood it correctly, right?
>>
>> => That's correct.
>
> Do you consider the scenario that the HA is located in the IPv4 network that
> behind NAT64 which may be DSMIP case?
>
> => No actually, I did not consider this one. Can you explain more about it
> and where you see the problem?

Hi, Wassim,

The problem here is that if the HA is located in the IPv4 network
which is behind NAT64, The BU message will traverse NAT64, but NAT64
will not translate the IPv6 BU message to the corresponding DSMIP BU
message. this may cause a problem.

BR,
Dapeng Liu

>
> Regards,
>
> Wassim H.
>

From xuxh@huawei.com  Wed Sep  2 19:17:19 2009
Return-Path: <xuxh@huawei.com>
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 2B0FF3A6ADA; Wed,  2 Sep 2009 19:17:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.329
X-Spam-Level: *
X-Spam-Status: No, score=1.329 tagged_above=-999 required=5 tests=[AWL=1.824,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  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 nELwjE2yHJ02; Wed,  2 Sep 2009 19:17:18 -0700 (PDT)
Received: from szxga04-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id 5767E3A6A96; Wed,  2 Sep 2009 19:17:18 -0700 (PDT)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KPD00EP3IA7TP@szxga04-in.huawei.com>; Thu, 03 Sep 2009 10:15:43 +0800 (CST)
Received: from huawei.com ([172.24.1.33]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KPD0088VIA7OG@szxga04-in.huawei.com>; Thu, 03 Sep 2009 10:15:43 +0800 (CST)
Received: from HUAWEIE75F8F11 ([10.111.12.212]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KPD00MAEIA7ZS@szxml06-in.huawei.com>; Thu, 03 Sep 2009 10:15:43 +0800 (CST)
Date: Thu, 03 Sep 2009 10:15:43 +0800
From: Xu Xiaohu <xuxh@huawei.com>
To: softwires@ietf.org, 'Behave WG' <behave@ietf.org>
Message-id: <003201ca2c3c$70c77460$d40c6f0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: AcosPHCH+Xk9HqAuRLynwkG0AuOUTA==
Subject: [BEHAVE] Some Thought about the Automatic Tunnel Address
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/mail-archive/web/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>
X-List-Received-Date: Thu, 03 Sep 2009 02:17:19 -0000

Hi all,

As quoted from "IPv6 Transition Mechanism" [RFC1933], "...The tunnel
endpoint is the node to which the IPv6 packet is addressed.  Since the
endpoint of the tunnel is the destination of the IPv6 packet, the tunnel
endpoint can be determined from the destination IPv6 address of that packet:
If that address is an IPv4-compatible address, then the low-order 32-bits
hold the IPv4 address of the destination node, and that can be used as the
tunnel endpoint address." 

Unfortunately, the usage of IPv4-compatible address may cause routing
scalability issue for IPv6 in practice when multiple sites use such
addresses.

The ISATAP (RFC5214) solves the above routing scalability issue with the
automatic tunneling address by concatenating a /64 LIR prefix and an ISATAP
interface ID (which is constructed in the Modified EUI-64) to generate an
IPv6 Global unicast address. I wonder whether it is better to directly
concatenate a /96 LIR prefix (which can be learnt from the prefix
information option in the RA message) and a 32-bit IPv4 address to generate
an IPv6 address. One obvious benefit of this method is IPv6 prefix resource
can be allocated in a more efficient way. By the way, the IPv6 DAD action
can also be avoided since the IPv4 address is already guaranteed to be
unique.

Xiaohu


From caozhenpku@gmail.com  Thu Sep  3 07:02:27 2009
Return-Path: <caozhenpku@gmail.com>
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 0C45028C17E for <behave@core3.amsl.com>; Thu,  3 Sep 2009 07:02:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.348
X-Spam-Level: 
X-Spam-Status: No, score=-2.348 tagged_above=-999 required=5 tests=[AWL=0.251,  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 ohRoRQkR+60t for <behave@core3.amsl.com>; Thu,  3 Sep 2009 07:02:25 -0700 (PDT)
Received: from mail-vw0-f177.google.com (mail-vw0-f177.google.com [209.85.212.177]) by core3.amsl.com (Postfix) with ESMTP id 4BA8728C1C0 for <behave@ietf.org>; Thu,  3 Sep 2009 07:02:25 -0700 (PDT)
Received: by vws7 with SMTP id 7so1460696vws.29 for <behave@ietf.org>; Thu, 03 Sep 2009 07:01:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=zbX+1BFzBChKKVX71U3U7EQgGG3NoE/TjCFPv4QeqKk=; b=fZ2CJYupjgaFZ+nhTdXIG9ilWSjOthh3WlXyIrntibXN4ul9JrniZmaK4ddP9WXI7D dCruF4lhIq/aULb5eL2lRrdXXj+/dg4QPpiqn49omLljCZ5vKSut0X3rcp+YWxHV/sG7 8+oVi5oVP7rVbQ3acSH1MvTI0MIHXcXRMIY/A=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=NYNpqcRq0UBSoOefUyRoEY1o36baGl603vCJEkWMpdCgL4blmg/RQiTf/vtXl6v04I aQm8ClrS+VA5oWcX7hn+Pzlkt61cKIR/rntaUln1gt8RZsrddGy9dXjEN12cz6g3jpUl gdnRF7bqekIGkpK1Av/lQFEv5WwpYWblOU5uI=
MIME-Version: 1.0
Received: by 10.220.20.67 with SMTP id e3mr7087885vcb.75.1251986462764; Thu,  03 Sep 2009 07:01:02 -0700 (PDT)
In-Reply-To: <C6C2BA6B.36875%rpenno@juniper.net>
References: <128401ca0583$480210b0$c4f0200a@cisco.com> <C6C2BA6B.36875%rpenno@juniper.net>
Date: Thu, 3 Sep 2009 22:01:02 +0800
Message-ID: <a7c8d0a30909030701v47ea212bi7210ecfe005758e9@mail.gmail.com>
From: Zhen Cao <caozhenpku@gmail.com>
To: Reinaldo Penno <rpenno@juniper.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Behave WG <behave@ietf.org>, Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] NAT64 and TCP processing (was Re: Comments todraft-ietf-behave-v6v4-xlate-stateful-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/mail-archive/web/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>
X-List-Received-Date: Thu, 03 Sep 2009 14:02:27 -0000

Hi Reinaldo,

The issue you raise here is interesting. As you said, the NAT44
implementation already track TCP seq number. Is it mandated in the
NAT44 standard documents?

Thanks,
Zhen

On Wed, Sep 2, 2009 at 2:47 AM, Reinaldo Penno<rpenno@juniper.net> wrote:
> Hello,
>
> I read the paper reference by Dan below and the number of TCP connections
> that end with TCP RST is significant.
>
>> Martin Arlitt, Carey Williamson, "An Analysis of TCP Reset Behaviour on =
the
>> Internet", October, 2004,
>> http://pages.cpsc.ucalgary.ca/~carey/papers/2005/TCP-Resets.pdf
>
> Also, there is this draft which is categorized as standards track and tal=
ks
> about the many issues related to TCP window attacks and most of the
> mitigations discussed require TCP sequence tracking.
>
> http://www.ietf.org/id/draft-ietf-tcpm-tcpsecure-11.txt
>
> The issues found here are not exclusive of NAT64, NAT44 would suffer the
> same problems. But most NAT44 implementations today already track sequenc=
e
> numbers whether due to security concerns or ALGs.
>
> Thanks,
>
> Reinaldo
>
> On 7/15/09 12:34 PM, "Dan Wing" <dwing@cisco.com> wrote:
>
>>
>>
>>> -----Original Message-----
>>> From: behave-bounces@ietf.org
>>> [mailto:behave-bounces@ietf.org] On Behalf Of marcelo bagnulo braun
>>> Sent: Wednesday, July 15, 2009 12:31 AM
>>> To: Reinaldo Penno
>>> Cc: Behave WG
>>> Subject: Re: [BEHAVE] Comments
>>> todraft-ietf-behave-v6v4-xlate-stateful-01.txt
>>>
>>> Reinaldo Penno escribi=F3:
>>>>
>>>> On 7/14/09 9:30 AM, "marcelo bagnulo braun"
>>> <marcelo@it.uc3m.es> wrote:
>>>>
>>>>
>>>>> Reinaldo Penno escribi=F3:
>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> we should include how to handle TCP RSTs as well. Host
>>> implementations and
>>>>>> NATs might remove the tcpb (or binding) as soon as a RST
>>> is received (as
>>>>>> long as seq number checking passes).
>>>>>>
>>>>>>
>>>>> but that would imply to keep track of all the seq # for
>>> all the data
>>>>> packets for each of the flows....
>>>>> I don't think i would like to go there.
>>>>>
>>>>> In order to handle the RST packets, actually, i had
>>> thought of that and
>>>>> i included in the state machines, but it seems i forgot to
>>> include in
>>>>> the text...
>>>>>
>>>>> I think a RST coming from the Internet part should be
>>> ignored, cause as
>>>>> you say may be an attack, but i think that if the rst
>>> packet comes from
>>>>> the network side (the network that runs the nat64) then it
>>> should be
>>>>> honnoured.
>>>>>
>>>>
>>>> After the connection is established, and the v4 side sends
>>> a RST to end the
>>>> connection and we do not honor it we will have hanging TCP
>>> bindings. This is
>>>> exactly what we were trying to avoid by being diligent on following
>>>> FINs/ACKs and having timeouts.
>>>
>>> right, i guess the question is how often this happens.
>>
>> Martin Arlitt, Carey Williamson, "An Analysis of TCP Reset Behaviour on =
the
>> Internet", October, 2004,
>> http://pages.cpsc.ucalgary.ca/~carey/papers/2005/TCP-Resets.pdf
>>
>> -d
>>
>>> I like Iljitshc suggestion of reducing the lifetime of the
>>> binding when
>>> a RST is seen, what do you think about that?
>>>
>>>> A TCP connection ended by RST is reused pretty quickly and
>>> the issue I see
>>>> if we do not honor valid TCP RST it is that we can end up
>>> reusing a old
>>>> binding and all kinds of problems can exist.
>>>>
>>>
>>> I fail to see any problem here. I mean, if the new connection
>>> uses the
>>> same 5 tuple, then the state can be reused wihtout problem and if it
>>> doesn't, then a new binding will be created, what is the problem that
>>> you see?
>>>> On the other hand, spoofed TCP packets can end the
>>> connection and there are
>>>> specific seq checks needed (different from connecting state
>>> from established
>>>> state).
>>>>
>>>>
>>>
>>> right, this is my concern
>>>
>>>>> what do you think?
>>>>>
>>>>
>>>>
>>>>>> Here, I think checking seq numbers is important for
>>> security sake, specially
>>>>>> in the case of TCP RSTs.
>>>>>>
>>>>>> As far as ICMP response to unsolicited SYNs which we
>>> discussed before I
>>>>>> suggest the following amendment to your text
>>>>>>
>>>>>> From
>>>>>>
>>>>>> " =A0 =A0 =A0If the destination transport address contained in
>>> the incoming V4
>>>>>> =A0 =A0 =A0 SYN is not in use in the TCP BIB, then the packet
>>> is discarded and
>>>>>> =A0 =A0 =A0 an ICMP Port Unreachable error (Type 3, Code 3) is
>>> sent back to
>>>>>> =A0 =A0 =A0 the source of the v4 SYN. =A0The state remains
>>> unchanged in CLOSED"
>>>>>>
>>>>>> To
>>>>>>
>>>>>> " =A0 =A0 =A0If the destination transport address contained in
>>> the incoming V4
>>>>>> =A0 =A0 =A0 SYN is not in use in the TCP BIB, then the packet
>>> is discarded and
>>>>>> =A0 =A0 =A0 an ICMP Port Unreachable error (Type 3, Code 3) is
>>> sent back to
>>>>>> =A0 =A0 =A0 the source of the v4 SYN unless REQ-4a of RFC5382
>>> applies. =A0The state
>>>>>> =A0 =A0 =A0 remains unchanged in CLOSED"
>>>>>>
>>>>>>
>>>>>>
>>>>> right
>>>>>
>>>>> thanks, marcelo
>>>>>
>>>>>
>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Reinaldo
>>>>>>
>>>>>>
>>>>>> On 7/11/09 1:52 AM, "marcelo bagnulo braun"
>>> <marcelo@it.uc3m.es> wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> We have posted a new version of the NAT64 draft.
>>>>>>>
>>>>>>> As discussed lately in the ml, we are using the FINs and
>>> the SYNs to
>>>>>>> close and establish the TCP session state in the NAT.
>>>>>>>
>>>>>>> The document still needs quite some work, but if people
>>> can take a quick
>>>>>>> look and let us know if the overall direction is ok, it
>>> would be great.
>>>>>>>
>>>>>>> Thanks, marcelo
>>>>>>>
>>>>>>>
>>>>>>> -------- Mensaje original --------
>>>>>>> Asunto: =A0 =A0 =A0 =A0 [BEHAVE] I-D
>>>>>>> Action:draft-ietf-behave-v6v4-xlate-stateful-01.txt
>>>>>>> Fecha: =A0Sat, 11 Jul 2009 01:45:01 -0700 (PDT)
>>>>>>> De: =A0 =A0 Internet-Drafts@ietf.org
>>>>>>> Para: =A0 i-d-announce@ietf.org
>>>>>>> CC: =A0 =A0 behave@ietf.org
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> 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.
>>>>>>>
>>>>>>>
>>>>>>> =A0 =A0 =A0 =A0 Title =A0 =A0 =A0 =A0 =A0 : NAT64: Network Address =
and
>>> Protocol Translation
>>>>>>> from
>>>>>>> IPv6 Clients to IPv4 Servers
>>>>>>> =A0 =A0 =A0 =A0 Author(s) =A0 =A0 =A0 : M. Bagnulo, et al.
>>>>>>> =A0 =A0 =A0 =A0 Filename =A0 =A0 =A0 =A0:
>>> draft-ietf-behave-v6v4-xlate-stateful-01.txt
>>>>>>> =A0 =A0 =A0 =A0 Pages =A0 =A0 =A0 =A0 =A0 : 35
>>>>>>> =A0 =A0 =A0 =A0 Date =A0 =A0 =A0 =A0 =A0 =A0: 2009-07-11
>>>>>>>
>>>>>>> NAT64 is a mechanism for translating IPv6 packets to
>>> IPv4 packets and
>>>>>>> vice-versa. =A0DNS64 is a mechanism for synthesizing AAAA
>>> records from
>>>>>>> A records. =A0These two mechanisms together enable client-server
>>>>>>> communication between an IPv6-only client and an
>>> IPv4-only server,
>>>>>>> without requiring any changes to either the IPv6 or the
>>> IPv4 node,
>>>>>>> for the class of applications that work through NATs. =A0They also
>>>>>>> enable peer-to-peer communication between an IPv4 and an
>>> IPv6 node,
>>>>>>> where the communication can be initiated by either end using
>>>>>>> existing, NAT-traversing, peer-to-peer communication techniques.
>>>>>>> This document specifies NAT64, and gives suggestions on how they
>>>>>>> should be deployed.
>>>>>>>
>>>>>>> A URL for this Internet-Draft is:
>>>>>>>
>>> http://www.ietf.org/internet-drafts/draft-ietf-behave-v6v4-xla
>>> te-stateful-01
>>>>>>> .t
>>>>>>> xt
>>>>>>>
>>>>>>> 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 magnus.westerlund@ericsson.com  Thu Sep  3 07:31:07 2009
Return-Path: <magnus.westerlund@ericsson.com>
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 3B43D28C269 for <behave@core3.amsl.com>; Thu,  3 Sep 2009 07:31:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.745
X-Spam-Level: 
X-Spam-Status: No, score=-5.745 tagged_above=-999 required=5 tests=[AWL=0.504,  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 7GT2-xqjYjm1 for <behave@core3.amsl.com>; Thu,  3 Sep 2009 07:31:06 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62]) by core3.amsl.com (Postfix) with ESMTP id 2B14828C266 for <behave@ietf.org>; Thu,  3 Sep 2009 07:31:06 -0700 (PDT)
X-AuditID: c1b4fb3e-b7c00ae0000007bf-be-4a9fcf28f53a
Received: from esealmw128.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw4.ericsson.se (Symantec Mail Security) with SMTP id 58.ED.01983.82FCF9A4; Thu,  3 Sep 2009 16:14:00 +0200 (CEST)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.176]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 3 Sep 2009 16:12:53 +0200
Received: from [147.214.183.250] ([147.214.183.250]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 3 Sep 2009 16:12:52 +0200
Message-ID: <4A9FCEE4.8070809@ericsson.com>
Date: Thu, 03 Sep 2009 16:12:52 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Philip Matthews <philip_matthews@magma.ca>
References: <4A6D9D29.2050901@ericsson.com> <4A6DA11B.3010300@viagenie.ca> <4A6DA77B.4060702@ericsson.com> <4A6DAB04.4000006@viagenie.ca> <4A6DD882.6000603@ericsson.com> <E4561B14EE2A3E4E9D478EBFB5416E1B155641@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com> <A6B46D38-18B1-43B9-9784-D15201DA6A19@magma.ca>
In-Reply-To: <A6B46D38-18B1-43B9-9784-D15201DA6A19@magma.ca>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-OriginalArrivalTime: 03 Sep 2009 14:12:52.0930 (UTC) FILETIME=[A04D7220:01CA2CA0]
X-Brightmail-Tracker: AAAAAA==
Cc: "matthew@matthew.at" <matthew@matthew.at>, Behave WG <behave@ietf.org>, Dave Thaler <dthaler@microsoft.com>, Tim Polk <tim.polk@nist.gov>
Subject: Re: [BEHAVE] Discusses regarding security mechanism usage for TURN
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/mail-archive/web/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>
X-List-Received-Date: Thu, 03 Sep 2009 14:31:07 -0000

Philip Matthews skrev:
> Magnus:
> 
> What is your proposal for the case where TLS transport is used between
> the client and the server. Would the client have to use the Long-Term
> Credential mechanism in this case?

Well, if you actually used real certificates for TLS in the client that
would clearly satisfy the security requirement of identifying the
client. Which would be an argument for saying MUST use Long-Term
credential mechanism or other equal or stronger mechanism to identify
the client.

But in most cases aren't the TLS clients using self signed certificates
that provide no value for client authentication.

Cheers

Magnus Westerlund

IETF Transport Area Director
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------

From rpenno@juniper.net  Thu Sep  3 11:03:19 2009
Return-Path: <rpenno@juniper.net>
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 801013A680A for <behave@core3.amsl.com>; Thu,  3 Sep 2009 11:03:19 -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 Lkp+BeFgDLFD for <behave@core3.amsl.com>; Thu,  3 Sep 2009 11:03:18 -0700 (PDT)
Received: from exprod7og116.obsmtp.com (exprod7og116.obsmtp.com [64.18.2.219]) by core3.amsl.com (Postfix) with ESMTP id B8DDF3A6806 for <behave@ietf.org>; Thu,  3 Sep 2009 11:03:17 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob116.postini.com ([64.18.6.12]) with SMTP ID DSNKSqAEwtASDNmBESv3u1IVQg+j5kM0MsoH@postini.com; Thu, 03 Sep 2009 11:03:36 PDT
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server (TLS) id 8.1.375.2; Thu, 3 Sep 2009 10:43:48 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Thu, 3 Sep 2009 13:43:48 -0400
From: Reinaldo Penno <rpenno@juniper.net>
To: Zhen Cao <caozhenpku@gmail.com>
Date: Thu, 3 Sep 2009 13:43:47 -0400
Thread-Topic: [BEHAVE] NAT64 and TCP processing (was Re: Comments todraft-ietf-behave-v6v4-xlate-stateful-01.txt)
Thread-Index: AcosnwpkMBQmSOO6SPaBgsLJEyNrDAAHwxRG
Message-ID: <C6C54E63.36D5C%rpenno@juniper.net>
In-Reply-To: <a7c8d0a30909030701v47ea212bi7210ecfe005758e9@mail.gmail.com>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Behave WG <behave@ietf.org>, Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] NAT64 and TCP processing (was Re: Comments todraft-ietf-behave-v6v4-xlate-stateful-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/mail-archive/web/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>
X-List-Received-Date: Thu, 03 Sep 2009 18:03:19 -0000

No, in general the area where TCP, NAT44 and security intersect is very
light on standards.

There are comments in BEHAVE NAT TCP (NAT Session Refresh section) about ho=
w
a NAT can detect if a connection is still alive by sending TCP keep alive
packets (which require some seq/ack tracking).

I would venture to say TCP tracking is probably the de facto standard due t=
o
ALGs, security and others, but it is something tricky to standardize. NAT64
current draft relies on a series of timers.

I wanted to bring this issue forth again after I read the references since
there was some doubt regarding attacks, percentage of connections that end
'nicely', other standards within IETF, etc.

Whatever method(s) we go with NAT64, the security and performance
implications need to be well-understood.

Thanks,


On 9/3/09 7:01 AM, "Zhen Cao" <caozhenpku@gmail.com> wrote:

> Hi Reinaldo,
>=20
> The issue you raise here is interesting. As you said, the NAT44
> implementation already track TCP seq number. Is it mandated in the
> NAT44 standard documents?
>=20
> Thanks,
> Zhen
>=20
> On Wed, Sep 2, 2009 at 2:47 AM, Reinaldo Penno<rpenno@juniper.net> wrote:
>> Hello,
>>=20
>> I read the paper reference by Dan below and the number of TCP connection=
s
>> that end with TCP RST is significant.
>>=20
>>> Martin Arlitt, Carey Williamson, "An Analysis of TCP Reset Behaviour on=
 the
>>> Internet", October, 2004,
>>> http://pages.cpsc.ucalgary.ca/~carey/papers/2005/TCP-Resets.pdf
>>=20
>> Also, there is this draft which is categorized as standards track and ta=
lks
>> about the many issues related to TCP window attacks and most of the
>> mitigations discussed require TCP sequence tracking.
>>=20
>> http://www.ietf.org/id/draft-ietf-tcpm-tcpsecure-11.txt
>>=20
>> The issues found here are not exclusive of NAT64, NAT44 would suffer the
>> same problems. But most NAT44 implementations today already track sequen=
ce
>> numbers whether due to security concerns or ALGs.
>>=20
>> Thanks,
>>=20
>> Reinaldo
>>=20
>> On 7/15/09 12:34 PM, "Dan Wing" <dwing@cisco.com> wrote:
>>=20
>>>=20
>>>=20
>>>> -----Original Message-----
>>>> From: behave-bounces@ietf.org
>>>> [mailto:behave-bounces@ietf.org] On Behalf Of marcelo bagnulo braun
>>>> Sent: Wednesday, July 15, 2009 12:31 AM
>>>> To: Reinaldo Penno
>>>> Cc: Behave WG
>>>> Subject: Re: [BEHAVE] Comments
>>>> todraft-ietf-behave-v6v4-xlate-stateful-01.txt
>>>>=20
>>>> Reinaldo Penno escribi=F3:
>>>>>=20
>>>>> On 7/14/09 9:30 AM, "marcelo bagnulo braun"
>>>> <marcelo@it.uc3m.es> wrote:
>>>>>=20
>>>>>=20
>>>>>> Reinaldo Penno escribi=F3:
>>>>>>=20
>>>>>>> Hello,
>>>>>>>=20
>>>>>>> we should include how to handle TCP RSTs as well. Host
>>>> implementations and
>>>>>>> NATs might remove the tcpb (or binding) as soon as a RST
>>>> is received (as
>>>>>>> long as seq number checking passes).
>>>>>>>=20
>>>>>>>=20
>>>>>> but that would imply to keep track of all the seq # for
>>>> all the data
>>>>>> packets for each of the flows....
>>>>>> I don't think i would like to go there.
>>>>>>=20
>>>>>> In order to handle the RST packets, actually, i had
>>>> thought of that and
>>>>>> i included in the state machines, but it seems i forgot to
>>>> include in
>>>>>> the text...
>>>>>>=20
>>>>>> I think a RST coming from the Internet part should be
>>>> ignored, cause as
>>>>>> you say may be an attack, but i think that if the rst
>>>> packet comes from
>>>>>> the network side (the network that runs the nat64) then it
>>>> should be
>>>>>> honnoured.
>>>>>>=20
>>>>>=20
>>>>> After the connection is established, and the v4 side sends
>>>> a RST to end the
>>>>> connection and we do not honor it we will have hanging TCP
>>>> bindings. This is
>>>>> exactly what we were trying to avoid by being diligent on following
>>>>> FINs/ACKs and having timeouts.
>>>>=20
>>>> right, i guess the question is how often this happens.
>>>=20
>>> Martin Arlitt, Carey Williamson, "An Analysis of TCP Reset Behaviour on=
 the
>>> Internet", October, 2004,
>>> http://pages.cpsc.ucalgary.ca/~carey/papers/2005/TCP-Resets.pdf
>>>=20
>>> -d
>>>=20
>>>> I like Iljitshc suggestion of reducing the lifetime of the
>>>> binding when
>>>> a RST is seen, what do you think about that?
>>>>=20
>>>>> A TCP connection ended by RST is reused pretty quickly and
>>>> the issue I see
>>>>> if we do not honor valid TCP RST it is that we can end up
>>>> reusing a old
>>>>> binding and all kinds of problems can exist.
>>>>>=20
>>>>=20
>>>> I fail to see any problem here. I mean, if the new connection
>>>> uses the
>>>> same 5 tuple, then the state can be reused wihtout problem and if it
>>>> doesn't, then a new binding will be created, what is the problem that
>>>> you see?
>>>>> On the other hand, spoofed TCP packets can end the
>>>> connection and there are
>>>>> specific seq checks needed (different from connecting state
>>>> from established
>>>>> state).
>>>>>=20
>>>>>=20
>>>>=20
>>>> right, this is my concern
>>>>=20
>>>>>> what do you think?
>>>>>>=20
>>>>>=20
>>>>>=20
>>>>>>> Here, I think checking seq numbers is important for
>>>> security sake, specially
>>>>>>> in the case of TCP RSTs.
>>>>>>>=20
>>>>>>> As far as ICMP response to unsolicited SYNs which we
>>>> discussed before I
>>>>>>> suggest the following amendment to your text
>>>>>>>=20
>>>>>>> From
>>>>>>>=20
>>>>>>> " =A0 =A0 =A0If the destination transport address contained in
>>>> the incoming V4
>>>>>>> =A0 =A0 =A0 SYN is not in use in the TCP BIB, then the packet
>>>> is discarded and
>>>>>>> =A0 =A0 =A0 an ICMP Port Unreachable error (Type 3, Code 3) is
>>>> sent back to
>>>>>>> =A0 =A0 =A0 the source of the v4 SYN. =A0The state remains
>>>> unchanged in CLOSED"
>>>>>>>=20
>>>>>>> To
>>>>>>>=20
>>>>>>> " =A0 =A0 =A0If the destination transport address contained in
>>>> the incoming V4
>>>>>>> =A0 =A0 =A0 SYN is not in use in the TCP BIB, then the packet
>>>> is discarded and
>>>>>>> =A0 =A0 =A0 an ICMP Port Unreachable error (Type 3, Code 3) is
>>>> sent back to
>>>>>>> =A0 =A0 =A0 the source of the v4 SYN unless REQ-4a of RFC5382
>>>> applies. =A0The state
>>>>>>> =A0 =A0 =A0 remains unchanged in CLOSED"
>>>>>>>=20
>>>>>>>=20
>>>>>>>=20
>>>>>> right
>>>>>>=20
>>>>>> thanks, marcelo
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>>> Thanks,
>>>>>>>=20
>>>>>>> Reinaldo
>>>>>>>=20
>>>>>>>=20
>>>>>>> On 7/11/09 1:52 AM, "marcelo bagnulo braun"
>>>> <marcelo@it.uc3m.es> wrote:
>>>>>>>=20
>>>>>>>=20
>>>>>>>=20
>>>>>>>> Hi,
>>>>>>>>=20
>>>>>>>> We have posted a new version of the NAT64 draft.
>>>>>>>>=20
>>>>>>>> As discussed lately in the ml, we are using the FINs and
>>>> the SYNs to
>>>>>>>> close and establish the TCP session state in the NAT.
>>>>>>>>=20
>>>>>>>> The document still needs quite some work, but if people
>>>> can take a quick
>>>>>>>> look and let us know if the overall direction is ok, it
>>>> would be great.
>>>>>>>>=20
>>>>>>>> Thanks, marcelo
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>> -------- Mensaje original --------
>>>>>>>> Asunto: =A0 =A0 =A0 =A0 [BEHAVE] I-D
>>>>>>>> Action:draft-ietf-behave-v6v4-xlate-stateful-01.txt
>>>>>>>> Fecha: =A0Sat, 11 Jul 2009 01:45:01 -0700 (PDT)
>>>>>>>> De: =A0 =A0 Internet-Drafts@ietf.org
>>>>>>>> Para: =A0 i-d-announce@ietf.org
>>>>>>>> CC: =A0 =A0 behave@ietf.org
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>> 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.
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>> =A0 =A0 =A0 =A0 Title =A0 =A0 =A0 =A0 =A0 : NAT64: Network Address=
 and
>>>> Protocol Translation
>>>>>>>> from
>>>>>>>> IPv6 Clients to IPv4 Servers
>>>>>>>> =A0 =A0 =A0 =A0 Author(s) =A0 =A0 =A0 : M. Bagnulo, et al.
>>>>>>>> =A0 =A0 =A0 =A0 Filename =A0 =A0 =A0 =A0:
>>>> draft-ietf-behave-v6v4-xlate-stateful-01.txt
>>>>>>>> =A0 =A0 =A0 =A0 Pages =A0 =A0 =A0 =A0 =A0 : 35
>>>>>>>> =A0 =A0 =A0 =A0 Date =A0 =A0 =A0 =A0 =A0 =A0: 2009-07-11
>>>>>>>>=20
>>>>>>>> NAT64 is a mechanism for translating IPv6 packets to
>>>> IPv4 packets and
>>>>>>>> vice-versa. =A0DNS64 is a mechanism for synthesizing AAAA
>>>> records from
>>>>>>>> A records. =A0These two mechanisms together enable client-server
>>>>>>>> communication between an IPv6-only client and an
>>>> IPv4-only server,
>>>>>>>> without requiring any changes to either the IPv6 or the
>>>> IPv4 node,
>>>>>>>> for the class of applications that work through NATs. =A0They also
>>>>>>>> enable peer-to-peer communication between an IPv4 and an
>>>> IPv6 node,
>>>>>>>> where the communication can be initiated by either end using
>>>>>>>> existing, NAT-traversing, peer-to-peer communication techniques.
>>>>>>>> This document specifies NAT64, and gives suggestions on how they
>>>>>>>> should be deployed.
>>>>>>>>=20
>>>>>>>> A URL for this Internet-Draft is:
>>>>>>>>=20
>>>> http://www.ietf.org/internet-drafts/draft-ietf-behave-v6v4-xla
>>>> te-stateful-01
>>>>>>>> .t
>>>>>>>> xt
>>>>>>>>=20
>>>>>>>> Internet-Drafts are also available by anonymous FTP at:
>>>>>>>> ftp://ftp.ietf.org/internet-drafts/
>>>>>>>>=20
>>>>>>>> Below is the data which will enable a MIME compliant mail reader
>>>>>>>> implementation to automatically retrieve the ASCII version of the
>>>>>>>> Internet-Draft.
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>=20
>>>>>>>=20
>>>>>=20
>>>>>=20
>>>>>=20
>>>>=20
>>>> _______________________________________________
>>>> Behave mailing list
>>>> Behave@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/behave
>>>=20
>>=20
>> _______________________________________________
>> Behave mailing list
>> Behave@ietf.org
>> https://www.ietf.org/mailman/listinfo/behave
>>=20


From magnus.westerlund@ericsson.com  Thu Sep  3 15:17:51 2009
Return-Path: <magnus.westerlund@ericsson.com>
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 4130F28C120 for <behave@core3.amsl.com>; Thu,  3 Sep 2009 15:17:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.786
X-Spam-Level: 
X-Spam-Status: No, score=-5.786 tagged_above=-999 required=5 tests=[AWL=0.463,  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 nX4ojC3N2WNl for <behave@core3.amsl.com>; Thu,  3 Sep 2009 15:17:49 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62]) by core3.amsl.com (Postfix) with ESMTP id 2D7183A698D for <behave@ietf.org>; Thu,  3 Sep 2009 15:17:48 -0700 (PDT)
X-AuditID: c1b4fb3e-b7c00ae0000007bf-92-4a9fd1a71b1c
Received: from esealmw126.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw4.ericsson.se (Symantec Mail Security) with SMTP id 02.3F.01983.7A1DF9A4; Thu,  3 Sep 2009 16:24:40 +0200 (CEST)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.174]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 3 Sep 2009 16:24:39 +0200
Received: from [147.214.183.250] ([147.214.183.250]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 3 Sep 2009 16:24:39 +0200
Message-ID: <4A9FD1A7.8090209@ericsson.com>
Date: Thu, 03 Sep 2009 16:24:39 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Hadriel Kaplan <HKaplan@acmepacket.com>,  Cullen Jennings <fluffy@cisco.com>
References: <4A6D9D29.2050901@ericsson.com> <E6C2E8958BA59A4FB960963D475F7AC31984EBB0D6@mail>
In-Reply-To: <E6C2E8958BA59A4FB960963D475F7AC31984EBB0D6@mail>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-OriginalArrivalTime: 03 Sep 2009 14:24:39.0650 (UTC) FILETIME=[458A5C20:01CA2CA2]
X-Brightmail-Tracker: AAAAAA==
Cc: Tim Polk <tim.polk@nist.gov>, Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Discusses regarding security mechanism usage for TURN
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/mail-archive/web/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>
X-List-Received-Date: Thu, 03 Sep 2009 22:17:51 -0000

Hadriel Kaplan skrev:
> Can you summarize why you guys feel turning on TURN authentication would make an Enterprise any more willing to allow TURN through their firewall?
> 
> Maybe I'm not thinking clearly, but ISTM that an Enterprise would block TURN because they don't want their PC's opening permanent holes for "inbound" traffic.  The fact that a PC can prove it's known to a TURN server in the Internet - not owned by the Enterprise - does nothing to help the Enterprise feel safer, does it??  (did I miss something in TURN auth that actually cleared the evil-bit somehow?)

First of all TURN allocation on a TURN server does not allow inbound
traffic openly. The client must have installed a permission. Thus it can
only receive traffic from known peers, not anyone.

However, TURN servers that do not require using authentication of any
TURN clients request are vulnerable to attacks that allows the attacker
to install permissions. Thus enabling an attacker to send traffic to the
target on the inside.

Please do review the security consideration section and think about all
the attacks that are listed but said to be stopped by authentication.
They are all possible if authentication is not used.

Cheers

Magnus

> 
> -hadriel
> 
>> -----Original Message-----
>> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On Behalf
>> Of Magnus Westerlund
>> Sent: Monday, July 27, 2009 8:27 AM
>> To: Behave WG
>> Cc: Tim Polk
>> Subject: [BEHAVE] Discusses regarding security mechanism usage for TURN
>>
>> Behave WG,
>>
>> Cullen Jennings and Tim Polk each have a discuss on TURN on the same
>> basic issue. The issue is around what security functions must be used to
>> ensure that TURN operates in a secure and usable fashion. This has been
>> discussed a number of times if one reviews the list and minutes from
>> meetings. The last time was in April when Philip brought this up as a
>> result of these discusses. All three of us had some additional
>> discussion around the implications of the currently document MUST
>> implement SHOULD use authentication in the TURN specification. Our joint
>> view is that this appears too weak a recommendation from IETF around
>> usage of authentication for the TURN protocol. We therefore are strongly
>> proposing that TURN actually needs specify that one MUST use
>> authentication.
>>
>> The reasons we have for this proposal is directly related to the core of
>> TURN's purpose. The main usage of TURN will be with publicly reachable
>> relays. In most cases located outside of firewalls belonging to
>> companies, governmental agencies, private homes, etc. These firewalls
>> needs to have a certain trust in TURN so that they allow TURN to pass
>> through. The security vulnerabilities that exist with TURN if
>> authentication is not used, will prevent that trust to exist. As a
>> result we see that IETF only by publishing TURN saying SHOULD use
>> authentication rather than MUST use authentication has severe impact on
>> TURN's main purpose. We do note that the usage documented in TURN
>> (Version 16) that motivates the SHOULD appears to have acceptable
>> security. However, that usage is judged from our point of view to be a
>> marginal one, and the "SHOULD use" will open a hole for other usage with
>> less satisfying securities that we deem to be very serious.
>>
>> Thus we strongly urge the WG to discuss our views and recommendation to
>> sharpen the SHOULD use authentication to a MUST use authentication.
>> Magnus will make a decision based on any received input after two weeks
>> and present that to the discussing ADs.
>>
>> Best Regards
>>
>> Magnus Westerlund
>> Tim Polk
>> Cullen Jennings
>> _______________________________________________
>> Behave mailing list
>> Behave@ietf.org
>> https://www.ietf.org/mailman/listinfo/behave
> 


-- 

Magnus Westerlund

IETF Transport Area Director
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------

From Fred.L.Templin@boeing.com  Thu Sep  3 16:16:54 2009
Return-Path: <Fred.L.Templin@boeing.com>
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 593993A681D; Thu,  3 Sep 2009 16:16:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.949
X-Spam-Level: 
X-Spam-Status: No, score=-5.949 tagged_above=-999 required=5 tests=[AWL=0.650,  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 UOK-DrFgjQX0; Thu,  3 Sep 2009 16:16:53 -0700 (PDT)
Received: from slb-smtpout-01.boeing.com (slb-smtpout-01.boeing.com [130.76.64.48]) by core3.amsl.com (Postfix) with ESMTP id 7E65C3A687C; Thu,  3 Sep 2009 16:16:53 -0700 (PDT)
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4]) by slb-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id n83NDg8q027142 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 3 Sep 2009 16:13:42 -0700 (PDT)
Received: from slb-av-01.boeing.com (localhost [127.0.0.1]) by slb-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id n83NDgu2014474; Thu, 3 Sep 2009 16:13:42 -0700 (PDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com [130.247.55.84]) by slb-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id n83NDbws014339; Thu, 3 Sep 2009 16:13:42 -0700 (PDT)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 3 Sep 2009 16:13:28 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 3 Sep 2009 16:13:27 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1065D7921@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <003201ca2c3c$70c77460$d40c6f0a@china.huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Softwires] Some Thought about the Automatic Tunnel Address
Thread-Index: AcosPHCH+Xk9HqAuRLynwkG0AuOUTAArSSsg
References: <003201ca2c3c$70c77460$d40c6f0a@china.huawei.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Xu Xiaohu" <xuxh@huawei.com>, <softwires@ietf.org>, "Behave WG" <behave@ietf.org>
X-OriginalArrivalTime: 03 Sep 2009 23:13:28.0822 (UTC) FILETIME=[2599C960:01CA2CEC]
Subject: Re: [BEHAVE] [Softwires] Some Thought about the Automatic Tunnel Address
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/mail-archive/web/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>
X-List-Received-Date: Thu, 03 Sep 2009 23:16:54 -0000

Hi Xu,

> -----Original Message-----
> From: Xu Xiaohu [mailto:xuxh@huawei.com]
> Sent: Wednesday, September 02, 2009 7:16 PM
> To: softwires@ietf.org; 'Behave WG'
> Subject: [Softwires] Some Thought about the Automatic Tunnel Address
>=20
> Hi all,
>=20
> As quoted from "IPv6 Transition Mechanism" [RFC1933], "...The tunnel
> endpoint is the node to which the IPv6 packet is addressed.  Since the
> endpoint of the tunnel is the destination of the IPv6 packet, the
tunnel
> endpoint can be determined from the destination IPv6 address of that
packet:
> If that address is an IPv4-compatible address, then the low-order
32-bits
> hold the IPv4 address of the destination node, and that can be used as
the
> tunnel endpoint address."
>=20
> Unfortunately, the usage of IPv4-compatible address may cause routing
> scalability issue for IPv6 in practice when multiple sites use such
> addresses.
>=20
> The ISATAP (RFC5214) solves the above routing scalability issue with
the
> automatic tunneling address by concatenating a /64 LIR prefix and an
ISATAP
> interface ID (which is constructed in the Modified EUI-64) to generate
an
> IPv6 Global unicast address. I wonder whether it is better to directly
> concatenate a /96 LIR prefix (which can be learnt from the prefix
> information option in the RA message) and a 32-bit IPv4 address to
generate
> an IPv6 address. One obvious benefit of this method is IPv6 prefix
resource
> can be allocated in a more efficient way.

I floated the idea of a /96 for ISATAP during either an
intarea or ipv6 meeting several years ago (can't remember
which) but there was no uptake. Looking back, I don't see
any advantages, and in fact it goes against the model in
which IPv6 addresses beginning with other than '000' use
a 64-bit prefix. Indeed, ISATAP and SLAAC already fit
together naturally, and I see no reason to change that.=20
=20
> By the way, the IPv6 DAD action
> can also be avoided since the IPv4 address is already guaranteed to be
> unique.

This was left as a silent assumption in RFC5214, but it
is called out explicitly in VET.

Thanks - Fred
fred.l.templin@boeing.com

>=20
> Xiaohu
>=20
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires

From xuxh@huawei.com  Thu Sep  3 20:43:11 2009
Return-Path: <xuxh@huawei.com>
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 759F63A67AB; Thu,  3 Sep 2009 20:43:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.276
X-Spam-Level: *
X-Spam-Status: No, score=1.276 tagged_above=-999 required=5 tests=[AWL=1.771,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  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 B6FyP8UIbKaZ; Thu,  3 Sep 2009 20:43:04 -0700 (PDT)
Received: from szxga01-in.huawei.com (unknown [119.145.14.64]) by core3.amsl.com (Postfix) with ESMTP id D150C3A697E; Thu,  3 Sep 2009 20:43:03 -0700 (PDT)
Received: from huawei.com (szxga01-in [172.24.2.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KPF005UWDEMQO@szxga01-in.huawei.com>; Fri, 04 Sep 2009 10:25:34 +0800 (CST)
Received: from huawei.com ([172.24.1.24]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KPF00ANEDEMCT@szxga01-in.huawei.com>; Fri, 04 Sep 2009 10:25:34 +0800 (CST)
Received: from HUAWEIE75F8F11 ([10.111.12.212]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KPF001BXDEK9B@szxml04-in.huawei.com>; Fri, 04 Sep 2009 10:25:34 +0800 (CST)
Date: Fri, 04 Sep 2009 10:25:32 +0800
From: Xu Xiaohu <xuxh@huawei.com>
In-reply-to: <39C363776A4E8C4A94691D2BD9D1C9A1065D7921@XCH-NW-7V2.nw.nos.boeing.com>
To: "'Templin, Fred L'" <Fred.L.Templin@boeing.com>, softwires@ietf.org, 'Behave WG' <behave@ietf.org>
Message-id: <001c01ca2d06$fa6ef5b0$d40c6f0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: AcosPHCH+Xk9HqAuRLynwkG0AuOUTAArSSsgAAYsBdA=
Subject: Re: [BEHAVE] [Softwires] Some Thought about the Automatic Tunnel Address
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/mail-archive/web/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>
X-List-Received-Date: Fri, 04 Sep 2009 03:43:11 -0000

Hi Templin,

> > The ISATAP (RFC5214) solves the above routing scalability issue with
> the
> > automatic tunneling address by concatenating a /64 LIR prefix and an
> ISATAP
> > interface ID (which is constructed in the Modified EUI-64) to generate
> an
> > IPv6 Global unicast address. I wonder whether it is better to directly
> > concatenate a /96 LIR prefix (which can be learnt from the prefix
> > information option in the RA message) and a 32-bit IPv4 address to
> generate
> > an IPv6 address. One obvious benefit of this method is IPv6 prefix
> resource
> > can be allocated in a more efficient way.
> 
> I floated the idea of a /96 for ISATAP during either an
> intarea or ipv6 meeting several years ago (can't remember
> which) but there was no uptake. Looking back, I don't see
> any advantages, and in fact it goes against the model in
> which IPv6 addresses beginning with other than '000' use
> a 64-bit prefix. 

Yes, I also noticed the above specification defined in RFC4291 as "... for
all unicast addresses, except those that start with the binary value 000,
Interface IDs are required to be 64 bits long and to be constructed in
Modified EUI-64 format". However, I don't know what the real meaning of such
constraint is in practice. Can anybody kindly help me understanding this?

> Indeed, ISATAP and SLAAC already fit
> together naturally, and I see no reason to change that.

Yes, I agree with your opinion to some extent. It seems too early to
consider how to use the IPv6 address resource in an efficiently way.
However, the Internet history is, at the initial stage of the Internet
deployment, seldom people thought about CIDR since most people believed the
IPv4 address is most enough for use in the future. Unfortunately, the
reality is beyond most people's expectations. Maybe the same problem will
not happen on IPv6.

Xiaohu

> > By the way, the IPv6 DAD action
> > can also be avoided since the IPv4 address is already guaranteed to be
> > unique.
> 
> This was left as a silent assumption in RFC5214, but it
> is called out explicitly in VET.
> 
> Thanks - Fred
> fred.l.templin@boeing.com
> 
> >
> > Xiaohu
> >
> > _______________________________________________
> > Softwires mailing list
> > Softwires@ietf.org
> > https://www.ietf.org/mailman/listinfo/softwires


From xuxh@huawei.com  Mon Sep  7 21:16:52 2009
Return-Path: <xuxh@huawei.com>
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 E44203A681D; Mon,  7 Sep 2009 21:16:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.535
X-Spam-Level: **
X-Spam-Status: No, score=2.535 tagged_above=-999 required=5 tests=[AWL=0.430,  BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  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 lG0VRNRlGMcE; Mon,  7 Sep 2009 21:16:52 -0700 (PDT)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id 0A28A3A67B0; Mon,  7 Sep 2009 21:16:52 -0700 (PDT)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KPM00CMFX8MM4@szxga03-in.huawei.com>; Tue, 08 Sep 2009 12:17:10 +0800 (CST)
Received: from huawei.com ([172.24.1.33]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KPM00MPKX8LOF@szxga03-in.huawei.com>; Tue, 08 Sep 2009 12:17:10 +0800 (CST)
Received: from HUAWEIE75F8F11 ([10.111.12.212]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KPM00GCJX8LLF@szxml06-in.huawei.com>; Tue, 08 Sep 2009 12:17:09 +0800 (CST)
Date: Tue, 08 Sep 2009 12:17:09 +0800
From: Xu Xiaohu <xuxh@huawei.com>
In-reply-to: <39C363776A4E8C4A94691D2BD9D1C9A1065D7921@XCH-NW-7V2.nw.nos.boeing.com>
To: "'Templin, Fred L'" <Fred.L.Templin@boeing.com>, softwires@ietf.org, 'Behave WG' <behave@ietf.org>
Message-id: <000701ca303b$3bc26600$d40c6f0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: AcosPHCH+Xk9HqAuRLynwkG0AuOUTAArSSsgANRGurA=
Subject: Re: [BEHAVE] [Softwires] Some Thought about the Automatic Tunnel Address
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/mail-archive/web/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>
X-List-Received-Date: Tue, 08 Sep 2009 04:16:53 -0000

> I floated the idea of a /96 for ISATAP during either an
> intarea or ipv6 meeting several years ago (can't remember
> which) but there was no uptake. Looking back, I don't see
> any advantages, and in fact it goes against the model in
> which IPv6 addresses beginning with other than '000' use
> a 64-bit prefix. 

What's the real purpose of the above model (IPv6 addresses beginning with
other than '000' use a 64-bit prefix)? Can somebody help explain it?

Thanks,
Xiaohu


From caozhenpku@gmail.com  Tue Sep  8 06:45:40 2009
Return-Path: <caozhenpku@gmail.com>
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 DC1E228C161 for <behave@core3.amsl.com>; Tue,  8 Sep 2009 06:45:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.39
X-Spam-Level: 
X-Spam-Status: No, score=-2.39 tagged_above=-999 required=5 tests=[AWL=0.208,  BAYES_00=-2.599, HTML_MESSAGE=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 ykkWRzQmHNit for <behave@core3.amsl.com>; Tue,  8 Sep 2009 06:45:40 -0700 (PDT)
Received: from mail-vw0-f201.google.com (mail-vw0-f201.google.com [209.85.212.201]) by core3.amsl.com (Postfix) with ESMTP id A805228C201 for <behave@ietf.org>; Tue,  8 Sep 2009 06:45:11 -0700 (PDT)
Received: by vws39 with SMTP id 39so8363vws.29 for <behave@ietf.org>; Tue, 08 Sep 2009 06:45:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=nIyXDwD46xYtfVH7eHLvYhoYBbf6stf0UmD+roFO+Nw=; b=ZpD+jQhD/yxF3AOkJgTFT8NNsfSP6lDOhR2u2QlIRdmE8NJG9EQqRUQXvc89ym1xLq 2eRrYwk9ba7x28V1oiKOzXaMBNW0SBJbUuu26QvSM3nyR2IQo94Zp+FuG/1WhrNaWFRR OksvjMoSKdt/QnAz9cz4ssBmG5N/k0kpJFzWE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=A5fjPRj90ZZ6lfOtfoLue4zvb2ilwGm8/Lz+JG/xU66PMVrDEa3JduYR+0FPWfnbYp 1bXX7ysktS76I3kaYzcCNZf9c0vL+eIFHUMsYsjEwlU3W//HU8GX/c8qWzWf8O40PKTf qAzzx5VcaTmCwpWvPxAND4wd6x/y6z9IPafjI=
MIME-Version: 1.0
Received: by 10.220.68.155 with SMTP id v27mr5634624vci.32.1252417537345; Tue,  08 Sep 2009 06:45:37 -0700 (PDT)
Date: Tue, 8 Sep 2009 21:45:37 +0800
Message-ID: <a7c8d0a30909080645t342f7bd7udfc553c0303f25ff@mail.gmail.com>
From: Zhen Cao <caozhenpku@gmail.com>
To: Dave Thaler <dthaler@microsoft.com>, Behave WG <behave@ietf.org>
Content-Type: multipart/alternative; boundary=0016363b7cfe6c8d0b0473112e18
Subject: [BEHAVE] Stateless translation definition
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/mail-archive/web/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>
X-List-Received-Date: Tue, 08 Sep 2009 13:45:41 -0000

--0016363b7cfe6c8d0b0473112e18
Content-Type: text/plain; charset=ISO-8859-1

Hi Dave and all,

I have a concern with respect to the definition of stateful/stateless
translation. Could you help me? Thanks in advance.

The framework draft defines stateful translation as:

*A translation algorithm may be said to
"require state in a network element" or be "stateful" if the
transmission or reception of a packet creates or modifies a data
structure in the relevant network element.*


According to this definition, say, if hosts are configured with a public
IPv4 address in the host-based translation
(draft-huang-pnat-host-ipv6-02), and the used local prefix is unique, then
the translation on prefix-nat will NOT create or modify any data structure.
Can we call it stateless translation?
Thanks for your help.

Best regards,
Zhen

--0016363b7cfe6c8d0b0473112e18
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<span class=3D"Apple-style-span" style=3D"font-size: small;">Hi Dave and al=
l, <br><br>I have a concern with respect to the definition of stateful/stat=
eless translation. Could you help me? Thanks in advance.=A0<br><br>The fram=
ework draft defines stateful translation as: <br>
</span><blockquote class=3D"webkit-indent-blockquote" style=3D"margin: 0 0 =
0 40px; border: none; padding: 0px;"><i><span class=3D"Apple-style-span" st=
yle=3D"font-size: small;">A translation algorithm may be said to<br>&quot;r=
equire state in a network element&quot; or be &quot;stateful&quot; if the<b=
r>
transmission or reception of a packet creates or modifies a data<br>structu=
re in the relevant network element.</span></i></blockquote><span class=3D"A=
pple-style-span" style=3D"font-size: small;"><br>According to this definiti=
on, say, if hosts are configured with a public IPv4 address in the host-bas=
ed translation (draft-huang-pnat-host-ipv6-02),=A0and the used local prefix=
 is unique, then the translation on prefix-nat will NOT create or modify an=
y data structure. Can we call it stateless translation?=A0</span><div>
<span class=3D"Apple-style-span" style=3D"font-size: small;"><br></span></d=
iv><div><span class=3D"Apple-style-span" style=3D"font-size: small;">Thanks=
 for your help.=A0</span></div><div><span class=3D"Apple-style-span" style=
=3D"font-size: small;"><br>
</span></div><div><span class=3D"Apple-style-span" style=3D"font-size: smal=
l;">Best regards,</span></div><div><span class=3D"Apple-style-span" style=
=3D"font-size: small;">Zhen</span></div>

--0016363b7cfe6c8d0b0473112e18--

From dwing@cisco.com  Tue Sep  8 09:18:03 2009
Return-Path: <dwing@cisco.com>
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 894403A6A8F for <behave@core3.amsl.com>; Tue,  8 Sep 2009 09:18:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.389
X-Spam-Level: 
X-Spam-Status: No, score=-6.389 tagged_above=-999 required=5 tests=[AWL=0.210,  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 hyMDEccv4nuK for <behave@core3.amsl.com>; Tue,  8 Sep 2009 09:18:02 -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 AF3F93A6A2C for <behave@ietf.org>; Tue,  8 Sep 2009 09:18:02 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Aq8EAEshpkqrR7MV/2dsb2JhbACLGrsEiEMBj14FhBiBWQ
X-IronPort-AV: E=Sophos;i="4.44,353,1249257600"; d="scan'208";a="202584838"
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-2.cisco.com with ESMTP; 08 Sep 2009 16:18:31 +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 n88GIVwU022965;  Tue, 8 Sep 2009 09:18:31 -0700
Received: from dwingwxp01 ([10.32.240.198]) by sj-core-4.cisco.com (8.13.8/8.14.3) with ESMTP id n88GIVKh021531; Tue, 8 Sep 2009 16:18:31 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Zhen Cao'" <caozhenpku@gmail.com>, "'Dave Thaler'" <dthaler@microsoft.com>, "'Behave WG'" <behave@ietf.org>
References: <a7c8d0a30909080645t342f7bd7udfc553c0303f25ff@mail.gmail.com>
Date: Tue, 8 Sep 2009 09:18:31 -0700
Message-ID: <09f701ca30a0$01e90730$c5f0200a@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Acowir7oObZv+786S7mgXQW9/FTiqwAFPkFQ
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
In-Reply-To: <a7c8d0a30909080645t342f7bd7udfc553c0303f25ff@mail.gmail.com>
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1439; t=1252426712; x=1253290712; 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]=20Stateless=20translation=20de finition |Sender:=20; bh=JmX75opRmjwuOztGjkbuyL5g99CYdMHVwvrzjQqXo8c=; b=rkh3uA3XXgnARmi1n5CSstR30Sg7E9SEftdRTkHd4OpJdNQ5ms203hV+ZX YKY546md9/krctd0X2vbEbbyziCCHHgg07JXdgS8Jz6KC4kHPb6QaPWRSgx9 FzL9gLH8jBERCnOjHt1vCwKRWbIuriwdpIQMcPgHXvZGTEwEknI0k=;
Authentication-Results: sj-dkim-1; header.From=dwing@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; ); 
Subject: Re: [BEHAVE] Stateless translation definition
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/mail-archive/web/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>
X-List-Received-Date: Tue, 08 Sep 2009 16:18:03 -0000

 

> -----Original Message-----
> From: behave-bounces@ietf.org 
> [mailto:behave-bounces@ietf.org] On Behalf Of Zhen Cao
> Sent: Tuesday, September 08, 2009 6:46 AM
> To: Dave Thaler; Behave WG
> Subject: [BEHAVE] Stateless translation definition
> 
> Hi Dave and all, 
> 
> I have a concern with respect to the definition of 
> stateful/stateless translation. Could you help me? Thanks in advance. 
> 
> The framework draft defines stateful translation as: 
> 
> 
> 	A translation algorithm may be said to
> 	"require state in a network element" or be "stateful" if the
> 	transmission or reception of a packet creates or modifies a data
> 	structure in the relevant network element.
> 
> 
> According to this definition, say, if hosts are configured 
> with a public IPv4 address in the host-based translation 
> (draft-huang-pnat-host-ipv6-02), and the used local prefix is 
> unique, then the translation on prefix-nat will NOT create or 
> modify any data structure. Can we call it stateless translation? 

Yes, that would be stateless translation on the network-based 
NAT device.

However, there is stateful translation in the host device:  
specifically, a DNS query creates state inside of the host's
stack (that state maps IPv4 to IPv6).

So the system, as a whole, is not stateless or stateful.  It
is both.

-d


> 
> 
> Thanks for your help. 
> 
> 
> Best regards,
> Zhen
> 


From root@core3.amsl.com  Tue Sep  8 18:30:03 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: behave@ietf.org
Delivered-To: behave@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 369F43A69B5; Tue,  8 Sep 2009 18:30: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: <20090909013003.369F43A69B5@core3.amsl.com>
Date: Tue,  8 Sep 2009 18:30:02 -0700 (PDT)
Cc: behave@ietf.org
Subject: [BEHAVE] I-D Action:draft-ietf-behave-v6v4-framework-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/mail-archive/web/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>
X-List-Received-Date: Wed, 09 Sep 2009 01:30:03 -0000

--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           : Framework for IPv4/IPv6 Translation
	Author(s)       : F. Baker, et al.
	Filename        : draft-ietf-behave-v6v4-framework-01.txt
	Pages           : 31
	Date            : 2009-09-08

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.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-behave-v6v4-framework-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
Content-Type: Message/External-body;
	name="draft-ietf-behave-v6v4-framework-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From xing@cernet.edu.cn  Tue Sep  8 18:36:50 2009
Return-Path: <xing@cernet.edu.cn>
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 8BF853A68DF for <behave@core3.amsl.com>; Tue,  8 Sep 2009 18:36:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.822
X-Spam-Level: *
X-Spam-Status: No, score=1.822 tagged_above=-999 required=5 tests=[AWL=-0.875,  BAYES_50=0.001, FH_HAS_XAIMC=2.696]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wZy0dAOGq0Ea for <behave@core3.amsl.com>; Tue,  8 Sep 2009 18:36:49 -0700 (PDT)
Received: from cernet.edu.cn (sea.net.edu.cn [202.112.3.66]) by core3.amsl.com (Postfix) with SMTP id 43AE13A6B19 for <behave@ietf.org>; Tue,  8 Sep 2009 18:36:48 -0700 (PDT)
Received: from [59.66.24.75]([59.66.24.75]) by cernet.edu.cn(AIMC 3.2.0.0) with SMTP id jm254aa76196; Wed, 09 Sep 2009 09:37:18 +0800
Message-ID: <4AA706C2.6020804@cernet.edu.cn>
Date: Wed, 09 Sep 2009 09:37:06 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: 'Behave WG' <behave@ietf.org>, Kevin Yin <kyin@cisco.com>
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: 7bit
X-AIMC-AUTH: xing
X-AIMC-MAILFROM: xing@cernet.edu.cn
X-AIMC-Msg-ID: q8aHMlWB
Cc: congxiao <congxiao@cernet.edu.cn>, Xing Li <xing@cernet.edu.cn>, Fred Baker <fred@cisco.com>
Subject: [BEHAVE] draft-ietf-behave-v6v4-framework-01 uploaded
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/mail-archive/web/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>
X-List-Received-Date: Wed, 09 Sep 2009 01:36:50 -0000

Hi, All,

Based on Dave's comment, the discussions in the mailing list and the
meeting notes of IETF75, the authors have made the modifications and
uploaded the 01 version of the Framework for IPv4/IPv6 Translation. Here
are some editorial notes.

(1) Most of the grammar and spelling errors are corrected.

(2) Terminology (Sec 1.2): Since the terminologies are not consistent in
the current translation related documents. We will compile a list of the
terminology and send to the behave@ietf.org to get the consensus before
we modify the related documents.

(3) Address Translation (Sec. 3.1.1, etc): The discussion will be move
to the address format document and we will insert the conclusion in the
framework document later.

Please review this version and send your comments and suggestions, so we
can edit the next version.

Regards,

xing






From dwing@cisco.com  Tue Sep  8 19:08:30 2009
Return-Path: <dwing@cisco.com>
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 DEF2F3A68C7 for <behave@core3.amsl.com>; Tue,  8 Sep 2009 19:08:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.505
X-Spam-Level: 
X-Spam-Status: No, score=-6.505 tagged_above=-999 required=5 tests=[AWL=-0.221, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_MILLIONSOF=0.315]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OQ987bXHuDcV for <behave@core3.amsl.com>; Tue,  8 Sep 2009 19:08:28 -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 DFF1028C269 for <behave@ietf.org>; Tue,  8 Sep 2009 19:08:28 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AsAEAJ6rpkqrR7PD/2dsb2JhbACLGroniEMBkCEFgiiBcIFZ
X-IronPort-AV: E=Sophos;i="4.44,355,1249257600"; d="scan'208";a="202787807"
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-2.cisco.com with ESMTP; 09 Sep 2009 02:09:00 +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 n89290jX028575;  Tue, 8 Sep 2009 19:09:00 -0700
Received: from dwingwxp01 ([10.32.240.198]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n8928wuW010553; Wed, 9 Sep 2009 02:08:58 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Reinaldo Penno'" <rpenno@juniper.net>, "'Zhen Cao'" <caozhenpku@gmail.com>
References: <a7c8d0a30909030701v47ea212bi7210ecfe005758e9@mail.gmail.com> <C6C54E63.36D5C%rpenno@juniper.net>
Date: Tue, 8 Sep 2009 19:08:58 -0700
Message-ID: <024501ca30f2$7e6e09c0$c6f0200a@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcosnwpkMBQmSOO6SPaBgsLJEyNrDAAHwxRGAQz7VIA=
In-Reply-To: <C6C54E63.36D5C%rpenno@juniper.net>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=11685; t=1252462140; x=1253326140; 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]=20NAT64=20and=20TCP=20processi ng=20(was=20Re=3A=20Comments=20=20todraft-ietf-behave-v6v4-x late-stateful-01.txt) |Sender:=20; bh=848TVJBi9+SjDIY4N/EalBgWQpOKDNXR9nrBYGc4m84=; b=EOr142NcrHdlwyyqaBJv7jhRq6s1yD+X+37apKhE0OP46+iAuMDtMbJRA4 vldHBHZxWqKFasEsXEaaVYCj+loJHiU63G8dXBbNk0+Ooq52ViCan9pBA2H8 GaJhRVZJSz;
Authentication-Results: sj-dkim-3; header.From=dwing@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; ); 
Cc: 'Behave WG' <behave@ietf.org>
Subject: Re: [BEHAVE] NAT64 and TCP processing (was Re: Comments todraft-ietf-behave-v6v4-xlate-stateful-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/mail-archive/web/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>
X-List-Received-Date: Wed, 09 Sep 2009 02:08:31 -0000

=20

> -----Original Message-----
> From: Reinaldo Penno [mailto:rpenno@juniper.net]=20
> Sent: Thursday, September 03, 2009 10:44 AM
> To: Zhen Cao
> Cc: Dan Wing; marcelo bagnulo braun; Behave WG
> Subject: Re: [BEHAVE] NAT64 and TCP processing (was Re:=20
> Comments todraft-ietf-behave-v6v4-xlate-stateful-01.txt)
>=20
> No, in general the area where TCP, NAT44 and security=20
> intersect is very
> light on standards.
>=20
> There are comments in BEHAVE NAT TCP (NAT Session Refresh=20
> section) about how
> a NAT can detect if a connection is still alive by sending=20
> TCP keep alive
> packets (which require some seq/ack tracking).
>=20
> I would venture to say TCP tracking is probably the de facto=20
> standard due to
> ALGs, security and others, but it is something tricky to=20
> standardize.=20

BEHAVE's published RFCs related to NAT44 did not attempt to
define new behavior, as it was regarded as pointless to do
so:  NATs exist, they do what they do, and so on.

For new things, such as stateful IPv6/IPv4 translation, we
are ahead of the curve.  There are not millions of IPv6/IPv4
translators deployed on the Internet.

> NAT64
> current draft relies on a series of timers.
>=20
> I wanted to bring this issue forth again after I read the=20
> references since
> there was some doubt regarding attacks, percentage of=20
> connections that end
> 'nicely', other standards within IETF, etc.
>=20
> Whatever method(s) we go with NAT64, the security and performance
> implications need to be well-understood.

Agreed. =20

I hope we can continue a discussion regarding the tradeoffs and
incorporate the discussion into the document so that implementors
receive useful guidance from the peer review of the IETF standards
process!  :-)

-d


> Thanks,
>=20
>=20
> On 9/3/09 7:01 AM, "Zhen Cao" <caozhenpku@gmail.com> wrote:
>=20
> > Hi Reinaldo,
> >=20
> > The issue you raise here is interesting. As you said, the NAT44
> > implementation already track TCP seq number. Is it mandated in the
> > NAT44 standard documents?
> >=20
> > Thanks,
> > Zhen
> >=20
> > On Wed, Sep 2, 2009 at 2:47 AM, Reinaldo=20
> Penno<rpenno@juniper.net> wrote:
> >> Hello,
> >>=20
> >> I read the paper reference by Dan below and the number of=20
> TCP connections
> >> that end with TCP RST is significant.
> >>=20
> >>> Martin Arlitt, Carey Williamson, "An Analysis of TCP=20
> Reset Behaviour on the
> >>> Internet", October, 2004,
> >>> http://pages.cpsc.ucalgary.ca/~carey/papers/2005/TCP-Resets.pdf
> >>=20
> >> Also, there is this draft which is categorized as=20
> standards track and talks
> >> about the many issues related to TCP window attacks and most of the
> >> mitigations discussed require TCP sequence tracking.
> >>=20
> >> http://www.ietf.org/id/draft-ietf-tcpm-tcpsecure-11.txt
> >>=20
> >> The issues found here are not exclusive of NAT64, NAT44=20
> would suffer the
> >> same problems. But most NAT44 implementations today=20
> already track sequence
> >> numbers whether due to security concerns or ALGs.
> >>=20
> >> Thanks,
> >>=20
> >> Reinaldo
> >>=20
> >> On 7/15/09 12:34 PM, "Dan Wing" <dwing@cisco.com> wrote:
> >>=20
> >>>=20
> >>>=20
> >>>> -----Original Message-----
> >>>> From: behave-bounces@ietf.org
> >>>> [mailto:behave-bounces@ietf.org] On Behalf Of marcelo=20
> bagnulo braun
> >>>> Sent: Wednesday, July 15, 2009 12:31 AM
> >>>> To: Reinaldo Penno
> >>>> Cc: Behave WG
> >>>> Subject: Re: [BEHAVE] Comments
> >>>> todraft-ietf-behave-v6v4-xlate-stateful-01.txt
> >>>>=20
> >>>> Reinaldo Penno escribi=F3:
> >>>>>=20
> >>>>> On 7/14/09 9:30 AM, "marcelo bagnulo braun"
> >>>> <marcelo@it.uc3m.es> wrote:
> >>>>>=20
> >>>>>=20
> >>>>>> Reinaldo Penno escribi=F3:
> >>>>>>=20
> >>>>>>> Hello,
> >>>>>>>=20
> >>>>>>> we should include how to handle TCP RSTs as well. Host
> >>>> implementations and
> >>>>>>> NATs might remove the tcpb (or binding) as soon as a RST
> >>>> is received (as
> >>>>>>> long as seq number checking passes).
> >>>>>>>=20
> >>>>>>>=20
> >>>>>> but that would imply to keep track of all the seq # for
> >>>> all the data
> >>>>>> packets for each of the flows....
> >>>>>> I don't think i would like to go there.
> >>>>>>=20
> >>>>>> In order to handle the RST packets, actually, i had
> >>>> thought of that and
> >>>>>> i included in the state machines, but it seems i forgot to
> >>>> include in
> >>>>>> the text...
> >>>>>>=20
> >>>>>> I think a RST coming from the Internet part should be
> >>>> ignored, cause as
> >>>>>> you say may be an attack, but i think that if the rst
> >>>> packet comes from
> >>>>>> the network side (the network that runs the nat64) then it
> >>>> should be
> >>>>>> honnoured.
> >>>>>>=20
> >>>>>=20
> >>>>> After the connection is established, and the v4 side sends
> >>>> a RST to end the
> >>>>> connection and we do not honor it we will have hanging TCP
> >>>> bindings. This is
> >>>>> exactly what we were trying to avoid by being diligent=20
> on following
> >>>>> FINs/ACKs and having timeouts.
> >>>>=20
> >>>> right, i guess the question is how often this happens.
> >>>=20
> >>> Martin Arlitt, Carey Williamson, "An Analysis of TCP=20
> Reset Behaviour on the
> >>> Internet", October, 2004,
> >>> http://pages.cpsc.ucalgary.ca/~carey/papers/2005/TCP-Resets.pdf
> >>>=20
> >>> -d
> >>>=20
> >>>> I like Iljitshc suggestion of reducing the lifetime of the
> >>>> binding when
> >>>> a RST is seen, what do you think about that?
> >>>>=20
> >>>>> A TCP connection ended by RST is reused pretty quickly and
> >>>> the issue I see
> >>>>> if we do not honor valid TCP RST it is that we can end up
> >>>> reusing a old
> >>>>> binding and all kinds of problems can exist.
> >>>>>=20
> >>>>=20
> >>>> I fail to see any problem here. I mean, if the new connection
> >>>> uses the
> >>>> same 5 tuple, then the state can be reused wihtout=20
> problem and if it
> >>>> doesn't, then a new binding will be created, what is the=20
> problem that
> >>>> you see?
> >>>>> On the other hand, spoofed TCP packets can end the
> >>>> connection and there are
> >>>>> specific seq checks needed (different from connecting state
> >>>> from established
> >>>>> state).
> >>>>>=20
> >>>>>=20
> >>>>=20
> >>>> right, this is my concern
> >>>>=20
> >>>>>> what do you think?
> >>>>>>=20
> >>>>>=20
> >>>>>=20
> >>>>>>> Here, I think checking seq numbers is important for
> >>>> security sake, specially
> >>>>>>> in the case of TCP RSTs.
> >>>>>>>=20
> >>>>>>> As far as ICMP response to unsolicited SYNs which we
> >>>> discussed before I
> >>>>>>> suggest the following amendment to your text
> >>>>>>>=20
> >>>>>>> From
> >>>>>>>=20
> >>>>>>> " =A0 =A0 =A0If the destination transport address contained in
> >>>> the incoming V4
> >>>>>>> =A0 =A0 =A0 SYN is not in use in the TCP BIB, then the packet
> >>>> is discarded and
> >>>>>>> =A0 =A0 =A0 an ICMP Port Unreachable error (Type 3, Code 3) is
> >>>> sent back to
> >>>>>>> =A0 =A0 =A0 the source of the v4 SYN. =A0The state remains
> >>>> unchanged in CLOSED"
> >>>>>>>=20
> >>>>>>> To
> >>>>>>>=20
> >>>>>>> " =A0 =A0 =A0If the destination transport address contained in
> >>>> the incoming V4
> >>>>>>> =A0 =A0 =A0 SYN is not in use in the TCP BIB, then the packet
> >>>> is discarded and
> >>>>>>> =A0 =A0 =A0 an ICMP Port Unreachable error (Type 3, Code 3) is
> >>>> sent back to
> >>>>>>> =A0 =A0 =A0 the source of the v4 SYN unless REQ-4a of RFC5382
> >>>> applies. =A0The state
> >>>>>>> =A0 =A0 =A0 remains unchanged in CLOSED"
> >>>>>>>=20
> >>>>>>>=20
> >>>>>>>=20
> >>>>>> right
> >>>>>>=20
> >>>>>> thanks, marcelo
> >>>>>>=20
> >>>>>>=20
> >>>>>>=20
> >>>>>>> Thanks,
> >>>>>>>=20
> >>>>>>> Reinaldo
> >>>>>>>=20
> >>>>>>>=20
> >>>>>>> On 7/11/09 1:52 AM, "marcelo bagnulo braun"
> >>>> <marcelo@it.uc3m.es> wrote:
> >>>>>>>=20
> >>>>>>>=20
> >>>>>>>=20
> >>>>>>>> Hi,
> >>>>>>>>=20
> >>>>>>>> We have posted a new version of the NAT64 draft.
> >>>>>>>>=20
> >>>>>>>> As discussed lately in the ml, we are using the FINs and
> >>>> the SYNs to
> >>>>>>>> close and establish the TCP session state in the NAT.
> >>>>>>>>=20
> >>>>>>>> The document still needs quite some work, but if people
> >>>> can take a quick
> >>>>>>>> look and let us know if the overall direction is ok, it
> >>>> would be great.
> >>>>>>>>=20
> >>>>>>>> Thanks, marcelo
> >>>>>>>>=20
> >>>>>>>>=20
> >>>>>>>> -------- Mensaje original --------
> >>>>>>>> Asunto: =A0 =A0 =A0 =A0 [BEHAVE] I-D
> >>>>>>>> Action:draft-ietf-behave-v6v4-xlate-stateful-01.txt
> >>>>>>>> Fecha: =A0Sat, 11 Jul 2009 01:45:01 -0700 (PDT)
> >>>>>>>> De: =A0 =A0 Internet-Drafts@ietf.org
> >>>>>>>> Para: =A0 i-d-announce@ietf.org
> >>>>>>>> CC: =A0 =A0 behave@ietf.org
> >>>>>>>>=20
> >>>>>>>>=20
> >>>>>>>>=20
> >>>>>>>> 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.
> >>>>>>>>=20
> >>>>>>>>=20
> >>>>>>>> =A0 =A0 =A0 =A0 Title =A0 =A0 =A0 =A0 =A0 : NAT64: Network =
Address and
> >>>> Protocol Translation
> >>>>>>>> from
> >>>>>>>> IPv6 Clients to IPv4 Servers
> >>>>>>>> =A0 =A0 =A0 =A0 Author(s) =A0 =A0 =A0 : M. Bagnulo, et al.
> >>>>>>>> =A0 =A0 =A0 =A0 Filename =A0 =A0 =A0 =A0:
> >>>> draft-ietf-behave-v6v4-xlate-stateful-01.txt
> >>>>>>>> =A0 =A0 =A0 =A0 Pages =A0 =A0 =A0 =A0 =A0 : 35
> >>>>>>>> =A0 =A0 =A0 =A0 Date =A0 =A0 =A0 =A0 =A0 =A0: 2009-07-11
> >>>>>>>>=20
> >>>>>>>> NAT64 is a mechanism for translating IPv6 packets to
> >>>> IPv4 packets and
> >>>>>>>> vice-versa. =A0DNS64 is a mechanism for synthesizing AAAA
> >>>> records from
> >>>>>>>> A records. =A0These two mechanisms together enable=20
> client-server
> >>>>>>>> communication between an IPv6-only client and an
> >>>> IPv4-only server,
> >>>>>>>> without requiring any changes to either the IPv6 or the
> >>>> IPv4 node,
> >>>>>>>> for the class of applications that work through=20
> NATs. =A0They also
> >>>>>>>> enable peer-to-peer communication between an IPv4 and an
> >>>> IPv6 node,
> >>>>>>>> where the communication can be initiated by either end using
> >>>>>>>> existing, NAT-traversing, peer-to-peer communication=20
> techniques.
> >>>>>>>> This document specifies NAT64, and gives suggestions=20
> on how they
> >>>>>>>> should be deployed.
> >>>>>>>>=20
> >>>>>>>> A URL for this Internet-Draft is:
> >>>>>>>>=20
> >>>> http://www.ietf.org/internet-drafts/draft-ietf-behave-v6v4-xla
> >>>> te-stateful-01
> >>>>>>>> .t
> >>>>>>>> xt
> >>>>>>>>=20
> >>>>>>>> Internet-Drafts are also available by anonymous FTP at:
> >>>>>>>> ftp://ftp.ietf.org/internet-drafts/
> >>>>>>>>=20
> >>>>>>>> Below is the data which will enable a MIME compliant=20
> mail reader
> >>>>>>>> implementation to automatically retrieve the ASCII=20
> version of the
> >>>>>>>> Internet-Draft.
> >>>>>>>>=20
> >>>>>>>>=20
> >>>>>>>>=20
> >>>>>>>>=20
> >>>>>>>=20
> >>>>>>>=20
> >>>>>=20
> >>>>>=20
> >>>>>=20
> >>>>=20
> >>>> _______________________________________________
> >>>> Behave mailing list
> >>>> Behave@ietf.org
> >>>> https://www.ietf.org/mailman/listinfo/behave
> >>>=20
> >>=20
> >> _______________________________________________
> >> Behave mailing list
> >> Behave@ietf.org
> >> https://www.ietf.org/mailman/listinfo/behave
> >>=20
>=20


From root@core3.amsl.com  Wed Sep  9 02:15:01 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: behave@ietf.org
Delivered-To: behave@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id EFF623A68BC; Wed,  9 Sep 2009 02: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: <20090909091501.EFF623A68BC@core3.amsl.com>
Date: Wed,  9 Sep 2009 02:15:01 -0700 (PDT)
Cc: behave@ietf.org
Subject: [BEHAVE] I-D Action:draft-ietf-behave-v6v4-xlate-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/mail-archive/web/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>
X-List-Received-Date: Wed, 09 Sep 2009 09:15:02 -0000

--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           : IP/ICMP Translation Algorithm
	Author(s)       : X. Li, et al.
	Filename        : draft-ietf-behave-v6v4-xlate-01.txt
	Pages           : 24
	Date            : 2009-09-09

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 stateless and a stateful mode.
In the stateless mode, translation information is carried in the
address itself, permitting both IPv4->IPv6 and IPv6->IPv4 session
establishment without maintaining state in the IP/ICMP translator.
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.  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 stateless and stateful modes that are
not addressed in this document, related to the address assignment and
the maintenance of the translation tables, respectively.  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.

The changes in this document reflect five components:

1.  Redescribing the network model to map to present and projected

 usage [I-D.ietf-behave-v6v4-framework].

2.  Moving the address format to the address format document

 [I-D.ietf-behave-address-format], to coordinate with other drafts

 on the topic.

3.  Describing both stateful and stateless operation.
4.  Some changes in ICMP.

5.  Updating references.

Requirements

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-behave-v6v4-xlate-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
Content-Type: Message/External-body;
	name="draft-ietf-behave-v6v4-xlate-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From xing@cernet.edu.cn  Wed Sep  9 02:18:59 2009
Return-Path: <xing@cernet.edu.cn>
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 9BF463A67A3 for <behave@core3.amsl.com>; Wed,  9 Sep 2009 02:18:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.968
X-Spam-Level: *
X-Spam-Status: No, score=1.968 tagged_above=-999 required=5 tests=[AWL=-0.729,  BAYES_50=0.001, FH_HAS_XAIMC=2.696]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bSb9h+OsluLk for <behave@core3.amsl.com>; Wed,  9 Sep 2009 02:18:59 -0700 (PDT)
Received: from cernet.edu.cn (sea.net.edu.cn [202.112.3.66]) by core3.amsl.com (Postfix) with SMTP id 4CEB83A6783 for <behave@ietf.org>; Wed,  9 Sep 2009 02:18:57 -0700 (PDT)
Received: from [59.66.24.75]([59.66.24.75]) by cernet.edu.cn(AIMC 3.2.0.0) with SMTP id jm104aa7cde8; Wed, 09 Sep 2009 17:19:28 +0800
Message-ID: <4AA7730F.6040602@cernet.edu.cn>
Date: Wed, 09 Sep 2009 17:19:11 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: 'Behave WG' <behave@ietf.org>
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: 7bit
X-AIMC-AUTH: xing
X-AIMC-MAILFROM: xing@cernet.edu.cn
X-AIMC-Msg-ID: q4qUTlWB
Cc: congxiao <congxiao@cernet.edu.cn>, Xing Li <xing@cernet.edu.cn>, Fred Baker <fred@cisco.com>
Subject: [BEHAVE] version 01 of xlate
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/mail-archive/web/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>
X-List-Received-Date: Wed, 09 Sep 2009 09:18:59 -0000

Hi, All,

Based on Dave's comment, the discussions in the mailing list and the
meeting notes of IETF75, the authors have made the modifications and
uploaded the 01 version of the IP/ICMP Translation Algorithm. Here are
some editorial notes.

(1) Most of the grammar and spelling errors are corrected.
(2) Translating UDP over IPv4 (Sec. 2.2): Rewritten based on the
discussions on the mailing list.
(3) Transport-layer Header Translation (Sec. 2.5 and Sec 3.4): Reflected
the checksum neutral case.
(4) Translator sending ICMP error message: add the configuration
concerns in new sections (2.5 and 3.4).
(5) Translating ICMP extensions: add notes.
(6) Translating multicast packets: add notes.

Please review this version and send your comments and suggestions.

Regards,

xing






From caozhenpku@gmail.com  Wed Sep  9 18:03:46 2009
Return-Path: <caozhenpku@gmail.com>
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 BD14E3A6A6E for <behave@core3.amsl.com>; Wed,  9 Sep 2009 18:03:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.406
X-Spam-Level: 
X-Spam-Status: No, score=-2.406 tagged_above=-999 required=5 tests=[AWL=0.193,  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 oeBx9mfeqeLj for <behave@core3.amsl.com>; Wed,  9 Sep 2009 18:03:46 -0700 (PDT)
Received: from mail-pz0-f183.google.com (mail-pz0-f183.google.com [209.85.222.183]) by core3.amsl.com (Postfix) with ESMTP id BEFCF3A6A99 for <behave@ietf.org>; Wed,  9 Sep 2009 18:03:37 -0700 (PDT)
Received: by pzk13 with SMTP id 13so254410pzk.5 for <behave@ietf.org>; Wed, 09 Sep 2009 18:04:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=O6kM/SYXjWNImhrYD7hIyKU29m2G0EMyCWiUjZU+gWs=; b=qQhAycH8v92sC7MtUIUS34+C6PtlfEjOVJoUoaHFvvQLf3GblpQ4KdSF+WUGNR+UZn tZaHCMdd75eC9TkzO8iDi6Sw9tWjjTj2n++5/2v9USCeh9xikTLrG5SN1+uSsxBAzR9G F3O1xED0CPOOANVbp4OyFrpDhLeN83CnfzG9k=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=bGLHLNMv1nu3IPH5Dty3UlonbBjM95DqzDeN9zvENEOVboGi50Q9nuaTj8IFLKc804 APrdxGJqBcmtEMRq95E+7dla6mimQG5tke5/+zXH68r7X0/HeQu2pjMXrmrDc31MCzvw m9Plh5Whz0DhAGSHuiyZ/Ri91xIGd6zvS52SQ=
MIME-Version: 1.0
Received: by 10.142.5.25 with SMTP id 25mr125804wfe.80.1252544648240; Wed, 09  Sep 2009 18:04:08 -0700 (PDT)
In-Reply-To: <09f701ca30a0$01e90730$c5f0200a@cisco.com>
References: <a7c8d0a30909080645t342f7bd7udfc553c0303f25ff@mail.gmail.com> <09f701ca30a0$01e90730$c5f0200a@cisco.com>
Date: Thu, 10 Sep 2009 09:04:08 +0800
Message-ID: <a7c8d0a30909091804j368a8a6fr4ee1b75eb7081559@mail.gmail.com>
From: Zhen Cao <caozhenpku@gmail.com>
To: Dan Wing <dwing@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Stateless translation definition
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/mail-archive/web/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>
X-List-Received-Date: Thu, 10 Sep 2009 01:03:46 -0000

On Wed, Sep 9, 2009 at 12:18 AM, Dan Wing <dwing@cisco.com> wrote:
>
>
> > -----Original Message-----
> > From: behave-bounces@ietf.org
> > [mailto:behave-bounces@ietf.org] On Behalf Of Zhen Cao
> > Sent: Tuesday, September 08, 2009 6:46 AM
> > To: Dave Thaler; Behave WG
> > Subject: [BEHAVE] Stateless translation definition
> >
> > Hi Dave and all,
> >
> > I have a concern with respect to the definition of
> > stateful/stateless translation. Could you help me? Thanks in advance.
> >
> > The framework draft defines stateful translation as:
> >
> >
> > =A0 =A0 =A0 A translation algorithm may be said to
> > =A0 =A0 =A0 "require state in a network element" or be "stateful" if th=
e
> > =A0 =A0 =A0 transmission or reception of a packet creates or modifies a=
 data
> > =A0 =A0 =A0 structure in the relevant network element.
> >
> >
> > According to this definition, say, if hosts are configured
> > with a public IPv4 address in the host-based translation
> > (draft-huang-pnat-host-ipv6-02), and the used local prefix is
> > unique, then the translation on prefix-nat will NOT create or
> > modify any data structure. Can we call it stateless translation?
>
> Yes, that would be stateless translation on the network-based
> NAT device.
>
> However, there is stateful translation in the host device:
> specifically, a DNS query creates state inside of the host's
> stack (that state maps IPv4 to IPv6).

Since the WKP is unique, this actually does not create a 'state', it
just append the ipv4 address to the well known prefix.

>
> So the system, as a whole, is not stateless or stateful. =A0It
> is both.
>
> -d
>
>
> >
> >
> > Thanks for your help.
> >
> >
> > Best regards,
> > Zhen
> >
>

From dwing@cisco.com  Wed Sep  9 18:30:44 2009
Return-Path: <dwing@cisco.com>
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 0E37D3A69E2 for <behave@core3.amsl.com>; Wed,  9 Sep 2009 18:30:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.654
X-Spam-Level: 
X-Spam-Status: No, score=-6.654 tagged_above=-999 required=5 tests=[AWL=-0.055, 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 8gJqxqu1Kcia for <behave@core3.amsl.com>; Wed,  9 Sep 2009 18:30:43 -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 F160E3A6ABA for <behave@ietf.org>; Wed,  9 Sep 2009 18:30:42 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqYEAEXzp0qrR7O6/2dsb2JhbACLHLoWiEMBkFwFhBiBWQ
X-IronPort-AV: E=Sophos;i="4.44,361,1249257600"; d="scan'208";a="188631507"
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-3.cisco.com with ESMTP; 10 Sep 2009 01:31:10 +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 n8A1VAa3007287;  Wed, 9 Sep 2009 18:31:10 -0700
Received: from dwingwxp01 ([10.32.240.198]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id n8A1VANg019671; Thu, 10 Sep 2009 01:31:10 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Zhen Cao'" <caozhenpku@gmail.com>
References: <a7c8d0a30909080645t342f7bd7udfc553c0303f25ff@mail.gmail.com> <09f701ca30a0$01e90730$c5f0200a@cisco.com> <a7c8d0a30909091804j368a8a6fr4ee1b75eb7081559@mail.gmail.com>
Date: Wed, 9 Sep 2009 18:31:09 -0700
Message-ID: <073801ca31b6$60299ff0$c6f0200a@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Acoxspnvcyt0zocZTQGfYBDWGVF4ggAAxlZA
In-Reply-To: <a7c8d0a30909091804j368a8a6fr4ee1b75eb7081559@mail.gmail.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3110; t=1252546270; x=1253410270; 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]=20Stateless=20translation=20de finition |Sender:=20; bh=+BwTkt1hHG+VWTXg3bOKhGb8V4mX9s6dQDq9WtRq7wY=; b=MaguhuBw2rns2MZr2mRZldGNMeVEfI2VhVCoKhSV6qLRihlrWh6lEV5klF /rfrejHvAn2VJpN6iywI9KIfI/PTwCUtMQZWLTzg4FtXehvc40iG/r4qoQQJ UYrT88LDji;
Authentication-Results: sj-dkim-2; header.From=dwing@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; ); 
Cc: 'Behave WG' <behave@ietf.org>
Subject: Re: [BEHAVE] Stateless translation definition
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/mail-archive/web/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>
X-List-Received-Date: Thu, 10 Sep 2009 01:30:44 -0000

=20

> -----Original Message-----
> From: Zhen Cao [mailto:caozhenpku@gmail.com]=20
> Sent: Wednesday, September 09, 2009 6:04 PM
> To: Dan Wing
> Cc: Behave WG
> Subject: Re: [BEHAVE] Stateless translation definition
>=20
> On Wed, Sep 9, 2009 at 12:18 AM, Dan Wing <dwing@cisco.com> wrote:
> >
> >
> > > -----Original Message-----
> > > From: behave-bounces@ietf.org
> > > [mailto:behave-bounces@ietf.org] On Behalf Of Zhen Cao
> > > Sent: Tuesday, September 08, 2009 6:46 AM
> > > To: Dave Thaler; Behave WG
> > > Subject: [BEHAVE] Stateless translation definition
> > >
> > > Hi Dave and all,
> > >
> > > I have a concern with respect to the definition of
> > > stateful/stateless translation. Could you help me? Thanks=20
> in advance.
> > >
> > > The framework draft defines stateful translation as:
> > >
> > >
> > > =A0 =A0 =A0 A translation algorithm may be said to
> > > =A0 =A0 =A0 "require state in a network element" or be "stateful" =
if the
> > > =A0 =A0 =A0 transmission or reception of a packet creates or=20
> modifies a data
> > > =A0 =A0 =A0 structure in the relevant network element.
> > >
> > >
> > > According to this definition, say, if hosts are configured
> > > with a public IPv4 address in the host-based translation
> > > (draft-huang-pnat-host-ipv6-02), and the used local prefix is
> > > unique, then the translation on prefix-nat will NOT create or
> > > modify any data structure. Can we call it stateless translation?
> >
> > Yes, that would be stateless translation on the network-based
> > NAT device.
> >
> > However, there is stateful translation in the host device:
> > specifically, a DNS query creates state inside of the host's
> > stack (that state maps IPv4 to IPv6).
>=20
> Since the WKP is unique, this actually does not create a 'state', it
> just append the ipv4 address to the well known prefix.

There isn't enough IPv4 address space to map the entire IPv6
address space, so there is state and old mappings need to be
destroyed.

For example, if an IPv4 application looks up host1.example.net,
the underlying Bump-in-the-Stack/-API of draft-huang-pnat-host-ipv6
will take that IPv4 application's API calls and do an AAAA
query over the air, which returns in AAAA response.  The=20
Bump-in-the-Stack/-API will create a mapping from that AAAA
address to an IPv4 address, and provide that IPv4 address=20
to the application.  When the IPv4 application looks up
host2.example.net, the same thing occurs, consuming another
IPv4 address in that mapping table inside the host.  This
continues until the IPv4 application has exhausted all of
the IPv4 mapping entries in the host, or until old entries
start being destroyed.

That is, at least, my understanding of the mapping and
NATting that is occuring in the host's stack.  If it works=20
some other way, please explain it. =20

-d

> > So the system, as a whole, is not stateless or stateful. =A0It
> > is both.
> >
> > -d
> >
> >
> > >
> > >
> > > Thanks for your help.
> > >
> > >
> > > Best regards,
> > > Zhen
> > >
> >


From caozhenpku@gmail.com  Thu Sep 10 03:04:29 2009
Return-Path: <caozhenpku@gmail.com>
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 19ED528C0FB for <behave@core3.amsl.com>; Thu, 10 Sep 2009 03:04:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.42
X-Spam-Level: 
X-Spam-Status: No, score=-2.42 tagged_above=-999 required=5 tests=[AWL=0.179,  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 5YohgT9A9j8g for <behave@core3.amsl.com>; Thu, 10 Sep 2009 03:04:28 -0700 (PDT)
Received: from mail-vw0-f201.google.com (mail-vw0-f201.google.com [209.85.212.201]) by core3.amsl.com (Postfix) with ESMTP id E8D6728C103 for <behave@ietf.org>; Thu, 10 Sep 2009 03:04:27 -0700 (PDT)
Received: by vws39 with SMTP id 39so550140vws.29 for <behave@ietf.org>; Thu, 10 Sep 2009 03:04:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=4XDJpldzaeEMSCQVHQUPx8YWXdy8EsikLy48Zc7ijdo=; b=bESMwLSOpztsRQxgv7uwqqRyRpab14gxf8VidOIcAEcwgrGmKeiYzeX26yLAN0LCWJ bCX23kA5K8u4fiyUxF0DUc0RP6F4O/9Eyd6pKSP2FqIvPTFLhnieX9/equV66alIdxg6 D3NE/1wfE+4LxoTUeCZmokSElMP9ba/iYNi9I=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=RE6dYBrhEGzsmG0wdwaf1L/y6pGsefyHZbSLtKvomwGhzX1W5dyID8dL2YqSUyplSO 7iwaQxc1xKqGnGnXvRxMhwvZeNlMa9UGpHqghs17unr0oFj3Fc3VJmgYKQQpABMVq0T0 bzYnLgR0N82AbW5Hdu3Ng2KEQz+1eHI/KcxVc=
MIME-Version: 1.0
Received: by 10.220.79.105 with SMTP id o41mr1131125vck.70.1252577098797; Thu,  10 Sep 2009 03:04:58 -0700 (PDT)
In-Reply-To: <073801ca31b6$60299ff0$c6f0200a@cisco.com>
References: <a7c8d0a30909080645t342f7bd7udfc553c0303f25ff@mail.gmail.com> <09f701ca30a0$01e90730$c5f0200a@cisco.com> <a7c8d0a30909091804j368a8a6fr4ee1b75eb7081559@mail.gmail.com> <073801ca31b6$60299ff0$c6f0200a@cisco.com>
Date: Thu, 10 Sep 2009 18:04:58 +0800
Message-ID: <a7c8d0a30909100304w69593812o29778ad80f28451c@mail.gmail.com>
From: Zhen Cao <caozhenpku@gmail.com>
To: Dan Wing <dwing@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Stateless translation definition
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/mail-archive/web/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>
X-List-Received-Date: Thu, 10 Sep 2009 10:04:29 -0000

On Thu, Sep 10, 2009 at 9:31 AM, Dan Wing <dwing@cisco.com> wrote:
>
>
>> -----Original Message-----
>> From: Zhen Cao [mailto:caozhenpku@gmail.com]
>> Sent: Wednesday, September 09, 2009 6:04 PM
>> To: Dan Wing
>> Cc: Behave WG
>> Subject: Re: [BEHAVE] Stateless translation definition
>>
>> On Wed, Sep 9, 2009 at 12:18 AM, Dan Wing <dwing@cisco.com> wrote:
>> >
>> >
>> > > -----Original Message-----
>> > > From: behave-bounces@ietf.org
>> > > [mailto:behave-bounces@ietf.org] On Behalf Of Zhen Cao
>> > > Sent: Tuesday, September 08, 2009 6:46 AM
>> > > To: Dave Thaler; Behave WG
>> > > Subject: [BEHAVE] Stateless translation definition
>> > >
>> > > Hi Dave and all,
>> > >
>> > > I have a concern with respect to the definition of
>> > > stateful/stateless translation. Could you help me? Thanks
>> in advance.
>> > >
>> > > The framework draft defines stateful translation as:
>> > >
>> > >
>> > > =A0 =A0 =A0 A translation algorithm may be said to
>> > > =A0 =A0 =A0 "require state in a network element" or be "stateful" if=
 the
>> > > =A0 =A0 =A0 transmission or reception of a packet creates or
>> modifies a data
>> > > =A0 =A0 =A0 structure in the relevant network element.
>> > >
>> > >
>> > > According to this definition, say, if hosts are configured
>> > > with a public IPv4 address in the host-based translation
>> > > (draft-huang-pnat-host-ipv6-02), and the used local prefix is
>> > > unique, then the translation on prefix-nat will NOT create or
>> > > modify any data structure. Can we call it stateless translation?
>> >
>> > Yes, that would be stateless translation on the network-based
>> > NAT device.
>> >
>> > However, there is stateful translation in the host device:
>> > specifically, a DNS query creates state inside of the host's
>> > stack (that state maps IPv4 to IPv6).
>>
>> Since the WKP is unique, this actually does not create a 'state', it
>> just append the ipv4 address to the well known prefix.
>
> There isn't enough IPv4 address space to map the entire IPv6
> address space, so there is state and old mappings need to be
> destroyed.
>
> For example, if an IPv4 application looks up host1.example.net,
> the underlying Bump-in-the-Stack/-API of draft-huang-pnat-host-ipv6
> will take that IPv4 application's API calls and do an AAAA
> query over the air, which returns in AAAA response. =A0The
> Bump-in-the-Stack/-API will create a mapping from that AAAA
> address to an IPv4 address, and provide that IPv4 address
> to the application. =A0When the IPv4 application looks up
> host2.example.net, the same thing occurs, consuming another
> IPv4 address in that mapping table inside the host. =A0This
> continues until the IPv4 application has exhausted all of
> the IPv4 mapping entries in the host, or until old entries
> start being destroyed.

Thanks for the detailed explanation of the above pnat 46 communication
scenario. For pnat 44 communication, DNS responds with A records, we
believe it is stateless.

>
> That is, at least, my understanding of the mapping and
> NATting that is occuring in the host's stack. =A0If it works
> some other way, please explain it.
>
> -d
>
>> > So the system, as a whole, is not stateless or stateful. =A0It
>> > is both.
>> >
>> > -d
>> >
>> >
>> > >
>> > >
>> > > Thanks for your help.
>> > >
>> > >
>> > > Best regards,
>> > > Zhen
>> > >
>> >
>
>

From iljitsch@muada.com  Thu Sep 10 03:45:17 2009
Return-Path: <iljitsch@muada.com>
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 2A8CA3A635F for <behave@core3.amsl.com>; Thu, 10 Sep 2009 03:45:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.416
X-Spam-Level: 
X-Spam-Status: No, score=-4.416 tagged_above=-999 required=5 tests=[AWL=-1.817, 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 dA-I2ROxpvyr for <behave@core3.amsl.com>; Thu, 10 Sep 2009 03:45:16 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2]) by core3.amsl.com (Postfix) with ESMTP id 0E4093A67F2 for <behave@ietf.org>; Thu, 10 Sep 2009 03:45:15 -0700 (PDT)
Received: from wifi-82-83.uc3m.es (wifi-82-83.uc3m.es [163.117.82.83]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id n8AAjdFi027873 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 10 Sep 2009 12:45:40 +0200 (CEST) (envelope-from iljitsch@muada.com)
Mime-Version: 1.0 (Apple Message framework v1075.2)
Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <1d38a3350908310904m13adea1eg966751031cc30f6b@mail.gmail.com>
Date: Thu, 10 Sep 2009 12:45:34 +0200
Content-Transfer-Encoding: 7bit
Message-Id: <0EAA62DC-5576-4DC2-BACF-66EAECA083DD@muada.com>
References: <2991246A29623A4082EB2B06A2B891A41B7C3D85A9@EUSAACMS0703.eamcs.ericsson.se> <1d38a3350908271948l7e55b0cai38e40cfb4edc30d7@mail.gmail.com> <200908280743.18009.simon.perreault@viagenie.ca> <1d38a3350908282029m78ccdf5bg3e23a848029e282b@mail.gmail.com> <4A98E2F2.4020401@it.uc3m.es> <1d38a3350908290300u30735251ga4ef617e653047a0@mail.gmail.com> <4A9A296B.5040405@it.uc3m.es> <1d38a3350908310904m13adea1eg966751031cc30f6b@mail.gmail.com>
To: Hui Deng <denghui02@gmail.com>
X-Mailer: Apple Mail (2.1075.2)
Cc: behave@ietf.org, Wassim Haddad <wassim.haddad@ericsson.com>, =?utf-8?B?5ZGo5Y2a?= <zhouboyj@chinamobile.com>
Subject: Re: [BEHAVE] NAT64 and MIPv6
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/mail-archive/web/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>
X-List-Received-Date: Thu, 10 Sep 2009 10:45:17 -0000

On 31 Aug 2009, at 18:04 , Hui Deng wrote:

> Here you state without IPv4 address is IPv6 only, then sometime it  
> get Ipv4
> address but without IPv4 connection is another kind of IPv6 only?

(Sorry for the delay.)

In my opinion, the thing that makes all the difference is a default  
route.

When we were doing the "IPv6 experiment" during the Philadelphia  
meeting, we had to find a workaround to make Windows XP hosts do DNS  
requests because they can't do those over IPv6. A good way to fix this  
is to give the host an IPv4 address on a subnet where there is a  
nameserver, so the machine can query the nameserver over IPv4.  
However, as there is no IPv4 default route, the system still tries to  
connect to non-local systems only over IPv6.

I know this is not the way all operating systems work with regard to  
IPv6. Because RAs themselves and prefixes in RAs have their own valid  
timers, you can either have an IPv6 address but no default route or an  
IPv6 default route and no address. I believe Windows (XP, at least)  
and Linux take the presence of the address to mean there is working  
IPv6, possibly because of the on-link assuption. (If you have no  
default you're supposed to treat the entire IPv6 space as on-link.  
This is a pretty bad idea, though.) However MacOS and BSD take the  
presence of a default route to mean that IPv6 is available.

From iljitsch@muada.com  Thu Sep 10 03:52:29 2009
Return-Path: <iljitsch@muada.com>
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 99AAA28C132 for <behave@core3.amsl.com>; Thu, 10 Sep 2009 03:52:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.241
X-Spam-Level: 
X-Spam-Status: No, score=-4.241 tagged_above=-999 required=5 tests=[AWL=-1.942, 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 zQ4JQJ859yDp for <behave@core3.amsl.com>; Thu, 10 Sep 2009 03:52:29 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2]) by core3.amsl.com (Postfix) with ESMTP id 943B828C129 for <behave@ietf.org>; Thu, 10 Sep 2009 03:52:28 -0700 (PDT)
Received: from wifi-82-83.uc3m.es (wifi-82-83.uc3m.es [163.117.82.83]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id n8AAquC8027922 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 10 Sep 2009 12:53:00 +0200 (CEST) (envelope-from iljitsch@muada.com)
Mime-Version: 1.0 (Apple Message framework v1075.2)
Content-Type: text/plain; charset=iso-8859-1; format=flowed; delsp=yes
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <0A5916B6-4B95-4818-B099-044701D4B659@free.fr>
Date: Thu, 10 Sep 2009 12:52:51 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <B364BB7D-FABD-425A-BBE3-2E8695A7D6D5@muada.com>
References: <0A5916B6-4B95-4818-B099-044701D4B659@free.fr>
To: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
X-Mailer: Apple Mail (2.1075.2)
Cc: Behave WG <behave@ietf.org>, Dave Thaler <dthaler@windows.microsoft.com>
Subject: Re: [BEHAVE] draft-ietf-behave-address-format-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/mail-archive/web/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>
X-List-Received-Date: Thu, 10 Sep 2009 10:52:29 -0000

On 1 Sep 2009, at 18:29 , R=E9mi Despr=E9s wrote:

> Here is a text that, without changing the conclusion, would in my =20
> understanding better reflect points that were made.

I disagree with this. Leave the u/l and group bits alone.=

From iljitsch@muada.com  Thu Sep 10 03:59:45 2009
Return-Path: <iljitsch@muada.com>
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 A80C33A6A32; Thu, 10 Sep 2009 03:59:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.364
X-Spam-Level: 
X-Spam-Status: No, score=-4.364 tagged_above=-999 required=5 tests=[AWL=-1.765, 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 aV1iynjcWzvt; Thu, 10 Sep 2009 03:59:45 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2]) by core3.amsl.com (Postfix) with ESMTP id A64A13A6A35; Thu, 10 Sep 2009 03:59:44 -0700 (PDT)
Received: from wifi-82-83.uc3m.es (wifi-82-83.uc3m.es [163.117.82.83]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id n8AAxdPZ027979 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 10 Sep 2009 12:59:42 +0200 (CEST) (envelope-from iljitsch@muada.com)
Mime-Version: 1.0 (Apple Message framework v1075.2)
Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <000701ca303b$3bc26600$d40c6f0a@china.huawei.com>
Date: Thu, 10 Sep 2009 12:59:34 +0200
Content-Transfer-Encoding: 7bit
Message-Id: <9A461C22-1DCE-4041-ACD1-D658F7E4BC01@muada.com>
References: <000701ca303b$3bc26600$d40c6f0a@china.huawei.com>
To: Xu Xiaohu <xuxh@huawei.com>
X-Mailer: Apple Mail (2.1075.2)
Cc: softwires@ietf.org, "'Templin, Fred L'" <Fred.L.Templin@boeing.com>, 'Behave WG' <behave@ietf.org>
Subject: Re: [BEHAVE] [Softwires] Some Thought about the Automatic Tunnel Address
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/mail-archive/web/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>
X-List-Received-Date: Thu, 10 Sep 2009 10:59:45 -0000

On 8 Sep 2009, at 6:17 , Xu Xiaohu wrote:

> What's the real purpose of the above model (IPv6 addresses beginning  
> with
> other than '000' use a 64-bit prefix)? Can somebody help explain it?

The IPv6 addresses in ::/3 are/were used for special purposes, such as  
the localhost address, IPv4-mapped addresses and mapping NSAPs and  
IPX. So the requirement that there should be a valid IID in those  
addresses doesn't make sense.

From remi.despres@free.fr  Thu Sep 10 05:08:03 2009
Return-Path: <remi.despres@free.fr>
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 A8B1C28C14C; Thu, 10 Sep 2009 05:08:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.524
X-Spam-Level: 
X-Spam-Status: No, score=-1.524 tagged_above=-999 required=5 tests=[AWL=-0.175, BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_13=0.6, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3Rdn2cBKEEZr; Thu, 10 Sep 2009 05:08:02 -0700 (PDT)
Received: from smtp6-g21.free.fr (smtp6-g21.free.fr [212.27.42.6]) by core3.amsl.com (Postfix) with ESMTP id F0F6428C14E; Thu, 10 Sep 2009 05:08:00 -0700 (PDT)
Received: from smtp6-g21.free.fr (localhost [127.0.0.1]) by smtp6-g21.free.fr (Postfix) with ESMTP id 03193E081A3; Thu, 10 Sep 2009 14:08:26 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by smtp6-g21.free.fr (Postfix) with ESMTP id 46B7AE080E1; Thu, 10 Sep 2009 14:08:22 +0200 (CEST)
Mime-Version: 1.0 (Apple Message framework v753.1)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <576F9230-1A07-479F-8336-6906658736BB@free.fr>
Content-Transfer-Encoding: 7bit
From: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
Date: Thu, 10 Sep 2009 14:08:16 +0200
To: Margaret Wasserman <mrw@lilacglade.org>, Fred Baker <fred@cisco.com>, Christian Huitema <huitema@microsoft.com>, Dave Thaler <dthaler@windows.microsoft.com>
X-Mailer: Apple Mail (2.753.1)
Cc: IPv6 v6ops <v6ops@ops.ietf.org>, Behave WG <behave@ietf.org>, Fred L Templin <Fred.L.Templin@boeing.com>, 6man 6man <ipv6@ietf.org>, Gabi Nakibly <gnakibly@yahoo.com>
Subject: [BEHAVE] IID-format constraint applicable to all IPv6 addresses for routing-loop attack protection
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/mail-archive/web/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>
X-List-Received-Date: Thu, 10 Sep 2009 12:08:03 -0000

Hi all,

Should IID-format constraints be applicable to IPv6 addresses, even  
if they don't contain real IIDs?

I have proposed in various occasions that they would apply only to  
addresses that do contain real IIDs.

This mail is to WITHDRAW this proposal, to explain why it was  
proposed, and to explain why it is withdrawn.


GENERAL ANALYSIS

New IPv6-address formats are being considered for IPv6 addresses  
that, in IPv6/IPv4 NATs, identify IPv4 hosts. Some others are  
considered for new tunneling mechanisms, in particular the SAM I  
presented in Stockholm for IPv6 multihoming.

In these addresses, the lower 64 bits are not real IIDs:
- RFC 3513 says that "Interface identifiers in IPv6 unicast addresses  
are used to identify  interfaces on a link").
- The lower 64 bits of these addresses are never "used to identify  
interfaces on a link". It is only IPv4 or IPv6 addresses obtained  
after some mapping that are used for on-link interface  
identification. They in general don't contain the initial lower 64 bits.

We will call such addresses "mappable-only" addresses.

RFC 3513 also says, as we all know, that "For all unicast addresses,  
except those that start with binary value 000, Interface IDs are  
required to be 64 bits long and to be constructed in Modified EUI-64  
format".

We will call this constraint the "IID-format constraint"

Since mappable-only addresses have no real "Interface ID", they may  
be interpreted as out of the scope of the IID-format constraint.

If they are indeed out of scope, that's good news because new formats  
of mappable-only addresses can be simpler than if they are in scope  
(no constraint on the two lower bits of their 9th octet).

If mappable-only addresses should be considered in the constraint  
scope, some technical reason for it should at least be documented.

Since no such technical reason was identified, I proposed to make  
official that the IID-format constraint doesn't apply to mappable- 
only addresses.

Now, it happens that such a technical reason has just been  
identified. As explained below, it relates to a subtle attack  
possibility with some ISATAP and 6to4 nodes conforming to current  
RFCs. The only choice that remains is then to clearly include  
mappable-only addresses in the scope of the IID-format constraint.



ROUTING-LOOP ATTACK PROTECTION AND ITS IMPLICATION ON IPV6 ADDRESS  
FORMATS

In a mail of Aug 17 (www.ops.ietf.org/lists/v6ops/v6ops.2009/ 
msg00601), Gabi Nakibly documented a new type of attack: the "routing  
loop" attack. With it, some packets can be repeatedly retransmitted  
between two ISATAP routers, or between an ISATAP router and a 6to4  
relay router.

For a brief illustration of one instance of the the attack, here is  
an example:

+-------------------------------------------------------+
| IPv6                   IPv6 packet                    |
|Internet        dst6:  2002:198.16.9.9::1              |
|                src6:  2001:db8:1::200:5efe:192.88.99.1|
|                                           |           |
|                                           V           |
|          .--------------->--------------. |           |
|         /                                \|           |
+--------+----------------------------------+-----------+
          |                                  |
   2001:db8:1::/48                       2002::/16
     +---------+                        +---------+
     | ISATAP  |                        |  6to4   |
     +---------+                        +---------+
     198.16.9.9                         192.88.99.1
          |                                  |
+--------+---------+                        |
| IPv4   ^         |                        |
| site   ^         |                        |
|        ^         |                        V
|        ^         |                        |
+--------+---------+                        |
     198.16.9.0/24                           |
          |                                  |
          |                                  |
+--------+----------------------------------+-----------+
| IPv4    \                                /            |
|internet  '----------------<-------------'             |
|                 IPv6 in IPv4 packet                   |
|                  dst4: 198.16.9.9                     |
|                  src4: 192.88.99.1                    |
|                                                       |
+--------+----------------------------------+-----------+


Detailed protection mechanisms against these attacks are being  
discussed on the v6ops and 6man lists, in particular with Gabi  
Nakibly, Fred Templin, and Christian Huitema, and are out of scope  
here. Suffice it to say that a  6to4 relay router may need, to be  
safe, to look at IPv4 addresses that are embedded in ISATAP IPv6  
addresses. In the above example, if the 6to4 relay router sees that  
the IPv4 embedded address in the IPv6 destination is its own IPv4  
address 192.88.99.1, it can discard the packet and thus prevent the  
loop.

Now, IPv4 addresses embedded in ISATAP addresses can be reliably  
detected ONLY if non-ISATAP addresses NEVER have 200:5efe::/32 in  
their octets 8 to 15. If some mappable-only address would have this  
pattern, there could be a slight but real possibility that an  
intermediate 6to4 relay would discard packets sent to this address.

This is, in my understanding, a sufficient technical reason for the  
IID-format constraint to apply to all IPv6 addresses (with or without  
real IID).


Regards,
RD


From caozhenpku@gmail.com  Thu Sep 10 06:29:35 2009
Return-Path: <caozhenpku@gmail.com>
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 AECF43A693F for <behave@core3.amsl.com>; Thu, 10 Sep 2009 06:29:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.432
X-Spam-Level: 
X-Spam-Status: No, score=-2.432 tagged_above=-999 required=5 tests=[AWL=0.167,  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 efOuqg1+4BFu for <behave@core3.amsl.com>; Thu, 10 Sep 2009 06:29:34 -0700 (PDT)
Received: from mail-vw0-f201.google.com (mail-vw0-f201.google.com [209.85.212.201]) by core3.amsl.com (Postfix) with ESMTP id 6C8383A69B5 for <behave@ietf.org>; Thu, 10 Sep 2009 06:29:34 -0700 (PDT)
Received: by vws39 with SMTP id 39so59022vws.29 for <behave@ietf.org>; Thu, 10 Sep 2009 06:30:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=eKisLIWFciU1h+8eHlL3VTz9qYpS3aEFnn1wNoAcke0=; b=Bs62tKtESI/VXCrY9jJ/BzPx1ghfOEcWPfvrqIQK90MflfDzs/AF/Wh35Cpf3NpHLa ocpvTYYqDHdln1fiiifVoEze22keboj39mzFQC5g5Q/rk0eGRWTaomdl1bDa/VLjL0ln o4d/QgWmtCG/SPMr92U0rO3YMFFDWFC3HtLL0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=EDIHpQrbx0XRINLqX5OUH7F44PG9hRr2KvkxvVkgGdyks+we6AVPk7yEO9m/9yrd4v L1zmW7TChjnuyeIHqV/95upHoWObcJ1/v2tSgYy0xEG5Spmbj860DUKiGfjLAmPcSAjz hCylk3hFthw3EOt+vN4r/a4sppa4DfJoOBSFs=
MIME-Version: 1.0
Received: by 10.220.88.209 with SMTP id b17mr1450779vcm.98.1252589405630; Thu,  10 Sep 2009 06:30:05 -0700 (PDT)
In-Reply-To: <A09ECC61-E8CB-430B-A891-53902BEA083D@muada.com>
References: <A09ECC61-E8CB-430B-A891-53902BEA083D@muada.com>
Date: Thu, 10 Sep 2009 21:30:05 +0800
Message-ID: <a7c8d0a30909100630y32e30024s68d17487612ebd37@mail.gmail.com>
From: Zhen Cao <caozhenpku@gmail.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] 64 MTU and fragmentation handling
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/mail-archive/web/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>
X-List-Received-Date: Thu, 10 Sep 2009 13:29:35 -0000

Hi Iljitsch,

The current discussion only focused on the black hole for 1280
fragments where an IPv4 router reports MTU <1280. IMO, the black hole
may happen in many scenarios.  For instance, if MTU is 1600 for ipv6
side and 1500 for ipv4 side, an IPv6 sender starts sending 1600-byte
packets without fragmentation header to discover the PMTU. But the
ICMP PktTooBig message is blocked or lost due to whatever reasons, the
sender continues to send 1600-byte packets without frag header,
resulting DF=1 translated ipv4 packets longer than 1500 and
communication is lost then.  Has this case been handled by some
existing specfications?

Moreover, current IPv4 network always has MTU greater than 1400, so
the possibility of reporting a <1280 MTU is slim.

Thanks,
Zhen

On Thu, Aug 20, 2009 at 11:57 PM, Iljitsch van Beijnum
<iljitsch@muada.com> wrote:
> Hi,
>
> We had a fruitful discussion about MTU and fragmentation handling in the
> online interim meeting yesterday. My original options for handing < 1280
> MTUs on the IPv4 side for stateful translation:
>
> 1. Depend on RFC 2460/2765 behavior where 1280-byte packets with a fragment
> header are sent after a < 1280 "too big" message, translator sets DF=0 when
> translating packets with a fragment header, DF=1 otherwise.
>
> The problem with this is that there is the possibility of a black hole when
> the operator disables path MTU discovery on the IPv6 side by setting the MTU
> to 1280 and filtering "too big" messages. In that case, the fragment header
> is never included, the translator generates a 1260-byte IPv6 packet with
> DF=1 and communication is impossible. This requires unusual, but not unheard
> of cases on both the v4 and v6 sides (< 1260 MTU, PMTUD disabled), but the
> problem is that in the pure IPv4 and pure IPv6 cases these wouldn't cause
> trouble, it's only when communicating through a translator that the black
> hole presents itself.
>
> Solution in the draft:
>
> 3. Rewrite "too big" messages to provide a 1280-byte MTU and have the
> translator set DF=0 for packets <= 1280 bytes and DF=1 for packets > 1280
> bytes.
>
> Alternative solution:
>
> 2. Adopt the RFC 2460/2765 behavior, except that to avoid the black hole,
> packets <= 1280 are sent with DF=0 even if there is no fragment header.
>
> Additional solution mentioned yesterday:
>
> 4. Let the translator track path MTU sizes for IPv4 destinations and
> fragment packets at the source where needed (just like normal IPv6 hosts do
> for IPv6, and in our specification, the translator also does this for
> packets going towards the IPv6 side).
>
> One argument that was made yesterday was the applicability to stateless
> translation. Obviously a mechanism that works for both stateful and
> stateless would be better than separate mechanisms for both. (However, note
> that the identification value handling needs to be different between
> stateful and stateless translation regardless of path MTU discovery
> handling.)
>
> However, solutions 2 and 4 equally apply to the stateful and stateless
> cases. Solution 3 is somewhat less suited for the stateless case, because it
> requires the translator to come up with an identification value. If traffic
> is flowing through multiple translators the identification values could
> clash and result in reassembly errors.
>
> All solutions produce fragments (except perhaps option 4 in the case of TCP
> when TCP is resegmented rather than fragmented), with the associated risk of
> incorrect reassemly and subsequent dependence on the weak TCP/UDP checksum
> to avoid data corruption.
>
> Option 4 has the disadvantage of creating more work for the translator and
> generating more packets and bits, taking over this work from the router in
> front of the < 1280 byte MTU link on the IPv4 side.
>
> As such, I favor option 2 for both stateful and stateless translation, and
> if implementers feel 4 is a viable option I would be willing to include that
> as a not specifically recommended alternative.
>
> Thoughts?
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>

From iljitsch@muada.com  Thu Sep 10 07:15:25 2009
Return-Path: <iljitsch@muada.com>
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 8994A3A6916 for <behave@core3.amsl.com>; Thu, 10 Sep 2009 07:15:25 -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 TQGoBOb0QFlz for <behave@core3.amsl.com>; Thu, 10 Sep 2009 07:15:24 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2]) by core3.amsl.com (Postfix) with ESMTP id 01B4D28C110 for <behave@ietf.org>; Thu, 10 Sep 2009 07:15:22 -0700 (PDT)
Received: from [IPv6:2001:720:410:100f:223:32ff:fec4:ba94] ([IPv6:2001:720:410:100f:223:32ff:fec4:ba94]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id n8AEFrEB029317 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 10 Sep 2009 16:15:54 +0200 (CEST) (envelope-from iljitsch@muada.com)
Mime-Version: 1.0 (Apple Message framework v1075.2)
Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <a7c8d0a30909100630y32e30024s68d17487612ebd37@mail.gmail.com>
Date: Thu, 10 Sep 2009 16:15:54 +0200
Content-Transfer-Encoding: 7bit
Message-Id: <74AA3C18-B735-4020-9FEB-B1ABBED1ACFF@muada.com>
References: <A09ECC61-E8CB-430B-A891-53902BEA083D@muada.com> <a7c8d0a30909100630y32e30024s68d17487612ebd37@mail.gmail.com>
To: Zhen Cao <caozhenpku@gmail.com>
X-Mailer: Apple Mail (2.1075.2)
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] 64 MTU and fragmentation handling
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/mail-archive/web/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>
X-List-Received-Date: Thu, 10 Sep 2009 14:15:25 -0000

On 10 Sep 2009, at 15:30 , Zhen Cao wrote:

> The current discussion only focused on the black hole for 1280
> fragments where an IPv4 router reports MTU <1280. IMO, the black hole
> may happen in many scenarios.  For instance, if MTU is 1600 for ipv6
> side and 1500 for ipv4 side, an IPv6 sender starts sending 1600-byte
> packets without fragmentation header to discover the PMTU. But the
> ICMP PktTooBig message is blocked or lost due to whatever reasons, the
> sender continues to send 1600-byte packets without frag header,
> resulting DF=1 translated ipv4 packets longer than 1500 and
> communication is lost then.  Has this case been handled by some
> existing specfications?

This is true. However, someone sending 1600-byte packets and filtering  
too big messages would very quickly find out that that combination of  
settings is problematic and fix this one way or another. (Although  
there will be some PMTUD black holes when the sender of 1600-byte  
packets accepts too bigs but the other side fails to generate them.)  
So this situation is orthogonal to the IPv6/IPv4 translation.

The only good solution for this is RFC 4821, but I understand that  
there are other PMTUD blackhole detection mechanisms, and that  
Microsoft implements one of those. Not sure how they work.

> Moreover, current IPv4 network always has MTU greater than 1400, so
> the possibility of reporting a <1280 MTU is slim.

I agree that this wouldn't be a common situation, but "always" is too  
optimistic, I'm afraid...

Iljitsch

From dwing@cisco.com  Thu Sep 10 09:08:21 2009
Return-Path: <dwing@cisco.com>
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 B0DE828C102 for <behave@core3.amsl.com>; Thu, 10 Sep 2009 09:08:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.652
X-Spam-Level: 
X-Spam-Status: No, score=-6.652 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 oGt7b1xN2UEo for <behave@core3.amsl.com>; Thu, 10 Sep 2009 09:08:20 -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 AEC2C28C101 for <behave@ietf.org>; Thu, 10 Sep 2009 09:08:20 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArcEAAPBqEqrR7O6/2dsb2JhbACLHLsQiEYBkEIFhBg
X-IronPort-AV: E=Sophos;i="4.44,365,1249257600"; d="scan'208";a="386066169"
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-6.cisco.com with ESMTP; 10 Sep 2009 16:08:56 +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 n8AG8tvu024934;  Thu, 10 Sep 2009 09:08:55 -0700
Received: from dwingwxp01 ([10.32.240.198]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id n8AG8t1G020475; Thu, 10 Sep 2009 16:08:55 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Behave WG'" <behave@ietf.org>
Date: Thu, 10 Sep 2009 09:08:55 -0700
Message-ID: <080801ca3230$ff3542a0$c6f0200a@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcoyMP7yIswwltwFQNC25BSyUg/RGQ==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=806; t=1252598935; x=1253462935; 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:=20changing=20XOR-RESPONSE-TARGET=20in=20draft-iet f-behave-nat-behavior-discovery-07 |Sender:=20; bh=45ODJWgOZBDZ1o274zxvqHTvtw1ZMa6tFgHw/h6UQu0=; b=yJbeWoeq8GL4XvKXeWYqwJWZeKOY8dn0dFtuNXSPYvPbJLNJrImjJsdag9 dn7ZSi+7KiHp/cp3oT8MPCXb7iln+ZUO4alY6abNF+C76T3UtAd9pKUButvF vdnGdtnDKy;
Authentication-Results: sj-dkim-2; header.From=dwing@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; ); 
Cc: draft-ietf-behave-nat-behavior-discovery@tools.ietf.org, 'Behave Chairs' <behave-chairs@tools.ietf.org>
Subject: [BEHAVE] changing XOR-RESPONSE-TARGET in draft-ietf-behave-nat-behavior-discovery-07
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/mail-archive/web/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>
X-List-Received-Date: Thu, 10 Sep 2009 16:08:21 -0000

As defined in draft-ietf-behave-nat-behavior-discovery-07, the
XOR-RESPONSE-TARGET attribute is sent from the client to server and asks the
server to send the response to an alternate IP address and alternate port.
This is used to test the NAT's filtering and mapping behavior.

During IESG review, it was suggested that security of Behavior Discovery could
be improved by changing XOR-RESPONSE-TARGET so that it only sends the response
to an alternate port (and eliminate the ability to specify an alternate IP
address).

If anyone sees a need for Behavior Discovery to send a response to alternate
IP address, please speak up now.  Currently the authors are planning to adjust
the document and re-submit it so that XOR-RESPONSE-TARGET can only send the
response to an alternate port.

-d




From dwing@cisco.com  Thu Sep 10 11:39:04 2009
Return-Path: <dwing@cisco.com>
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 1C4AF3A6AF6 for <behave@core3.amsl.com>; Thu, 10 Sep 2009 11:39:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.651
X-Spam-Level: 
X-Spam-Status: No, score=-6.651 tagged_above=-999 required=5 tests=[AWL=-0.052, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sUYJpYXYR5q2 for <behave@core3.amsl.com>; Thu, 10 Sep 2009 11:39:03 -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 EFF653A6A6B for <behave@ietf.org>; Thu, 10 Sep 2009 11:39:02 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArcEAKPkqEqrR7PE/2dsb2JhbACLHLtCiEYBkEYFhBiBWQ
X-IronPort-AV: E=Sophos;i="4.44,365,1249257600"; d="scan'208";a="188829973"
Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-3.cisco.com with ESMTP; 10 Sep 2009 18:39:18 +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 n8AIdIC6029871;  Thu, 10 Sep 2009 11:39:18 -0700
Received: from dwingwxp01 ([10.32.240.198]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n8AIdIwo007968; Thu, 10 Sep 2009 18:39:18 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Zhen Cao'" <caozhenpku@gmail.com>
References: <a7c8d0a30909080645t342f7bd7udfc553c0303f25ff@mail.gmail.com> <09f701ca30a0$01e90730$c5f0200a@cisco.com> <a7c8d0a30909091804j368a8a6fr4ee1b75eb7081559@mail.gmail.com> <073801ca31b6$60299ff0$c6f0200a@cisco.com> <a7c8d0a30909100304w69593812o29778ad80f28451c@mail.gmail.com>
Date: Thu, 10 Sep 2009 11:39:18 -0700
Message-ID: <004701ca3246$015ea5c0$c6f0200a@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
In-Reply-To: <a7c8d0a30909100304w69593812o29778ad80f28451c@mail.gmail.com>
Thread-Index: Acox/iekKiehZgLtQZm9sXfuj5eiuwARvIQQ
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=4663; t=1252607958; x=1253471958; 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]=20Stateless=20translation=20de finition |Sender:=20; bh=Tug+wtwVVyTv+dZpGT6eMBg3WpLM36eTzYKWHwipwl0=; b=RLcM0UHf9OBc7SdLt7PUsi04BoowW81x2p7PP1tZmf6KPAGEi9VQeBz3hG JMiQxKJPazHUyLM/q4G5wQoifj2QuKfeWZ7BEHT7SG426G9yReiZe81kRe/s 6eETYw5/9/;
Authentication-Results: sj-dkim-4; header.From=dwing@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; ); 
Cc: 'Behave WG' <behave@ietf.org>
Subject: Re: [BEHAVE] Stateless translation definition
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/mail-archive/web/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>
X-List-Received-Date: Thu, 10 Sep 2009 18:39:04 -0000

=20

> -----Original Message-----
> From: Zhen Cao [mailto:caozhenpku@gmail.com]=20
> Sent: Thursday, September 10, 2009 3:05 AM
> To: Dan Wing
> Cc: Behave WG
> Subject: Re: [BEHAVE] Stateless translation definition
>=20
> On Thu, Sep 10, 2009 at 9:31 AM, Dan Wing <dwing@cisco.com> wrote:
> >
> >
> >> -----Original Message-----
> >> From: Zhen Cao [mailto:caozhenpku@gmail.com]
> >> Sent: Wednesday, September 09, 2009 6:04 PM
> >> To: Dan Wing
> >> Cc: Behave WG
> >> Subject: Re: [BEHAVE] Stateless translation definition
> >>
> >> On Wed, Sep 9, 2009 at 12:18 AM, Dan Wing <dwing@cisco.com> wrote:
> >> >
> >> >
> >> > > -----Original Message-----
> >> > > From: behave-bounces@ietf.org
> >> > > [mailto:behave-bounces@ietf.org] On Behalf Of Zhen Cao
> >> > > Sent: Tuesday, September 08, 2009 6:46 AM
> >> > > To: Dave Thaler; Behave WG
> >> > > Subject: [BEHAVE] Stateless translation definition
> >> > >
> >> > > Hi Dave and all,
> >> > >
> >> > > I have a concern with respect to the definition of
> >> > > stateful/stateless translation. Could you help me? Thanks
> >> in advance.
> >> > >
> >> > > The framework draft defines stateful translation as:
> >> > >
> >> > >
> >> > > =A0 =A0 =A0 A translation algorithm may be said to
> >> > > =A0 =A0 =A0 "require state in a network element" or be=20
> "stateful" if the
> >> > > =A0 =A0 =A0 transmission or reception of a packet creates or
> >> modifies a data
> >> > > =A0 =A0 =A0 structure in the relevant network element.
> >> > >
> >> > >
> >> > > According to this definition, say, if hosts are configured
> >> > > with a public IPv4 address in the host-based translation
> >> > > (draft-huang-pnat-host-ipv6-02), and the used local prefix is
> >> > > unique, then the translation on prefix-nat will NOT create or
> >> > > modify any data structure. Can we call it stateless=20
> translation?
> >> >
> >> > Yes, that would be stateless translation on the network-based
> >> > NAT device.
> >> >
> >> > However, there is stateful translation in the host device:
> >> > specifically, a DNS query creates state inside of the host's
> >> > stack (that state maps IPv4 to IPv6).
> >>
> >> Since the WKP is unique, this actually does not create a=20
> 'state', it
> >> just append the ipv4 address to the well known prefix.
> >
> > There isn't enough IPv4 address space to map the entire IPv6
> > address space, so there is state and old mappings need to be
> > destroyed.
> >
> > For example, if an IPv4 application looks up host1.example.net,
> > the underlying Bump-in-the-Stack/-API of draft-huang-pnat-host-ipv6
> > will take that IPv4 application's API calls and do an AAAA
> > query over the air, which returns in AAAA response. =A0The
> > Bump-in-the-Stack/-API will create a mapping from that AAAA
> > address to an IPv4 address, and provide that IPv4 address
> > to the application. =A0When the IPv4 application looks up
> > host2.example.net, the same thing occurs, consuming another
> > IPv4 address in that mapping table inside the host. =A0This
> > continues until the IPv4 application has exhausted all of
> > the IPv4 mapping entries in the host, or until old entries
> > start being destroyed.
>=20
> Thanks for the detailed explanation of the above pnat 46 communication
> scenario. For pnat 44 communication, DNS responds with A records, we
> believe it is stateless.

Sorry I misunderstood; I thought you were discussing PNAT46.


Looking at the diagram in
http://tools.ietf.org/html/draft-huang-pnat-host-ipv6-01#section-2 and =
reading
the PNAT44COM definition in that section, the conclusion I reach is that =
it
can be done statelessly if both of these are true:

 1. each IPv6 host consumes one IPv4 address in the PNAT64 device;=20
    this allows a stateless, algorithmic mapping on the PNAT64 device
    similar to what is described in the IVI drafts and in
    =
http://tools.ietf.org/html/draft-ietf-behave-address-format-00#section-2.=
3

and
 2. there are only routable, non-overlapping IPv4 addresses on=20
    the IPv4 site.

But if either of those are false, there needs to be per-flow state =
somewhere.

-d



> > That is, at least, my understanding of the mapping and
> > NATting that is occuring in the host's stack. =A0If it works
> > some other way, please explain it.
> >
> > -d
> >
> >> > So the system, as a whole, is not stateless or stateful. =A0It
> >> > is both.
> >> >
> >> > -d
> >> >
> >> >
> >> > >
> >> > >
> >> > > Thanks for your help.
> >> > >
> >> > >
> >> > > Best regards,
> >> > > Zhen
> >> > >
> >> >
> >
> >


From xing@cernet.edu.cn  Thu Sep 10 16:01:09 2009
Return-Path: <xing@cernet.edu.cn>
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 726473A6810 for <behave@core3.amsl.com>; Thu, 10 Sep 2009 16:01:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.492
X-Spam-Level: *
X-Spam-Status: No, score=1.492 tagged_above=-999 required=5 tests=[AWL=-0.095,  BAYES_05=-1.11, FH_HAS_XAIMC=2.696]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5I+7jwxar-TT for <behave@core3.amsl.com>; Thu, 10 Sep 2009 16:01:08 -0700 (PDT)
Received: from cernet.edu.cn (sea.net.edu.cn [202.112.3.66]) by core3.amsl.com (Postfix) with SMTP id 28E5E3A63EC for <behave@ietf.org>; Thu, 10 Sep 2009 16:01:07 -0700 (PDT)
Received: from [192.168.1.100]([125.34.45.27]) by cernet.edu.cn(AIMC 3.2.0.0) with SMTP id jm04aa9e107; Fri, 11 Sep 2009 07:01:39 +0800
Message-ID: <4AA98542.60904@cernet.edu.cn>
Date: Fri, 11 Sep 2009 07:01:22 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Iljitsch van Beijnum <iljitsch@muada.com>
References: <0A5916B6-4B95-4818-B099-044701D4B659@free.fr> <B364BB7D-FABD-425A-BBE3-2E8695A7D6D5@muada.com>
In-Reply-To: <B364BB7D-FABD-425A-BBE3-2E8695A7D6D5@muada.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-AIMC-AUTH: xing
X-AIMC-MAILFROM: xing@cernet.edu.cn
X-AIMC-Msg-ID: eaDeslWB
Cc: Behave WG <behave@ietf.org>, Dave Thaler <dthaler@windows.microsoft.com>
Subject: Re: [BEHAVE] draft-ietf-behave-address-format-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/mail-archive/web/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>
X-List-Received-Date: Thu, 10 Sep 2009 23:01:09 -0000

Iljitsch van Beijnum 写道:
> On 1 Sep 2009, at 18:29 , Rémi Després wrote:
>
>> Here is a text that, without changing the conclusion, would in my 
>> understanding better reflect points that were made.
>
> I disagree with this. Leave the u/l and group bits alone.

we have methods to leave the u/l and group bits alone for the stateless 
translator even the prefix length is longer than 64 bits.

xing

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


From xing@cernet.edu.cn  Thu Sep 10 16:12:42 2009
Return-Path: <xing@cernet.edu.cn>
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 10F5828C199 for <behave@core3.amsl.com>; Thu, 10 Sep 2009 16:12:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.379
X-Spam-Level: *
X-Spam-Status: No, score=1.379 tagged_above=-999 required=5 tests=[AWL=0.082,  BAYES_00=-2.599, FH_HAS_XAIMC=2.696, J_CHICKENPOX_13=0.6, J_CHICKENPOX_19=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 ZKDWZ5BF9r1o for <behave@core3.amsl.com>; Thu, 10 Sep 2009 16:12:41 -0700 (PDT)
Received: from cernet.edu.cn (sea.net.edu.cn [202.112.3.66]) by core3.amsl.com (Postfix) with SMTP id 5E4ED28C174 for <behave@ietf.org>; Thu, 10 Sep 2009 16:12:40 -0700 (PDT)
Received: from [192.168.1.100]([125.34.45.27]) by cernet.edu.cn(AIMC 3.2.0.0) with SMTP id jm644aa9e3be; Fri, 11 Sep 2009 07:13:15 +0800
Message-ID: <4AA9880E.3000007@cernet.edu.cn>
Date: Fri, 11 Sep 2009 07:13:18 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: bo zhou <zhouboyj@gmail.com>
References: <36a593230908232300m45a10136wce25d01ef8bac439@mail.gmail.com>	<4A9B7BA1.6000807@cernet.edu.cn> <36a593230908310651kd76a383j28b845bb07ebba55@mail.gmail.com>
In-Reply-To: <36a593230908310651kd76a383j28b845bb07ebba55@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-AIMC-AUTH: xing
X-AIMC-MAILFROM: xing@cernet.edu.cn
X-AIMC-Msg-ID: e3RpslWB
Cc: denghui02@gmail.com, congxiao@cernet.edu.cn, behave@ietf.org, liu dapeng <maxpassion@gmail.com>, kyin@cisco.com, fred@cisco.com, phdgang@gmail.com
Subject: Re: [BEHAVE] Proposed text and comments for framework for IPv4/IPv6 translation
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/mail-archive/web/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>
X-List-Received-Date: Thu, 10 Sep 2009 23:12:42 -0000

bo zhou 写道:
>
>
>
>     However, if the consensus is to add the discussion on application
>     instances, I am happy to add the words.
>
> [bo] Yes, we want to introduce the application type to make the 
> definition more clearly.
we have made some modifications in draft-ietf-behave-v6v4-framework-01
>
>
>     (2) Please see the Sec. 1.2, the border between an IPvx network
>     and the IPvx Internet is not defined by NAT.
>
> [bo] Sorry, I cannot find any words in Sec.1.2 to define the 
> difference between network and Internet.

  An IPv4 network:  A specific network that has an IPv4-only
      deployment.  This could be an enterprise's IPv4-only network or an
      ISP's IPv4-only network.  The size of an IPv4 network is
      relatively small comparing to the global IPv4 Internet.

The key words are: "A specific network" and "relatively small comparing 
to the global IPv4 Internet".
>
>
>     (3) Other comments are inline.
>     [bo] Yes, we knew NAT-PT was deprecated by RFC 4966. However, the
>     comments we pointed out is focus on stateful translation's
>     limitation. We think "the stateful translation only support IPv6
>     initiated communication" is only related to NAT64. It is hard
>     to say "stateful translation can only support IPv6 initiated
>     communication" because "NAT64 can only do it". We agreed NAT64 is
>     one of significant stateful translation, but we do not agree it
>     represents all behaviours of stateful translation.
>

We are working on the standard of translation. NAT-PT was deprecated and 
the stateful translation proved by behave working group is NAT64 at this 
moment.
>
>     [bo]About the ALG issue, we should state "all IP packet payload
>     included IP address need do ALG".
>
Agree, if the end systems are in different address families.

xing




>  
>  
>  
>  
>
>     Regards,
>
>     xing
>
>
>     bo zhou 写道:
>
>         Hi Fred and others authors of framework for IPv4/IPv6 translation
>          We have some texts and comments for this draft. Originally,
>         we tried to propose our comments and discuss them inside last
>         Wed's interim meeting, Unfortunately, the shortage of time
>         caused we have no time to address them. Hence, we pointed them
>         out here.
>          1)  We need more clear IP family host definitions
>         Inside the draft, existing “IPv6-only” and “IPv4-only”
>         definitions are targeting to IP host capabilities, but there
>         are unclear descriptions of “application instances”. Hence we
>         propose the  IP family host shall be defined combining with
>         four aspects:
>         a. the application type installed on the host,
>         b.the IP family stack supported by a host
>         c.the IP family routing assigned by a network
>         d.available IP family connectivity
>         According to the above principles, following IP family host
>         definitions are suggested to replace current “IPv6-only” and
>         “IPv4-only” definitions and propose a new definition for
>         supplement:
>         IPv4 only host comprises an IPv4 enabled end system stack plus
>         routing in the network, IPv4 applications installed on the
>         host. It implies two application instances with installed IPv4
>         applications are capable of communication using IPv4, but not
>         IPv6 ……
>         IPv6 only host comprises an IPv6 enabled end system stack plus
>         routing in the network, IPv6 applications installed on the
>         host. It implies two application instances with installed IPv6
>         applications are capable of communication using IPv6, but not
>         IPv4 ……
>         IPv4-inherited IPv6 host comprises an IPv4/IPv6 enabled end
>         system dual-stack plus IPv6 routing in the network, IPv4/IPv6
>         applications installed on the host. It implies two application
>         instances with installed IPv4/IPv6 applications are capable of
>         communication using IPv6 – they have IPv4/IPv6 dual-stack,
>         network support including routing in IPv6, IPv4/IPv6
>         applications can communicate with IPv4/IPv6 hosts respectively.
>         Furthermore, the “An IPv6 network” are proposed to redefined
>         as: A specific network that has IPv6-only and IPv4-inherited
>         IPv6 implementation.
>          2）How to differentiate IPv6 network & IPv6 Internet
>         The difference between IPv4 network and IPv4 Internet could be
>         identified by CGN (NAT) functionalities. However, there are no
>         CGN(NAT) functionalities defined in IPv6 world. It’s difficult
>         to differentiate IPv6 network and Internet. Hence, we suggest
>         to re-define the IPv6 Internet in the framework draft based on
>         network scale size, as follows: IPv6 Internet means a global
>         system of interconnected IPv6 networks, including enterprise’s
>         IPv6 networks and ISP’s IPv6 networks.
>         Otherwise, we have to introduce a new NAT equipment with NAT66
>         functionalities to differentiate IPv6 network & IPv6 Internet.
>          3) Other comments related to the contexts
>         Comments for 3.1.1 and 3.2.2 about stateful translation
>         statements:
>         For stateful translation, the draft has mentioned “the
>         stateful translation only support IPv6 initiated
>         communication”. But NAT-PT could support both directional
>         communication without this limitation. Hence, we suggest to
>         remove this descriptions or point out it is only targeting to
>         NAT64
>
>
>     NAT-PT was deprecated by RFC 4966.
>
>
>         Comments for 3.3 about ALG descriptions:
>         It only list the demand for FTP ALG. But there should be
>         support any kind of applications in which IP address is
>         concluded in payload, such as SIP, RTSP. Hence, we suggest to
>         extend ALG scope avoid reader’s misunderstanding.
>
>
>     Yes, agree.
>
>          Hope all these are meaningful.
>          Regards,
>
>         Bo Zhou
>         China Mobile
>         ------------------------------------------------------------------------
>
>         _______________________________________________
>         Behave mailing list
>         Behave@ietf.org <mailto:Behave@ietf.org>
>         https://www.ietf.org/mailman/listinfo/behave
>          
>
>
>
>
>
> -- 
> Regards,
>
> Bo Zhou
> China Mobile
> ------------------------------------------------------------------------
>
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>   


From phdgang@gmail.com  Thu Sep 10 20:06:40 2009
Return-Path: <phdgang@gmail.com>
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 1ED603A69C5 for <behave@core3.amsl.com>; Thu, 10 Sep 2009 20:06:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.185
X-Spam-Level: *
X-Spam-Status: No, score=1.185 tagged_above=-999 required=5 tests=[AWL=-1.356,  BAYES_05=-1.11, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, J_CHICKENPOX_19=0.6, MIME_CHARSET_FARAWAY=2.45]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sAOKUk0cTpXU for <behave@core3.amsl.com>; Thu, 10 Sep 2009 20:06:30 -0700 (PDT)
Received: from mail-px0-f181.google.com (mail-px0-f181.google.com [209.85.216.181]) by core3.amsl.com (Postfix) with ESMTP id 3A9FB3A688D for <behave@ietf.org>; Thu, 10 Sep 2009 20:06:29 -0700 (PDT)
Received: by pxi11 with SMTP id 11so544580pxi.17 for <behave@ietf.org>; Thu, 10 Sep 2009 20:07:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=8F62k1LBZ+51pt+lsEirAvXj8dG70YocWBwIrvt1K8s=; b=pP+rDk+iMBK8jkAt6ie8v9GZRHAOToW9H3COw8jsr5hJggGkMNJkR2gbXNnEqypzFk Kq/POSPqkQtQVJN+T1I/14keu3g4rjSB2EcVWfI4pP6vwdDFtTa7FMADwSC/A8SziJ6t yLZrYGEELtN4SyLWjYVZuCPptt4cdjBtWQp2Q=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=WzWlZX0DqTbc7pphJPxHialoo7WO6+2LQ8PR/JG64kQsQGsEZA7ddAYo+LUMFWPkG4 9LqwrJTV8SA6bMqioF4BOuQLmamPC//cExr3SiWsskQt9QSYuhLetXUsbjbzPgGbHfcQ locNFqRaFZDKwmk7panh2Qyuseft8IP5ghTBc=
MIME-Version: 1.0
Received: by 10.114.236.28 with SMTP id j28mr4302766wah.162.1252638426229;  Thu, 10 Sep 2009 20:07:06 -0700 (PDT)
In-Reply-To: <4AA9880E.3000007@cernet.edu.cn>
References: <36a593230908232300m45a10136wce25d01ef8bac439@mail.gmail.com> <4A9B7BA1.6000807@cernet.edu.cn> <36a593230908310651kd76a383j28b845bb07ebba55@mail.gmail.com> <4AA9880E.3000007@cernet.edu.cn>
Date: Fri, 11 Sep 2009 11:07:06 +0800
Message-ID: <36ba02b00909102007q7edbe8d1p2052a1853c233486@mail.gmail.com>
From: Chen Gang <phdgang@gmail.com>
To: Xing Li <xing@cernet.edu.cn>
Content-Type: multipart/alternative; boundary=0016e64bdaea6d6d220473449ca5
Cc: denghui02@gmail.com, congxiao@cernet.edu.cn, behave@ietf.org, liu dapeng <maxpassion@gmail.com>, kyin@cisco.com, bo zhou <zhouboyj@gmail.com>, fred@cisco.com
Subject: Re: [BEHAVE] Proposed text and comments for framework for IPv4/IPv6 translation
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/mail-archive/web/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>
X-List-Received-Date: Fri, 11 Sep 2009 03:06:40 -0000

--0016e64bdaea6d6d220473449ca5
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: quoted-printable

Hello Xing,

With regard to the latest difinition of IPv6-only, there are some questioin=
s
for clarifications.

Within the sentence "It implies that two application instances are capable
of communicating using IPv6, but not IPv4 - they have an IPv6 stack", does
"two application instances" means "IPv4 application instances and IPv6
application instances"?

If that is true, I guess "IPv6-only" need do some sort of application ALG o=
r
host-based translation in order to let IPv4 application to accomodate a
IPv6-only environment.

If my understanding is correct, you may also need to clarify this meaning i=
n
the IPv6-only definition or separate this meaning to new defined terms, lik=
e
Bo suggested "
IPv4-inherited IPv6 host".

Thanks

BRs

Gang




2009/9/11 Xing Li <xing@cernet.edu.cn>

> bo zhou =D0=B4=B5=C0:
>
>>
>>
>>
>>    However, if the consensus is to add the discussion on application
>>    instances, I am happy to add the words.
>>
>> [bo] Yes, we want to introduce the application type to make the definiti=
on
>> more clearly.
>>
> we have made some modifications in draft-ietf-behave-v6v4-framework-01
>
>>
>>
>>    (2) Please see the Sec. 1.2, the border between an IPvx network
>>    and the IPvx Internet is not defined by NAT.
>>
>> [bo] Sorry, I cannot find any words in Sec.1.2 to define the difference
>> between network and Internet.
>>
>
>  An IPv4 network:  A specific network that has an IPv4-only
>     deployment.  This could be an enterprise's IPv4-only network or an
>     ISP's IPv4-only network.  The size of an IPv4 network is
>     relatively small comparing to the global IPv4 Internet.
>
> The key words are: "A specific network" and "relatively small comparing t=
o
> the global IPv4 Internet".
>
>>
>>
>>    (3) Other comments are inline.
>>    [bo] Yes, we knew NAT-PT was deprecated by RFC 4966. However, the
>>    comments we pointed out is focus on stateful translation's
>>    limitation. We think "the stateful translation only support IPv6
>>    initiated communication" is only related to NAT64. It is hard
>>    to say "stateful translation can only support IPv6 initiated
>>    communication" because "NAT64 can only do it". We agreed NAT64 is
>>    one of significant stateful translation, but we do not agree it
>>    represents all behaviours of stateful translation.
>>
>>
> We are working on the standard of translation. NAT-PT was deprecated and
> the stateful translation proved by behave working group is NAT64 at this
> moment.
>
>>
>>    [bo]About the ALG issue, we should state "all IP packet payload
>>    included IP address need do ALG".
>>
>> Agree, if the end systems are in different address families.
>
> xing
>
>
>
>
>
>>    Regards,
>>
>>    xing
>>
>>
>>    bo zhou =D0=B4=B5=C0:
>>
>>        Hi Fred and others authors of framework for IPv4/IPv6 translation
>>         We have some texts and comments for this draft. Originally,
>>        we tried to propose our comments and discuss them inside last
>>        Wed's interim meeting, Unfortunately, the shortage of time
>>        caused we have no time to address them. Hence, we pointed them
>>        out here.
>>         1)  We need more clear IP family host definitions
>>        Inside the draft, existing =A1=B0IPv6-only=A1=B1 and =A1=B0IPv4-o=
nly=A1=B1
>>        definitions are targeting to IP host capabilities, but there
>>        are unclear descriptions of =A1=B0application instances=A1=B1. He=
nce we
>>        propose the  IP family host shall be defined combining with
>>        four aspects:
>>        a. the application type installed on the host,
>>        b.the IP family stack supported by a host
>>        c.the IP family routing assigned by a network
>>        d.available IP family connectivity
>>        According to the above principles, following IP family host
>>        definitions are suggested to replace current =A1=B0IPv6-only=A1=
=B1 and
>>        =A1=B0IPv4-only=A1=B1 definitions and propose a new definition fo=
r
>>        supplement:
>>        IPv4 only host comprises an IPv4 enabled end system stack plus
>>        routing in the network, IPv4 applications installed on the
>>        host. It implies two application instances with installed IPv4
>>        applications are capable of communication using IPv4, but not
>>        IPv6 =A1=AD=A1=AD
>>        IPv6 only host comprises an IPv6 enabled end system stack plus
>>        routing in the network, IPv6 applications installed on the
>>        host. It implies two application instances with installed IPv6
>>        applications are capable of communication using IPv6, but not
>>        IPv4 =A1=AD=A1=AD
>>        IPv4-inherited IPv6 host comprises an IPv4/IPv6 enabled end
>>        system dual-stack plus IPv6 routing in the network, IPv4/IPv6
>>        applications installed on the host. It implies two application
>>        instances with installed IPv4/IPv6 applications are capable of
>>        communication using IPv6 =A8C they have IPv4/IPv6 dual-stack,
>>        network support including routing in IPv6, IPv4/IPv6
>>        applications can communicate with IPv4/IPv6 hosts respectively.
>>        Furthermore, the =A1=B0An IPv6 network=A1=B1 are proposed to rede=
fined
>>        as: A specific network that has IPv6-only and IPv4-inherited
>>        IPv6 implementation.
>>         2=A3=A9How to differentiate IPv6 network & IPv6 Internet
>>        The difference between IPv4 network and IPv4 Internet could be
>>        identified by CGN (NAT) functionalities. However, there are no
>>        CGN(NAT) functionalities defined in IPv6 world. It=A1=AFs difficu=
lt
>>        to differentiate IPv6 network and Internet. Hence, we suggest
>>        to re-define the IPv6 Internet in the framework draft based on
>>        network scale size, as follows: IPv6 Internet means a global
>>        system of interconnected IPv6 networks, including enterprise=A1=
=AFs
>>        IPv6 networks and ISP=A1=AFs IPv6 networks.
>>        Otherwise, we have to introduce a new NAT equipment with NAT66
>>        functionalities to differentiate IPv6 network & IPv6 Internet.
>>         3) Other comments related to the contexts
>>        Comments for 3.1.1 and 3.2.2 about stateful translation
>>        statements:
>>        For stateful translation, the draft has mentioned =A1=B0the
>>        stateful translation only support IPv6 initiated
>>        communication=A1=B1. But NAT-PT could support both directional
>>        communication without this limitation. Hence, we suggest to
>>        remove this descriptions or point out it is only targeting to
>>        NAT64
>>
>>
>>    NAT-PT was deprecated by RFC 4966.
>>
>>
>>        Comments for 3.3 about ALG descriptions:
>>        It only list the demand for FTP ALG. But there should be
>>        support any kind of applications in which IP address is
>>        concluded in payload, such as SIP, RTSP. Hence, we suggest to
>>        extend ALG scope avoid reader=A1=AFs misunderstanding.
>>
>>
>>    Yes, agree.
>>
>>         Hope all these are meaningful.
>>         Regards,
>>
>>        Bo Zhou
>>        China Mobile
>>
>>  -----------------------------------------------------------------------=
-
>>
>>        _______________________________________________
>>        Behave mailing list
>>        Behave@ietf.org <mailto:Behave@ietf.org>
>>        https://www.ietf.org/mailman/listinfo/behave
>>
>>
>>
>>
>>
>> --
>> Regards,
>>
>> Bo Zhou
>> China Mobile
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Behave mailing list
>> Behave@ietf.org
>> https://www.ietf.org/mailman/listinfo/behave
>>
>>
>
>


--=20
=B3=C2=B8=D5
phdgang@gmail.com

--0016e64bdaea6d6d220473449ca5
Content-Type: text/html; charset=GB2312
Content-Transfer-Encoding: quoted-printable

<div>Hello Xing,</div>
<div>&nbsp;</div>
<div>With regard to the latest difinition of IPv6-only, there are some ques=
tioins for clarifications.</div>
<div>&nbsp;</div>
<div>Within the sentence &quot;It implies that <font color=3D"#ff0000">two =
application instances</font> are capable of communicating using IPv6, but n=
ot IPv4 - they have an IPv6 stack&quot;, does &quot;two application instanc=
es&quot; means &quot;IPv4 application instances and IPv6 application instan=
ces&quot;?</div>

<div>&nbsp;</div>
<div>If that is true, I guess &quot;IPv6-only&quot; need do&nbsp;some sort =
of application ALG or host-based translation&nbsp;in&nbsp;order&nbsp;to let=
 IPv4 application to&nbsp;accomodate a IPv6-only environment.</div>
<div>&nbsp;</div>
<div>If my understanding is correct, you may also need to clarify this mean=
ing in the IPv6-only definition or separate this meaning to new defined ter=
ms, like Bo suggested &quot;<br>IPv4-inherited IPv6 host&quot;.</div>
<div>&nbsp;</div>
<div>Thanks</div>
<div>&nbsp;</div>
<div>BRs</div>
<div>&nbsp;</div>
<div>Gang</div>
<div>&nbsp;</div>
<div><br><br>&nbsp;</div>
<div class=3D"gmail_quote">2009/9/11 Xing Li <span dir=3D"ltr">&lt;<a href=
=3D"mailto:xing@cernet.edu.cn">xing@cernet.edu.cn</a>&gt;</span><br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">bo zhou =D0=B4=B5=C0:=20
<div class=3D"im"><br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><br><br><br>&nbsp; &nbsp;However=
, if the consensus is to add the discussion on application<br>&nbsp; &nbsp;=
instances, I am happy to add the words.<br>
<br>[bo] Yes, we want to introduce the application type to make the definit=
ion more clearly.<br></blockquote></div>we have made some modifications in =
draft-ietf-behave-v6v4-framework-01=20
<div class=3D"im"><br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><br><br>&nbsp; &nbsp;(2) Please =
see the Sec. 1.2, the border between an IPvx network<br>&nbsp; &nbsp;and th=
e IPvx Internet is not defined by NAT.<br>
<br>[bo] Sorry, I cannot find any words in Sec.1.2 to define the difference=
 between network and Internet.<br></blockquote><br></div>&nbsp;An IPv4 netw=
ork: &nbsp;A specific network that has an IPv4-only<br>&nbsp; &nbsp; deploy=
ment. &nbsp;This could be an enterprise&#39;s IPv4-only network or an<br>
&nbsp; &nbsp; ISP&#39;s IPv4-only network. &nbsp;The size of an IPv4 networ=
k is<br>&nbsp; &nbsp; relatively small comparing to the global IPv4 Interne=
t.<br><br>The key words are: &quot;A specific network&quot; and &quot;relat=
ively small comparing to the global IPv4 Internet&quot;.=20
<div class=3D"im"><br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><br><br>&nbsp; &nbsp;(3) Other c=
omments are inline.<br>&nbsp; &nbsp;[bo] Yes, we knew NAT-PT was deprecated=
 by RFC 4966. However, the<br>
&nbsp; &nbsp;comments we pointed out is focus on stateful translation&#39;s=
<br>&nbsp; &nbsp;limitation. We think &quot;the stateful translation only s=
upport IPv6<br>&nbsp; &nbsp;initiated communication&quot; is only related t=
o NAT64. It is hard<br>&nbsp; &nbsp;to say &quot;stateful translation can o=
nly support IPv6 initiated<br>
&nbsp; &nbsp;communication&quot; because &quot;NAT64 can only do it&quot;. =
We agreed NAT64 is<br>&nbsp; &nbsp;one of significant stateful translation,=
 but we do not agree it<br>&nbsp; &nbsp;represents all behaviours of statef=
ul translation.<br><br></blockquote>
<br></div>We are working on the standard of translation. NAT-PT was depreca=
ted and the stateful translation proved by behave working group is NAT64 at=
 this moment.=20
<div class=3D"im"><br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><br>&nbsp; &nbsp;[bo]About the A=
LG issue, we should state &quot;all IP packet payload<br>&nbsp; &nbsp;inclu=
ded IP address need do ALG&quot;.<br>
<br></blockquote></div>Agree, if the end systems are in different address f=
amilies.<br><br>xing<br><br><br><br><br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>
<div></div>
<div class=3D"h5">&nbsp;&nbsp;&nbsp;&nbsp;<br>&nbsp; &nbsp;Regards,<br><br>=
&nbsp; &nbsp;xing<br><br><br>&nbsp; &nbsp;bo zhou =D0=B4=B5=C0:<br><br>&nbs=
p; &nbsp; &nbsp; &nbsp;Hi Fred and others authors of framework for IPv4/IPv=
6 translation<br>&nbsp; &nbsp; &nbsp; &nbsp; We have some texts and comment=
s for this draft. Originally,<br>
&nbsp; &nbsp; &nbsp; &nbsp;we tried to propose our comments and discuss the=
m inside last<br>&nbsp; &nbsp; &nbsp; &nbsp;Wed&#39;s interim meeting, Unfo=
rtunately, the shortage of time<br>&nbsp; &nbsp; &nbsp; &nbsp;caused we hav=
e no time to address them. Hence, we pointed them<br>&nbsp; &nbsp; &nbsp; &=
nbsp;out here.<br>
&nbsp; &nbsp; &nbsp; &nbsp; 1) &nbsp;We need more clear IP family host defi=
nitions<br>&nbsp; &nbsp; &nbsp; &nbsp;Inside the draft, existing &ldquo;IPv=
6-only&rdquo; and &ldquo;IPv4-only&rdquo;<br>&nbsp; &nbsp; &nbsp; &nbsp;def=
initions are targeting to IP host capabilities, but there<br>&nbsp; &nbsp; =
&nbsp; &nbsp;are unclear descriptions of &ldquo;application instances&rdquo=
;. Hence we<br>
&nbsp; &nbsp; &nbsp; &nbsp;propose the &nbsp;IP family host shall be define=
d combining with<br>&nbsp; &nbsp; &nbsp; &nbsp;four aspects:<br>&nbsp; &nbs=
p; &nbsp; &nbsp;a. the application type installed on the host,<br>&nbsp; &n=
bsp; &nbsp; &nbsp;b.the IP family stack supported by a host<br>&nbsp; &nbsp=
; &nbsp; &nbsp;c.the IP family routing assigned by a network<br>
&nbsp; &nbsp; &nbsp; &nbsp;d.available IP family connectivity<br>&nbsp; &nb=
sp; &nbsp; &nbsp;According to the above principles, following IP family hos=
t<br>&nbsp; &nbsp; &nbsp; &nbsp;definitions are suggested to replace curren=
t &ldquo;IPv6-only&rdquo; and<br>&nbsp; &nbsp; &nbsp; &nbsp;&ldquo;IPv4-onl=
y&rdquo; definitions and propose a new definition for<br>
&nbsp; &nbsp; &nbsp; &nbsp;supplement:<br>&nbsp; &nbsp; &nbsp; &nbsp;IPv4 o=
nly host comprises an IPv4 enabled end system stack plus<br>&nbsp; &nbsp; &=
nbsp; &nbsp;routing in the network, IPv4 applications installed on the<br>&=
nbsp; &nbsp; &nbsp; &nbsp;host. It implies two application instances with i=
nstalled IPv4<br>
&nbsp; &nbsp; &nbsp; &nbsp;applications are capable of communication using =
IPv4, but not<br>&nbsp; &nbsp; &nbsp; &nbsp;IPv6 &hellip;&hellip;<br>&nbsp;=
 &nbsp; &nbsp; &nbsp;IPv6 only host comprises an IPv6 enabled end system st=
ack plus<br>&nbsp; &nbsp; &nbsp; &nbsp;routing in the network, IPv6 applica=
tions installed on the<br>
&nbsp; &nbsp; &nbsp; &nbsp;host. It implies two application instances with =
installed IPv6<br>&nbsp; &nbsp; &nbsp; &nbsp;applications are capable of co=
mmunication using IPv6, but not<br>&nbsp; &nbsp; &nbsp; &nbsp;IPv4 &hellip;=
&hellip;<br>&nbsp; &nbsp; &nbsp; &nbsp;IPv4-inherited IPv6 host comprises a=
n IPv4/IPv6 enabled end<br>
&nbsp; &nbsp; &nbsp; &nbsp;system dual-stack plus IPv6 routing in the netwo=
rk, IPv4/IPv6<br>&nbsp; &nbsp; &nbsp; &nbsp;applications installed on the h=
ost. It implies two application<br>&nbsp; &nbsp; &nbsp; &nbsp;instances wit=
h installed IPv4/IPv6 applications are capable of<br>&nbsp; &nbsp; &nbsp; &=
nbsp;communication using IPv6 &ndash; they have IPv4/IPv6 dual-stack,<br>
&nbsp; &nbsp; &nbsp; &nbsp;network support including routing in IPv6, IPv4/=
IPv6<br>&nbsp; &nbsp; &nbsp; &nbsp;applications can communicate with IPv4/I=
Pv6 hosts respectively.<br>&nbsp; &nbsp; &nbsp; &nbsp;Furthermore, the &ldq=
uo;An IPv6 network&rdquo; are proposed to redefined<br>&nbsp; &nbsp; &nbsp;=
 &nbsp;as: A specific network that has IPv6-only and IPv4-inherited<br>
&nbsp; &nbsp; &nbsp; &nbsp;IPv6 implementation.<br>&nbsp; &nbsp; &nbsp; &nb=
sp; 2=A3=A9How to differentiate IPv6 network &amp; IPv6 Internet<br>&nbsp; =
&nbsp; &nbsp; &nbsp;The difference between IPv4 network and IPv4 Internet c=
ould be<br>&nbsp; &nbsp; &nbsp; &nbsp;identified by CGN (NAT) functionaliti=
es. However, there are no<br>
&nbsp; &nbsp; &nbsp; &nbsp;CGN(NAT) functionalities defined in IPv6 world. =
It&rsquo;s difficult<br>&nbsp; &nbsp; &nbsp; &nbsp;to differentiate IPv6 ne=
twork and Internet. Hence, we suggest<br>&nbsp; &nbsp; &nbsp; &nbsp;to re-d=
efine the IPv6 Internet in the framework draft based on<br>&nbsp; &nbsp; &n=
bsp; &nbsp;network scale size, as follows: IPv6 Internet means a global<br>
&nbsp; &nbsp; &nbsp; &nbsp;system of interconnected IPv6 networks, includin=
g enterprise&rsquo;s<br>&nbsp; &nbsp; &nbsp; &nbsp;IPv6 networks and ISP&rs=
quo;s IPv6 networks.<br>&nbsp; &nbsp; &nbsp; &nbsp;Otherwise, we have to in=
troduce a new NAT equipment with NAT66<br>&nbsp; &nbsp; &nbsp; &nbsp;functi=
onalities to differentiate IPv6 network &amp; IPv6 Internet.<br>
&nbsp; &nbsp; &nbsp; &nbsp; 3) Other comments related to the contexts<br>&n=
bsp; &nbsp; &nbsp; &nbsp;Comments for 3.1.1 and 3.2.2 about stateful transl=
ation<br>&nbsp; &nbsp; &nbsp; &nbsp;statements:<br>&nbsp; &nbsp; &nbsp; &nb=
sp;For stateful translation, the draft has mentioned &ldquo;the<br>&nbsp; &=
nbsp; &nbsp; &nbsp;stateful translation only support IPv6 initiated<br>
&nbsp; &nbsp; &nbsp; &nbsp;communication&rdquo;. But NAT-PT could support b=
oth directional<br>&nbsp; &nbsp; &nbsp; &nbsp;communication without this li=
mitation. Hence, we suggest to<br>&nbsp; &nbsp; &nbsp; &nbsp;remove this de=
scriptions or point out it is only targeting to<br>&nbsp; &nbsp; &nbsp; &nb=
sp;NAT64<br>
<br><br>&nbsp; &nbsp;NAT-PT was deprecated by RFC 4966.<br><br><br>&nbsp; &=
nbsp; &nbsp; &nbsp;Comments for 3.3 about ALG descriptions:<br>&nbsp; &nbsp=
; &nbsp; &nbsp;It only list the demand for FTP ALG. But there should be<br>=
&nbsp; &nbsp; &nbsp; &nbsp;support any kind of applications in which IP add=
ress is<br>
&nbsp; &nbsp; &nbsp; &nbsp;concluded in payload, such as SIP, RTSP. Hence, =
we suggest to<br>&nbsp; &nbsp; &nbsp; &nbsp;extend ALG scope avoid reader&r=
squo;s misunderstanding.<br><br><br>&nbsp; &nbsp;Yes, agree.<br><br>&nbsp; =
&nbsp; &nbsp; &nbsp; Hope all these are meaningful.<br>&nbsp; &nbsp; &nbsp;=
 &nbsp; Regards,<br>
<br>&nbsp; &nbsp; &nbsp; &nbsp;Bo Zhou<br>&nbsp; &nbsp; &nbsp; &nbsp;China =
Mobile<br>&nbsp; &nbsp; &nbsp; &nbsp;--------------------------------------=
----------------------------------<br><br>&nbsp; &nbsp; &nbsp; &nbsp;______=
_________________________________________<br>&nbsp; &nbsp; &nbsp; &nbsp;Beh=
ave mailing list<br></div>
</div>&nbsp; &nbsp; &nbsp; &nbsp;<a href=3D"mailto:Behave@ietf.org" target=
=3D"_blank">Behave@ietf.org</a> &lt;mailto:<a href=3D"mailto:Behave@ietf.or=
g" target=3D"_blank">Behave@ietf.org</a>&gt;=20
<div class=3D"im"><br>&nbsp; &nbsp; &nbsp; &nbsp;<a href=3D"https://www.iet=
f.org/mailman/listinfo/behave" target=3D"_blank">https://www.ietf.org/mailm=
an/listinfo/behave</a><br>&nbsp; &nbsp; &nbsp; &nbsp; <br><br><br><br><br>-=
- <br>Regards,<br><br>Bo Zhou<br>China Mobile<br>
------------------------------------------------------------------------<br=
><br>_______________________________________________<br>Behave mailing list=
<br><a href=3D"mailto:Behave@ietf.org" target=3D"_blank">Behave@ietf.org</a=
><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/behave" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/behave</a><br>&nbsp;<br></div></block=
quote><br></blockquote></div><br><br clear=3D"all">
<div></div><br>-- <br>=B3=C2=B8=D5<br><a href=3D"mailto:phdgang@gmail.com">=
phdgang@gmail.com</a><br>

--0016e64bdaea6d6d220473449ca5--

From zhouboyj@gmail.com  Thu Sep 10 22:41:15 2009
Return-Path: <zhouboyj@gmail.com>
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 081E83A6AA7 for <behave@core3.amsl.com>; Thu, 10 Sep 2009 22:41:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.731
X-Spam-Level: 
X-Spam-Status: No, score=0.731 tagged_above=-999 required=5 tests=[AWL=-2.180,  BAYES_20=-0.74, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, J_CHICKENPOX_19=0.6, MIME_CHARSET_FARAWAY=2.45]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BoozO6UzmB3Z for <behave@core3.amsl.com>; Thu, 10 Sep 2009 22:41:03 -0700 (PDT)
Received: from mail-iw0-f202.google.com (mail-iw0-f202.google.com [209.85.223.202]) by core3.amsl.com (Postfix) with ESMTP id 7E1F93A68E5 for <behave@ietf.org>; Thu, 10 Sep 2009 22:41:03 -0700 (PDT)
Received: by iwn40 with SMTP id 40so381938iwn.32 for <behave@ietf.org>; Thu, 10 Sep 2009 22:41:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=gNVLClxElKjet1KTFc17U4Xxrl19XzhHzYRPNwOLz1I=; b=SFRBrmENJnAOIwZqzgxE8WgCMhwmW3dtQXKVaGfxYBo4JjJeVuWAFh1sztvuhghimI 7RaVLnqN30hASE5dBlclmAO2HU086o/eS+1IeSlRShX/AXmaTLgsiHo45xVaMj5lYWRn opRFP07SX9NgF8wuSPy+Frqdltjo7mk9eMGQo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=FMwIFc2LBQWoj/KbE2dBVgxFY7bCJ7KDsSA8l5LN4T7BPHc9BdC/8JmzGdvhWqGeKH CUQFPixXI/Y9B4x11SVR9Bk39VF9syW1xPaOLWi3bGwuha9nBMVdLA+ddasr6xFZR4Hi HTI3+h/g3gRb/a53sFejFeWadrPDMU8X8uDUE=
MIME-Version: 1.0
Received: by 10.231.122.139 with SMTP id l11mr3086163ibr.53.1252647687293;  Thu, 10 Sep 2009 22:41:27 -0700 (PDT)
In-Reply-To: <36ba02b00909102007q7edbe8d1p2052a1853c233486@mail.gmail.com>
References: <36a593230908232300m45a10136wce25d01ef8bac439@mail.gmail.com> <4A9B7BA1.6000807@cernet.edu.cn> <36a593230908310651kd76a383j28b845bb07ebba55@mail.gmail.com> <4AA9880E.3000007@cernet.edu.cn> <36ba02b00909102007q7edbe8d1p2052a1853c233486@mail.gmail.com>
Date: Fri, 11 Sep 2009 13:41:27 +0800
Message-ID: <36a593230909102241w7a71cae0w3593dc48cff69dac@mail.gmail.com>
From: bo zhou <zhouboyj@gmail.com>
To: Chen Gang <phdgang@gmail.com>
Content-Type: multipart/alternative; boundary=001485f99caa6e0d00047346c439
Cc: denghui02@gmail.com, congxiao@cernet.edu.cn, behave@ietf.org, liu dapeng <maxpassion@gmail.com>, kyin@cisco.com, Xing Li <xing@cernet.edu.cn>, fred@cisco.com
Subject: Re: [BEHAVE] Proposed text and comments for framework for IPv4/IPv6 translation
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/mail-archive/web/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>
X-List-Received-Date: Fri, 11 Sep 2009 05:41:15 -0000

--001485f99caa6e0d00047346c439
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: quoted-printable

For my understanding, "two application instances" here indicates two
IPv6-only instances, like two IPv6  host, both installed IPv6 application,
and they want to communicate with each other via IPv6 network.
Am I right?

Regards,

Bo Zhou

2009/9/11 Chen Gang <phdgang@gmail.com>

> Hello Xing,
>
> With regard to the latest difinition of IPv6-only, there are some
> questioins for clarifications.
>
> Within the sentence "It implies that two application instances are capabl=
e
> of communicating using IPv6, but not IPv4 - they have an IPv6 stack", doe=
s
> "two application instances" means "IPv4 application instances and IPv6
> application instances"?
>
> If that is true, I guess "IPv6-only" need do some sort of application ALG
> or host-based translation in order to let IPv4 application to accomodate =
a
> IPv6-only environment.
>
> If my understanding is correct, you may also need to clarify this meaning
> in the IPv6-only definition or separate this meaning to new defined terms=
,
> like Bo suggested "
> IPv4-inherited IPv6 host".
>
> Thanks
>
> BRs
>
> Gang
>
>
>
>
> 2009/9/11 Xing Li <xing@cernet.edu.cn>
>
> bo zhou =D0=B4=B5=C0:
>>
>>>
>>>
>>>
>>>    However, if the consensus is to add the discussion on application
>>>    instances, I am happy to add the words.
>>>
>>> [bo] Yes, we want to introduce the application type to make the
>>> definition more clearly.
>>>
>> we have made some modifications in draft-ietf-behave-v6v4-framework-01
>>
>>>
>>>
>>>    (2) Please see the Sec. 1.2, the border between an IPvx network
>>>    and the IPvx Internet is not defined by NAT.
>>>
>>> [bo] Sorry, I cannot find any words in Sec.1.2 to define the difference
>>> between network and Internet.
>>>
>>
>>  An IPv4 network:  A specific network that has an IPv4-only
>>     deployment.  This could be an enterprise's IPv4-only network or an
>>     ISP's IPv4-only network.  The size of an IPv4 network is
>>     relatively small comparing to the global IPv4 Internet.
>>
>> The key words are: "A specific network" and "relatively small comparing =
to
>> the global IPv4 Internet".
>>
>>>
>>>
>>>    (3) Other comments are inline.
>>>    [bo] Yes, we knew NAT-PT was deprecated by RFC 4966. However, the
>>>    comments we pointed out is focus on stateful translation's
>>>    limitation. We think "the stateful translation only support IPv6
>>>    initiated communication" is only related to NAT64. It is hard
>>>    to say "stateful translation can only support IPv6 initiated
>>>    communication" because "NAT64 can only do it". We agreed NAT64 is
>>>    one of significant stateful translation, but we do not agree it
>>>    represents all behaviours of stateful translation.
>>>
>>>
>> We are working on the standard of translation. NAT-PT was deprecated and
>> the stateful translation proved by behave working group is NAT64 at this
>> moment.
>>
>>>
>>>    [bo]About the ALG issue, we should state "all IP packet payload
>>>    included IP address need do ALG".
>>>
>>> Agree, if the end systems are in different address families.
>>
>> xing
>>
>>
>>
>>
>>
>>>    Regards,
>>>
>>>    xing
>>>
>>>
>>>    bo zhou =D0=B4=B5=C0:
>>>
>>>        Hi Fred and others authors of framework for IPv4/IPv6 translatio=
n
>>>         We have some texts and comments for this draft. Originally,
>>>        we tried to propose our comments and discuss them inside last
>>>        Wed's interim meeting, Unfortunately, the shortage of time
>>>        caused we have no time to address them. Hence, we pointed them
>>>        out here.
>>>         1)  We need more clear IP family host definitions
>>>        Inside the draft, existing =A1=B0IPv6-only=A1=B1 and =A1=B0IPv4-=
only=A1=B1
>>>        definitions are targeting to IP host capabilities, but there
>>>        are unclear descriptions of =A1=B0application instances=A1=B1. H=
ence we
>>>        propose the  IP family host shall be defined combining with
>>>        four aspects:
>>>        a. the application type installed on the host,
>>>        b.the IP family stack supported by a host
>>>        c.the IP family routing assigned by a network
>>>        d.available IP family connectivity
>>>        According to the above principles, following IP family host
>>>        definitions are suggested to replace current =A1=B0IPv6-only=A1=
=B1 and
>>>        =A1=B0IPv4-only=A1=B1 definitions and propose a new definition f=
or
>>>        supplement:
>>>        IPv4 only host comprises an IPv4 enabled end system stack plus
>>>        routing in the network, IPv4 applications installed on the
>>>        host. It implies two application instances with installed IPv4
>>>        applications are capable of communication using IPv4, but not
>>>        IPv6 =A1=AD=A1=AD
>>>        IPv6 only host comprises an IPv6 enabled end system stack plus
>>>        routing in the network, IPv6 applications installed on the
>>>        host. It implies two application instances with installed IPv6
>>>        applications are capable of communication using IPv6, but not
>>>        IPv4 =A1=AD=A1=AD
>>>        IPv4-inherited IPv6 host comprises an IPv4/IPv6 enabled end
>>>        system dual-stack plus IPv6 routing in the network, IPv4/IPv6
>>>        applications installed on the host. It implies two application
>>>        instances with installed IPv4/IPv6 applications are capable of
>>>        communication using IPv6 =A8C they have IPv4/IPv6 dual-stack,
>>>        network support including routing in IPv6, IPv4/IPv6
>>>        applications can communicate with IPv4/IPv6 hosts respectively.
>>>        Furthermore, the =A1=B0An IPv6 network=A1=B1 are proposed to red=
efined
>>>        as: A specific network that has IPv6-only and IPv4-inherited
>>>        IPv6 implementation.
>>>         2=A3=A9How to differentiate IPv6 network & IPv6 Internet
>>>        The difference between IPv4 network and IPv4 Internet could be
>>>        identified by CGN (NAT) functionalities. However, there are no
>>>        CGN(NAT) functionalities defined in IPv6 world. It=A1=AFs diffic=
ult
>>>        to differentiate IPv6 network and Internet. Hence, we suggest
>>>        to re-define the IPv6 Internet in the framework draft based on
>>>        network scale size, as follows: IPv6 Internet means a global
>>>        system of interconnected IPv6 networks, including enterprise=A1=
=AFs
>>>        IPv6 networks and ISP=A1=AFs IPv6 networks.
>>>        Otherwise, we have to introduce a new NAT equipment with NAT66
>>>        functionalities to differentiate IPv6 network & IPv6 Internet.
>>>         3) Other comments related to the contexts
>>>        Comments for 3.1.1 and 3.2.2 about stateful translation
>>>        statements:
>>>        For stateful translation, the draft has mentioned =A1=B0the
>>>        stateful translation only support IPv6 initiated
>>>        communication=A1=B1. But NAT-PT could support both directional
>>>        communication without this limitation. Hence, we suggest to
>>>        remove this descriptions or point out it is only targeting to
>>>        NAT64
>>>
>>>
>>>    NAT-PT was deprecated by RFC 4966.
>>>
>>>
>>>        Comments for 3.3 about ALG descriptions:
>>>        It only list the demand for FTP ALG. But there should be
>>>        support any kind of applications in which IP address is
>>>        concluded in payload, such as SIP, RTSP. Hence, we suggest to
>>>        extend ALG scope avoid reader=A1=AFs misunderstanding.
>>>
>>>
>>>    Yes, agree.
>>>
>>>         Hope all these are meaningful.
>>>         Regards,
>>>
>>>        Bo Zhou
>>>        China Mobile
>>>
>>>  ----------------------------------------------------------------------=
--
>>>
>>>        _______________________________________________
>>>        Behave mailing list
>>>        Behave@ietf.org <mailto:Behave@ietf.org>
>>>        https://www.ietf.org/mailman/listinfo/behave
>>>
>>>
>>>
>>>
>>>
>>> --
>>> Regards,
>>>
>>> Bo Zhou
>>> China Mobile
>>> -----------------------------------------------------------------------=
-
>>>
>>> _______________________________________________
>>> Behave mailing list
>>> Behave@ietf.org
>>> https://www.ietf.org/mailman/listinfo/behave
>>>
>>>
>>
>>
>
>
> --
> =B3=C2=B8=D5
> phdgang@gmail.com
>



--=20
Regards,

Bo Zhou
China Mobile

--001485f99caa6e0d00047346c439
Content-Type: text/html; charset=GB2312
Content-Transfer-Encoding: quoted-printable

<div>For my understanding, &quot;two application instances&quot; here indic=
ates two IPv6-only instances, like two IPv6 &nbsp;host, both installed&nbsp=
;IPv6 application, and they want to communicate with&nbsp;each other via IP=
v6 network.</div>

<div>Am I right?</div>
<div>&nbsp;</div>
<div>Regards,</div>
<div>&nbsp;</div>
<div>Bo Zhou&nbsp;&nbsp;<br><br></div>
<div class=3D"gmail_quote">2009/9/11 Chen Gang <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:phdgang@gmail.com">phdgang@gmail.com</a>&gt;</span><br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>Hello Xing,</div>
<div>&nbsp;</div>
<div>With regard to the latest difinition of IPv6-only, there are some ques=
tioins for clarifications.</div>
<div>&nbsp;</div>
<div>Within the sentence &quot;It implies that <font color=3D"#ff0000">two =
application instances</font> are capable of communicating using IPv6, but n=
ot IPv4 - they have an IPv6 stack&quot;, does &quot;two application instanc=
es&quot; means &quot;IPv4 application instances and IPv6 application instan=
ces&quot;?</div>

<div>&nbsp;</div>
<div>If that is true, I guess &quot;IPv6-only&quot; need do&nbsp;some sort =
of application ALG or host-based translation&nbsp;in&nbsp;order&nbsp;to let=
 IPv4 application to&nbsp;accomodate a IPv6-only environment.</div>
<div>&nbsp;</div>
<div>If my understanding is correct, you may also need to clarify this mean=
ing in the IPv6-only definition or separate this meaning to new defined ter=
ms, like Bo suggested &quot;<br>IPv4-inherited IPv6 host&quot;.</div>
<div>&nbsp;</div>
<div>Thanks</div>
<div>&nbsp;</div>
<div>BRs</div>
<div>&nbsp;</div>
<div>Gang</div>
<div>&nbsp;</div>
<div><br><br>&nbsp;</div>
<div class=3D"gmail_quote">2009/9/11 Xing Li <span dir=3D"ltr">&lt;<a href=
=3D"mailto:xing@cernet.edu.cn" target=3D"_blank">xing@cernet.edu.cn</a>&gt;=
</span>=20
<div>
<div></div>
<div class=3D"h5"><br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">bo zhou =D0=B4=B5=C0:=20
<div><br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><br><br><br>&nbsp; &nbsp;However=
, if the consensus is to add the discussion on application<br>&nbsp; &nbsp;=
instances, I am happy to add the words.<br>
<br>[bo] Yes, we want to introduce the application type to make the definit=
ion more clearly.<br></blockquote></div>we have made some modifications in =
draft-ietf-behave-v6v4-framework-01=20
<div><br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><br><br>&nbsp; &nbsp;(2) Please =
see the Sec. 1.2, the border between an IPvx network<br>&nbsp; &nbsp;and th=
e IPvx Internet is not defined by NAT.<br>
<br>[bo] Sorry, I cannot find any words in Sec.1.2 to define the difference=
 between network and Internet.<br></blockquote><br></div>&nbsp;An IPv4 netw=
ork: &nbsp;A specific network that has an IPv4-only<br>&nbsp; &nbsp; deploy=
ment. &nbsp;This could be an enterprise&#39;s IPv4-only network or an<br>
&nbsp; &nbsp; ISP&#39;s IPv4-only network. &nbsp;The size of an IPv4 networ=
k is<br>&nbsp; &nbsp; relatively small comparing to the global IPv4 Interne=
t.<br><br>The key words are: &quot;A specific network&quot; and &quot;relat=
ively small comparing to the global IPv4 Internet&quot;.=20
<div><br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><br><br>&nbsp; &nbsp;(3) Other c=
omments are inline.<br>&nbsp; &nbsp;[bo] Yes, we knew NAT-PT was deprecated=
 by RFC 4966. However, the<br>
&nbsp; &nbsp;comments we pointed out is focus on stateful translation&#39;s=
<br>&nbsp; &nbsp;limitation. We think &quot;the stateful translation only s=
upport IPv6<br>&nbsp; &nbsp;initiated communication&quot; is only related t=
o NAT64. It is hard<br>&nbsp; &nbsp;to say &quot;stateful translation can o=
nly support IPv6 initiated<br>
&nbsp; &nbsp;communication&quot; because &quot;NAT64 can only do it&quot;. =
We agreed NAT64 is<br>&nbsp; &nbsp;one of significant stateful translation,=
 but we do not agree it<br>&nbsp; &nbsp;represents all behaviours of statef=
ul translation.<br><br></blockquote>
<br></div>We are working on the standard of translation. NAT-PT was depreca=
ted and the stateful translation proved by behave working group is NAT64 at=
 this moment.=20
<div><br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><br>&nbsp; &nbsp;[bo]About the A=
LG issue, we should state &quot;all IP packet payload<br>&nbsp; &nbsp;inclu=
ded IP address need do ALG&quot;.<br>
<br></blockquote></div>Agree, if the end systems are in different address f=
amilies.<br><br>xing<br><br><br><br><br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>
<div></div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;<br>&nbsp; &nbsp;Regards,<br><br>&nbsp; &nbsp;=
xing<br><br><br>&nbsp; &nbsp;bo zhou =D0=B4=B5=C0:<br><br>&nbsp; &nbsp; &nb=
sp; &nbsp;Hi Fred and others authors of framework for IPv4/IPv6 translation=
<br>&nbsp; &nbsp; &nbsp; &nbsp; We have some texts and comments for this dr=
aft. Originally,<br>
&nbsp; &nbsp; &nbsp; &nbsp;we tried to propose our comments and discuss the=
m inside last<br>&nbsp; &nbsp; &nbsp; &nbsp;Wed&#39;s interim meeting, Unfo=
rtunately, the shortage of time<br>&nbsp; &nbsp; &nbsp; &nbsp;caused we hav=
e no time to address them. Hence, we pointed them<br>&nbsp; &nbsp; &nbsp; &=
nbsp;out here.<br>
&nbsp; &nbsp; &nbsp; &nbsp; 1) &nbsp;We need more clear IP family host defi=
nitions<br>&nbsp; &nbsp; &nbsp; &nbsp;Inside the draft, existing &ldquo;IPv=
6-only&rdquo; and &ldquo;IPv4-only&rdquo;<br>&nbsp; &nbsp; &nbsp; &nbsp;def=
initions are targeting to IP host capabilities, but there<br>&nbsp; &nbsp; =
&nbsp; &nbsp;are unclear descriptions of &ldquo;application instances&rdquo=
;. Hence we<br>
&nbsp; &nbsp; &nbsp; &nbsp;propose the &nbsp;IP family host shall be define=
d combining with<br>&nbsp; &nbsp; &nbsp; &nbsp;four aspects:<br>&nbsp; &nbs=
p; &nbsp; &nbsp;a. the application type installed on the host,<br>&nbsp; &n=
bsp; &nbsp; &nbsp;b.the IP family stack supported by a host<br>&nbsp; &nbsp=
; &nbsp; &nbsp;c.the IP family routing assigned by a network<br>
&nbsp; &nbsp; &nbsp; &nbsp;d.available IP family connectivity<br>&nbsp; &nb=
sp; &nbsp; &nbsp;According to the above principles, following IP family hos=
t<br>&nbsp; &nbsp; &nbsp; &nbsp;definitions are suggested to replace curren=
t &ldquo;IPv6-only&rdquo; and<br>&nbsp; &nbsp; &nbsp; &nbsp;&ldquo;IPv4-onl=
y&rdquo; definitions and propose a new definition for<br>
&nbsp; &nbsp; &nbsp; &nbsp;supplement:<br>&nbsp; &nbsp; &nbsp; &nbsp;IPv4 o=
nly host comprises an IPv4 enabled end system stack plus<br>&nbsp; &nbsp; &=
nbsp; &nbsp;routing in the network, IPv4 applications installed on the<br>&=
nbsp; &nbsp; &nbsp; &nbsp;host. It implies two application instances with i=
nstalled IPv4<br>
&nbsp; &nbsp; &nbsp; &nbsp;applications are capable of communication using =
IPv4, but not<br>&nbsp; &nbsp; &nbsp; &nbsp;IPv6 &hellip;&hellip;<br>&nbsp;=
 &nbsp; &nbsp; &nbsp;IPv6 only host comprises an IPv6 enabled end system st=
ack plus<br>&nbsp; &nbsp; &nbsp; &nbsp;routing in the network, IPv6 applica=
tions installed on the<br>
&nbsp; &nbsp; &nbsp; &nbsp;host. It implies two application instances with =
installed IPv6<br>&nbsp; &nbsp; &nbsp; &nbsp;applications are capable of co=
mmunication using IPv6, but not<br>&nbsp; &nbsp; &nbsp; &nbsp;IPv4 &hellip;=
&hellip;<br>&nbsp; &nbsp; &nbsp; &nbsp;IPv4-inherited IPv6 host comprises a=
n IPv4/IPv6 enabled end<br>
&nbsp; &nbsp; &nbsp; &nbsp;system dual-stack plus IPv6 routing in the netwo=
rk, IPv4/IPv6<br>&nbsp; &nbsp; &nbsp; &nbsp;applications installed on the h=
ost. It implies two application<br>&nbsp; &nbsp; &nbsp; &nbsp;instances wit=
h installed IPv4/IPv6 applications are capable of<br>&nbsp; &nbsp; &nbsp; &=
nbsp;communication using IPv6 &ndash; they have IPv4/IPv6 dual-stack,<br>
&nbsp; &nbsp; &nbsp; &nbsp;network support including routing in IPv6, IPv4/=
IPv6<br>&nbsp; &nbsp; &nbsp; &nbsp;applications can communicate with IPv4/I=
Pv6 hosts respectively.<br>&nbsp; &nbsp; &nbsp; &nbsp;Furthermore, the &ldq=
uo;An IPv6 network&rdquo; are proposed to redefined<br>&nbsp; &nbsp; &nbsp;=
 &nbsp;as: A specific network that has IPv6-only and IPv4-inherited<br>
&nbsp; &nbsp; &nbsp; &nbsp;IPv6 implementation.<br>&nbsp; &nbsp; &nbsp; &nb=
sp; 2=A3=A9How to differentiate IPv6 network &amp; IPv6 Internet<br>&nbsp; =
&nbsp; &nbsp; &nbsp;The difference between IPv4 network and IPv4 Internet c=
ould be<br>&nbsp; &nbsp; &nbsp; &nbsp;identified by CGN (NAT) functionaliti=
es. However, there are no<br>
&nbsp; &nbsp; &nbsp; &nbsp;CGN(NAT) functionalities defined in IPv6 world. =
It&rsquo;s difficult<br>&nbsp; &nbsp; &nbsp; &nbsp;to differentiate IPv6 ne=
twork and Internet. Hence, we suggest<br>&nbsp; &nbsp; &nbsp; &nbsp;to re-d=
efine the IPv6 Internet in the framework draft based on<br>&nbsp; &nbsp; &n=
bsp; &nbsp;network scale size, as follows: IPv6 Internet means a global<br>
&nbsp; &nbsp; &nbsp; &nbsp;system of interconnected IPv6 networks, includin=
g enterprise&rsquo;s<br>&nbsp; &nbsp; &nbsp; &nbsp;IPv6 networks and ISP&rs=
quo;s IPv6 networks.<br>&nbsp; &nbsp; &nbsp; &nbsp;Otherwise, we have to in=
troduce a new NAT equipment with NAT66<br>&nbsp; &nbsp; &nbsp; &nbsp;functi=
onalities to differentiate IPv6 network &amp; IPv6 Internet.<br>
&nbsp; &nbsp; &nbsp; &nbsp; 3) Other comments related to the contexts<br>&n=
bsp; &nbsp; &nbsp; &nbsp;Comments for 3.1.1 and 3.2.2 about stateful transl=
ation<br>&nbsp; &nbsp; &nbsp; &nbsp;statements:<br>&nbsp; &nbsp; &nbsp; &nb=
sp;For stateful translation, the draft has mentioned &ldquo;the<br>&nbsp; &=
nbsp; &nbsp; &nbsp;stateful translation only support IPv6 initiated<br>
&nbsp; &nbsp; &nbsp; &nbsp;communication&rdquo;. But NAT-PT could support b=
oth directional<br>&nbsp; &nbsp; &nbsp; &nbsp;communication without this li=
mitation. Hence, we suggest to<br>&nbsp; &nbsp; &nbsp; &nbsp;remove this de=
scriptions or point out it is only targeting to<br>&nbsp; &nbsp; &nbsp; &nb=
sp;NAT64<br>
<br><br>&nbsp; &nbsp;NAT-PT was deprecated by RFC 4966.<br><br><br>&nbsp; &=
nbsp; &nbsp; &nbsp;Comments for 3.3 about ALG descriptions:<br>&nbsp; &nbsp=
; &nbsp; &nbsp;It only list the demand for FTP ALG. But there should be<br>=
&nbsp; &nbsp; &nbsp; &nbsp;support any kind of applications in which IP add=
ress is<br>
&nbsp; &nbsp; &nbsp; &nbsp;concluded in payload, such as SIP, RTSP. Hence, =
we suggest to<br>&nbsp; &nbsp; &nbsp; &nbsp;extend ALG scope avoid reader&r=
squo;s misunderstanding.<br><br><br>&nbsp; &nbsp;Yes, agree.<br><br>&nbsp; =
&nbsp; &nbsp; &nbsp; Hope all these are meaningful.<br>&nbsp; &nbsp; &nbsp;=
 &nbsp; Regards,<br>
<br>&nbsp; &nbsp; &nbsp; &nbsp;Bo Zhou<br>&nbsp; &nbsp; &nbsp; &nbsp;China =
Mobile<br>&nbsp; &nbsp; &nbsp; &nbsp;--------------------------------------=
----------------------------------<br><br>&nbsp; &nbsp; &nbsp; &nbsp;______=
_________________________________________<br>&nbsp; &nbsp; &nbsp; &nbsp;Beh=
ave mailing list<br></div>
</div>&nbsp; &nbsp; &nbsp; &nbsp;<a href=3D"mailto:Behave@ietf.org" target=
=3D"_blank">Behave@ietf.org</a> &lt;mailto:<a href=3D"mailto:Behave@ietf.or=
g" target=3D"_blank">Behave@ietf.org</a>&gt;=20
<div><br>&nbsp; &nbsp; &nbsp; &nbsp;<a href=3D"https://www.ietf.org/mailman=
/listinfo/behave" target=3D"_blank">https://www.ietf.org/mailman/listinfo/b=
ehave</a><br>&nbsp; &nbsp; &nbsp; &nbsp; <br><br><br><br><br>-- <br>Regards=
,<br><br>Bo Zhou<br>China Mobile<br>---------------------------------------=
---------------------------------<br>
<br>_______________________________________________<br>Behave mailing list<=
br><a href=3D"mailto:Behave@ietf.org" target=3D"_blank">Behave@ietf.org</a>=
<br><a href=3D"https://www.ietf.org/mailman/listinfo/behave" target=3D"_bla=
nk">https://www.ietf.org/mailman/listinfo/behave</a><br>
&nbsp;<br></div></blockquote><br></blockquote></div></div></div><font color=
=3D"#888888"><br><br clear=3D"all">
<div></div><br>-- <br>=B3=C2=B8=D5<br><a href=3D"mailto:phdgang@gmail.com" =
target=3D"_blank">phdgang@gmail.com</a><br></font></blockquote></div><br><b=
r clear=3D"all">
<div></div><br>-- <br>Regards,<br><br>Bo Zhou<br>China Mobile<br>

--001485f99caa6e0d00047346c439--

From zhouboyj@gmail.com  Thu Sep 10 23:02:08 2009
Return-Path: <zhouboyj@gmail.com>
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 DD86B3A696B for <behave@core3.amsl.com>; Thu, 10 Sep 2009 23:02:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.256
X-Spam-Level: 
X-Spam-Status: No, score=-1.256 tagged_above=-999 required=5 tests=[AWL=0.142,  BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, J_CHICKENPOX_19=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 oHLERKhE8KwG for <behave@core3.amsl.com>; Thu, 10 Sep 2009 23:02:07 -0700 (PDT)
Received: from mail-iw0-f202.google.com (mail-iw0-f202.google.com [209.85.223.202]) by core3.amsl.com (Postfix) with ESMTP id 472EF3A6810 for <behave@ietf.org>; Thu, 10 Sep 2009 23:02:07 -0700 (PDT)
Received: by iwn40 with SMTP id 40so386467iwn.32 for <behave@ietf.org>; Thu, 10 Sep 2009 23:02:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=orP8c7NmGOuMDzKli7jeEW8Amtben08JZTdqpBqE4Ek=; b=IOOziITwI31pJMzVECS/crgyvzCpqSt95sxfWfMUOmV1piJ8tt+oGFLP+ei5SzM4IP 8u06Z+lDOMlFU+ve2myUoZosD9O7ZGBiQ2DEzCwge/Ia0b1HYgMyMksNYxM9s7KeI1jI PO7o2DXQ5h55u4qL1pkkQZyo266xcNh4W0voI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=WRS8dLZbNJXayj1AS6zqEXbTZGDx7+H+bck117aYYubzNGp2bd+plRF/kZDlJn8OVz tJXyR89SM4H/N6eZs+V8lTRbdqjXRmCkCZQmMkBQrgE4zeGLx4XVT2xuPN0z+32rKlwr gcU7xcNkmC5wxXZAurBVdrgD9ZPsyNruxyzfA=
MIME-Version: 1.0
Received: by 10.231.6.164 with SMTP id 36mr4728568ibz.39.1252648940050; Thu,  10 Sep 2009 23:02:20 -0700 (PDT)
In-Reply-To: <4AA9880E.3000007@cernet.edu.cn>
References: <36a593230908232300m45a10136wce25d01ef8bac439@mail.gmail.com> <4A9B7BA1.6000807@cernet.edu.cn> <36a593230908310651kd76a383j28b845bb07ebba55@mail.gmail.com> <4AA9880E.3000007@cernet.edu.cn>
Date: Fri, 11 Sep 2009 14:02:20 +0800
Message-ID: <36a593230909102302k5df1fcfsda08e38e0068bb38@mail.gmail.com>
From: bo zhou <zhouboyj@gmail.com>
To: Xing Li <xing@cernet.edu.cn>
Content-Type: multipart/alternative; boundary=0015175ce068199c5a0473470f8e
Cc: denghui02@gmail.com, congxiao@cernet.edu.cn, behave@ietf.org, liu dapeng <maxpassion@gmail.com>, kyin@cisco.com, fred@cisco.com, phdgang@gmail.com
Subject: Re: [BEHAVE] Proposed text and comments for framework for IPv4/IPv6 translation
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/mail-archive/web/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>
X-List-Received-Date: Fri, 11 Sep 2009 06:02:09 -0000

--0015175ce068199c5a0473470f8e
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Reply inline.

On Fri, Sep 11, 2009 at 7:13 AM, Xing Li <xing@cernet.edu.cn> wrote:

> bo zhou =E5=86=99=E9=81=93:
>
>>
>>
>>
>>    However, if the consensus is to add the discussion on application
>>    instances, I am happy to add the words.
>>
>> [bo] Yes, we want to introduce the application type to make the definiti=
on
>> more clearly.
>>
> we have made some modifications in draft-ietf-behave-v6v4-framework-01

    [bo] Yes, I found it.

>
>
>>
>>    (2) Please see the Sec. 1.2, the border between an IPvx network
>>    and the IPvx Internet is not defined by NAT.
>>
>> [bo] Sorry, I cannot find any words in Sec.1.2 to define the difference
>> between network and Internet.
>>
>
>  An IPv4 network:  A specific network that has an IPv4-only
>     deployment.  This could be an enterprise's IPv4-only network or an
>     ISP's IPv4-only network.  The size of an IPv4 network is
>     relatively small comparing to the global IPv4 Internet.
>
> The key words are: "A specific network" and "relatively small comparing t=
o
> the global IPv4 Internet".

      [bo] From aboved words, i have feeling that the difference between
network and Internet is SIZE only. I am not sure the size is the major thin=
g
to distinguish between the network and Internet, Is there any equipment,
like NAT, inside the network can help us distinguish between network and
Internet?

>
>
>>
>>    (3) Other comments are inline.
>>    [bo] Yes, we knew NAT-PT was deprecated by RFC 4966. However, the
>>    comments we pointed out is focus on stateful translation's
>>    limitation. We think "the stateful translation only support IPv6
>>    initiated communication" is only related to NAT64. It is hard
>>    to say "stateful translation can only support IPv6 initiated
>>    communication" because "NAT64 can only do it". We agreed NAT64 is
>>    one of significant stateful translation, but we do not agree it
>>    represents all behaviours of stateful translation.
>>
>>
> We are working on the standard of translation. NAT-PT was deprecated and
> the stateful translation proved by behave working group is NAT64 at this
> moment.

       [bo] Agree at the moment, only NAT64 can behave stateful translation
inside behave working group, but how about in future. I am not sure the
NAT64 is the ONE solution to represent stateful translation.

>
>
>>    [bo]About the ALG issue, we should state "all IP packet payload
>>    included IP address need do ALG".
>>
>> Agree, if the end systems are in different address families.
>
> xing
>
>
>
>
>
>>    Regards,
>>
>>    xing
>>
>>
>>    bo zhou =E5=86=99=E9=81=93:
>>
>>        Hi Fred and others authors of framework for IPv4/IPv6 translation
>>         We have some texts and comments for this draft. Originally,
>>        we tried to propose our comments and discuss them inside last
>>        Wed's interim meeting, Unfortunately, the shortage of time
>>        caused we have no time to address them. Hence, we pointed them
>>        out here.
>>         1)  We need more clear IP family host definitions
>>        Inside the draft, existing =E2=80=9CIPv6-only=E2=80=9D and =E2=80=
=9CIPv4-only=E2=80=9D
>>        definitions are targeting to IP host capabilities, but there
>>        are unclear descriptions of =E2=80=9Capplication instances=E2=80=
=9D. Hence we
>>        propose the  IP family host shall be defined combining with
>>        four aspects:
>>        a. the application type installed on the host,
>>        b.the IP family stack supported by a host
>>        c.the IP family routing assigned by a network
>>        d.available IP family connectivity
>>        According to the above principles, following IP family host
>>        definitions are suggested to replace current =E2=80=9CIPv6-only=
=E2=80=9D and
>>        =E2=80=9CIPv4-only=E2=80=9D definitions and propose a new definit=
ion for
>>        supplement:
>>        IPv4 only host comprises an IPv4 enabled end system stack plus
>>        routing in the network, IPv4 applications installed on the
>>        host. It implies two application instances with installed IPv4
>>        applications are capable of communication using IPv4, but not
>>        IPv6 =E2=80=A6=E2=80=A6
>>        IPv6 only host comprises an IPv6 enabled end system stack plus
>>        routing in the network, IPv6 applications installed on the
>>        host. It implies two application instances with installed IPv6
>>        applications are capable of communication using IPv6, but not
>>        IPv4 =E2=80=A6=E2=80=A6
>>        IPv4-inherited IPv6 host comprises an IPv4/IPv6 enabled end
>>        system dual-stack plus IPv6 routing in the network, IPv4/IPv6
>>        applications installed on the host. It implies two application
>>        instances with installed IPv4/IPv6 applications are capable of
>>        communication using IPv6 =E2=80=93 they have IPv4/IPv6 dual-stack=
,
>>        network support including routing in IPv6, IPv4/IPv6
>>        applications can communicate with IPv4/IPv6 hosts respectively.
>>        Furthermore, the =E2=80=9CAn IPv6 network=E2=80=9D are proposed t=
o redefined
>>        as: A specific network that has IPv6-only and IPv4-inherited
>>        IPv6 implementation.
>>         2=EF=BC=89How to differentiate IPv6 network & IPv6 Internet
>>        The difference between IPv4 network and IPv4 Internet could be
>>        identified by CGN (NAT) functionalities. However, there are no
>>        CGN(NAT) functionalities defined in IPv6 world. It=E2=80=99s diff=
icult
>>        to differentiate IPv6 network and Internet. Hence, we suggest
>>        to re-define the IPv6 Internet in the framework draft based on
>>        network scale size, as follows: IPv6 Internet means a global
>>        system of interconnected IPv6 networks, including enterprise=E2=
=80=99s
>>        IPv6 networks and ISP=E2=80=99s IPv6 networks.
>>        Otherwise, we have to introduce a new NAT equipment with NAT66
>>        functionalities to differentiate IPv6 network & IPv6 Internet.
>>         3) Other comments related to the contexts
>>        Comments for 3.1.1 and 3.2.2 about stateful translation
>>        statements:
>>        For stateful translation, the draft has mentioned =E2=80=9Cthe
>>        stateful translation only support IPv6 initiated
>>        communication=E2=80=9D. But NAT-PT could support both directional
>>        communication without this limitation. Hence, we suggest to
>>        remove this descriptions or point out it is only targeting to
>>        NAT64
>>
>>
>>    NAT-PT was deprecated by RFC 4966.
>>
>>
>>        Comments for 3.3 about ALG descriptions:
>>        It only list the demand for FTP ALG. But there should be
>>        support any kind of applications in which IP address is
>>        concluded in payload, such as SIP, RTSP. Hence, we suggest to
>>        extend ALG scope avoid reader=E2=80=99s misunderstanding.
>>
>>
>>    Yes, agree.
>>
>>         Hope all these are meaningful.
>>         Regards,
>>
>>        Bo Zhou
>>        China Mobile
>>
>>  -----------------------------------------------------------------------=
-
>>
>>        _______________________________________________
>>        Behave mailing list
>>        Behave@ietf.org <mailto:Behave@ietf.org>
>>        https://www.ietf.org/mailman/listinfo/behave
>>
>>
>>
>>
>>
>> --
>> Regards,
>>
>> Bo Zhou
>> China Mobile
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Behave mailing list
>> Behave@ietf.org
>> https://www.ietf.org/mailman/listinfo/behave
>>
>>
>
>


--=20
Regards,

Bo Zhou
China Mobile

--0015175ce068199c5a0473470f8e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Reply inline.<br><br>
<div class=3D"gmail_quote">On Fri, Sep 11, 2009 at 7:13 AM, Xing Li <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:xing@cernet.edu.cn">xing@cernet.edu.cn</a>=
&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">bo zhou =E5=86=99=E9=81=93:=20
<div class=3D"im"><br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><br><br><br>=C2=A0 =C2=A0However=
, if the consensus is to add the discussion on application<br>=C2=A0 =C2=A0=
instances, I am happy to add the words.<br>
<br>[bo] Yes, we want to introduce the application type to make the definit=
ion more clearly.<br></blockquote></div>we have made some modifications in =
draft-ietf-behave-v6v4-framework-01</blockquote>
<div>=C2=A0=C2=A0=C2=A0<font color=3D"#000099"> </font><font color=3D"#ff00=
00">[bo] Yes, I found it.</font></div>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div class=3D"im"><br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><br><br>=C2=A0 =C2=A0(2) Please =
see the Sec. 1.2, the border between an IPvx network<br>=C2=A0 =C2=A0and th=
e IPvx Internet is not defined by NAT.<br>
<br>[bo] Sorry, I cannot find any words in Sec.1.2 to define the difference=
 between network and Internet.<br></blockquote><br></div>=C2=A0An IPv4 netw=
ork: =C2=A0A specific network that has an IPv4-only<br>=C2=A0 =C2=A0 deploy=
ment. =C2=A0This could be an enterprise&#39;s IPv4-only network or an<br>
=C2=A0 =C2=A0 ISP&#39;s IPv4-only network. =C2=A0The size of an IPv4 networ=
k is<br>=C2=A0 =C2=A0 relatively small comparing to the global IPv4 Interne=
t.<br><br>The key words are: &quot;A specific network&quot; and &quot;relat=
ively small comparing to the global IPv4 Internet&quot;. </blockquote>

<div>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0<font color=3D"#ff0000">[bo] From=
=C2=A0aboved words, i have feeling that the difference between network and =
Internet is SIZE only. I am not sure the size is the major thing to disting=
uish=C2=A0between the network and Internet, </font><font color=3D"#ff0000">=
Is there any equipment, like NAT, inside the network can help us=C2=A0disti=
nguish between network and Internet?</font>=C2=A0</div>

<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div class=3D"im"><br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><br><br>=C2=A0 =C2=A0(3) Other c=
omments are inline.<br>=C2=A0 =C2=A0[bo] Yes, we knew NAT-PT was deprecated=
 by RFC 4966. However, the<br>
=C2=A0 =C2=A0comments we pointed out is focus on stateful translation&#39;s=
<br>=C2=A0 =C2=A0limitation. We think &quot;the stateful translation only s=
upport IPv6<br>=C2=A0 =C2=A0initiated communication&quot; is only related t=
o NAT64. It is hard<br>=C2=A0 =C2=A0to say &quot;stateful translation can o=
nly support IPv6 initiated<br>
=C2=A0 =C2=A0communication&quot; because &quot;NAT64 can only do it&quot;. =
We agreed NAT64 is<br>=C2=A0 =C2=A0one of significant stateful translation,=
 but we do not agree it<br>=C2=A0 =C2=A0represents all behaviours of statef=
ul translation.<br><br></blockquote>
<br></div>We are working on the standard of translation. NAT-PT was depreca=
ted and the stateful translation proved by behave working group is NAT64 at=
 this moment. </blockquote>
<div>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0<font color=3D"#ff0000"> [bo] Agre=
e at the moment, only NAT64 can behave stateful translation inside behave w=
orking group, but how about in future. I am not sure the NAT64 is=C2=A0the =
ONE solution to represent stateful translation.=C2=A0</font></div>

<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div class=3D"im"><br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><br>=C2=A0 =C2=A0[bo]About the A=
LG issue, we should state &quot;all IP packet payload<br>=C2=A0 =C2=A0inclu=
ded IP address need do ALG&quot;.<br>
<br></blockquote></div>Agree, if the end systems are in different address f=
amilies.<br><br>xing<br><br><br><br><br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>
<div></div>
<div class=3D"h5">=C2=A0=C2=A0=C2=A0=C2=A0<br>=C2=A0 =C2=A0Regards,<br><br>=
=C2=A0 =C2=A0xing<br><br><br>=C2=A0 =C2=A0bo zhou =E5=86=99=E9=81=93:<br><b=
r>=C2=A0 =C2=A0 =C2=A0 =C2=A0Hi Fred and others authors of framework for IP=
v4/IPv6 translation<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 We have some texts and c=
omments for this draft. Originally,<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0we tried to propose our comments and discuss the=
m inside last<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0Wed&#39;s interim meeting, Unfo=
rtunately, the shortage of time<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0caused we hav=
e no time to address them. Hence, we pointed them<br>=C2=A0 =C2=A0 =C2=A0 =
=C2=A0out here.<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 1) =C2=A0We need more clear IP family host defi=
nitions<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0Inside the draft, existing =E2=80=9CI=
Pv6-only=E2=80=9D and =E2=80=9CIPv4-only=E2=80=9D<br>=C2=A0 =C2=A0 =C2=A0 =
=C2=A0definitions are targeting to IP host capabilities, but there<br>=C2=
=A0 =C2=A0 =C2=A0 =C2=A0are unclear descriptions of =E2=80=9Capplication in=
stances=E2=80=9D. Hence we<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0propose the =C2=A0IP family host shall be define=
d combining with<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0four aspects:<br>=C2=A0 =C2=
=A0 =C2=A0 =C2=A0a. the application type installed on the host,<br>=C2=A0 =
=C2=A0 =C2=A0 =C2=A0b.the IP family stack supported by a host<br>=C2=A0 =C2=
=A0 =C2=A0 =C2=A0c.the IP family routing assigned by a network<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0d.available IP family connectivity<br>=C2=A0 =C2=
=A0 =C2=A0 =C2=A0According to the above principles, following IP family hos=
t<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0definitions are suggested to replace curren=
t =E2=80=9CIPv6-only=E2=80=9D and<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0=E2=80=9CIP=
v4-only=E2=80=9D definitions and propose a new definition for<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0supplement:<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0IPv4 o=
nly host comprises an IPv4 enabled end system stack plus<br>=C2=A0 =C2=A0 =
=C2=A0 =C2=A0routing in the network, IPv4 applications installed on the<br>=
=C2=A0 =C2=A0 =C2=A0 =C2=A0host. It implies two application instances with =
installed IPv4<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0applications are capable of communication using =
IPv4, but not<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0IPv6 =E2=80=A6=E2=80=A6<br>=C2=
=A0 =C2=A0 =C2=A0 =C2=A0IPv6 only host comprises an IPv6 enabled end system=
 stack plus<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0routing in the network, IPv6 appl=
ications installed on the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0host. It implies two application instances with =
installed IPv6<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0applications are capable of co=
mmunication using IPv6, but not<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0IPv4 =E2=80=
=A6=E2=80=A6<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0IPv4-inherited IPv6 host compris=
es an IPv4/IPv6 enabled end<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0system dual-stack plus IPv6 routing in the netwo=
rk, IPv4/IPv6<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0applications installed on the h=
ost. It implies two application<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0instances wit=
h installed IPv4/IPv6 applications are capable of<br>=C2=A0 =C2=A0 =C2=A0 =
=C2=A0communication using IPv6 =E2=80=93 they have IPv4/IPv6 dual-stack,<br=
>
=C2=A0 =C2=A0 =C2=A0 =C2=A0network support including routing in IPv6, IPv4/=
IPv6<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0applications can communicate with IPv4/I=
Pv6 hosts respectively.<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0Furthermore, the =E2=
=80=9CAn IPv6 network=E2=80=9D are proposed to redefined<br>=C2=A0 =C2=A0 =
=C2=A0 =C2=A0as: A specific network that has IPv6-only and IPv4-inherited<b=
r>
=C2=A0 =C2=A0 =C2=A0 =C2=A0IPv6 implementation.<br>=C2=A0 =C2=A0 =C2=A0 =C2=
=A0 2=EF=BC=89How to differentiate IPv6 network &amp; IPv6 Internet<br>=C2=
=A0 =C2=A0 =C2=A0 =C2=A0The difference between IPv4 network and IPv4 Intern=
et could be<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0identified by CGN (NAT) functiona=
lities. However, there are no<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0CGN(NAT) functionalities defined in IPv6 world. =
It=E2=80=99s difficult<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0to differentiate IPv6 =
network and Internet. Hence, we suggest<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0to re=
-define the IPv6 Internet in the framework draft based on<br>=C2=A0 =C2=A0 =
=C2=A0 =C2=A0network scale size, as follows: IPv6 Internet means a global<b=
r>
=C2=A0 =C2=A0 =C2=A0 =C2=A0system of interconnected IPv6 networks, includin=
g enterprise=E2=80=99s<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0IPv6 networks and ISP=
=E2=80=99s IPv6 networks.<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0Otherwise, we have =
to introduce a new NAT equipment with NAT66<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0f=
unctionalities to differentiate IPv6 network &amp; IPv6 Internet.<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 3) Other comments related to the contexts<br>=
=C2=A0 =C2=A0 =C2=A0 =C2=A0Comments for 3.1.1 and 3.2.2 about stateful tran=
slation<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0statements:<br>=C2=A0 =C2=A0 =C2=A0 =
=C2=A0For stateful translation, the draft has mentioned =E2=80=9Cthe<br>=C2=
=A0 =C2=A0 =C2=A0 =C2=A0stateful translation only support IPv6 initiated<br=
>
=C2=A0 =C2=A0 =C2=A0 =C2=A0communication=E2=80=9D. But NAT-PT could support=
 both directional<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0communication without this =
limitation. Hence, we suggest to<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0remove this =
descriptions or point out it is only targeting to<br>=C2=A0 =C2=A0 =C2=A0 =
=C2=A0NAT64<br>
<br><br>=C2=A0 =C2=A0NAT-PT was deprecated by RFC 4966.<br><br><br>=C2=A0 =
=C2=A0 =C2=A0 =C2=A0Comments for 3.3 about ALG descriptions:<br>=C2=A0 =C2=
=A0 =C2=A0 =C2=A0It only list the demand for FTP ALG. But there should be<b=
r>=C2=A0 =C2=A0 =C2=A0 =C2=A0support any kind of applications in which IP a=
ddress is<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0concluded in payload, such as SIP, RTSP. Hence, =
we suggest to<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0extend ALG scope avoid reader=
=E2=80=99s misunderstanding.<br><br><br>=C2=A0 =C2=A0Yes, agree.<br><br>=C2=
=A0 =C2=A0 =C2=A0 =C2=A0 Hope all these are meaningful.<br>=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 Regards,<br>
<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0Bo Zhou<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0China =
Mobile<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0--------------------------------------=
----------------------------------<br><br>=C2=A0 =C2=A0 =C2=A0 =C2=A0______=
_________________________________________<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0Beh=
ave mailing list<br></div>
</div>=C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"mailto:Behave@ietf.org" target=
=3D"_blank">Behave@ietf.org</a> &lt;mailto:<a href=3D"mailto:Behave@ietf.or=
g" target=3D"_blank">Behave@ietf.org</a>&gt;=20
<div class=3D"im"><br>=C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://www.iet=
f.org/mailman/listinfo/behave" target=3D"_blank">https://www.ietf.org/mailm=
an/listinfo/behave</a><br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 <br><br><br><br><br>-=
- <br>Regards,<br><br>Bo Zhou<br>China Mobile<br>
------------------------------------------------------------------------<br=
><br>_______________________________________________<br>Behave mailing list=
<br><a href=3D"mailto:Behave@ietf.org" target=3D"_blank">Behave@ietf.org</a=
><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/behave" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/behave</a><br>=C2=A0<br></div></block=
quote><br></blockquote></div><br><br clear=3D"all">
<div></div><br>-- <br>Regards,<br><br>Bo Zhou<br>China Mobile<br>

--0015175ce068199c5a0473470f8e--

From phdgang@gmail.com  Thu Sep 10 23:07:43 2009
Return-Path: <phdgang@gmail.com>
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 121453A684E for <behave@core3.amsl.com>; Thu, 10 Sep 2009 23:07:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.45
X-Spam-Level: *
X-Spam-Status: No, score=1.45 tagged_above=-999 required=5 tests=[AWL=-1.461,  BAYES_20=-0.74, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, J_CHICKENPOX_19=0.6, MIME_CHARSET_FARAWAY=2.45]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DOXLMBuvisT4 for <behave@core3.amsl.com>; Thu, 10 Sep 2009 23:07:32 -0700 (PDT)
Received: from mail-px0-f181.google.com (mail-px0-f181.google.com [209.85.216.181]) by core3.amsl.com (Postfix) with ESMTP id 791953A691E for <behave@ietf.org>; Thu, 10 Sep 2009 23:07:32 -0700 (PDT)
Received: by pxi11 with SMTP id 11so636697pxi.17 for <behave@ietf.org>; Thu, 10 Sep 2009 23:07:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=Iy3Mp2Gz5CTn32Er+VYNicP1dvqOmSi4cx9kBe4BCqU=; b=CXJHlHoARrScbyvnLAWJ3XfhuEclg4BVn5EtV+U5z3QWKqXvqEKj9Qle5FevbIeIc9 3G2VDMvhvyxMlgDh955CwQguMY9nMj3BICwqlbbwaMVtuQ6J/KZa2gtgH1RC+RkLPGK3 YPGDiSIRF5Gh0kxlOi1cL6DQXEYj+KCtzxLpM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=xVBUqaFmxkEbo58iPLvAM7EHKx9sG6EO1bEWBvMiaulcLMSCjfaxV/UmPDBvRsmRtA fZBSHULN+ZjfsK47inW4pHPUqH3TrXZOR8KpmcEXFfyuj4XgknPUJfigeGZIVCScYsXv apvHRe5GAGWf5qqYoEliBBuqR2ua9HNzg/gB0=
MIME-Version: 1.0
Received: by 10.114.236.28 with SMTP id j28mr4623868wah.162.1252649256676;  Thu, 10 Sep 2009 23:07:36 -0700 (PDT)
In-Reply-To: <36a593230909102241w7a71cae0w3593dc48cff69dac@mail.gmail.com>
References: <36a593230908232300m45a10136wce25d01ef8bac439@mail.gmail.com> <4A9B7BA1.6000807@cernet.edu.cn> <36a593230908310651kd76a383j28b845bb07ebba55@mail.gmail.com> <4AA9880E.3000007@cernet.edu.cn> <36ba02b00909102007q7edbe8d1p2052a1853c233486@mail.gmail.com> <36a593230909102241w7a71cae0w3593dc48cff69dac@mail.gmail.com>
Date: Fri, 11 Sep 2009 14:07:36 +0800
Message-ID: <36ba02b00909102307m1485b007wf71a67ececb9de10@mail.gmail.com>
From: Chen Gang <phdgang@gmail.com>
To: bo zhou <zhouboyj@gmail.com>
Content-Type: multipart/alternative; boundary=0016e64bdaeaf8efa504734721c4
Cc: denghui02@gmail.com, congxiao@cernet.edu.cn, behave@ietf.org, liu dapeng <maxpassion@gmail.com>, kyin@cisco.com, Xing Li <xing@cernet.edu.cn>, fred@cisco.com
Subject: Re: [BEHAVE] Proposed text and comments for framework for IPv4/IPv6 translation
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/mail-archive/web/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>
X-List-Received-Date: Fri, 11 Sep 2009 06:07:43 -0000

--0016e64bdaeaf8efa504734721c4
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: quoted-printable

Anyhow, there are some ambiguities on application type.
The author is kindly asked to clarify the information and make IPv6-only
definition more clear.

Gang

2009/9/11 bo zhou <zhouboyj@gmail.com>

> For my understanding, "two application instances" here indicates two
> IPv6-only instances, like two IPv6  host, both installed IPv6 application=
,
> and they want to communicate with each other via IPv6 network.
> Am I right?
>
> Regards,
>
> Bo Zhou
>
> 2009/9/11 Chen Gang <phdgang@gmail.com>
>
>  Hello Xing,
>>
>> With regard to the latest difinition of IPv6-only, there are some
>> questioins for clarifications.
>>
>> Within the sentence "It implies that two application instances are
>> capable of communicating using IPv6, but not IPv4 - they have an IPv6
>> stack", does "two application instances" means "IPv4 application instanc=
es
>> and IPv6 application instances"?
>>
>> If that is true, I guess "IPv6-only" need do some sort of application AL=
G
>> or host-based translation in order to let IPv4 application to accomodate=
 a
>> IPv6-only environment.
>>
>> If my understanding is correct, you may also need to clarify this meanin=
g
>> in the IPv6-only definition or separate this meaning to new defined term=
s,
>> like Bo suggested "
>> IPv4-inherited IPv6 host".
>>
>> Thanks
>>
>> BRs
>>
>> Gang
>>
>>
>>
>>
>> 2009/9/11 Xing Li <xing@cernet.edu.cn>
>>
>> bo zhou =D0=B4=B5=C0:
>>>
>>>>
>>>>
>>>>
>>>>    However, if the consensus is to add the discussion on application
>>>>    instances, I am happy to add the words.
>>>>
>>>> [bo] Yes, we want to introduce the application type to make the
>>>> definition more clearly.
>>>>
>>> we have made some modifications in draft-ietf-behave-v6v4-framework-01
>>>
>>>>
>>>>
>>>>    (2) Please see the Sec. 1.2, the border between an IPvx network
>>>>    and the IPvx Internet is not defined by NAT.
>>>>
>>>> [bo] Sorry, I cannot find any words in Sec.1.2 to define the differenc=
e
>>>> between network and Internet.
>>>>
>>>
>>>  An IPv4 network:  A specific network that has an IPv4-only
>>>     deployment.  This could be an enterprise's IPv4-only network or an
>>>     ISP's IPv4-only network.  The size of an IPv4 network is
>>>     relatively small comparing to the global IPv4 Internet.
>>>
>>> The key words are: "A specific network" and "relatively small comparing
>>> to the global IPv4 Internet".
>>>
>>>>
>>>>
>>>>    (3) Other comments are inline.
>>>>    [bo] Yes, we knew NAT-PT was deprecated by RFC 4966. However, the
>>>>    comments we pointed out is focus on stateful translation's
>>>>    limitation. We think "the stateful translation only support IPv6
>>>>    initiated communication" is only related to NAT64. It is hard
>>>>    to say "stateful translation can only support IPv6 initiated
>>>>    communication" because "NAT64 can only do it". We agreed NAT64 is
>>>>    one of significant stateful translation, but we do not agree it
>>>>    represents all behaviours of stateful translation.
>>>>
>>>>
>>> We are working on the standard of translation. NAT-PT was deprecated an=
d
>>> the stateful translation proved by behave working group is NAT64 at thi=
s
>>> moment.
>>>
>>>>
>>>>    [bo]About the ALG issue, we should state "all IP packet payload
>>>>    included IP address need do ALG".
>>>>
>>>> Agree, if the end systems are in different address families.
>>>
>>> xing
>>>
>>>
>>>
>>>
>>>
>>>>    Regards,
>>>>
>>>>    xing
>>>>
>>>>
>>>>    bo zhou =D0=B4=B5=C0:
>>>>
>>>>        Hi Fred and others authors of framework for IPv4/IPv6 translati=
on
>>>>         We have some texts and comments for this draft. Originally,
>>>>        we tried to propose our comments and discuss them inside last
>>>>        Wed's interim meeting, Unfortunately, the shortage of time
>>>>        caused we have no time to address them. Hence, we pointed them
>>>>        out here.
>>>>         1)  We need more clear IP family host definitions
>>>>        Inside the draft, existing =A1=B0IPv6-only=A1=B1 and =A1=B0IPv4=
-only=A1=B1
>>>>        definitions are targeting to IP host capabilities, but there
>>>>        are unclear descriptions of =A1=B0application instances=A1=B1. =
Hence we
>>>>        propose the  IP family host shall be defined combining with
>>>>        four aspects:
>>>>        a. the application type installed on the host,
>>>>        b.the IP family stack supported by a host
>>>>        c.the IP family routing assigned by a network
>>>>        d.available IP family connectivity
>>>>        According to the above principles, following IP family host
>>>>        definitions are suggested to replace current =A1=B0IPv6-only=A1=
=B1 and
>>>>        =A1=B0IPv4-only=A1=B1 definitions and propose a new definition =
for
>>>>        supplement:
>>>>        IPv4 only host comprises an IPv4 enabled end system stack plus
>>>>        routing in the network, IPv4 applications installed on the
>>>>        host. It implies two application instances with installed IPv4
>>>>        applications are capable of communication using IPv4, but not
>>>>        IPv6 =A1=AD=A1=AD
>>>>        IPv6 only host comprises an IPv6 enabled end system stack plus
>>>>        routing in the network, IPv6 applications installed on the
>>>>        host. It implies two application instances with installed IPv6
>>>>        applications are capable of communication using IPv6, but not
>>>>        IPv4 =A1=AD=A1=AD
>>>>        IPv4-inherited IPv6 host comprises an IPv4/IPv6 enabled end
>>>>        system dual-stack plus IPv6 routing in the network, IPv4/IPv6
>>>>        applications installed on the host. It implies two application
>>>>        instances with installed IPv4/IPv6 applications are capable of
>>>>        communication using IPv6 =A8C they have IPv4/IPv6 dual-stack,
>>>>        network support including routing in IPv6, IPv4/IPv6
>>>>        applications can communicate with IPv4/IPv6 hosts respectively.
>>>>        Furthermore, the =A1=B0An IPv6 network=A1=B1 are proposed to re=
defined
>>>>        as: A specific network that has IPv6-only and IPv4-inherited
>>>>        IPv6 implementation.
>>>>         2=A3=A9How to differentiate IPv6 network & IPv6 Internet
>>>>        The difference between IPv4 network and IPv4 Internet could be
>>>>        identified by CGN (NAT) functionalities. However, there are no
>>>>        CGN(NAT) functionalities defined in IPv6 world. It=A1=AFs diffi=
cult
>>>>        to differentiate IPv6 network and Internet. Hence, we suggest
>>>>        to re-define the IPv6 Internet in the framework draft based on
>>>>        network scale size, as follows: IPv6 Internet means a global
>>>>        system of interconnected IPv6 networks, including enterprise=A1=
=AFs
>>>>        IPv6 networks and ISP=A1=AFs IPv6 networks.
>>>>        Otherwise, we have to introduce a new NAT equipment with NAT66
>>>>        functionalities to differentiate IPv6 network & IPv6 Internet.
>>>>         3) Other comments related to the contexts
>>>>        Comments for 3.1.1 and 3.2.2 about stateful translation
>>>>        statements:
>>>>        For stateful translation, the draft has mentioned =A1=B0the
>>>>        stateful translation only support IPv6 initiated
>>>>        communication=A1=B1. But NAT-PT could support both directional
>>>>        communication without this limitation. Hence, we suggest to
>>>>        remove this descriptions or point out it is only targeting to
>>>>        NAT64
>>>>
>>>>
>>>>    NAT-PT was deprecated by RFC 4966.
>>>>
>>>>
>>>>        Comments for 3.3 about ALG descriptions:
>>>>        It only list the demand for FTP ALG. But there should be
>>>>        support any kind of applications in which IP address is
>>>>        concluded in payload, such as SIP, RTSP. Hence, we suggest to
>>>>        extend ALG scope avoid reader=A1=AFs misunderstanding.
>>>>
>>>>
>>>>    Yes, agree.
>>>>
>>>>         Hope all these are meaningful.
>>>>         Regards,
>>>>
>>>>        Bo Zhou
>>>>        China Mobile
>>>>
>>>>  ---------------------------------------------------------------------=
---
>>>>
>>>>        _______________________________________________
>>>>        Behave mailing list
>>>>        Behave@ietf.org <mailto:Behave@ietf.org>
>>>>        https://www.ietf.org/mailman/listinfo/behave
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Regards,
>>>>
>>>> Bo Zhou
>>>> China Mobile
>>>> ----------------------------------------------------------------------=
--
>>>>
>>>> _______________________________________________
>>>> Behave mailing list
>>>> Behave@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/behave
>>>>
>>>>
>>>
>>>
>>
>>
>> --
>> =B3=C2=B8=D5
>> phdgang@gmail.com
>>
>
>
>
> --
>  Regards,
>
> Bo Zhou
> China Mobile
>



--=20
=B3=C2=B8=D5
phdgang@gmail.com

--0016e64bdaeaf8efa504734721c4
Content-Type: text/html; charset=GB2312
Content-Transfer-Encoding: quoted-printable

<div>Anyhow, there are some ambiguities on application type.</div>
<div>The author is kindly asked to clarify the information and make IPv6-on=
ly definition more clear.</div>
<div>&nbsp;</div>
<div>Gang<br><br></div>
<div class=3D"gmail_quote">2009/9/11 bo zhou <span dir=3D"ltr">&lt;<a href=
=3D"mailto:zhouboyj@gmail.com">zhouboyj@gmail.com</a>&gt;</span><br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>For my understanding, &quot;two application instances&quot; here indic=
ates two IPv6-only instances, like two IPv6 &nbsp;host, both installed&nbsp=
;IPv6 application, and they want to communicate with&nbsp;each other via IP=
v6 network.</div>

<div>Am I right?</div>
<div>&nbsp;</div>
<div>Regards,</div>
<div>&nbsp;</div>
<div>Bo Zhou&nbsp;&nbsp;<br><br></div>
<div class=3D"gmail_quote">2009/9/11 Chen Gang <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:phdgang@gmail.com" target=3D"_blank">phdgang@gmail.com</a>&gt;<=
/span>=20
<div>
<div></div>
<div class=3D"h5"><br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>Hello Xing,</div>
<div>&nbsp;</div>
<div>With regard to the latest difinition of IPv6-only, there are some ques=
tioins for clarifications.</div>
<div>&nbsp;</div>
<div>Within the sentence &quot;It implies that <font color=3D"#ff0000">two =
application instances</font> are capable of communicating using IPv6, but n=
ot IPv4 - they have an IPv6 stack&quot;, does &quot;two application instanc=
es&quot; means &quot;IPv4 application instances and IPv6 application instan=
ces&quot;?</div>

<div>&nbsp;</div>
<div>If that is true, I guess &quot;IPv6-only&quot; need do&nbsp;some sort =
of application ALG or host-based translation&nbsp;in&nbsp;order&nbsp;to let=
 IPv4 application to&nbsp;accomodate a IPv6-only environment.</div>
<div>&nbsp;</div>
<div>If my understanding is correct, you may also need to clarify this mean=
ing in the IPv6-only definition or separate this meaning to new defined ter=
ms, like Bo suggested &quot;<br>IPv4-inherited IPv6 host&quot;.</div>
<div>&nbsp;</div>
<div>Thanks</div>
<div>&nbsp;</div>
<div>BRs</div>
<div>&nbsp;</div>
<div>Gang</div>
<div>&nbsp;</div>
<div><br><br>&nbsp;</div>
<div class=3D"gmail_quote">2009/9/11 Xing Li <span dir=3D"ltr">&lt;<a href=
=3D"mailto:xing@cernet.edu.cn" target=3D"_blank">xing@cernet.edu.cn</a>&gt;=
</span>=20
<div>
<div></div>
<div><br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">bo zhou =D0=B4=B5=C0:=20
<div><br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><br><br><br>&nbsp; &nbsp;However=
, if the consensus is to add the discussion on application<br>&nbsp; &nbsp;=
instances, I am happy to add the words.<br>
<br>[bo] Yes, we want to introduce the application type to make the definit=
ion more clearly.<br></blockquote></div>we have made some modifications in =
draft-ietf-behave-v6v4-framework-01=20
<div><br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><br><br>&nbsp; &nbsp;(2) Please =
see the Sec. 1.2, the border between an IPvx network<br>&nbsp; &nbsp;and th=
e IPvx Internet is not defined by NAT.<br>
<br>[bo] Sorry, I cannot find any words in Sec.1.2 to define the difference=
 between network and Internet.<br></blockquote><br></div>&nbsp;An IPv4 netw=
ork: &nbsp;A specific network that has an IPv4-only<br>&nbsp; &nbsp; deploy=
ment. &nbsp;This could be an enterprise&#39;s IPv4-only network or an<br>
&nbsp; &nbsp; ISP&#39;s IPv4-only network. &nbsp;The size of an IPv4 networ=
k is<br>&nbsp; &nbsp; relatively small comparing to the global IPv4 Interne=
t.<br><br>The key words are: &quot;A specific network&quot; and &quot;relat=
ively small comparing to the global IPv4 Internet&quot;.=20
<div><br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><br><br>&nbsp; &nbsp;(3) Other c=
omments are inline.<br>&nbsp; &nbsp;[bo] Yes, we knew NAT-PT was deprecated=
 by RFC 4966. However, the<br>
&nbsp; &nbsp;comments we pointed out is focus on stateful translation&#39;s=
<br>&nbsp; &nbsp;limitation. We think &quot;the stateful translation only s=
upport IPv6<br>&nbsp; &nbsp;initiated communication&quot; is only related t=
o NAT64. It is hard<br>&nbsp; &nbsp;to say &quot;stateful translation can o=
nly support IPv6 initiated<br>
&nbsp; &nbsp;communication&quot; because &quot;NAT64 can only do it&quot;. =
We agreed NAT64 is<br>&nbsp; &nbsp;one of significant stateful translation,=
 but we do not agree it<br>&nbsp; &nbsp;represents all behaviours of statef=
ul translation.<br><br></blockquote>
<br></div>We are working on the standard of translation. NAT-PT was depreca=
ted and the stateful translation proved by behave working group is NAT64 at=
 this moment.=20
<div><br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><br>&nbsp; &nbsp;[bo]About the A=
LG issue, we should state &quot;all IP packet payload<br>&nbsp; &nbsp;inclu=
ded IP address need do ALG&quot;.<br>
<br></blockquote></div>Agree, if the end systems are in different address f=
amilies.<br><br>xing<br><br><br><br><br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>
<div></div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;<br>&nbsp; &nbsp;Regards,<br><br>&nbsp; &nbsp;=
xing<br><br><br>&nbsp; &nbsp;bo zhou =D0=B4=B5=C0:<br><br>&nbsp; &nbsp; &nb=
sp; &nbsp;Hi Fred and others authors of framework for IPv4/IPv6 translation=
<br>&nbsp; &nbsp; &nbsp; &nbsp; We have some texts and comments for this dr=
aft. Originally,<br>
&nbsp; &nbsp; &nbsp; &nbsp;we tried to propose our comments and discuss the=
m inside last<br>&nbsp; &nbsp; &nbsp; &nbsp;Wed&#39;s interim meeting, Unfo=
rtunately, the shortage of time<br>&nbsp; &nbsp; &nbsp; &nbsp;caused we hav=
e no time to address them. Hence, we pointed them<br>&nbsp; &nbsp; &nbsp; &=
nbsp;out here.<br>
&nbsp; &nbsp; &nbsp; &nbsp; 1) &nbsp;We need more clear IP family host defi=
nitions<br>&nbsp; &nbsp; &nbsp; &nbsp;Inside the draft, existing &ldquo;IPv=
6-only&rdquo; and &ldquo;IPv4-only&rdquo;<br>&nbsp; &nbsp; &nbsp; &nbsp;def=
initions are targeting to IP host capabilities, but there<br>&nbsp; &nbsp; =
&nbsp; &nbsp;are unclear descriptions of &ldquo;application instances&rdquo=
;. Hence we<br>
&nbsp; &nbsp; &nbsp; &nbsp;propose the &nbsp;IP family host shall be define=
d combining with<br>&nbsp; &nbsp; &nbsp; &nbsp;four aspects:<br>&nbsp; &nbs=
p; &nbsp; &nbsp;a. the application type installed on the host,<br>&nbsp; &n=
bsp; &nbsp; &nbsp;b.the IP family stack supported by a host<br>&nbsp; &nbsp=
; &nbsp; &nbsp;c.the IP family routing assigned by a network<br>
&nbsp; &nbsp; &nbsp; &nbsp;d.available IP family connectivity<br>&nbsp; &nb=
sp; &nbsp; &nbsp;According to the above principles, following IP family hos=
t<br>&nbsp; &nbsp; &nbsp; &nbsp;definitions are suggested to replace curren=
t &ldquo;IPv6-only&rdquo; and<br>&nbsp; &nbsp; &nbsp; &nbsp;&ldquo;IPv4-onl=
y&rdquo; definitions and propose a new definition for<br>
&nbsp; &nbsp; &nbsp; &nbsp;supplement:<br>&nbsp; &nbsp; &nbsp; &nbsp;IPv4 o=
nly host comprises an IPv4 enabled end system stack plus<br>&nbsp; &nbsp; &=
nbsp; &nbsp;routing in the network, IPv4 applications installed on the<br>&=
nbsp; &nbsp; &nbsp; &nbsp;host. It implies two application instances with i=
nstalled IPv4<br>
&nbsp; &nbsp; &nbsp; &nbsp;applications are capable of communication using =
IPv4, but not<br>&nbsp; &nbsp; &nbsp; &nbsp;IPv6 &hellip;&hellip;<br>&nbsp;=
 &nbsp; &nbsp; &nbsp;IPv6 only host comprises an IPv6 enabled end system st=
ack plus<br>&nbsp; &nbsp; &nbsp; &nbsp;routing in the network, IPv6 applica=
tions installed on the<br>
&nbsp; &nbsp; &nbsp; &nbsp;host. It implies two application instances with =
installed IPv6<br>&nbsp; &nbsp; &nbsp; &nbsp;applications are capable of co=
mmunication using IPv6, but not<br>&nbsp; &nbsp; &nbsp; &nbsp;IPv4 &hellip;=
&hellip;<br>&nbsp; &nbsp; &nbsp; &nbsp;IPv4-inherited IPv6 host comprises a=
n IPv4/IPv6 enabled end<br>
&nbsp; &nbsp; &nbsp; &nbsp;system dual-stack plus IPv6 routing in the netwo=
rk, IPv4/IPv6<br>&nbsp; &nbsp; &nbsp; &nbsp;applications installed on the h=
ost. It implies two application<br>&nbsp; &nbsp; &nbsp; &nbsp;instances wit=
h installed IPv4/IPv6 applications are capable of<br>&nbsp; &nbsp; &nbsp; &=
nbsp;communication using IPv6 &ndash; they have IPv4/IPv6 dual-stack,<br>
&nbsp; &nbsp; &nbsp; &nbsp;network support including routing in IPv6, IPv4/=
IPv6<br>&nbsp; &nbsp; &nbsp; &nbsp;applications can communicate with IPv4/I=
Pv6 hosts respectively.<br>&nbsp; &nbsp; &nbsp; &nbsp;Furthermore, the &ldq=
uo;An IPv6 network&rdquo; are proposed to redefined<br>&nbsp; &nbsp; &nbsp;=
 &nbsp;as: A specific network that has IPv6-only and IPv4-inherited<br>
&nbsp; &nbsp; &nbsp; &nbsp;IPv6 implementation.<br>&nbsp; &nbsp; &nbsp; &nb=
sp; 2=A3=A9How to differentiate IPv6 network &amp; IPv6 Internet<br>&nbsp; =
&nbsp; &nbsp; &nbsp;The difference between IPv4 network and IPv4 Internet c=
ould be<br>&nbsp; &nbsp; &nbsp; &nbsp;identified by CGN (NAT) functionaliti=
es. However, there are no<br>
&nbsp; &nbsp; &nbsp; &nbsp;CGN(NAT) functionalities defined in IPv6 world. =
It&rsquo;s difficult<br>&nbsp; &nbsp; &nbsp; &nbsp;to differentiate IPv6 ne=
twork and Internet. Hence, we suggest<br>&nbsp; &nbsp; &nbsp; &nbsp;to re-d=
efine the IPv6 Internet in the framework draft based on<br>&nbsp; &nbsp; &n=
bsp; &nbsp;network scale size, as follows: IPv6 Internet means a global<br>
&nbsp; &nbsp; &nbsp; &nbsp;system of interconnected IPv6 networks, includin=
g enterprise&rsquo;s<br>&nbsp; &nbsp; &nbsp; &nbsp;IPv6 networks and ISP&rs=
quo;s IPv6 networks.<br>&nbsp; &nbsp; &nbsp; &nbsp;Otherwise, we have to in=
troduce a new NAT equipment with NAT66<br>&nbsp; &nbsp; &nbsp; &nbsp;functi=
onalities to differentiate IPv6 network &amp; IPv6 Internet.<br>
&nbsp; &nbsp; &nbsp; &nbsp; 3) Other comments related to the contexts<br>&n=
bsp; &nbsp; &nbsp; &nbsp;Comments for 3.1.1 and 3.2.2 about stateful transl=
ation<br>&nbsp; &nbsp; &nbsp; &nbsp;statements:<br>&nbsp; &nbsp; &nbsp; &nb=
sp;For stateful translation, the draft has mentioned &ldquo;the<br>&nbsp; &=
nbsp; &nbsp; &nbsp;stateful translation only support IPv6 initiated<br>
&nbsp; &nbsp; &nbsp; &nbsp;communication&rdquo;. But NAT-PT could support b=
oth directional<br>&nbsp; &nbsp; &nbsp; &nbsp;communication without this li=
mitation. Hence, we suggest to<br>&nbsp; &nbsp; &nbsp; &nbsp;remove this de=
scriptions or point out it is only targeting to<br>&nbsp; &nbsp; &nbsp; &nb=
sp;NAT64<br>
<br><br>&nbsp; &nbsp;NAT-PT was deprecated by RFC 4966.<br><br><br>&nbsp; &=
nbsp; &nbsp; &nbsp;Comments for 3.3 about ALG descriptions:<br>&nbsp; &nbsp=
; &nbsp; &nbsp;It only list the demand for FTP ALG. But there should be<br>=
&nbsp; &nbsp; &nbsp; &nbsp;support any kind of applications in which IP add=
ress is<br>
&nbsp; &nbsp; &nbsp; &nbsp;concluded in payload, such as SIP, RTSP. Hence, =
we suggest to<br>&nbsp; &nbsp; &nbsp; &nbsp;extend ALG scope avoid reader&r=
squo;s misunderstanding.<br><br><br>&nbsp; &nbsp;Yes, agree.<br><br>&nbsp; =
&nbsp; &nbsp; &nbsp; Hope all these are meaningful.<br>&nbsp; &nbsp; &nbsp;=
 &nbsp; Regards,<br>
<br>&nbsp; &nbsp; &nbsp; &nbsp;Bo Zhou<br>&nbsp; &nbsp; &nbsp; &nbsp;China =
Mobile<br>&nbsp; &nbsp; &nbsp; &nbsp;--------------------------------------=
----------------------------------<br><br>&nbsp; &nbsp; &nbsp; &nbsp;______=
_________________________________________<br>&nbsp; &nbsp; &nbsp; &nbsp;Beh=
ave mailing list<br></div>
</div>&nbsp; &nbsp; &nbsp; &nbsp;<a href=3D"mailto:Behave@ietf.org" target=
=3D"_blank">Behave@ietf.org</a> &lt;mailto:<a href=3D"mailto:Behave@ietf.or=
g" target=3D"_blank">Behave@ietf.org</a>&gt;=20
<div><br>&nbsp; &nbsp; &nbsp; &nbsp;<a href=3D"https://www.ietf.org/mailman=
/listinfo/behave" target=3D"_blank">https://www.ietf.org/mailman/listinfo/b=
ehave</a><br>&nbsp; &nbsp; &nbsp; &nbsp; <br><br><br><br><br>-- <br>Regards=
,<br><br>Bo Zhou<br>China Mobile<br>---------------------------------------=
---------------------------------<br>
<br>_______________________________________________<br>Behave mailing list<=
br><a href=3D"mailto:Behave@ietf.org" target=3D"_blank">Behave@ietf.org</a>=
<br><a href=3D"https://www.ietf.org/mailman/listinfo/behave" target=3D"_bla=
nk">https://www.ietf.org/mailman/listinfo/behave</a><br>
&nbsp;<br></div></blockquote><br></blockquote></div></div></div><font color=
=3D"#888888"><br><br clear=3D"all">
<div></div><br>-- <br>=B3=C2=B8=D5<br><a href=3D"mailto:phdgang@gmail.com" =
target=3D"_blank">phdgang@gmail.com</a><br></font></blockquote></div></div>=
</div><br><br clear=3D"all">
<div></div><br>-- <br>
<div>
<div></div>
<div class=3D"h5">Regards,<br><br>Bo Zhou<br>China Mobile<br></div></div></=
blockquote></div><br><br clear=3D"all">
<div></div><br>-- <br>=B3=C2=B8=D5<br><a href=3D"mailto:phdgang@gmail.com">=
phdgang@gmail.com</a><br>

--0016e64bdaeaf8efa504734721c4--

From Fred.L.Templin@boeing.com  Fri Sep 11 10:55:40 2009
Return-Path: <Fred.L.Templin@boeing.com>
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 DBF0C3A68BB for <behave@core3.amsl.com>; Fri, 11 Sep 2009 10:55:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.92
X-Spam-Level: 
X-Spam-Status: No, score=-5.92 tagged_above=-999 required=5 tests=[AWL=0.679,  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 fF4spVFeCqVg for <behave@core3.amsl.com>; Fri, 11 Sep 2009 10:55:40 -0700 (PDT)
Received: from stl-smtpout-01.boeing.com (stl-smtpout-01.boeing.com [130.76.96.56]) by core3.amsl.com (Postfix) with ESMTP id ECF613A681F for <behave@ietf.org>; Fri, 11 Sep 2009 10:55:39 -0700 (PDT)
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6]) by stl-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id n8BHu8wI004893 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 11 Sep 2009 12:56:09 -0500 (CDT)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id n8BHu8Fl003098; Fri, 11 Sep 2009 12:56:08 -0500 (CDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com [130.247.55.84]) by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id n8BHu4ec002984; Fri, 11 Sep 2009 12:56:08 -0500 (CDT)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 11 Sep 2009 10:56:06 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 11 Sep 2009 10:56:05 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1066249A1@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <74AA3C18-B735-4020-9FEB-B1ABBED1ACFF@muada.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BEHAVE] 64 MTU and fragmentation handling
Thread-Index: AcoyITxNtTYP6ztCSEuzZtrdkdsQvgA52m4w
References: <A09ECC61-E8CB-430B-A891-53902BEA083D@muada.com><a7c8d0a30909100630y32e30024s68d17487612ebd37@mail.gmail.com> <74AA3C18-B735-4020-9FEB-B1ABBED1ACFF@muada.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Iljitsch van Beijnum" <iljitsch@muada.com>, "Zhen Cao" <caozhenpku@gmail.com>
X-OriginalArrivalTime: 11 Sep 2009 17:56:06.0209 (UTC) FILETIME=[229FA310:01CA3309]
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] 64 MTU and fragmentation handling
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/mail-archive/web/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>
X-List-Received-Date: Fri, 11 Sep 2009 17:55:40 -0000

Iljitsch,

> -----Original Message-----
> From: Iljitsch van Beijnum [mailto:iljitsch@muada.com]
> Sent: Thursday, September 10, 2009 7:16 AM
> To: Zhen Cao
> Cc: Behave WG
> Subject: Re: [BEHAVE] 64 MTU and fragmentation handling
>=20
> On 10 Sep 2009, at 15:30 , Zhen Cao wrote:
>=20
> > The current discussion only focused on the black hole for 1280
> > fragments where an IPv4 router reports MTU <1280. IMO, the black
hole
> > may happen in many scenarios.  For instance, if MTU is 1600 for ipv6
> > side and 1500 for ipv4 side, an IPv6 sender starts sending 1600-byte
> > packets without fragmentation header to discover the PMTU. But the
> > ICMP PktTooBig message is blocked or lost due to whatever reasons,
the
> > sender continues to send 1600-byte packets without frag header,
> > resulting DF=3D1 translated ipv4 packets longer than 1500 and
> > communication is lost then.  Has this case been handled by some
> > existing specfications?
>=20
> This is true. However, someone sending 1600-byte packets and filtering
> too big messages would very quickly find out that that combination of
> settings is problematic and fix this one way or another. (Although
> there will be some PMTUD black holes when the sender of 1600-byte
> packets accepts too bigs but the other side fails to generate them.)
> So this situation is orthogonal to the IPv6/IPv4 translation.
>=20
> The only good solution for this is RFC 4821, but I understand that
> there are other PMTUD blackhole detection mechanisms, and that
> Microsoft implements one of those. Not sure how they work.

I would go one step farther to say that any host sending
DF=3D1 packets larger than 1500 SHOULD use RFC 4821 or another
suitable PMTUD blackhole detection mechanism. And, failure
to observe the SHOULD may result in unpredictable behavior.

Fred
fred.l.templin@boeing.com

> > Moreover, current IPv4 network always has MTU greater than 1400, so
> > the possibility of reporting a <1280 MTU is slim.
>=20
> I agree that this wouldn't be a common situation, but "always" is too
> optimistic, I'm afraid...
>=20
> Iljitsch
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave

From iljitsch@muada.com  Fri Sep 11 12:26:17 2009
Return-Path: <iljitsch@muada.com>
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 EC1CB28C129 for <behave@core3.amsl.com>; Fri, 11 Sep 2009 12:26:17 -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 QhVUEDBtXswo for <behave@core3.amsl.com>; Fri, 11 Sep 2009 12:26:17 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2]) by core3.amsl.com (Postfix) with ESMTP id DC70628C1B8 for <behave@ietf.org>; Fri, 11 Sep 2009 12:26:16 -0700 (PDT)
Received: from cl-1496.ams-04.nl.sixxs.net (cl-1496.ams-04.nl.sixxs.net [IPv6:2001:960:2:5d7::2]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id n8BJQfqi050987 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 11 Sep 2009 21:26:42 +0200 (CEST) (envelope-from iljitsch@muada.com)
Mime-Version: 1.0 (Apple Message framework v1076)
Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <39C363776A4E8C4A94691D2BD9D1C9A1066249A1@XCH-NW-7V2.nw.nos.boeing.com>
Date: Fri, 11 Sep 2009 21:26:42 +0200
Content-Transfer-Encoding: 7bit
Message-Id: <D42C5920-C7D5-40E6-99A4-A26DE139746A@muada.com>
References: <A09ECC61-E8CB-430B-A891-53902BEA083D@muada.com><a7c8d0a30909100630y32e30024s68d17487612ebd37@mail.gmail.com> <74AA3C18-B735-4020-9FEB-B1ABBED1ACFF@muada.com> <39C363776A4E8C4A94691D2BD9D1C9A1066249A1@XCH-NW-7V2.nw.nos.boeing.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
X-Mailer: Apple Mail (2.1076)
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] 64 MTU and fragmentation handling
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/mail-archive/web/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>
X-List-Received-Date: Fri, 11 Sep 2009 19:26:18 -0000

We're getting a bit off topic for BEHAVE, but ok...

On 11 Sep 2009, at 19:56 , Templin, Fred L wrote:

> I would go one step farther to say that any host sending
> DF=1 packets larger than 1500 SHOULD use RFC 4821 or another
> suitable PMTUD blackhole detection mechanism. And, failure
> to observe the SHOULD may result in unpredictable behavior.

I don't see the relationship with 1500 bytes. You never know when you  
may be communicating through a path that supports a smaller MTU than  
your own MTU, so discovering the path MTU by modulating transport  
segment sizes as per RFC 4821 is ALWAYS a good idea. However, this is  
a complex solution and it only addresses the case where the sender can  
easily manipulate packet sizes. For many non-TCP protocols that isn't  
the case, especially not if the packets are created by the application  
rather than the OS.

Also note that using an MTU larger than 1500 is far less dangerous  
than using an MTU smaller than 1500. In the latter case, if there is a  
problem, the party with the non-1500-byte MTU is in no position to fix  
the problem: the too bigs are traveling towards the correspondent  
host, and are presumably filtered before they get there. And  
presumably increasing the MTU is infeasible, otherwise it wouldn't be  
so small in the first place. In the case of a larger than 1500-byte  
MTU, the operator is in a better position to remove stuff that blocks  
the too bigs, and it's always possible to reduce the MTU to 1500 as a  
last resort.

Last but not least, the TCP MSS option hides a multitude of sins. Only  
when both ends have an MTU larger than the path MTU there may be  
problems.

So I'm not worried about people using MTUs larger than 1500.

From Fred.L.Templin@boeing.com  Fri Sep 11 14:21:51 2009
Return-Path: <Fred.L.Templin@boeing.com>
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 E6BBF3A69AD for <behave@core3.amsl.com>; Fri, 11 Sep 2009 14:21:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.941
X-Spam-Level: 
X-Spam-Status: No, score=-5.941 tagged_above=-999 required=5 tests=[AWL=0.658,  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 27hrVLqjWWZo for <behave@core3.amsl.com>; Fri, 11 Sep 2009 14:21:51 -0700 (PDT)
Received: from slb-smtpout-01.boeing.com (slb-smtpout-01.boeing.com [130.76.64.48]) by core3.amsl.com (Postfix) with ESMTP id 1BC893A697A for <behave@ietf.org>; Fri, 11 Sep 2009 14:21:51 -0700 (PDT)
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4]) by slb-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id n8BLMO9I011589 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 11 Sep 2009 14:22:24 -0700 (PDT)
Received: from slb-av-01.boeing.com (localhost [127.0.0.1]) by slb-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id n8BLMNpU026226; Fri, 11 Sep 2009 14:22:24 -0700 (PDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com [130.247.55.84]) by slb-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id n8BLMN70026219; Fri, 11 Sep 2009 14:22:23 -0700 (PDT)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 11 Sep 2009 14:22:23 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 11 Sep 2009 14:22:22 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A106624B32@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <D42C5920-C7D5-40E6-99A4-A26DE139746A@muada.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BEHAVE] 64 MTU and fragmentation handling
Thread-Index: AcozFdH6aHKOX6GhRQCIShzt2pErVQADv5Lw
References: <A09ECC61-E8CB-430B-A891-53902BEA083D@muada.com><a7c8d0a30909100630y32e30024s68d17487612ebd37@mail.gmail.com> <74AA3C18-B735-4020-9FEB-B1ABBED1ACFF@muada.com> <39C363776A4E8C4A94691D2BD9D1C9A1066249A1@XCH-NW-7V2.nw.nos.boeing.com> <D42C5920-C7D5-40E6-99A4-A26DE139746A@muada.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Iljitsch van Beijnum" <iljitsch@muada.com>
X-OriginalArrivalTime: 11 Sep 2009 21:22:23.0697 (UTC) FILETIME=[F42E6C10:01CA3325]
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] 64 MTU and fragmentation handling
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/mail-archive/web/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>
X-List-Received-Date: Fri, 11 Sep 2009 21:21:52 -0000

Hi Iljitsch,

> -----Original Message-----
> From: Iljitsch van Beijnum [mailto:iljitsch@muada.com]
> Sent: Friday, September 11, 2009 12:27 PM
> To: Templin, Fred L
> Cc: Behave WG
> Subject: Re: [BEHAVE] 64 MTU and fragmentation handling
>=20
> We're getting a bit off topic for BEHAVE, but ok...
>=20
> On 11 Sep 2009, at 19:56 , Templin, Fred L wrote:
>=20
> > I would go one step farther to say that any host sending
> > DF=3D1 packets larger than 1500 SHOULD use RFC 4821 or another
> > suitable PMTUD blackhole detection mechanism. And, failure
> > to observe the SHOULD may result in unpredictable behavior.
>=20
> I don't see the relationship with 1500 bytes. You never know when you
> may be communicating through a path that supports a smaller MTU than
> your own MTU, so discovering the path MTU by modulating transport
> segment sizes as per RFC 4821 is ALWAYS a good idea.

Right.

> However, this is
> a complex solution and it only addresses the case where the sender can
> easily manipulate packet sizes. For many non-TCP protocols that isn't
> the case, especially not if the packets are created by the application
> rather than the OS.

So, RFC4821 does have something to say about implementation
in packetization layers other than TCP.
=20
> Also note that using an MTU larger than 1500 is far less dangerous
> than using an MTU smaller than 1500. In the latter case, if there is a
> problem, the party with the non-1500-byte MTU is in no position to fix
> the problem: the too bigs are traveling towards the correspondent
> host, and are presumably filtered before they get there. And
> presumably increasing the MTU is infeasible, otherwise it wouldn't be
> so small in the first place. In the case of a larger than 1500-byte
> MTU, the operator is in a better position to remove stuff that blocks
> the too bigs, and it's always possible to reduce the MTU to 1500 as a
> last resort.

Not sure I get the distinction you are making, but I will
agree that a 1500- MTU is more likely to be closer toward
the final destination while a 1500+ MTU is more likely to
be closer toward the original source. So that would tend
to reduce the exposure to ICMP filtering simply due to
fewer hops traversed along the reverse path.

> Last but not least, the TCP MSS option hides a multitude of sins. Only
> when both ends have an MTU larger than the path MTU there may be
> problems.

I put MSS clamping in the "band aid solution" category. When
it works, it works great, but IMHO we will begin to see more
and more non-TCP communications that can't use it.

Fred
fred.l.templin@boeing.com

> So I'm not worried about people using MTUs larger than 1500.

From dwing@cisco.com  Fri Sep 11 14:43:54 2009
Return-Path: <dwing@cisco.com>
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 82EC328C1F2 for <behave@core3.amsl.com>; Fri, 11 Sep 2009 14:43:54 -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 A1ATGkqJTeS8 for <behave@core3.amsl.com>; Fri, 11 Sep 2009 14:43:53 -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 8CE0228C20A for <behave@ietf.org>; Fri, 11 Sep 2009 14:43:52 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApsEAPdhqkqrR7O6/2dsb2JhbACLHLk3iEgBkAcFhBiBWYkM
X-IronPort-AV: E=Sophos;i="4.44,372,1249257600"; d="scan'208";a="203964961"
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-2.cisco.com with ESMTP; 11 Sep 2009 21:44:26 +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 n8BLiNWl014103;  Fri, 11 Sep 2009 14:44:23 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id n8BLiNWK009519; Fri, 11 Sep 2009 21:44:23 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 11 Sep 2009 14:44:23 -0700
Received: from dwingwxp01 ([10.32.240.198]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 11 Sep 2009 14:44:22 -0700
From: "Dan Wing" <dwing@cisco.com>
To: "'Xing Li'" <xing@cernet.edu.cn>, "'bo zhou'" <zhouboyj@gmail.com>
References: <36a593230908232300m45a10136wce25d01ef8bac439@mail.gmail.com>	<4A9B7BA1.6000807@cernet.edu.cn><36a593230908310651kd76a383j28b845bb07ebba55@mail.gmail.com> <4AA9880E.3000007@cernet.edu.cn>
Date: Fri, 11 Sep 2009 14:44:22 -0700
Message-ID: <038201ca3329$06870c70$c6f0200a@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcoybEnUdz+YHOppRgmmdgp9MnnS7gAu5/vQ
In-Reply-To: <4AA9880E.3000007@cernet.edu.cn>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-OriginalArrivalTime: 11 Sep 2009 21:44:22.0918 (UTC) FILETIME=[067F9260:01CA3329]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=352; t=1252705466; x=1253569466; 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]=20Proposed=20text=20and=20comm ents=20for=20framework=20for=20IPv4/IPv6=20translation |Sender:=20; bh=4pOxOYmTIhxJtI01DcBAF0+EULd5seVSv0aQCo5ns78=; b=KJZsaQu6EhDKOB49oSt5yH4QZI8BtQcpz+9RKlTZQsFj4xJCh71BliC1Fc O6yvn/w8H0YJBVCKDcTMLgQoY2B/HNHh+RRMvQtXy2Igk98tVLBmIAHNLFWR nxX3qto/ep;
Authentication-Results: sj-dkim-2; header.From=dwing@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; ); 
Cc: denghui02@gmail.com, congxiao@cernet.edu.cn, behave@ietf.org, 'liu dapeng' <maxpassion@gmail.com>, kyin@cisco.com, fred@cisco.com, phdgang@gmail.com
Subject: Re: [BEHAVE] Proposed text and comments for framework for IPv4/IPv6 translation
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/mail-archive/web/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>
X-List-Received-Date: Fri, 11 Sep 2009 21:43:54 -0000

On Thursday, September 10, 2009 4:13pm, Xing Li wrote:

...
> >     [bo]About the ALG issue, we should state "all IP packet payload
> >     included IP address need do ALG".
> 
> Agree, if the end systems are in different address families.

It is important to avoid ALG issues raised in 
http://tools.ietf.org/html/rfc4924#section-2.3 

-d


From brian.e.carpenter@gmail.com  Fri Sep 11 16:14:05 2009
Return-Path: <brian.e.carpenter@gmail.com>
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 31DE03A67E7 for <behave@core3.amsl.com>; Fri, 11 Sep 2009 16:14:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.221
X-Spam-Level: 
X-Spam-Status: No, score=-2.221 tagged_above=-999 required=5 tests=[AWL=0.378,  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 gh4hbyQk3j04 for <behave@core3.amsl.com>; Fri, 11 Sep 2009 16:14:04 -0700 (PDT)
Received: from mail-pz0-f195.google.com (mail-pz0-f195.google.com [209.85.222.195]) by core3.amsl.com (Postfix) with ESMTP id 73D0E3A67C0 for <behave@ietf.org>; Fri, 11 Sep 2009 16:14:04 -0700 (PDT)
Received: by pzk33 with SMTP id 33so1212918pzk.24 for <behave@ietf.org>; Fri, 11 Sep 2009 16:14: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=l7nGp3OYVnfgOFEqWkyvaUEMfUCWbtNdDSit6EyH+ZY=; b=Kh4x+EWFOb1WO6FcoXF+zX3VFE6VZVGgHzAkd/aV9Z7UKkLSNwlR7HPq2OyVU2MlIj 2vEOHXjTt7quR/5ZXQgL1kYJXDI3pR79RFuyd+qAyxhYnsqQZL13dO08FRUwnjLxdAIQ 8aq6wsMc/yfnQ6eLAGqJTZm/0KeIL0ZUAbD2o=
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=aD1X74UlxyEygm+wTJ+oicJ5024ez3d2+PRof//L5rGd/S9whY4PwRnFN5NXHOY2r1 3SQZpeSzHdkL6vpSWjv3yD4pX7YRrMchtyK8bQ8DF0nvH7rPoiNgLDOmpvh9xrRkcp/f PvUhRnnuwuh9Cxip2hhVcCrDQAbcTdf4ae6nQ=
Received: by 10.115.39.23 with SMTP id r23mr6476308waj.2.1252710880175; Fri, 11 Sep 2009 16:14:40 -0700 (PDT)
Received: from ?10.1.1.4? (118-92-111-74.dsl.dyn.ihug.co.nz [118.92.111.74]) by mx.google.com with ESMTPS id 20sm962142pzk.9.2009.09.11.16.14.36 (version=SSLv3 cipher=RC4-MD5); Fri, 11 Sep 2009 16:14:39 -0700 (PDT)
Message-ID: <4AAAD9D7.6080904@gmail.com>
Date: Sat, 12 Sep 2009 11:14:31 +1200
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: bo zhou <zhouboyj@gmail.com>
References: <36a593230908232300m45a10136wce25d01ef8bac439@mail.gmail.com>	<4A9B7BA1.6000807@cernet.edu.cn>	<36a593230908310651kd76a383j28b845bb07ebba55@mail.gmail.com>	<4AA9880E.3000007@cernet.edu.cn> <36a593230909102302k5df1fcfsda08e38e0068bb38@mail.gmail.com>
In-Reply-To: <36a593230909102302k5df1fcfsda08e38e0068bb38@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: denghui02@gmail.com, congxiao@cernet.edu.cn, behave@ietf.org, liu dapeng <maxpassion@gmail.com>, kyin@cisco.com, Xing Li <xing@cernet.edu.cn>, fred@cisco.com, phdgang@gmail.com
Subject: Re: [BEHAVE] Proposed text and comments for framework for IPv4/IPv6 translation
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/mail-archive/web/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>
X-List-Received-Date: Fri, 11 Sep 2009 23:14:05 -0000

On 2009-09-11 18:02, bo zhou wrote:
...
>>> [bo] Sorry, I cannot find any words in Sec.1.2 to define the difference
>>> between network and Internet.
>>>
>>  An IPv4 network:  A specific network that has an IPv4-only
>>     deployment.  This could be an enterprise's IPv4-only network or an
>>     ISP's IPv4-only network.  The size of an IPv4 network is
>>     relatively small comparing to the global IPv4 Internet.
>>
>> The key words are: "A specific network" and "relatively small comparing to
>> the global IPv4 Internet".
> 
>       [bo] From aboved words, i have feeling that the difference between
> network and Internet is SIZE only. I am not sure the size is the major thing
> to distinguish between the network and Internet, Is there any equipment,
> like NAT, inside the network can help us distinguish between network and
> Internet?

I think the honest answer is no. The variations of how addressing realms
are separated from each other are so great that I can't see any
mathematically precise way to define them.

Operationally, we can perhaps define the point of separation as anywhere
that it is decided to put a translation device. But that doesn't help
anybody to decide where such a point is. I think the definition quoted
above is as good as it can be.

    Brian

From dthaler@microsoft.com  Fri Sep 11 16:44:21 2009
Return-Path: <dthaler@microsoft.com>
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 8A4FC28C1A1 for <behave@core3.amsl.com>; Fri, 11 Sep 2009 16:44:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.456
X-Spam-Level: 
X-Spam-Status: No, score=-10.456 tagged_above=-999 required=5 tests=[AWL=0.143, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ro8ltuMnjRTT for <behave@core3.amsl.com>; Fri, 11 Sep 2009 16:44:20 -0700 (PDT)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.214]) by core3.amsl.com (Postfix) with ESMTP id A210028C147 for <behave@ietf.org>; Fri, 11 Sep 2009 16:44:19 -0700 (PDT)
Received: from TK5EX14MLTC103.redmond.corp.microsoft.com (157.54.79.174) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.2.176.0; Fri, 11 Sep 2009 16:44:56 -0700
Received: from TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com (157.54.71.68) by TK5EX14MLTC103.redmond.corp.microsoft.com (157.54.79.174) with Microsoft SMTP Server id 14.0.639.13; Fri, 11 Sep 2009 16:44:56 -0700
Received: from TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com ([169.254.1.2]) by TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.68]) with mapi; Fri, 11 Sep 2009 16:44:56 -0700
From: Dave Thaler <dthaler@microsoft.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, bo zhou <zhouboyj@gmail.com>
Thread-Topic: [BEHAVE] Proposed text and comments for framework for IPv4/IPv6 translation
Thread-Index: AQHKMzWyNi1jrpdoU0WKtPJoa8g9bpDSDHTA
Date: Fri, 11 Sep 2009 23:44:49 +0000
Message-ID: <E4561B14EE2A3E4E9D478EBFB5416E1B1CC5667B@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com>
References: <36a593230908232300m45a10136wce25d01ef8bac439@mail.gmail.com> <4A9B7BA1.6000807@cernet.edu.cn> <36a593230908310651kd76a383j28b845bb07ebba55@mail.gmail.com> <4AA9880E.3000007@cernet.edu.cn> <36a593230909102302k5df1fcfsda08e38e0068bb38@mail.gmail.com> <4AAAD9D7.6080904@gmail.com>
In-Reply-To: <4AAAD9D7.6080904@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "denghui02@gmail.com" <denghui02@gmail.com>, "congxiao@cernet.edu.cn" <congxiao@cernet.edu.cn>, "behave@ietf.org" <behave@ietf.org>, liu dapeng <maxpassion@gmail.com>, "kyin@cisco.com" <kyin@cisco.com>, Xing Li <xing@cernet.edu.cn>, "fred@cisco.com" <fred@cisco.com>, "phdgang@gmail.com" <phdgang@gmail.com>
Subject: Re: [BEHAVE] Proposed text and comments for framework for IPv4/IPv6 translation
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/mail-archive/web/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>
X-List-Received-Date: Fri, 11 Sep 2009 23:44:21 -0000

One distinction, which isn't always precise but is probably useful is
that "a network" is often managed by a common organization, whereas
the "Internet" is certainly not.  Hence a scenario with "a network"
implies the operators of that network can unilaterally do something
to enable that scenario.

-Dave

-----Original Message-----
From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On Behalf Of=
 Brian E Carpenter
Sent: Friday, September 11, 2009 4:15 PM
To: bo zhou
Cc: denghui02@gmail.com; congxiao@cernet.edu.cn; behave@ietf.org; liu dapen=
g; kyin@cisco.com; Xing Li; fred@cisco.com; phdgang@gmail.com
Subject: Re: [BEHAVE] Proposed text and comments for framework for IPv4/IPv=
6 translation

On 2009-09-11 18:02, bo zhou wrote:
...
>>> [bo] Sorry, I cannot find any words in Sec.1.2 to define the difference
>>> between network and Internet.
>>>
>>  An IPv4 network:  A specific network that has an IPv4-only
>>     deployment.  This could be an enterprise's IPv4-only network or an
>>     ISP's IPv4-only network.  The size of an IPv4 network is
>>     relatively small comparing to the global IPv4 Internet.
>>
>> The key words are: "A specific network" and "relatively small comparing =
to
>> the global IPv4 Internet".
>
>       [bo] From aboved words, i have feeling that the difference between
> network and Internet is SIZE only. I am not sure the size is the major th=
ing
> to distinguish between the network and Internet, Is there any equipment,
> like NAT, inside the network can help us distinguish between network and
> Internet?

I think the honest answer is no. The variations of how addressing realms
are separated from each other are so great that I can't see any
mathematically precise way to define them.

Operationally, we can perhaps define the point of separation as anywhere
that it is decided to put a translation device. But that doesn't help
anybody to decide where such a point is. I think the definition quoted
above is as good as it can be.

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


From brian.e.carpenter@gmail.com  Fri Sep 11 18:24:08 2009
Return-Path: <brian.e.carpenter@gmail.com>
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 6E4943A6A9B for <behave@core3.amsl.com>; Fri, 11 Sep 2009 18:24:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.194
X-Spam-Level: 
X-Spam-Status: No, score=-2.194 tagged_above=-999 required=5 tests=[AWL=0.405,  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 4WYNceIRmsce for <behave@core3.amsl.com>; Fri, 11 Sep 2009 18:24:07 -0700 (PDT)
Received: from mail-px0-f181.google.com (mail-px0-f181.google.com [209.85.216.181]) by core3.amsl.com (Postfix) with ESMTP id 304263A6ABE for <behave@ietf.org>; Fri, 11 Sep 2009 18:24:07 -0700 (PDT)
Received: by pxi11 with SMTP id 11so1176654pxi.17 for <behave@ietf.org>; Fri, 11 Sep 2009 18:24:43 -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=XZ/q4unJn2BzPt5VCvebMMUBue0gQXboDvoFazci/iA=; b=LG4pYH5/4Olj/fGH1Wzl+FBWFm6LZKBg4+wBhdZx8p1wOEZU+RH+UrOAPjA/DrYxBE yZkODKsz3STM9RMgChuRxBgvmxKKP9iKuy3n+meqflCwLi1uipQ7JmeILUH/o1oYRcoG R4SbfsabeTuMtjbnuwT36OmEMjojfM1j5TpcM=
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=cfntZt00AtNRx03R6g2Nq/RIbbL/kncfzbYZlBOEg28rHhdB0BB2nud6brdVxmvmIP NFmsC6ZceJ8xmQ5edabA/+gRfQpp06jn0L+NI4q2rHTSaz4C80t3HXzB6Xcu4kI6arnI DiCBREPAaQfOVg75tnzhSkSpRVyyzvCpPgxm8=
Received: by 10.114.32.28 with SMTP id f28mr6613037waf.130.1252718683194; Fri, 11 Sep 2009 18:24:43 -0700 (PDT)
Received: from ?10.1.1.4? (118-92-111-74.dsl.dyn.ihug.co.nz [118.92.111.74]) by mx.google.com with ESMTPS id 23sm2623534pzk.12.2009.09.11.18.24.38 (version=SSLv3 cipher=RC4-MD5); Fri, 11 Sep 2009 18:24:42 -0700 (PDT)
Message-ID: <4AAAF852.1070505@gmail.com>
Date: Sat, 12 Sep 2009 13:24:34 +1200
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: Dave Thaler <dthaler@microsoft.com>
References: <36a593230908232300m45a10136wce25d01ef8bac439@mail.gmail.com>	<4A9B7BA1.6000807@cernet.edu.cn>	<36a593230908310651kd76a383j28b845bb07ebba55@mail.gmail.com>	<4AA9880E.3000007@cernet.edu.cn>	<36a593230909102302k5df1fcfsda08e38e0068bb38@mail.gmail.com> <4AAAD9D7.6080904@gmail.com> <E4561B14EE2A3E4E9D478EBFB5416E1B1CC5667B@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <E4561B14EE2A3E4E9D478EBFB5416E1B1CC5667B@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "denghui02@gmail.com" <denghui02@gmail.com>, "congxiao@cernet.edu.cn" <congxiao@cernet.edu.cn>, "behave@ietf.org" <behave@ietf.org>, liu dapeng <maxpassion@gmail.com>, "kyin@cisco.com" <kyin@cisco.com>, bo zhou <zhouboyj@gmail.com>, Xing Li <xing@cernet.edu.cn>, "fred@cisco.com" <fred@cisco.com>, "phdgang@gmail.com" <phdgang@gmail.com>
Subject: Re: [BEHAVE] Proposed text and comments for framework for IPv4/IPv6 translation
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/mail-archive/web/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>
X-List-Received-Date: Sat, 12 Sep 2009 01:24:08 -0000

Hi Dave,

Yes, and that fits well with my point, since presumably it's
the operator of the "network" that will decide to configure
a translator at the boundary.

Of course, this can be confused if the network is a virtual
one, overlaid on a physical network managed by someone else.

    Brian

On 2009-09-12 11:44, Dave Thaler wrote:
> One distinction, which isn't always precise but is probably useful is
> that "a network" is often managed by a common organization, whereas
> the "Internet" is certainly not.  Hence a scenario with "a network"
> implies the operators of that network can unilaterally do something
> to enable that scenario.
> 
> -Dave
> 
> -----Original Message-----
> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On Behalf Of Brian E Carpenter
> Sent: Friday, September 11, 2009 4:15 PM
> To: bo zhou
> Cc: denghui02@gmail.com; congxiao@cernet.edu.cn; behave@ietf.org; liu dapeng; kyin@cisco.com; Xing Li; fred@cisco.com; phdgang@gmail.com
> Subject: Re: [BEHAVE] Proposed text and comments for framework for IPv4/IPv6 translation
> 
> On 2009-09-11 18:02, bo zhou wrote:
> ...
>>>> [bo] Sorry, I cannot find any words in Sec.1.2 to define the difference
>>>> between network and Internet.
>>>>
>>>  An IPv4 network:  A specific network that has an IPv4-only
>>>     deployment.  This could be an enterprise's IPv4-only network or an
>>>     ISP's IPv4-only network.  The size of an IPv4 network is
>>>     relatively small comparing to the global IPv4 Internet.
>>>
>>> The key words are: "A specific network" and "relatively small comparing to
>>> the global IPv4 Internet".
>>       [bo] From aboved words, i have feeling that the difference between
>> network and Internet is SIZE only. I am not sure the size is the major thing
>> to distinguish between the network and Internet, Is there any equipment,
>> like NAT, inside the network can help us distinguish between network and
>> Internet?
> 
> I think the honest answer is no. The variations of how addressing realms
> are separated from each other are so great that I can't see any
> mathematically precise way to define them.
> 
> Operationally, we can perhaps define the point of separation as anywhere
> that it is decided to put a translation device. But that doesn't help
> anybody to decide where such a point is. I think the definition quoted
> above is as good as it can be.
> 
>     Brian
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
> 
> 

From caozhenpku@gmail.com  Fri Sep 11 23:03:59 2009
Return-Path: <caozhenpku@gmail.com>
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 26C3C3A659C for <behave@core3.amsl.com>; Fri, 11 Sep 2009 23:03:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.442
X-Spam-Level: 
X-Spam-Status: No, score=-2.442 tagged_above=-999 required=5 tests=[AWL=0.157,  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 ndVMlH2W1tO5 for <behave@core3.amsl.com>; Fri, 11 Sep 2009 23:03:58 -0700 (PDT)
Received: from mail-vw0-f201.google.com (mail-vw0-f201.google.com [209.85.212.201]) by core3.amsl.com (Postfix) with ESMTP id 124663A677C for <behave@ietf.org>; Fri, 11 Sep 2009 23:03:57 -0700 (PDT)
Received: by vws39 with SMTP id 39so1075348vws.29 for <behave@ietf.org>; Fri, 11 Sep 2009 23:04:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=Mc94uP/Oc5JkWmKSobrp/8Wqsl+gAw+ggVvQhczUVRo=; b=np9iFKqvj53ptYS6avY3txTaLX2QHRzA5p7x/47G6aw6DWSVogE0uF6N8ywIT8G5ui XrA2euZYlcyi7FY30CRoPZyIOObxIJ1Fuz70CE/AypFvtjgQ0+s+Z9F1SBUi4L+zHbkz AoHYvVi+y3WoTbgK/54RWK30+p8fi9wIlujNA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=boo09NEd8lvQpcOZGGSppCE5a9CBieTLU4SI4UT9iNz1IsEknz0ZziNK5QmwmBXwh2 2Eb/+yJt6Kt0RVZHFh5B1mK7j4OEZncCocTZb6CrGo43wKprlLyiGb6aI3DDzSzIzhYH vVx8FsDf8dSWmBKN8XWIv0L6OgLkvFark5axw=
MIME-Version: 1.0
Received: by 10.220.12.68 with SMTP id w4mr4554731vcw.111.1252735474105; Fri,  11 Sep 2009 23:04:34 -0700 (PDT)
In-Reply-To: <D42C5920-C7D5-40E6-99A4-A26DE139746A@muada.com>
References: <A09ECC61-E8CB-430B-A891-53902BEA083D@muada.com> <a7c8d0a30909100630y32e30024s68d17487612ebd37@mail.gmail.com> <74AA3C18-B735-4020-9FEB-B1ABBED1ACFF@muada.com> <39C363776A4E8C4A94691D2BD9D1C9A1066249A1@XCH-NW-7V2.nw.nos.boeing.com> <D42C5920-C7D5-40E6-99A4-A26DE139746A@muada.com>
Date: Sat, 12 Sep 2009 14:04:34 +0800
Message-ID: <a7c8d0a30909112304v6023d610n883220b8843582fd@mail.gmail.com>
From: Zhen Cao <caozhenpku@gmail.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "Templin, Fred L" <Fred.L.Templin@boeing.com>, Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] 64 MTU and fragmentation handling
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/mail-archive/web/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>
X-List-Received-Date: Sat, 12 Sep 2009 06:03:59 -0000

On Sat, Sep 12, 2009 at 3:26 AM, Iljitsch van Beijnum
<iljitsch@muada.com> wrote:
> We're getting a bit off topic for BEHAVE, but ok...

I guess you are saying that the black hole problem not only targets
translation. But translation, especially v4-to-v6 which lengthens the
packet, makes this problem worse. So translation algorithm should take
special care of this problem?

>
> On 11 Sep 2009, at 19:56 , Templin, Fred L wrote:
>
>> I would go one step farther to say that any host sending
>> DF=1 packets larger than 1500 SHOULD use RFC 4821 or another
>> suitable PMTUD blackhole detection mechanism. And, failure
>> to observe the SHOULD may result in unpredictable behavior.
>
> I don't see the relationship with 1500 bytes. You never know when you may be
> communicating through a path that supports a smaller MTU than your own MTU,
> so discovering the path MTU by modulating transport segment sizes as per RFC
> 4821 is ALWAYS a good idea. However, this is a complex solution and it only
> addresses the case where the sender can easily manipulate packet sizes. For
> many non-TCP protocols that isn't the case, especially not if the packets
> are created by the application rather than the OS.
>
> Also note that using an MTU larger than 1500 is far less dangerous than
> using an MTU smaller than 1500. In the latter case, if there is a problem,
> the party with the non-1500-byte MTU is in no position to fix the problem:
> the too bigs are traveling towards the correspondent host, and are
> presumably filtered before they get there. And presumably increasing the MTU
> is infeasible, otherwise it wouldn't be so small in the first place. In the
> case of a larger than 1500-byte MTU, the operator is in a better position to
> remove stuff that blocks the too bigs, and it's always possible to reduce
> the MTU to 1500 as a last resort.

Not sure i have understood your point correctly. Do you mean that it
is more comfortable for operator to handle 1500+ bytes packets if they
exceed the limit?

I thought they were as dangerous if the ICMP error message could get through.

>
> Last but not least, the TCP MSS option hides a multitude of sins. Only when
> both ends have an MTU larger than the path MTU there may be problems.
>
> So I'm not worried about people using MTUs larger than 1500.
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>

From phdgang@gmail.com  Sat Sep 12 07:39:45 2009
Return-Path: <phdgang@gmail.com>
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 666063A67D2 for <behave@core3.amsl.com>; Sat, 12 Sep 2009 07:39:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.002
X-Spam-Level: 
X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_CHARSET_FARAWAY=2.45]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VQwqascSQtvt for <behave@core3.amsl.com>; Sat, 12 Sep 2009 07:39:44 -0700 (PDT)
Received: from mail-pz0-f172.google.com (mail-pz0-f172.google.com [209.85.222.172]) by core3.amsl.com (Postfix) with ESMTP id 41F013A68C1 for <behave@ietf.org>; Sat, 12 Sep 2009 07:39:44 -0700 (PDT)
Received: by pzk2 with SMTP id 2so1537461pzk.19 for <behave@ietf.org>; Sat, 12 Sep 2009 07:40:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=zAbxsHPNSVfnfaEXQCs4OFBIAQ6xMlRQ2R1UK15jDOo=; b=FUufwbmQHTrX8+GoboSaf6hychzBCZmkE6pxxeajoShQVE/jATVjNao/1MLIR1Jrmi N2V45yGjRSyVEVdkivBWPHFi3E0Bvy+zbq+IwCPgtBkezbkoKR8twRNy4t7y1QbgKkI1 NZKFJ6GNokL4NHcd5Wolt7CVBFhMO6Sfevcx0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=bEo5Ph8m3FrCmzHYkQLoFg1sFBZGui6xVzsNNreVnKcl6Nk73DQihzhl5iwRo3C2hT p5E0X3HLfifV75LvRwWOtbaU6FobwvWLBDFDmgDDpcyAp5pDcXKx/F07Rj+2En1eh9H8 7MpSoSzANQF6L1ChEXtHf3U7qwWxnzocdTX+4=
MIME-Version: 1.0
Received: by 10.115.81.24 with SMTP id i24mr7639400wal.194.1252766421289; Sat,  12 Sep 2009 07:40:21 -0700 (PDT)
In-Reply-To: <4AAAF852.1070505@gmail.com>
References: <36a593230908232300m45a10136wce25d01ef8bac439@mail.gmail.com> <4A9B7BA1.6000807@cernet.edu.cn> <36a593230908310651kd76a383j28b845bb07ebba55@mail.gmail.com> <4AA9880E.3000007@cernet.edu.cn> <36a593230909102302k5df1fcfsda08e38e0068bb38@mail.gmail.com> <4AAAD9D7.6080904@gmail.com> <E4561B14EE2A3E4E9D478EBFB5416E1B1CC5667B@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com> <4AAAF852.1070505@gmail.com>
Date: Sat, 12 Sep 2009 22:40:21 +0800
Message-ID: <36ba02b00909120740q74c2857bv7282d1d13ed5099@mail.gmail.com>
From: Chen Gang <phdgang@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=0016e64de622870c8f04736269e2
Cc: "denghui02@gmail.com" <denghui02@gmail.com>, "congxiao@cernet.edu.cn" <congxiao@cernet.edu.cn>, "behave@ietf.org" <behave@ietf.org>, liu dapeng <maxpassion@gmail.com>, Dave Thaler <dthaler@microsoft.com>, "kyin@cisco.com" <kyin@cisco.com>, bo zhou <zhouboyj@gmail.com>, Xing Li <xing@cernet.edu.cn>, "fred@cisco.com" <fred@cisco.com>
Subject: Re: [BEHAVE] Proposed text and comments for framework for IPv4/IPv6 translation
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/mail-archive/web/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>
X-List-Received-Date: Sat, 12 Sep 2009 14:39:45 -0000

--0016e64de622870c8f04736269e2
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: quoted-printable

For my understanding, current definitions of network and Internet are
distinguished from operational views, which may lack technical
considerations. We may need to find an technical dividing line to make that
more clear.
Could the NAT or any equipment be served as the distinction point?

Gang
2009/9/12 Brian E Carpenter <brian.e.carpenter@gmail.com>

> Hi Dave,
>
> Yes, and that fits well with my point, since presumably it's
> the operator of the "network" that will decide to configure
> a translator at the boundary.
>
> Of course, this can be confused if the network is a virtual
> one, overlaid on a physical network managed by someone else.
>
>    Brian
>
> On 2009-09-12 11:44, Dave Thaler wrote:
> > One distinction, which isn't always precise but is probably useful is
> > that "a network" is often managed by a common organization, whereas
> > the "Internet" is certainly not.  Hence a scenario with "a network"
> > implies the operators of that network can unilaterally do something
> > to enable that scenario.
> >
> > -Dave
> >
> > -----Original Message-----
> > From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On Behal=
f
> Of Brian E Carpenter
> > Sent: Friday, September 11, 2009 4:15 PM
> > To: bo zhou
> > Cc: denghui02@gmail.com; congxiao@cernet.edu.cn; behave@ietf.org; liu
> dapeng; kyin@cisco.com; Xing Li; fred@cisco.com; phdgang@gmail.com
> > Subject: Re: [BEHAVE] Proposed text and comments for framework for
> IPv4/IPv6 translation
> >
> > On 2009-09-11 18:02, bo zhou wrote:
> > ...
> >>>> [bo] Sorry, I cannot find any words in Sec.1.2 to define the
> difference
> >>>> between network and Internet.
> >>>>
> >>>  An IPv4 network:  A specific network that has an IPv4-only
> >>>     deployment.  This could be an enterprise's IPv4-only network or a=
n
> >>>     ISP's IPv4-only network.  The size of an IPv4 network is
> >>>     relatively small comparing to the global IPv4 Internet.
> >>>
> >>> The key words are: "A specific network" and "relatively small compari=
ng
> to
> >>> the global IPv4 Internet".
> >>       [bo] From aboved words, i have feeling that the difference betwe=
en
> >> network and Internet is SIZE only. I am not sure the size is the major
> thing
> >> to distinguish between the network and Internet, Is there any equipmen=
t,
> >> like NAT, inside the network can help us distinguish between network a=
nd
> >> Internet?
> >
> > I think the honest answer is no. The variations of how addressing realm=
s
> > are separated from each other are so great that I can't see any
> > mathematically precise way to define them.
> >
> > Operationally, we can perhaps define the point of separation as anywher=
e
> > that it is decided to put a translation device. But that doesn't help
> > anybody to decide where such a point is. I think the definition quoted
> > above is as good as it can be.
> >
> >     Brian
> > _______________________________________________
> > Behave mailing list
> > Behave@ietf.org
> > https://www.ietf.org/mailman/listinfo/behave
> >
> >
>



--=20
=B3=C2=B8=D5
phdgang@gmail.com

--0016e64de622870c8f04736269e2
Content-Type: text/html; charset=GB2312
Content-Transfer-Encoding: quoted-printable

<div>For my understanding, current definitions of network and Internet are =
distinguished from operational views, which may lack technical consideratio=
ns. We may need to find an technical dividing line to make that more clear.=
 </div>

<div>Could the NAT or any&nbsp;equipment&nbsp;be served&nbsp;as the distinc=
tion point? </div>
<div>&nbsp;</div>
<div>Gang<br></div>
<div class=3D"gmail_quote">2009/9/12 Brian E Carpenter <span dir=3D"ltr">&l=
t;<a href=3D"mailto:brian.e.carpenter@gmail.com">brian.e.carpenter@gmail.co=
m</a>&gt;</span><br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hi Dave,<br><br>Yes, and that fi=
ts well with my point, since presumably it&#39;s<br>the operator of the &qu=
ot;network&quot; that will decide to configure<br>
a translator at the boundary.<br><br>Of course, this can be confused if the=
 network is a virtual<br>one, overlaid on a physical network managed by som=
eone else.<br><font color=3D"#888888"><br>&nbsp; &nbsp;Brian<br></font>
<div>
<div></div>
<div class=3D"h5"><br>On 2009-09-12 11:44, Dave Thaler wrote:<br>&gt; One d=
istinction, which isn&#39;t always precise but is probably useful is<br>&gt=
; that &quot;a network&quot; is often managed by a common organization, whe=
reas<br>
&gt; the &quot;Internet&quot; is certainly not. &nbsp;Hence a scenario with=
 &quot;a network&quot;<br>&gt; implies the operators of that network can un=
ilaterally do something<br>&gt; to enable that scenario.<br>&gt;<br>&gt; -D=
ave<br>
&gt;<br>&gt; -----Original Message-----<br>&gt; From: <a href=3D"mailto:beh=
ave-bounces@ietf.org">behave-bounces@ietf.org</a> [mailto:<a href=3D"mailto=
:behave-bounces@ietf.org">behave-bounces@ietf.org</a>] On Behalf Of Brian E=
 Carpenter<br>
&gt; Sent: Friday, September 11, 2009 4:15 PM<br>&gt; To: bo zhou<br>&gt; C=
c: <a href=3D"mailto:denghui02@gmail.com">denghui02@gmail.com</a>; <a href=
=3D"mailto:congxiao@cernet.edu.cn">congxiao@cernet.edu.cn</a>; <a href=3D"m=
ailto:behave@ietf.org">behave@ietf.org</a>; liu dapeng; <a href=3D"mailto:k=
yin@cisco.com">kyin@cisco.com</a>; Xing Li; <a href=3D"mailto:fred@cisco.co=
m">fred@cisco.com</a>; <a href=3D"mailto:phdgang@gmail.com">phdgang@gmail.c=
om</a><br>
&gt; Subject: Re: [BEHAVE] Proposed text and comments for framework for IPv=
4/IPv6 translation<br>&gt;<br>&gt; On 2009-09-11 18:02, bo zhou wrote:<br>&=
gt; ...<br>&gt;&gt;&gt;&gt; [bo] Sorry, I cannot find any words in Sec.1.2 =
to define the difference<br>
&gt;&gt;&gt;&gt; between network and Internet.<br>&gt;&gt;&gt;&gt;<br>&gt;&=
gt;&gt; &nbsp;An IPv4 network: &nbsp;A specific network that has an IPv4-on=
ly<br>&gt;&gt;&gt; &nbsp; &nbsp; deployment. &nbsp;This could be an enterpr=
ise&#39;s IPv4-only network or an<br>
&gt;&gt;&gt; &nbsp; &nbsp; ISP&#39;s IPv4-only network. &nbsp;The size of a=
n IPv4 network is<br>&gt;&gt;&gt; &nbsp; &nbsp; relatively small comparing =
to the global IPv4 Internet.<br>&gt;&gt;&gt;<br>&gt;&gt;&gt; The key words =
are: &quot;A specific network&quot; and &quot;relatively small comparing to=
<br>
&gt;&gt;&gt; the global IPv4 Internet&quot;.<br>&gt;&gt; &nbsp; &nbsp; &nbs=
p; [bo] From aboved words, i have feeling that the difference between<br>&g=
t;&gt; network and Internet is SIZE only. I am not sure the size is the maj=
or thing<br>
&gt;&gt; to distinguish between the network and Internet, Is there any equi=
pment,<br>&gt;&gt; like NAT, inside the network can help us distinguish bet=
ween network and<br>&gt;&gt; Internet?<br>&gt;<br>&gt; I think the honest a=
nswer is no. The variations of how addressing realms<br>
&gt; are separated from each other are so great that I can&#39;t see any<br=
>&gt; mathematically precise way to define them.<br>&gt;<br>&gt; Operationa=
lly, we can perhaps define the point of separation as anywhere<br>&gt; that=
 it is decided to put a translation device. But that doesn&#39;t help<br>
&gt; anybody to decide where such a point is. I think the definition quoted=
<br>&gt; above is as good as it can be.<br>&gt;<br>&gt; &nbsp; &nbsp; Brian=
<br>&gt; _______________________________________________<br>&gt; Behave mai=
ling list<br>
&gt; <a href=3D"mailto:Behave@ietf.org">Behave@ietf.org</a><br>&gt; <a href=
=3D"https://www.ietf.org/mailman/listinfo/behave" target=3D"_blank">https:/=
/www.ietf.org/mailman/listinfo/behave</a><br>&gt;<br>&gt;<br></div></div></=
blockquote>
</div><br><br clear=3D"all">
<div></div><br>-- <br>=B3=C2=B8=D5<br><a href=3D"mailto:phdgang@gmail.com">=
phdgang@gmail.com</a><br>

--0016e64de622870c8f04736269e2--

From zhouboyj@gmail.com  Sun Sep 13 00:35:13 2009
Return-Path: <zhouboyj@gmail.com>
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 9DEED3A6810 for <behave@core3.amsl.com>; Sun, 13 Sep 2009 00:35:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.641
X-Spam-Level: 
X-Spam-Status: No, score=-0.641 tagged_above=-999 required=5 tests=[AWL=-0.493, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_CHARSET_FARAWAY=2.45]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZwS8ZctES9Z1 for <behave@core3.amsl.com>; Sun, 13 Sep 2009 00:35:12 -0700 (PDT)
Received: from mail-iw0-f183.google.com (mail-iw0-f183.google.com [209.85.223.183]) by core3.amsl.com (Postfix) with ESMTP id 5F5133A681F for <behave@ietf.org>; Sun, 13 Sep 2009 00:35:12 -0700 (PDT)
Received: by iwn13 with SMTP id 13so1045885iwn.6 for <behave@ietf.org>; Sun, 13 Sep 2009 00:35:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=is5cbauneE61WUy8mjXS11tcCuOWrvobxG/pswueq98=; b=Iqs0KF/FYPWsYqcezVy1u1GQziyl6wQyOBmRcG1mh1bmTwwyiGq3GbXjz9/HMC+yl5 F3efhUTg8S+A22LwZD/CKdWFT/t280UTxZl3dM0/1R50oiWV3NCUYHAyqf0Y4uq3mjfE oY3cXpPlv1zkUh0V1tvd8SpWYgH7kjTlPh37Q=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=npdgyfa6/6TMiM/0TbIN0EnLhm3Zc2P2pHSjS2S9wybvWkO4s/a5sTpQeSavmNG1Xg oEQL96tiOgHc4xmcfYg+qB+X5+oAlHZ3NLijq9mVQ++zoQngOqEKVKiNgpo3QM9Mlqpr FhEYJEaM8mmB5o3kTmIWKsXeBt1gcOt1WJWBg=
MIME-Version: 1.0
Received: by 10.231.124.22 with SMTP id s22mr10103316ibr.33.1252827350982;  Sun, 13 Sep 2009 00:35:50 -0700 (PDT)
In-Reply-To: <36ba02b00909120740q74c2857bv7282d1d13ed5099@mail.gmail.com>
References: <36a593230908232300m45a10136wce25d01ef8bac439@mail.gmail.com> <4A9B7BA1.6000807@cernet.edu.cn> <36a593230908310651kd76a383j28b845bb07ebba55@mail.gmail.com> <4AA9880E.3000007@cernet.edu.cn> <36a593230909102302k5df1fcfsda08e38e0068bb38@mail.gmail.com> <4AAAD9D7.6080904@gmail.com> <E4561B14EE2A3E4E9D478EBFB5416E1B1CC5667B@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com> <4AAAF852.1070505@gmail.com> <36ba02b00909120740q74c2857bv7282d1d13ed5099@mail.gmail.com>
Date: Sun, 13 Sep 2009 15:35:50 +0800
Message-ID: <36a593230909130035l5383e81fnc1e08b357db8de95@mail.gmail.com>
From: bo zhou <zhouboyj@gmail.com>
To: Chen Gang <phdgang@gmail.com>
Content-Type: multipart/alternative; boundary=0016e6468fa838749d04737099b4
Cc: "denghui02@gmail.com" <denghui02@gmail.com>, "congxiao@cernet.edu.cn" <congxiao@cernet.edu.cn>, "behave@ietf.org" <behave@ietf.org>, liu dapeng <maxpassion@gmail.com>, Dave Thaler <dthaler@microsoft.com>, "kyin@cisco.com" <kyin@cisco.com>, Xing Li <xing@cernet.edu.cn>, "fred@cisco.com" <fred@cisco.com>
Subject: Re: [BEHAVE] Proposed text and comments for framework for IPv4/IPv6 translation
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/mail-archive/web/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>
X-List-Received-Date: Sun, 13 Sep 2009 07:35:13 -0000

--0016e6468fa838749d04737099b4
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: quoted-printable

NAT44 can be the distinction point for IPv4 network and IPv4 Internet.
But how about the distinction point for IPv6 network and IPv6 Internet,
shall we introduce NAT66?

regards,

Bo Zhou

2009/9/12 Chen Gang <phdgang@gmail.com>

> For my understanding, current definitions of network and Internet are
> distinguished from operational views, which may lack technical
> considerations. We may need to find an technical dividing line to make th=
at
> more clear.
> Could the NAT or any equipment be served as the distinction point?
>
> Gang
> 2009/9/12 Brian E Carpenter <brian.e.carpenter@gmail.com>
>
> Hi Dave,
>>
>> Yes, and that fits well with my point, since presumably it's
>> the operator of the "network" that will decide to configure
>> a translator at the boundary.
>>
>> Of course, this can be confused if the network is a virtual
>> one, overlaid on a physical network managed by someone else.
>>
>>    Brian
>>
>> On 2009-09-12 11:44, Dave Thaler wrote:
>> > One distinction, which isn't always precise but is probably useful is
>> > that "a network" is often managed by a common organization, whereas
>> > the "Internet" is certainly not.  Hence a scenario with "a network"
>> > implies the operators of that network can unilaterally do something
>> > to enable that scenario.
>> >
>> > -Dave
>> >
>> > -----Original Message-----
>> > From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On
>> Behalf Of Brian E Carpenter
>> > Sent: Friday, September 11, 2009 4:15 PM
>> > To: bo zhou
>> > Cc: denghui02@gmail.com; congxiao@cernet.edu.cn; behave@ietf.org; liu
>> dapeng; kyin@cisco.com; Xing Li; fred@cisco.com; phdgang@gmail.com
>> > Subject: Re: [BEHAVE] Proposed text and comments for framework for
>> IPv4/IPv6 translation
>> >
>> > On 2009-09-11 18:02, bo zhou wrote:
>> > ...
>> >>>> [bo] Sorry, I cannot find any words in Sec.1.2 to define the
>> difference
>> >>>> between network and Internet.
>> >>>>
>> >>>  An IPv4 network:  A specific network that has an IPv4-only
>> >>>     deployment.  This could be an enterprise's IPv4-only network or =
an
>> >>>     ISP's IPv4-only network.  The size of an IPv4 network is
>> >>>     relatively small comparing to the global IPv4 Internet.
>> >>>
>> >>> The key words are: "A specific network" and "relatively small
>> comparing to
>> >>> the global IPv4 Internet".
>> >>       [bo] From aboved words, i have feeling that the difference
>> between
>> >> network and Internet is SIZE only. I am not sure the size is the majo=
r
>> thing
>> >> to distinguish between the network and Internet, Is there any
>> equipment,
>> >> like NAT, inside the network can help us distinguish between network
>> and
>> >> Internet?
>> >
>> > I think the honest answer is no. The variations of how addressing real=
ms
>> > are separated from each other are so great that I can't see any
>> > mathematically precise way to define them.
>> >
>> > Operationally, we can perhaps define the point of separation as anywhe=
re
>> > that it is decided to put a translation device. But that doesn't help
>> > anybody to decide where such a point is. I think the definition quoted
>> > above is as good as it can be.
>> >
>> >     Brian
>> > _______________________________________________
>> > Behave mailing list
>> > Behave@ietf.org
>> > https://www.ietf.org/mailman/listinfo/behave
>> >
>> >
>>
>
>
>
> --
> =B3=C2=B8=D5
> phdgang@gmail.com
>



--=20
Regards,

Bo Zhou
China Mobile

--0016e6468fa838749d04737099b4
Content-Type: text/html; charset=GB2312
Content-Transfer-Encoding: quoted-printable

<div>NAT44 can be the distinction point for IPv4 network and IPv4 Internet.=
</div>
<div>But how about the distinction point for IPv6 network and IPv6 Internet=
, shall we introduce NAT66?</div>
<div>&nbsp;</div>
<div>regards,</div>
<div>&nbsp;</div>
<div>Bo Zhou<br><br></div>
<div class=3D"gmail_quote">2009/9/12 Chen Gang <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:phdgang@gmail.com">phdgang@gmail.com</a>&gt;</span><br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>For my understanding, current definitions of network and Internet are =
distinguished from operational views, which may lack technical consideratio=
ns. We may need to find an technical dividing line to make that more clear.=
 </div>

<div>Could the NAT or any&nbsp;equipment&nbsp;be served&nbsp;as the distinc=
tion point? </div>
<div>&nbsp;</div>
<div>Gang<br></div>
<div class=3D"gmail_quote">2009/9/12 Brian E Carpenter <span dir=3D"ltr">&l=
t;<a href=3D"mailto:brian.e.carpenter@gmail.com" target=3D"_blank">brian.e.=
carpenter@gmail.com</a>&gt;</span>=20
<div>
<div></div>
<div class=3D"h5"><br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hi Dave,<br><br>Yes, and that fi=
ts well with my point, since presumably it&#39;s<br>the operator of the &qu=
ot;network&quot; that will decide to configure<br>
a translator at the boundary.<br><br>Of course, this can be confused if the=
 network is a virtual<br>one, overlaid on a physical network managed by som=
eone else.<br><font color=3D"#888888"><br>&nbsp; &nbsp;Brian<br></font>
<div>
<div></div>
<div><br>On 2009-09-12 11:44, Dave Thaler wrote:<br>&gt; One distinction, w=
hich isn&#39;t always precise but is probably useful is<br>&gt; that &quot;=
a network&quot; is often managed by a common organization, whereas<br>
&gt; the &quot;Internet&quot; is certainly not. &nbsp;Hence a scenario with=
 &quot;a network&quot;<br>&gt; implies the operators of that network can un=
ilaterally do something<br>&gt; to enable that scenario.<br>&gt;<br>&gt; -D=
ave<br>
&gt;<br>&gt; -----Original Message-----<br>&gt; From: <a href=3D"mailto:beh=
ave-bounces@ietf.org" target=3D"_blank">behave-bounces@ietf.org</a> [mailto=
:<a href=3D"mailto:behave-bounces@ietf.org" target=3D"_blank">behave-bounce=
s@ietf.org</a>] On Behalf Of Brian E Carpenter<br>
&gt; Sent: Friday, September 11, 2009 4:15 PM<br>&gt; To: bo zhou<br>&gt; C=
c: <a href=3D"mailto:denghui02@gmail.com" target=3D"_blank">denghui02@gmail=
.com</a>; <a href=3D"mailto:congxiao@cernet.edu.cn" target=3D"_blank">congx=
iao@cernet.edu.cn</a>; <a href=3D"mailto:behave@ietf.org" target=3D"_blank"=
>behave@ietf.org</a>; liu dapeng; <a href=3D"mailto:kyin@cisco.com" target=
=3D"_blank">kyin@cisco.com</a>; Xing Li; <a href=3D"mailto:fred@cisco.com" =
target=3D"_blank">fred@cisco.com</a>; <a href=3D"mailto:phdgang@gmail.com" =
target=3D"_blank">phdgang@gmail.com</a><br>
&gt; Subject: Re: [BEHAVE] Proposed text and comments for framework for IPv=
4/IPv6 translation<br>&gt;<br>&gt; On 2009-09-11 18:02, bo zhou wrote:<br>&=
gt; ...<br>&gt;&gt;&gt;&gt; [bo] Sorry, I cannot find any words in Sec.1.2 =
to define the difference<br>
&gt;&gt;&gt;&gt; between network and Internet.<br>&gt;&gt;&gt;&gt;<br>&gt;&=
gt;&gt; &nbsp;An IPv4 network: &nbsp;A specific network that has an IPv4-on=
ly<br>&gt;&gt;&gt; &nbsp; &nbsp; deployment. &nbsp;This could be an enterpr=
ise&#39;s IPv4-only network or an<br>
&gt;&gt;&gt; &nbsp; &nbsp; ISP&#39;s IPv4-only network. &nbsp;The size of a=
n IPv4 network is<br>&gt;&gt;&gt; &nbsp; &nbsp; relatively small comparing =
to the global IPv4 Internet.<br>&gt;&gt;&gt;<br>&gt;&gt;&gt; The key words =
are: &quot;A specific network&quot; and &quot;relatively small comparing to=
<br>
&gt;&gt;&gt; the global IPv4 Internet&quot;.<br>&gt;&gt; &nbsp; &nbsp; &nbs=
p; [bo] From aboved words, i have feeling that the difference between<br>&g=
t;&gt; network and Internet is SIZE only. I am not sure the size is the maj=
or thing<br>
&gt;&gt; to distinguish between the network and Internet, Is there any equi=
pment,<br>&gt;&gt; like NAT, inside the network can help us distinguish bet=
ween network and<br>&gt;&gt; Internet?<br>&gt;<br>&gt; I think the honest a=
nswer is no. The variations of how addressing realms<br>
&gt; are separated from each other are so great that I can&#39;t see any<br=
>&gt; mathematically precise way to define them.<br>&gt;<br>&gt; Operationa=
lly, we can perhaps define the point of separation as anywhere<br>&gt; that=
 it is decided to put a translation device. But that doesn&#39;t help<br>
&gt; anybody to decide where such a point is. I think the definition quoted=
<br>&gt; above is as good as it can be.<br>&gt;<br>&gt; &nbsp; &nbsp; Brian=
<br>&gt; _______________________________________________<br>&gt; Behave mai=
ling list<br>
&gt; <a href=3D"mailto:Behave@ietf.org" target=3D"_blank">Behave@ietf.org</=
a><br>&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/behave" target=
=3D"_blank">https://www.ietf.org/mailman/listinfo/behave</a><br>&gt;<br>&gt=
;<br>
</div></div></blockquote></div></div></div><font color=3D"#888888"><br><br =
clear=3D"all">
<div></div><br>-- <br>=B3=C2=B8=D5<br><a href=3D"mailto:phdgang@gmail.com" =
target=3D"_blank">phdgang@gmail.com</a><br></font></blockquote></div><br><b=
r clear=3D"all">
<div></div><br>-- <br>Regards,<br><br>Bo Zhou<br>China Mobile<br>

--0016e6468fa838749d04737099b4--

From joelja@bogus.com  Sun Sep 13 00:55:57 2009
Return-Path: <joelja@bogus.com>
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 B47D63A6805 for <behave@core3.amsl.com>; Sun, 13 Sep 2009 00:55:57 -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 jw0TS8vI1Oyv for <behave@core3.amsl.com>; Sun, 13 Sep 2009 00:55:56 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by core3.amsl.com (Postfix) with ESMTP id 45E363A679F for <behave@ietf.org>; Sun, 13 Sep 2009 00:55:56 -0700 (PDT)
Received: from [192.168.1.131] (c-98-234-104-156.hsd1.ca.comcast.net [98.234.104.156]) (authenticated bits=0) by nagasaki.bogus.com (8.14.3/8.14.3) with ESMTP id n8D7uO3T039382 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 13 Sep 2009 07:56:25 GMT (envelope-from joelja@bogus.com)
Message-ID: <4AACA59A.9060904@bogus.com>
Date: Sun, 13 Sep 2009 00:56:10 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: bo zhou <zhouboyj@gmail.com>
References: <36a593230908232300m45a10136wce25d01ef8bac439@mail.gmail.com>	<4A9B7BA1.6000807@cernet.edu.cn>	<36a593230908310651kd76a383j28b845bb07ebba55@mail.gmail.com>	<4AA9880E.3000007@cernet.edu.cn>	<36a593230909102302k5df1fcfsda08e38e0068bb38@mail.gmail.com>	<4AAAD9D7.6080904@gmail.com>	<E4561B14EE2A3E4E9D478EBFB5416E1B1CC5667B@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com>	<4AAAF852.1070505@gmail.com>	<36ba02b00909120740q74c2857bv7282d1d13ed5099@mail.gmail.com> <36a593230909130035l5383e81fnc1e08b357db8de95@mail.gmail.com>
In-Reply-To: <36a593230909130035l5383e81fnc1e08b357db8de95@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.2 (nagasaki.bogus.com [147.28.0.81]); Sun, 13 Sep 2009 07:56:25 +0000 (UTC)
Cc: "denghui02@gmail.com" <denghui02@gmail.com>, "congxiao@cernet.edu.cn" <congxiao@cernet.edu.cn>, "behave@ietf.org" <behave@ietf.org>, liu dapeng <maxpassion@gmail.com>, Dave Thaler <dthaler@microsoft.com>, Chen Gang <phdgang@gmail.com>, Xing Li <xing@cernet.edu.cn>, "fred@cisco.com" <fred@cisco.com>, "kyin@cisco.com" <kyin@cisco.com>
Subject: Re: [BEHAVE] Proposed text and comments for framework for IPv4/IPv6 translation
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/mail-archive/web/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>
X-List-Received-Date: Sun, 13 Sep 2009 07:55:57 -0000

One would think that the terms:

"intranet"

"A network" (Singluar0

"an internet(work)"

and

"the Internet"

Would be sufficiently unambiguous that we would not have to resort to
wordsmithing or the imposition of NAT in the definition in order to have
meaning.

And no I don't distinguish between internal connectivity and external on
the basis of the existence or lack thereof of a nat and neither should you.

bo zhou wrote:
> NAT44 can be the distinction point for IPv4 network and IPv4 Internet.
> But how about the distinction point for IPv6 network and IPv6 Internet,
> shall we introduce NAT66?
>  
> regards,
>  
> Bo Zhou
> 
> 2009/9/12 Chen Gang <phdgang@gmail.com <mailto:phdgang@gmail.com>>
> 
>     For my understanding, current definitions of network and Internet
>     are distinguished from operational views, which may lack technical
>     considerations. We may need to find an technical dividing line to
>     make that more clear.
>     Could the NAT or any equipment be served as the distinction point?
>      
>     Gang
>     2009/9/12 Brian E Carpenter <brian.e.carpenter@gmail.com
>     <mailto:brian.e.carpenter@gmail.com>>
> 
>         Hi Dave,
> 
>         Yes, and that fits well with my point, since presumably it's
>         the operator of the "network" that will decide to configure
>         a translator at the boundary.
> 
>         Of course, this can be confused if the network is a virtual
>         one, overlaid on a physical network managed by someone else.
> 
>            Brian
> 
>         On 2009-09-12 11:44, Dave Thaler wrote:
>         > One distinction, which isn't always precise but is probably
>         useful is
>         > that "a network" is often managed by a common organization,
>         whereas
>         > the "Internet" is certainly not.  Hence a scenario with "a
>         network"
>         > implies the operators of that network can unilaterally do
>         something
>         > to enable that scenario.
>         >
>         > -Dave
>         >
>         > -----Original Message-----
>         > From: behave-bounces@ietf.org <mailto:behave-bounces@ietf.org>
>         [mailto:behave-bounces@ietf.org
>         <mailto:behave-bounces@ietf.org>] On Behalf Of Brian E Carpenter
>         > Sent: Friday, September 11, 2009 4:15 PM
>         > To: bo zhou
>         > Cc: denghui02@gmail.com <mailto:denghui02@gmail.com>;
>         congxiao@cernet.edu.cn <mailto:congxiao@cernet.edu.cn>;
>         behave@ietf.org <mailto:behave@ietf.org>; liu dapeng;
>         kyin@cisco.com <mailto:kyin@cisco.com>; Xing Li; fred@cisco.com
>         <mailto:fred@cisco.com>; phdgang@gmail.com
>         <mailto:phdgang@gmail.com>
>         > Subject: Re: [BEHAVE] Proposed text and comments for framework
>         for IPv4/IPv6 translation
>         >
>         > On 2009-09-11 18:02, bo zhou wrote:
>         > ...
>         >>>> [bo] Sorry, I cannot find any words in Sec.1.2 to define
>         the difference
>         >>>> between network and Internet.
>         >>>>
>         >>>  An IPv4 network:  A specific network that has an IPv4-only
>         >>>     deployment.  This could be an enterprise's IPv4-only
>         network or an
>         >>>     ISP's IPv4-only network.  The size of an IPv4 network is
>         >>>     relatively small comparing to the global IPv4 Internet.
>         >>>
>         >>> The key words are: "A specific network" and "relatively
>         small comparing to
>         >>> the global IPv4 Internet".
>         >>       [bo] From aboved words, i have feeling that the
>         difference between
>         >> network and Internet is SIZE only. I am not sure the size is
>         the major thing
>         >> to distinguish between the network and Internet, Is there any
>         equipment,
>         >> like NAT, inside the network can help us distinguish between
>         network and
>         >> Internet?
>         >
>         > I think the honest answer is no. The variations of how
>         addressing realms
>         > are separated from each other are so great that I can't see any
>         > mathematically precise way to define them.
>         >
>         > Operationally, we can perhaps define the point of separation
>         as anywhere
>         > that it is decided to put a translation device. But that
>         doesn't help
>         > anybody to decide where such a point is. I think the
>         definition quoted
>         > above is as good as it can be.
>         >
>         >     Brian
>         > _______________________________________________
>         > Behave mailing list
>         > Behave@ietf.org <mailto:Behave@ietf.org>
>         > https://www.ietf.org/mailman/listinfo/behave
>         >
>         >
> 
> 
> 
> 
>     -- 
>     陈刚
>     phdgang@gmail.com <mailto:phdgang@gmail.com>
> 
> 
> 
> 
> -- 
> Regards,
> 
> Bo Zhou
> China Mobile
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave


From iljitsch@muada.com  Sun Sep 13 15:05:24 2009
Return-Path: <iljitsch@muada.com>
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 091093A6947 for <behave@core3.amsl.com>; Sun, 13 Sep 2009 15:05:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.219
X-Spam-Level: 
X-Spam-Status: No, score=-4.219 tagged_above=-999 required=5 tests=[AWL=-1.620, 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 WpKap7slchgb for <behave@core3.amsl.com>; Sun, 13 Sep 2009 15:05:23 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2]) by core3.amsl.com (Postfix) with ESMTP id E73633A68E2 for <behave@ietf.org>; Sun, 13 Sep 2009 15:05:22 -0700 (PDT)
Received: from [192.168.2.11] (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 n8DM5pMB068608 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 14 Sep 2009 00:05:52 +0200 (CEST) (envelope-from iljitsch@muada.com)
Mime-Version: 1.0 (Apple Message framework v1076)
Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <a7c8d0a30909112304v6023d610n883220b8843582fd@mail.gmail.com>
Date: Mon, 14 Sep 2009 00:05:48 +0200
Content-Transfer-Encoding: 7bit
Message-Id: <1491EEEF-ED8E-46B7-9FDD-20DD305A0399@muada.com>
References: <A09ECC61-E8CB-430B-A891-53902BEA083D@muada.com> <a7c8d0a30909100630y32e30024s68d17487612ebd37@mail.gmail.com> <74AA3C18-B735-4020-9FEB-B1ABBED1ACFF@muada.com> <39C363776A4E8C4A94691D2BD9D1C9A1066249A1@XCH-NW-7V2.nw.nos.boeing.com> <D42C5920-C7D5-40E6-99A4-A26DE139746A@muada.com> <a7c8d0a30909112304v6023d610n883220b8843582fd@mail.gmail.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, Zhen Cao <caozhenpku@gmail.com>
X-Mailer: Apple Mail (2.1076)
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] 64 MTU and fragmentation handling
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/mail-archive/web/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>
X-List-Received-Date: Sun, 13 Sep 2009 22:05:24 -0000

On 11 Sep 2009, at 23:22 , Templin, Fred L wrote:

> So, RFC4821 does have something to say about implementation
> in packetization layers other than TCP.

Right. It's not necessarily impossible, but considering we don't have  
it for TCP yet...

> Not sure I get the distinction you are making,

If you use a larger-than-mainstream MTU then the too bigs are sent to  
you for the packets you send so you can debug them. If you use a  
smaller-than-mainstream MTU the too bigs go from some place in the  
middle to the other end, there's nothing you can see or do in that case.

>> Last but not least, the TCP MSS option hides a multitude of sins.  
>> Only
>> when both ends have an MTU larger than the path MTU there may be
>> problems.

> I put MSS clamping in the "band aid solution" category. When
> it works, it works great, but IMHO we will begin to see more
> and more non-TCP communications that can't use it.

No, I wasn't talking about clamping. Although this is a useful hack in  
a PPPoE box in today's IPv4 internet, implementing MSS clamping in  
pretty much all the routers across the internet isn't feasible and  
also extremely ugly. The point is that when you talk to someone with a  
1500-byte MTU you will be sending 1500-byte (or smaller) TCP packets  
even without clamping.

On 12 Sep 2009, at 8:04 , Zhen Cao wrote:

> I guess you are saying that the black hole problem not only targets
> translation. But translation, especially v4-to-v6 which lengthens the
> packet, makes this problem worse. So translation algorithm should take
> special care of this problem?

In an earlier version of my text I took this into account, but since  
then I have changed my mind: I don't think it's worth the trouble to  
do this. The common situation will be for all the systems involved to  
have 1500-byte MTUs. In that case, the IPv6 host will advertise a 1440- 
byte MSS (1500 - 40 bytes IPv6 - 20 bytes TCP) so the IPv4 host will  
send TCP packets of 1480 bytes (1440 + 20 bytes IPv4 + 20 bytes IPv4)  
which the translator then translates into 1500-byte IPv6 packets.

From ietfdbh@comcast.net  Sun Sep 13 17:27:49 2009
Return-Path: <ietfdbh@comcast.net>
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 759BA3A694A for <behave@core3.amsl.com>; Sun, 13 Sep 2009 17:27:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.041
X-Spam-Level: 
X-Spam-Status: No, score=-2.041 tagged_above=-999 required=5 tests=[AWL=0.558,  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 zhcQU1oPR-DQ for <behave@core3.amsl.com>; Sun, 13 Sep 2009 17:27:48 -0700 (PDT)
Received: from QMTA01.westchester.pa.mail.comcast.net (qmta01.westchester.pa.mail.comcast.net [76.96.62.16]) by core3.amsl.com (Postfix) with ESMTP id 344773A691B for <behave@ietf.org>; Sun, 13 Sep 2009 17:27:47 -0700 (PDT)
Received: from OMTA12.westchester.pa.mail.comcast.net ([76.96.62.44]) by QMTA01.westchester.pa.mail.comcast.net with comcast id gQ8E1c0040xGWP851QUXhr; Mon, 14 Sep 2009 00:28:31 +0000
Received: from Harrington73653 ([24.147.240.21]) by OMTA12.westchester.pa.mail.comcast.net with comcast id gQUW1c00B0UQ6dC3YQUWwe; Mon, 14 Sep 2009 00:28:31 +0000
From: "David Harrington" <ietfdbh@comcast.net>
To: "'joel jaeggli'" <joelja@bogus.com>, "'bo zhou'" <zhouboyj@gmail.com>
References: <36a593230908232300m45a10136wce25d01ef8bac439@mail.gmail.com>	<4A9B7BA1.6000807@cernet.edu.cn>	<36a593230908310651kd76a383j28b845bb07ebba55@mail.gmail.com>	<4AA9880E.3000007@cernet.edu.cn>	<36a593230909102302k5df1fcfsda08e38e0068bb38@mail.gmail.com>	<4AAAD9D7.6080904@gmail.com>	<E4561B14EE2A3E4E9D478EBFB5416E1B1CC5667B@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com>	<4AAAF852.1070505@gmail.com>	<36ba02b00909120740q74c2857bv7282d1d13ed5099@mail.gmail.com><36a593230909130035l5383e81fnc1e08b357db8de95@mail.gmail.com> <4AACA59A.9060904@bogus.com>
Date: Sun, 13 Sep 2009 20:28:28 -0400
Message-ID: <02d701ca34d2$48801310$0600a8c0@china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <4AACA59A.9060904@bogus.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Thread-Index: Aco0R7u07PAqHEShTmS9VSZAPeioCQAioQ+A
Cc: denghui02@gmail.com, congxiao@cernet.edu.cn, behave@ietf.org, 'liu dapeng' <maxpassion@gmail.com>, 'Dave Thaler' <dthaler@microsoft.com>, 'Chen Gang' <phdgang@gmail.com>, 'Xing Li' <xing@cernet.edu.cn>, fred@cisco.com, kyin@cisco.com
Subject: Re: [BEHAVE] Proposed text and comments for framework for IPv4/IPv6 translation
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/mail-archive/web/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>
X-List-Received-Date: Mon, 14 Sep 2009 00:27:49 -0000

+1

dbh 

> -----Original Message-----
> From: behave-bounces@ietf.org 
> [mailto:behave-bounces@ietf.org] On Behalf Of joel jaeggli
> Sent: Sunday, September 13, 2009 3:56 AM
> To: bo zhou
> Cc: denghui02@gmail.com; congxiao@cernet.edu.cn; 
> behave@ietf.org; liu dapeng; Dave Thaler; Chen Gang; Xing Li; 
> fred@cisco.com; kyin@cisco.com
> Subject: Re: [BEHAVE] Proposed text and comments for 
> framework for IPv4/IPv6 translation
> 
> One would think that the terms:
> 
> "intranet"
> 
> "A network" (Singluar0
> 
> "an internet(work)"
> 
> and
> 
> "the Internet"
> 
> Would be sufficiently unambiguous that we would not have to resort
to
> wordsmithing or the imposition of NAT in the definition in 
> order to have
> meaning.
> 
> And no I don't distinguish between internal connectivity and 
> external on
> the basis of the existence or lack thereof of a nat and 
> neither should you.
> 
> bo zhou wrote:
> > NAT44 can be the distinction point for IPv4 network and 
> IPv4 Internet.
> > But how about the distinction point for IPv6 network and 
> IPv6 Internet,
> > shall we introduce NAT66?
> >  
> > regards,
> >  
> > Bo Zhou
> > 
> > 2009/9/12 Chen Gang <phdgang@gmail.com <mailto:phdgang@gmail.com>>
> > 
> >     For my understanding, current definitions of network 
> and Internet
> >     are distinguished from operational views, which may 
> lack technical
> >     considerations. We may need to find an technical 
> dividing line to
> >     make that more clear.
> >     Could the NAT or any equipment be served as the 
> distinction point?
> >      
> >     Gang
> >     2009/9/12 Brian E Carpenter <brian.e.carpenter@gmail.com
> >     <mailto:brian.e.carpenter@gmail.com>>
> > 
> >         Hi Dave,
> > 
> >         Yes, and that fits well with my point, since presumably
it's
> >         the operator of the "network" that will decide to
configure
> >         a translator at the boundary.
> > 
> >         Of course, this can be confused if the network is a
virtual
> >         one, overlaid on a physical network managed by someone
else.
> > 
> >            Brian
> > 
> >         On 2009-09-12 11:44, Dave Thaler wrote:
> >         > One distinction, which isn't always precise but 
> is probably
> >         useful is
> >         > that "a network" is often managed by a common 
> organization,
> >         whereas
> >         > the "Internet" is certainly not.  Hence a scenario with
"a
> >         network"
> >         > implies the operators of that network can unilaterally
do
> >         something
> >         > to enable that scenario.
> >         >
> >         > -Dave
> >         >
> >         > -----Original Message-----
> >         > From: behave-bounces@ietf.org 
> <mailto:behave-bounces@ietf.org>
> >         [mailto:behave-bounces@ietf.org
> >         <mailto:behave-bounces@ietf.org>] On Behalf Of 
> Brian E Carpenter
> >         > Sent: Friday, September 11, 2009 4:15 PM
> >         > To: bo zhou
> >         > Cc: denghui02@gmail.com <mailto:denghui02@gmail.com>;
> >         congxiao@cernet.edu.cn <mailto:congxiao@cernet.edu.cn>;
> >         behave@ietf.org <mailto:behave@ietf.org>; liu dapeng;
> >         kyin@cisco.com <mailto:kyin@cisco.com>; Xing Li; 
> fred@cisco.com
> >         <mailto:fred@cisco.com>; phdgang@gmail.com
> >         <mailto:phdgang@gmail.com>
> >         > Subject: Re: [BEHAVE] Proposed text and comments 
> for framework
> >         for IPv4/IPv6 translation
> >         >
> >         > On 2009-09-11 18:02, bo zhou wrote:
> >         > ...
> >         >>>> [bo] Sorry, I cannot find any words in Sec.1.2 
> to define
> >         the difference
> >         >>>> between network and Internet.
> >         >>>>
> >         >>>  An IPv4 network:  A specific network that has 
> an IPv4-only
> >         >>>     deployment.  This could be an enterprise's
IPv4-only
> >         network or an
> >         >>>     ISP's IPv4-only network.  The size of an 
> IPv4 network is
> >         >>>     relatively small comparing to the global 
> IPv4 Internet.
> >         >>>
> >         >>> The key words are: "A specific network" and
"relatively
> >         small comparing to
> >         >>> the global IPv4 Internet".
> >         >>       [bo] From aboved words, i have feeling that the
> >         difference between
> >         >> network and Internet is SIZE only. I am not sure 
> the size is
> >         the major thing
> >         >> to distinguish between the network and Internet, 
> Is there any
> >         equipment,
> >         >> like NAT, inside the network can help us 
> distinguish between
> >         network and
> >         >> Internet?
> >         >
> >         > I think the honest answer is no. The variations of how
> >         addressing realms
> >         > are separated from each other are so great that I 
> can't see any
> >         > mathematically precise way to define them.
> >         >
> >         > Operationally, we can perhaps define the point of 
> separation
> >         as anywhere
> >         > that it is decided to put a translation device. But that
> >         doesn't help
> >         > anybody to decide where such a point is. I think the
> >         definition quoted
> >         > above is as good as it can be.
> >         >
> >         >     Brian
> >         > _______________________________________________
> >         > Behave mailing list
> >         > Behave@ietf.org <mailto:Behave@ietf.org>
> >         > https://www.ietf.org/mailman/listinfo/behave
> >         >
> >         >
> > 
> > 
> > 
> > 
> >     -- 
> >     ??
> >     phdgang@gmail.com <mailto:phdgang@gmail.com>
> > 
> > 
> > 
> > 
> > -- 
> > Regards,
> > 
> > Bo Zhou
> > China Mobile
> > 
> > 
> > 
> --------------------------------------------------------------
> ----------
> > 
> > _______________________________________________
> > 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 caozhenpku@gmail.com  Sun Sep 13 21:05:35 2009
Return-Path: <caozhenpku@gmail.com>
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 8A2E23A6861 for <behave@core3.amsl.com>; Sun, 13 Sep 2009 21:05:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.452
X-Spam-Level: 
X-Spam-Status: No, score=-2.452 tagged_above=-999 required=5 tests=[AWL=0.147,  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 sGXoWpvRr2oI for <behave@core3.amsl.com>; Sun, 13 Sep 2009 21:05:34 -0700 (PDT)
Received: from mail-vw0-f201.google.com (mail-vw0-f201.google.com [209.85.212.201]) by core3.amsl.com (Postfix) with ESMTP id 940813A67EC for <behave@ietf.org>; Sun, 13 Sep 2009 21:05:34 -0700 (PDT)
Received: by vws39 with SMTP id 39so1645117vws.29 for <behave@ietf.org>; Sun, 13 Sep 2009 21:06:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=gP22vt3Z+m3IAY92yQPVlfdtPyU3lcgDEk9W7/X8Ins=; b=vKSEactA/aeuHcS08qJ+PDAgDs20jdlvglfqKHv5BcU7xwn7qFtZYqXhohQIAoBHf4 z6mIAjYpFnpY9K5SGV65OZSNwC42mFE4kqlcqBXnD+71JXoWxDq/YxH/OQO5VTSPuIqz h3zT6gB2ZEUUuZIHdVjE8dSVSPCTVOQQhOIL4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=XQvaCf5xdWnc0mm9hMXhD1Zug4KjfigG7R0a6wQrUMfNxM431rLy3J9PZhlofGG7wN b5wwJ4tIIWIT07oV3C98C9MOnYch1g0B8bovJy6Rd/81g4GInVsmyQ+q7Di809HoVSno JtCYot9zguCZ+FpXiRqdXpmAmVfW+SlrpmVRo=
MIME-Version: 1.0
Received: by 10.220.101.105 with SMTP id b41mr7428351vco.59.1252901173984;  Sun, 13 Sep 2009 21:06:13 -0700 (PDT)
In-Reply-To: <1491EEEF-ED8E-46B7-9FDD-20DD305A0399@muada.com>
References: <A09ECC61-E8CB-430B-A891-53902BEA083D@muada.com> <a7c8d0a30909100630y32e30024s68d17487612ebd37@mail.gmail.com> <74AA3C18-B735-4020-9FEB-B1ABBED1ACFF@muada.com> <39C363776A4E8C4A94691D2BD9D1C9A1066249A1@XCH-NW-7V2.nw.nos.boeing.com> <D42C5920-C7D5-40E6-99A4-A26DE139746A@muada.com> <a7c8d0a30909112304v6023d610n883220b8843582fd@mail.gmail.com> <1491EEEF-ED8E-46B7-9FDD-20DD305A0399@muada.com>
Date: Mon, 14 Sep 2009 12:06:13 +0800
Message-ID: <a7c8d0a30909132106i4dca4867kcfb3baa706bcb022@mail.gmail.com>
From: Zhen Cao <caozhenpku@gmail.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "Templin, Fred L" <Fred.L.Templin@boeing.com>, Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] 64 MTU and fragmentation handling
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/mail-archive/web/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>
X-List-Received-Date: Mon, 14 Sep 2009 04:05:35 -0000

On Mon, Sep 14, 2009 at 6:05 AM, Iljitsch van Beijnum
<iljitsch@muada.com> wrote:
> On 11 Sep 2009, at 23:22 , Templin, Fred L wrote:
>
>> So, RFC4821 does have something to say about implementation
>> in packetization layers other than TCP.
>
> Right. It's not necessarily impossible, but considering we don't have it for
> TCP yet...
>
>> Not sure I get the distinction you are making,
>
> If you use a larger-than-mainstream MTU then the too bigs are sent to you
> for the packets you send so you can debug them. If you use a
> smaller-than-mainstream MTU the too bigs go from some place in the middle to
> the other end, there's nothing you can see or do in that case.
>
>>> Last but not least, the TCP MSS option hides a multitude of sins. Only
>>> when both ends have an MTU larger than the path MTU there may be
>>> problems.
>
>> I put MSS clamping in the "band aid solution" category. When
>> it works, it works great, but IMHO we will begin to see more
>> and more non-TCP communications that can't use it.
>
> No, I wasn't talking about clamping. Although this is a useful hack in a
> PPPoE box in today's IPv4 internet, implementing MSS clamping in pretty much
> all the routers across the internet isn't feasible and also extremely ugly.
> The point is that when you talk to someone with a 1500-byte MTU you will be
> sending 1500-byte (or smaller) TCP packets even without clamping.
>
> On 12 Sep 2009, at 8:04 , Zhen Cao wrote:
>
>> I guess you are saying that the black hole problem not only targets
>> translation. But translation, especially v4-to-v6 which lengthens the
>> packet, makes this problem worse. So translation algorithm should take
>> special care of this problem?
>
> In an earlier version of my text I took this into account, but since then I
> have changed my mind: I don't think it's worth the trouble to do this. The
> common situation will be for all the systems involved to have 1500-byte
> MTUs. In that case, the IPv6 host will advertise a 1440-byte MSS (1500 - 40
> bytes IPv6 - 20 bytes TCP) so the IPv4 host will send TCP packets of 1480
> bytes (1440 + 20 bytes IPv4 + 20 bytes IPv4) which the translator then
> translates into 1500-byte IPv6 packets.
>
For TCP, yes, For UDP, it is really a problem.

From magnus.westerlund@ericsson.com  Mon Sep 14 00:14:24 2009
Return-Path: <magnus.westerlund@ericsson.com>
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 6448B28C107 for <behave@core3.amsl.com>; Mon, 14 Sep 2009 00:14:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.35
X-Spam-Level: 
X-Spam-Status: No, score=-4.35 tagged_above=-999 required=5 tests=[AWL=-0.515,  BAYES_40=-0.185, 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 NAN7MFHPy4IC for <behave@core3.amsl.com>; Mon, 14 Sep 2009 00:14:23 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60]) by core3.amsl.com (Postfix) with ESMTP id 0003828C0FE for <behave@ietf.org>; Mon, 14 Sep 2009 00:14:22 -0700 (PDT)
X-AuditID: c1b4fb3c-b7b6eae000001984-a0-4aaded799003
Received: from esealmw127.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw3.ericsson.se (Symantec Mail Security) with SMTP id 7B.94.06532.97DEDAA4; Mon, 14 Sep 2009 09:15:05 +0200 (CEST)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.175]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 14 Sep 2009 09:15:04 +0200
Received: from [147.214.183.250] ([147.214.183.250]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 14 Sep 2009 09:15:04 +0200
Message-ID: <4AADED78.7010905@ericsson.com>
Date: Mon, 14 Sep 2009 09:15:04 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
References: <4A6D9D29.2050901@ericsson.com>
In-Reply-To: <4A6D9D29.2050901@ericsson.com>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-OriginalArrivalTime: 14 Sep 2009 07:15:04.0756 (UTC) FILETIME=[150CE740:01CA350B]
X-Brightmail-Tracker: AAAAAA==
Cc: Tim Polk <tim.polk@nist.gov>, Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Discusses regarding security mechanism usage for TURN
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/mail-archive/web/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>
X-List-Received-Date: Mon, 14 Sep 2009 07:14:24 -0000

WG,

This topic has now been open for a month and a half. I have seen no
comments on my latest posting (10 days ago). Thus, I am proposing an
RFC-editor note to change the wording in the document (on version 16).

Section 4, page 20, third paragraph in section:

OLD:
   [RFC5389] specifies a Long-Term Credential mechanism for STUN.  TURN
   servers and clients MUST implement this mechanism.  The server SHOULD
   demand that all requests from the client be authenticated using this
   mechanism, and the client MUST be prepared to authenticate requests
   if required.

NEW:
   [RFC5389] specifies a Long-Term Credential mechanism for STUN.  TURN
   servers and clients MUST implement this mechanism.  The server MUST
   demand that all requests from the client be authenticated using this
   mechanism, or that a equally strong or stronger mechanism for client
   authentication is used. One such mechanism is TLS, if using client
   and server certificates that actually identify the parties, i.e. no
   self-signed certificates.  The client MUST always be prepared to
   authenticate requests use the Long-Term Credential mechanism if
   required.

Cullen and Tim, does this text satisfies your discusses?

Cheers

Magnus



Magnus Westerlund skrev:
> Behave WG,
> 
> Cullen Jennings and Tim Polk each have a discuss on TURN on the same
> basic issue. The issue is around what security functions must be used to
> ensure that TURN operates in a secure and usable fashion. This has been
> discussed a number of times if one reviews the list and minutes from
> meetings. The last time was in April when Philip brought this up as a
> result of these discusses. All three of us had some additional
> discussion around the implications of the currently document MUST
> implement SHOULD use authentication in the TURN specification. Our joint
> view is that this appears too weak a recommendation from IETF around
> usage of authentication for the TURN protocol. We therefore are strongly
> proposing that TURN actually needs specify that one MUST use
> authentication.
> 
> The reasons we have for this proposal is directly related to the core of
> TURN's purpose. The main usage of TURN will be with publicly reachable
> relays. In most cases located outside of firewalls belonging to
> companies, governmental agencies, private homes, etc. These firewalls
> needs to have a certain trust in TURN so that they allow TURN to pass
> through. The security vulnerabilities that exist with TURN if
> authentication is not used, will prevent that trust to exist. As a
> result we see that IETF only by publishing TURN saying SHOULD use
> authentication rather than MUST use authentication has severe impact on
> TURN's main purpose. We do note that the usage documented in TURN
> (Version 16) that motivates the SHOULD appears to have acceptable
> security. However, that usage is judged from our point of view to be a
> marginal one, and the "SHOULD use" will open a hole for other usage with
> less satisfying securities that we deem to be very serious.
> 
> Thus we strongly urge the WG to discuss our views and recommendation to
> sharpen the SHOULD use authentication to a MUST use authentication.
> Magnus will make a decision based on any received input after two weeks
> and present that to the discussing ADs.
> 
> Best Regards
> 
> Magnus Westerlund
> Tim Polk
> Cullen Jennings
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
> 


-- 

Magnus Westerlund

IETF Transport Area Director
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------

From iljitsch@muada.com  Mon Sep 14 00:44:49 2009
Return-Path: <iljitsch@muada.com>
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 3F00828C10D for <behave@core3.amsl.com>; Mon, 14 Sep 2009 00:44:49 -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 0V2OKb0coSZs for <behave@core3.amsl.com>; Mon, 14 Sep 2009 00:44:48 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2]) by core3.amsl.com (Postfix) with ESMTP id 4A06428C0F5 for <behave@ietf.org>; Mon, 14 Sep 2009 00:44:48 -0700 (PDT)
Received: from [IPv6:2001:720:410:100f:223:32ff:fec4:ba94] ([IPv6:2001:720:410:100f:223:32ff:fec4:ba94]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id n8E7jKp9071193 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 14 Sep 2009 09:45:20 +0200 (CEST) (envelope-from iljitsch@muada.com)
Mime-Version: 1.0 (Apple Message framework v1076)
Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <a7c8d0a30909132106i4dca4867kcfb3baa706bcb022@mail.gmail.com>
Date: Mon, 14 Sep 2009 09:45:23 +0200
Content-Transfer-Encoding: 7bit
Message-Id: <D8EFA55D-1077-4CFF-9ED7-56F4995F5DCE@muada.com>
References: <A09ECC61-E8CB-430B-A891-53902BEA083D@muada.com> <a7c8d0a30909100630y32e30024s68d17487612ebd37@mail.gmail.com> <74AA3C18-B735-4020-9FEB-B1ABBED1ACFF@muada.com> <39C363776A4E8C4A94691D2BD9D1C9A1066249A1@XCH-NW-7V2.nw.nos.boeing.com> <D42C5920-C7D5-40E6-99A4-A26DE139746A@muada.com> <a7c8d0a30909112304v6023d610n883220b8843582fd@mail.gmail.com> <1491EEEF-ED8E-46B7-9FDD-20DD305A0399@muada.com> <a7c8d0a30909132106i4dca4867kcfb3baa706bcb022@mail.gmail.com>
To: Zhen Cao <caozhenpku@gmail.com>
X-Mailer: Apple Mail (2.1076)
Cc: "Templin, Fred L" <Fred.L.Templin@boeing.com>, Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] 64 MTU and fragmentation handling
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/mail-archive/web/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>
X-List-Received-Date: Mon, 14 Sep 2009 07:44:49 -0000

On 14 Sep 2009, at 6:06 , Zhen Cao wrote:

>> In an earlier version of my text I took this into account, but  
>> since then I
>> have changed my mind: I don't think it's worth the trouble to do  
>> this. The
>> common situation will be for all the systems involved to have 1500- 
>> byte
>> MTUs. In that case, the IPv6 host will advertise a 1440-byte MSS

> For TCP, yes, For UDP, it is really a problem.

But since UDP doesn't have an MSS option, how do you propose to solve  
this?

As long as UDP packets are sent with DF=0 there shouldn't be too much  
of a problem.

However, I've seen a root DNS server send UDP DNS packets with DF=1 a  
few years ago... Since in IPv4 the OS doesn't do path MTU discovery  
and unless I'm very much mistaken, neither does DNS server software,  
this is a big problem if the DNS server sends a packet larger than the  
path MTU.

From simon.perreault@viagenie.ca  Mon Sep 14 04:47:43 2009
Return-Path: <simon.perreault@viagenie.ca>
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 16A0E3A6A20 for <behave@core3.amsl.com>; Mon, 14 Sep 2009 04:47:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.81
X-Spam-Level: 
X-Spam-Status: No, score=-1.81 tagged_above=-999 required=5 tests=[AWL=-0.699,  BAYES_05=-1.11, 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 JKroQtKw4PNO for <behave@core3.amsl.com>; Mon, 14 Sep 2009 04:47:42 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by core3.amsl.com (Postfix) with ESMTP id 3ADEE3A6A1C for <behave@ietf.org>; Mon, 14 Sep 2009 04:47:41 -0700 (PDT)
Received: by jazz.viagenie.ca (Postfix, from userid 8) id 7AEE229E1614; Mon, 14 Sep 2009 07:48:22 -0400 (EDT)
Received: from ringo.viagenie.ca (ringo.viagenie.ca [IPv6:2620:0:230:c000::67]) by jazz.viagenie.ca (Postfix) with ESMTP id 7094D29E160F; Mon, 14 Sep 2009 07:48:22 -0400 (EDT)
From: Simon Perreault <simon.perreault@viagenie.ca>
Organization: =?iso-8859-1?q?Viag=E9nie?=
To: behave@ietf.org
Date: Mon, 14 Sep 2009 07:48:18 -0400
User-Agent: KMail/1.12.0 (Linux/2.6.30.5-43.fc11.x86_64; KDE/4.3.0; x86_64; ; )
References: <4A6D9D29.2050901@ericsson.com> <4AADED78.7010905@ericsson.com>
In-Reply-To: <4AADED78.7010905@ericsson.com>
MIME-Version: 1.0
Content-Type: Text/Plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <200909140748.18459.simon.perreault@viagenie.ca>
Cc: Tim Polk <tim.polk@nist.gov>
Subject: Re: [BEHAVE] Discusses regarding security mechanism usage for TURN
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/mail-archive/web/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>
X-List-Received-Date: Mon, 14 Sep 2009 11:47:43 -0000

On Monday 14 September 2009 03:15:04 Magnus Westerlund wrote:
> NEW:
>    [RFC5389] specifies a Long-Term Credential mechanism for STUN.  TURN
>    servers and clients MUST implement this mechanism.  The server MUST
>    demand that all requests from the client be authenticated using this
>    mechanism, or that a equally strong or stronger mechanism for client
>    authentication is used. One such mechanism is TLS, if using client
>    and server certificates that actually identify the parties, i.e. no
>    self-signed certificates.  The client MUST always be prepared to
>    authenticate requests use the Long-Term Credential mechanism if
>    required.

I strongly disagree. I once again point you to Matthew Kaufman's argument, 
which you seemed to agree with last time (I wasn't sure from your response):
http://www.ietf.org/mail-archive/web/behave/current/msg05733.html

Don't you think this is a valid (and potentially frequent) use case where not 
using authentication can be justified?

Simon
-- 
DNS64 open-source   --> http://ecdysis.viagenie.ca
STUN/TURN server    --> http://numb.viagenie.ca
vCard 4.0           --> http://www.vcarddav.org

From matthew@matthew.at  Mon Sep 14 07:27:25 2009
Return-Path: <matthew@matthew.at>
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 AC61B28C159 for <behave@core3.amsl.com>; Mon, 14 Sep 2009 07:27:25 -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 YYn3Uf2xOOLO for <behave@core3.amsl.com>; Mon, 14 Sep 2009 07:27:25 -0700 (PDT)
Received: from where.matthew.at (where.matthew.at [198.202.199.1]) by core3.amsl.com (Postfix) with ESMTP id 0966128C156 for <behave@ietf.org>; Mon, 14 Sep 2009 07:27:25 -0700 (PDT)
Received: from [10.10.155.2] (unknown [10.10.155.2]) by where.matthew.at (Postfix) with ESMTP id CDA1E148049; Mon, 14 Sep 2009 07:28:09 -0700 (PDT)
Message-ID: <4AAE52F9.2050203@matthew.at>
Date: Mon, 14 Sep 2009 07:28:09 -0700
From: Matthew Kaufman <matthew@matthew.at>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Simon Perreault <simon.perreault@viagenie.ca>
References: <4A6D9D29.2050901@ericsson.com> <4AADED78.7010905@ericsson.com> <200909140748.18459.simon.perreault@viagenie.ca>
In-Reply-To: <200909140748.18459.simon.perreault@viagenie.ca>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Tim Polk <tim.polk@nist.gov>, behave@ietf.org
Subject: Re: [BEHAVE] Discusses regarding security mechanism usage for TURN
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/mail-archive/web/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>
X-List-Received-Date: Mon, 14 Sep 2009 14:27:25 -0000

Simon Perreault wrote:
> On Monday 14 September 2009 03:15:04 Magnus Westerlund wrote:
>   
>> NEW:
>>    [RFC5389] specifies a Long-Term Credential mechanism for STUN.  TURN
>>    servers and clients MUST implement this mechanism.  The server MUST
>>    demand that all requests from the client be authenticated using this
>>    mechanism, or that a equally strong or stronger mechanism for client
>>    authentication is used. One such mechanism is TLS, if using client
>>    and server certificates that actually identify the parties, i.e. no
>>    self-signed certificates.  The client MUST always be prepared to
>>    authenticate requests use the Long-Term Credential mechanism if
>>    required.
>>     
>
> I strongly disagree. I once again point you to Matthew Kaufman's argument, 
> which you seemed to agree with last time (I wasn't sure from your response):
> http://www.ietf.org/mail-archive/web/behave/current/msg05733.html
>
>   

Both the above-mentioed long-term credential requirement and the failure 
to address applications/protocols for which the added requirement of 
CreatePermission for each destination address is incompatible are still 
open problems with TURN, as far as I'm concerned.

Matthew Kaufman


From matthew@matthew.at  Mon Sep 14 07:42:41 2009
Return-Path: <matthew@matthew.at>
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 A4C373A689F for <behave@core3.amsl.com>; Mon, 14 Sep 2009 07:42:41 -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 ltJY4WykLAND for <behave@core3.amsl.com>; Mon, 14 Sep 2009 07:42:41 -0700 (PDT)
Received: from where.matthew.at (where.matthew.at [198.202.199.1]) by core3.amsl.com (Postfix) with ESMTP id E0F9C28C0E9 for <behave@ietf.org>; Mon, 14 Sep 2009 07:42:40 -0700 (PDT)
Received: from [10.10.155.2] (unknown [10.10.155.2]) by where.matthew.at (Postfix) with ESMTP id E2E2514806D; Mon, 14 Sep 2009 07:43:25 -0700 (PDT)
Message-ID: <4AAE568D.9000804@matthew.at>
Date: Mon, 14 Sep 2009 07:43:25 -0700
From: Matthew Kaufman <matthew@matthew.at>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
References: <4A6D9D29.2050901@ericsson.com>
In-Reply-To: <4A6D9D29.2050901@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Tim Polk <tim.polk@nist.gov>, Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Discusses regarding security mechanism usage for TURN
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/mail-archive/web/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>
X-List-Received-Date: Mon, 14 Sep 2009 14:42:41 -0000

For additional background, I see that I failed to notice/respond to 
discussion earlier on this topic:

Magnus Westerlund wrote:
> ...
>
> The reasons we have for this proposal is directly related to the core of
> TURN's purpose. The main usage of TURN will be with publicly reachable
> relays. In most cases located outside of firewalls belonging to
> companies, governmental agencies, private homes, etc. These firewalls
> needs to have a certain trust in TURN so that they allow TURN to pass
> through. The security vulnerabilities that exist with TURN if
> authentication is not used, will prevent that trust to exist. As a
> result we see that IETF only by publishing TURN saying SHOULD use
> authentication rather than MUST use authentication has severe impact on
> TURN's main purpose. 

The problem with this is that doing this also converts TURN's 
generality, with a "main purpose" of Internet-accessible relays and a 
"secondary purpose" as a proxy protocol which started out superior to 
SOCKS (and other proprietary choices) for the corporate mandatory-proxy 
case, into a more narrower protocol which has an "only purpose" of 
Internet-accessible relays and a large number of other applications for 
which Yet Another Protocol must now be implemented/deployed.

Not only does that increase the number of different protocols in the 
world, but it also means that clients may now be forced for reasons of 
code size or implementation time to do only one or the other, thus 
eliminating the possibility of interworking with the other.

If I were engineering a widely-deployed application which needs a proxy 
protocol for the second use case (which I am), I wouldn't object to TURN 
making the long-term credential mechanism a MUST... but I'd stop using 
TURN and switch to an alternative proxy protocol for that reason.

Matthew Kaufman


From matthew@matthew.at  Mon Sep 14 07:45:38 2009
Return-Path: <matthew@matthew.at>
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 58F763A688A for <behave@core3.amsl.com>; Mon, 14 Sep 2009 07:45:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.13
X-Spam-Level: 
X-Spam-Status: No, score=-0.13 tagged_above=-999 required=5 tests=[AWL=-1.300,  BAYES_50=0.001, 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 Bn3cJkr4gJrR for <behave@core3.amsl.com>; Mon, 14 Sep 2009 07:45:37 -0700 (PDT)
Received: from where.matthew.at (where.matthew.at [198.202.199.1]) by core3.amsl.com (Postfix) with ESMTP id 96B233A682A for <behave@ietf.org>; Mon, 14 Sep 2009 07:45:37 -0700 (PDT)
Received: from [10.10.155.2] (unknown [10.10.155.2]) by where.matthew.at (Postfix) with ESMTP id 97F1D14804E; Mon, 14 Sep 2009 07:46:22 -0700 (PDT)
Message-ID: <4AAE573E.7030602@matthew.at>
Date: Mon, 14 Sep 2009 07:46:22 -0700
From: Matthew Kaufman <matthew@matthew.at>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
References: <4A6D9D29.2050901@ericsson.com> <4A6DA11B.3010300@viagenie.ca> <4A6DA77B.4060702@ericsson.com>
In-Reply-To: <4A6DA77B.4060702@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Behave WG <behave@ietf.org>, Tim Polk <tim.polk@nist.gov>
Subject: Re: [BEHAVE] Discusses regarding security mechanism usage for TURN
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/mail-archive/web/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>
X-List-Received-Date: Mon, 14 Sep 2009 14:45:38 -0000

Magnus Westerlund wrote:
> ...
> So if I understand this correctly, this deployment is exactly such a one
> that will be vulnerable to the security threats. You have some TURN
> servers operated by Adobe, they are located in the Internet as viewed
> from the client perspective. Thus, they are not fulfilling even the
> exception case for using security based on TURN server policies with
> restricting the location of the clients to the internal domain.
>
> So running without security in this case do leave TURN wide open to the
> threats listed in the security consideration.
> ...
>   
>
> Well, the argument is operational and does not appear to me to take the
> security issues with TURN itself into consideration.
>
> Am I misunderstanding the deployment in the flash case?
>
>   
Yes. The deployment in the Flash case is *not* that Adobe provides 
public TURN servers for use by Flash Player. Rather, Adobe has made it 
possible for corporate IT departments to deploy Flash Player along with 
a static configuration file which points them at a TURN server operated 
by that IT department which is only accessible from the inside network 
and which can only initiate sessions towards outside addresses. The TURN 
server is secured and operated in parallel with an equally 
unauthenticated-but-secured HTTP proxy.

Matthew Kaufman

From matthew@matthew.at  Mon Sep 14 08:56:57 2009
Return-Path: <matthew@matthew.at>
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 CBB1B3A68B0 for <behave@core3.amsl.com>; Mon, 14 Sep 2009 08:56:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.303
X-Spam-Level: 
X-Spam-Status: No, score=0.303 tagged_above=-999 required=5 tests=[AWL=-0.867,  BAYES_50=0.001, 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 OhG1S9zvoHmS for <behave@core3.amsl.com>; Mon, 14 Sep 2009 08:56:57 -0700 (PDT)
Received: from where.matthew.at (where.matthew.at [198.202.199.1]) by core3.amsl.com (Postfix) with ESMTP id 064DD3A6A58 for <behave@ietf.org>; Mon, 14 Sep 2009 08:56:57 -0700 (PDT)
Received: from [10.10.155.2] (unknown [10.10.155.2]) by where.matthew.at (Postfix) with ESMTP id 1E720148057; Mon, 14 Sep 2009 08:57:42 -0700 (PDT)
Message-ID: <4AAE67F5.1040003@matthew.at>
Date: Mon, 14 Sep 2009 08:57:41 -0700
From: Matthew Kaufman <matthew@matthew.at>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
References: <4A6D9D29.2050901@ericsson.com>
In-Reply-To: <4A6D9D29.2050901@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Tim Polk <tim.polk@nist.gov>, Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Discusses regarding security mechanism usage for TURN
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/mail-archive/web/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>
X-List-Received-Date: Mon, 14 Sep 2009 15:56:57 -0000

And to second what Hadriel Kaplan asked,...

Magnus Westerlund wrote:
> The main usage of TURN will be with publicly reachable
> relays. In most cases located outside of firewalls belonging to
> companies, governmental agencies, private homes, etc. These firewalls
> needs to have a certain trust in TURN so that they allow TURN to pass
> through. The security vulnerabilities that exist with TURN if
> authentication is not used, will prevent that trust to exist. 

I don't understand this argument at all. There are only a few firewall 
configurations that matter:

1) Deciding whether or not to enable outbound access from my client PCs 
to the TURN port generally.

In this case, I need to decide if I'm ok with my PC users initiating UDP 
sessions to a service that I may not control at all. Having TURN 
long-term-credentials mandatory makes no difference here, because an 
evil TURN server could just let anyone in... or it might not even run 
TURN but instead run some other evil protocol.

I also need to decide if I'm ok with my PC users using such a thing to 
get traffic relayed back to them... but then I have that same problem 
when I let them use HTTP to get to the outside world.

2) Deciding whether or not to enable outbound access from my client PCs 
to a *specific* TURN server (port and IP address).

In this case, I need to decide if I'm ok with my PC users initiating UDP 
sessions to a specific server which I then need to trust. I trust this 
best if it is in a DMZ that I control so that I can prevent 
externally-initiated traffic from coming to the TURN port/address, but I 
might for whatever reason need to trust one that is out on the wild 
Internet. That's not as safe, and so then I need to consider whether its 
operator is or is not running it in a relatively safe manner, and 
long-term credentials is something I might expect them to have turned on.

3) Deciding whether or not to enable inbound access to a TURN server I 
am running.

In this case, I'm the provider of a TURN server accessible to other 
hosts that I don't control. Relaying traffic costs me money, so I need 
to do everything possible to make sure that I control who uses the 
server. Of course I'll enable long-term credentials. I'll also turn on a 
whole lot of logging, do traffic shaping, set up alerts for suspicious 
traffic patterns, etc. If I'm an IT department, I never open a port up 
without a full security analysis of the system I'm providing access to, 
so there's not really any way the port is getting opened without the 
server being set up properly first.


None of these use cases is made safer by *requiring* long-term 
credential authentication, or any authentication. In use case 1, once 
you've allowed your clients out, they might be connecting to *anything*, 
and you don't really care if the server gets abused. In use case 2, 
you've still let your clients out and it still isn't really your problem 
if the server gets misused by others. In use case 3, you're the 
responsible operator of the server and so you already need to be fully 
aware of the risks of running such a thing in whatever mode you've 
configured it in.

The reality is that most firewalls will be configured to let UDP 
sessions initiated from inside go to the outside, on all ports, and a 
few (run by paranoid IT departments, as opposed to being freebies that 
come with home gateways) will be configured to let *no* UDP sessions 
initiated from inside to go to the outside. The latter ones may make 
exceptions for specific ports, but TURN's advertised ability to be used 
as a way for people to get back to the originating host will make that 
one of the less-likely exceptions... and mandatory authentication 
doesn't solve the problem they're worried about at all.

Matthew Kaufman

From petithug@acm.org  Mon Sep 14 09:00:26 2009
Return-Path: <petithug@acm.org>
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 D514F3A6A60 for <behave@core3.amsl.com>; Mon, 14 Sep 2009 09:00:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.965
X-Spam-Level: 
X-Spam-Status: No, score=-100.965 tagged_above=-999 required=5 tests=[AWL=-1.300, BAYES_50=0.001, 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 l9Z9z-aQKzWc for <behave@core3.amsl.com>; Mon, 14 Sep 2009 09:00:26 -0700 (PDT)
Received: from server.implementers.org (server.implementers.org [69.55.225.91]) by core3.amsl.com (Postfix) with ESMTP id F0C4A3A689F for <behave@ietf.org>; Mon, 14 Sep 2009 09:00:25 -0700 (PDT)
Received: by server.implementers.org (Postfix, from userid 1001) id 0EC51DBCC088; Mon, 14 Sep 2009 16:01:10 +0000 (UTC)
Received: from [192.168.2.3] (server.implementers.org [127.0.0.1]) by server.implementers.org (Postfix) with ESMTPA id 649D9DBCC08A; Mon, 14 Sep 2009 16:01:04 +0000 (UTC)
Message-ID: <4AAE68BF.2030401@acm.org>
Date: Mon, 14 Sep 2009 09:01:03 -0700
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla-Thunderbird 2.0.0.22 (X11/20090701)
MIME-Version: 1.0
To: matthew@matthew.at
References: <4A6D9D29.2050901@ericsson.com> <4A6DA11B.3010300@viagenie.ca>	<4A6DA77B.4060702@ericsson.com> <4AAE573E.7030602@matthew.at>
In-Reply-To: <4AAE573E.7030602@matthew.at>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Behave WG <behave@ietf.org>, Tim Polk <tim.polk@nist.gov>
Subject: Re: [BEHAVE] Discusses regarding security mechanism usage for TURN
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/mail-archive/web/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>
X-List-Received-Date: Mon, 14 Sep 2009 16:00:26 -0000

Matthew Kaufman wrote:
> Magnus Westerlund wrote:
>> ...
>> So if I understand this correctly, this deployment is exactly such a one
>> that will be vulnerable to the security threats. You have some TURN
>> servers operated by Adobe, they are located in the Internet as viewed
>> from the client perspective. Thus, they are not fulfilling even the
>> exception case for using security based on TURN server policies with
>> restricting the location of the clients to the internal domain.
>>
>> So running without security in this case do leave TURN wide open to the
>> threats listed in the security consideration.
>> ...
>>  
>> Well, the argument is operational and does not appear to me to take the
>> security issues with TURN itself into consideration.
>>
>> Am I misunderstanding the deployment in the flash case?
>>
>>   
> Yes. The deployment in the Flash case is *not* that Adobe provides
> public TURN servers for use by Flash Player. Rather, Adobe has made it
> possible for corporate IT departments to deploy Flash Player along with
> a static configuration file which points them at a TURN server operated
> by that IT department which is only accessible from the inside network
> and which can only initiate sessions towards outside addresses. The TURN
> server is secured and operated in parallel with an equally
> unauthenticated-but-secured HTTP proxy.

IT department can deploy whatever they want, with whatever security level they
want on an inside network.  But TURN, which is an *Internet* protocol, must be
secure.

I fully support Magnus text.

-- 
Marc Petit-Huguenin
Personal email: marc@petit-huguenin.org
Professional email: petithug@acm.org
Blog: http://blog.marc.petit-huguenin.org

From matthew@matthew.at  Mon Sep 14 10:21:42 2009
Return-Path: <matthew@matthew.at>
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 7E5713A68D1 for <behave@core3.amsl.com>; Mon, 14 Sep 2009 10:21:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.78
X-Spam-Level: 
X-Spam-Status: No, score=-0.78 tagged_above=-999 required=5 tests=[AWL=0.650,  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 EZKGWSpHp78a for <behave@core3.amsl.com>; Mon, 14 Sep 2009 10:21:41 -0700 (PDT)
Received: from where.matthew.at (where.matthew.at [198.202.199.1]) by core3.amsl.com (Postfix) with ESMTP id CFB613A67A8 for <behave@ietf.org>; Mon, 14 Sep 2009 10:21:41 -0700 (PDT)
Received: from [10.10.155.2] (unknown [10.10.155.2]) by where.matthew.at (Postfix) with ESMTP id 0243714805A; Mon, 14 Sep 2009 10:22:27 -0700 (PDT)
Message-ID: <4AAE7BD2.3000406@matthew.at>
Date: Mon, 14 Sep 2009 10:22:26 -0700
From: Matthew Kaufman <matthew@matthew.at>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Marc Petit-Huguenin <petithug@acm.org>
References: <4A6D9D29.2050901@ericsson.com> <4A6DA11B.3010300@viagenie.ca>	<4A6DA77B.4060702@ericsson.com> <4AAE573E.7030602@matthew.at> <4AAE68BF.2030401@acm.org>
In-Reply-To: <4AAE68BF.2030401@acm.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Behave WG <behave@ietf.org>, Tim Polk <tim.polk@nist.gov>
Subject: Re: [BEHAVE] Discusses regarding security mechanism usage for TURN
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/mail-archive/web/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>
X-List-Received-Date: Mon, 14 Sep 2009 17:21:42 -0000

Marc Petit-Huguenin wrote:
>
> IT department can deploy whatever they want, with whatever security level they
> want on an inside network.  But TURN, which is an *Internet* protocol, must be
> secure.
>   
[Delete references to many recent insecure Internet protocols as 
counterexamples]

As I said, I have no problem with TURN going this way, but then a widely 
deployed TURN (draft) client will undoubtedly be switching to a 
different, most likely proprietary, proxy protocol. Which is really 
unfortunate in that it could be a big driver for TURN server 
implementation and deployment, but seems already necessary in light of 
the lack of response on the CreatePermission issue.

Matthew Kaufman


From phdgang@gmail.com  Mon Sep 14 10:38:12 2009
Return-Path: <phdgang@gmail.com>
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 F153A28C1C6 for <behave@core3.amsl.com>; Mon, 14 Sep 2009 10:38:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.231
X-Spam-Level: 
X-Spam-Status: No, score=-1.231 tagged_above=-999 required=5 tests=[AWL=1.367,  BAYES_00=-2.599, HTML_MESSAGE=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 wc-g9TpDgumV for <behave@core3.amsl.com>; Mon, 14 Sep 2009 10:38:12 -0700 (PDT)
Received: from mail-px0-f181.google.com (mail-px0-f181.google.com [209.85.216.181]) by core3.amsl.com (Postfix) with ESMTP id E9B4728C1CE for <behave@ietf.org>; Mon, 14 Sep 2009 10:38:11 -0700 (PDT)
Received: by pxi11 with SMTP id 11so2500007pxi.17 for <behave@ietf.org>; Mon, 14 Sep 2009 10:38:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=KEJRGMUuI6GbSBnKyRBr0TC+1GWNmeLa7g1PsgwJfqg=; b=fYNi7Om6y2DDSG3kBXHJ8LkKt2pRRoH2lIy8f8QMVh5yHWt2KFoMmF0xVpbns34tM3 EnAkAI7wbgnleV/pktiOVkic5H4ixVH3Hh1q3RDzsHIjtZaO8puob9cMgabXZPHXnVIA wa8KyICRbleQvEifeWSTab5oLxUdbgNBzNwjc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=coM8Hx6TelFuVSUQNQ/M2xcOMgcwyl/91KxMrX33CicQpQLGIia1dhvT91BQeIBZbB lYTjsesdpszwt4XvAu60rnY+OPNOyUoZGzwZ4tIbJue7FoMcYm/srrNvcOD0fI2ZSRyx hgoKTlZhTBBpL9dJv2uCkSSZAs920rj/v3/L8=
MIME-Version: 1.0
Received: by 10.114.236.28 with SMTP id j28mr11769211wah.162.1252949932180;  Mon, 14 Sep 2009 10:38:52 -0700 (PDT)
In-Reply-To: <4AA7730F.6040602@cernet.edu.cn>
References: <4AA7730F.6040602@cernet.edu.cn>
Date: Tue, 15 Sep 2009 01:38:52 +0800
Message-ID: <36ba02b00909141038i1611b5d6ide4fd96157ed2bc8@mail.gmail.com>
From: Chen Gang <phdgang@gmail.com>
To: Xing Li <xing@cernet.edu.cn>
Content-Type: multipart/alternative; boundary=0016e64bdaeaa104ff04738d233a
Cc: congxiao <congxiao@cernet.edu.cn>, Behave WG <behave@ietf.org>, Fred Baker <fred@cisco.com>
Subject: Re: [BEHAVE] version 01 of xlate
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/mail-archive/web/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>
X-List-Received-Date: Mon, 14 Sep 2009 17:38:13 -0000

--0016e64bdaeaa104ff04738d233a
Content-Type: text/plain; charset=ISO-8859-1

Hello Xing,

I have observed that you have also updated dual-stack implmentation,
IPv4-only and IPv6-only definition. For my understanding, these three terms
are basic adjectives and can be used to describe a host, which will appear
in several BEHAVE scenarios.

However, for the purpose of describing all cases of a host implmentation,
three adjectives is appearantly not enough. For example, IVI can be used in
scenario 1 and 2. Especially, in scenario 1, can I call IVI host located in
an IPv6 network as IPv6-only host or dual-stack host? No, since it has
double IVI appproach, in which the functions of the first IVI translator is
patched into the end systemthe, and it has IPv4-based application software
and IPv6/IPv4 enable system stack, IPv6 routing and address. Similar
examples will be appreared in many cases.

So, I suggest to add a new sort of adjective to deal with this problem. We
could define a general terms to cover various IPv4/IPv6 implementations.
Like following:

IPvX-adapted-IPvY implmentation: in this context, comprises an IPvX/IPvY
enabled end system stack, IPvX applications plus IPvY routing and address in
the network.  It implies that two application instances are capable of
communicating using IPvY by some sort of tranlations mechanisms to
accomodate IPvY environments.

The definition may need more works, but this sort of definition could fill
in a omission in current framework defintions.

Thanks for your attantion.


Best Regards

Gang



2009/9/9 Xing Li <xing@cernet.edu.cn>

> Hi, All,
>
> Based on Dave's comment, the discussions in the mailing list and the
> meeting notes of IETF75, the authors have made the modifications and
> uploaded the 01 version of the IP/ICMP Translation Algorithm. Here are
> some editorial notes.
>
> (1) Most of the grammar and spelling errors are corrected.
> (2) Translating UDP over IPv4 (Sec. 2.2): Rewritten based on the
> discussions on the mailing list.
> (3) Transport-layer Header Translation (Sec. 2.5 and Sec 3.4): Reflected
> the checksum neutral case.
> (4) Translator sending ICMP error message: add the configuration
> concerns in new sections (2.5 and 3.4).
> (5) Translating ICMP extensions: add notes.
> (6) Translating multicast packets: add notes.
>
> Please review this version and send your comments and suggestions.
>
> Regards,
>
> xing
>
>
>
>
>
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>

--0016e64bdaeaa104ff04738d233a
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div>Hello Xing,</div>
<div>=A0</div>
<div>I have observed that you have also updated dual-stack implmentation, I=
Pv4-only and IPv6-only definition. For my understanding, these three terms =
are basic adjectives and can be used to describe a host, which will appear =
in several BEHAVE scenarios.</div>

<div>=A0</div>
<div>However, for the purpose of describing all cases of a host implmentati=
on, three adjectives is appearantly not enough. For example, IVI can be use=
d in scenario 1 and 2. Especially, in scenario 1, can I call IVI host locat=
ed in an IPv6 network as IPv6-only host or dual-stack host? No, since it ha=
s double IVI appproach, in which the functions of the first IVI translator =
is patched into the end systemthe, and it has IPv4-based application softwa=
re and IPv6/IPv4 enable system stack, IPv6 routing and address. Similar exa=
mples will be appreared in many cases.</div>

<div>=A0</div>
<div>So, I suggest to add a new sort of adjective to deal with this problem=
. We could define a general terms to cover various IPv4/IPv6 implementation=
s. Like following:</div>
<div>=A0</div>
<div>IPvX-adapted-IPvY implmentation: in this context, comprises an IPvX/IP=
vY enabled end system stack, IPvX applications plus IPvY routing and addres=
s in the network.=A0 It implies that two application instances are capable =
of communicating using IPvY by some sort of tranlations mechanisms to accom=
odate IPvY environments.</div>

<div><br>The definition may need more works, but this sort of definition co=
uld fill in a omission in current framework defintions.</div>
<div>=A0</div>
<div>Thanks for your attantion.</div>
<div>=A0</div>
<div>=A0</div>
<div>Best Regards</div>
<div>=A0</div>
<div>Gang</div>
<div><br><br>=A0</div>
<div class=3D"gmail_quote">2009/9/9 Xing Li <span dir=3D"ltr">&lt;<a href=
=3D"mailto:xing@cernet.edu.cn">xing@cernet.edu.cn</a>&gt;</span><br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hi, All,<br><br>Based on Dave&#3=
9;s comment, the discussions in the mailing list and the<br>meeting notes o=
f IETF75, the authors have made the modifications and<br>
uploaded the 01 version of the IP/ICMP Translation Algorithm. Here are<br>s=
ome editorial notes.<br><br>(1) Most of the grammar and spelling errors are=
 corrected.<br>(2) Translating UDP over IPv4 (Sec. 2.2): Rewritten based on=
 the<br>
discussions on the mailing list.<br>(3) Transport-layer Header Translation =
(Sec. 2.5 and Sec 3.4): Reflected<br>the checksum neutral case.<br>(4) Tran=
slator sending ICMP error message: add the configuration<br>concerns in new=
 sections (2.5 and 3.4).<br>
(5) Translating ICMP extensions: add notes.<br>(6) Translating multicast pa=
ckets: add notes.<br><br>Please review this version and send your comments =
and suggestions.<br><br>Regards,<br><br>xing<br><br><br><br><br><br>_______=
________________________________________<br>
Behave mailing list<br><a href=3D"mailto:Behave@ietf.org">Behave@ietf.org</=
a><br><a href=3D"https://www.ietf.org/mailman/listinfo/behave" target=3D"_b=
lank">https://www.ietf.org/mailman/listinfo/behave</a><br></blockquote></di=
v>
<br>

--0016e64bdaeaa104ff04738d233a--

From dthaler@microsoft.com  Mon Sep 14 13:09:23 2009
Return-Path: <dthaler@microsoft.com>
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 9FF843A68CF for <behave@core3.amsl.com>; Mon, 14 Sep 2009 13:09:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.475
X-Spam-Level: 
X-Spam-Status: No, score=-10.475 tagged_above=-999 required=5 tests=[AWL=0.124, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LXjcOfYbqwdr for <behave@core3.amsl.com>; Mon, 14 Sep 2009 13:09:22 -0700 (PDT)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.215]) by core3.amsl.com (Postfix) with ESMTP id BEA063A682F for <behave@ietf.org>; Mon, 14 Sep 2009 13:09:22 -0700 (PDT)
Received: from TK5EX14HUBC101.redmond.corp.microsoft.com (157.54.7.153) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.176.0; Mon, 14 Sep 2009 13:10:07 -0700
Received: from TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com (157.54.71.68) by TK5EX14HUBC101.redmond.corp.microsoft.com (157.54.7.153) with Microsoft SMTP Server id 14.0.639.20; Mon, 14 Sep 2009 13:10:07 -0700
Received: from TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com ([169.254.1.186]) by TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.68]) with mapi; Mon, 14 Sep 2009 13:10:07 -0700
From: Dave Thaler <dthaler@microsoft.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Thread-Topic: [BEHAVE] Discusses regarding security mechanism usage for TURN
Thread-Index: AQHKDrW7rDvACuhYKUSVinn4sbSSaZDWbhYAgABiH2A=
Date: Mon, 14 Sep 2009 20:10:06 +0000
Message-ID: <E4561B14EE2A3E4E9D478EBFB5416E1B1CC70457@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com>
References: <4A6D9D29.2050901@ericsson.com> <4AADED78.7010905@ericsson.com>
In-Reply-To: <4AADED78.7010905@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Tim Polk <tim.polk@nist.gov>, Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Discusses regarding security mechanism usage for TURN
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/mail-archive/web/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>
X-List-Received-Date: Mon, 14 Sep 2009 20:09:23 -0000

Magnus Westerlund writes:
> NEW:
>    [RFC5389] specifies a Long-Term Credential mechanism for STUN.  TURN
>    servers and clients MUST implement this mechanism.  The server MUST
>    demand that all requests from the client be authenticated using this
>    mechanism, or that a equally strong or stronger mechanism for client
>    authentication is used. One such mechanism is TLS, if using client
>    and server certificates that actually identify the parties, i.e. no
>    self-signed certificates.  The client MUST always be prepared to
>    authenticate requests use the Long-Term Credential mechanism if
>    required.

IF we go with MUST, then I disagree with the phrasing
" if using client and server certificates that actually identify=20
the parties, i.e. no self-signed certificates"
My understanding is that whether the certificates are self-signed or=20
signed by someone else is irrelevant.  What is relevant is whether they're
signed by something that the server trusts.  The server can certainly
be configured to trust a specific self-signed cert.

Suggest "if using client certificates that the server trusts" or
equivalent wording, if the decision is to go with the proposed new text.

-Dave

From huitema@microsoft.com  Mon Sep 14 14:50:46 2009
Return-Path: <huitema@microsoft.com>
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 A9B3F3A688C for <behave@core3.amsl.com>; Mon, 14 Sep 2009 14:50:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.524
X-Spam-Level: 
X-Spam-Status: No, score=-10.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H5xWtp3D7phc for <behave@core3.amsl.com>; Mon, 14 Sep 2009 14:50:45 -0700 (PDT)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.215]) by core3.amsl.com (Postfix) with ESMTP id BA06B3A681E for <behave@ietf.org>; Mon, 14 Sep 2009 14:50:45 -0700 (PDT)
Received: from TK5EX14MLTC101.redmond.corp.microsoft.com (157.54.79.178) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.176.0; Mon, 14 Sep 2009 14:51:30 -0700
Received: from TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com (157.54.71.68) by TK5EX14MLTC101.redmond.corp.microsoft.com (157.54.79.178) with Microsoft SMTP Server id 14.0.639.20; Mon, 14 Sep 2009 14:51:30 -0700
Received: from TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com ([169.254.3.19]) by TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.68]) with mapi; Mon, 14 Sep 2009 14:51:30 -0700
From: Christian Huitema <huitema@microsoft.com>
To: Behave WG <behave@ietf.org>
Thread-Topic: Security implications of protocol translation
Thread-Index: AQHKNYWEBnE24aDknUeUmfJ2WD0dLg==
Date: Mon, 14 Sep 2009 21:51:27 +0000
Message-ID: <6B55F0F93C3E9D45AF283313B8D342BA20F54E47@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
References: <4AA7730F.6040602@cernet.edu.cn> <36ba02b00909141038i1611b5d6ide4fd96157ed2bc8@mail.gmail.com>
In-Reply-To: <36ba02b00909141038i1611b5d6ide4fd96157ed2bc8@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-cr-hashedpuzzle: OnY= e3g= AKsX BCX+ BOz3 BQkA B3z7 CUZi EzmF FR1o FeEq HuXP I31+ JGte LXyj Lfik; 1; YgBlAGgAYQB2AGUAQABpAGUAdABmAC4AbwByAGcA; Sosha1_v1; 7; {6C339BF5-D7A8-49CB-BB33-1733E925AD10}; aAB1AGkAdABlAG0AYQBAAG0AaQBjAHIAbwBzAG8AZgB0AC4AYwBvAG0A; Mon, 14 Sep 2009 21:51:27 GMT; UwBlAGMAdQByAGkAdAB5ACAAaQBtAHAAbABpAGMAYQB0AGkAbwBuAHMAIABvAGYAIABwAHIAbwB0AG8AYwBvAGwAIAB0AHIAYQBuAHMAbABhAHQAaQBvAG4A
x-cr-puzzleid: {6C339BF5-D7A8-49CB-BB33-1733E925AD10}
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [BEHAVE] Security implications of protocol translation
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/mail-archive/web/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>
X-List-Received-Date: Mon, 14 Sep 2009 21:50:46 -0000

Reading a couple drafts, I was wondering about the security aspects of prot=
ocol translation.=20

Take the IPv4 Internet to IPv6 network scenario. It differs from the "class=
ic IPv4 NAT" in one great respect. While the IPv4 NAT mostly acts as the bo=
rder between "the Internet" and "the private network", the v6-v4 NAT acts m=
ostly as a bridge, not a border. The bridge can be accessed by the IPv4 Int=
ernet", as expected, but it could also be accessed from the IPv6 Internet, =
since we suppose connectivity between the IPv6 network and the IPv6 Interne=
t. Accessibility from both sides clearly creates a different level of risk.

Or take the scenario of stateless translators sitting on the Internet, and =
accessible by pretty much everybody. These are essentially alternate paths =
for reaching IPv4 or IPv6 hosts. It seems to me that such translators will =
have many of the security properties of "anonymous relays", such as for exa=
mple 6to4 gateways.=20

I wonder how much of these security implications are already analyzed. I wo=
uld very much like to take this analysis into consideration before the next=
 iteration of the address format draft.

-- Christian Huitema





From marka@isc.org  Mon Sep 14 16:09:49 2009
Return-Path: <marka@isc.org>
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 000A83A6932 for <behave@core3.amsl.com>; Mon, 14 Sep 2009 16:09:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.423
X-Spam-Level: 
X-Spam-Status: No, score=-2.423 tagged_above=-999 required=5 tests=[AWL=0.176,  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 oS223sqZ6N+a for <behave@core3.amsl.com>; Mon, 14 Sep 2009 16:09:48 -0700 (PDT)
Received: from farside.isc.org (farside.isc.org [IPv6:2001:4f8:3:bb::5]) by core3.amsl.com (Postfix) with ESMTP id 061593A6926 for <behave@ietf.org>; Mon, 14 Sep 2009 16:09:48 -0700 (PDT)
Received: from drugs.dv.isc.org (drugs.dv.isc.org [IPv6:2001:470:1f00:820:214:22ff:fed9:fbdc]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "drugs.dv.isc.org", Issuer "ISC CA" (not verified)) by farside.isc.org (Postfix) with ESMTP id 8D3B4E6059; Mon, 14 Sep 2009 23:10:30 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (8.14.3/8.14.3) with ESMTP id n8ENAGw1001342; Tue, 15 Sep 2009 09:10:18 +1000 (EST) (envelope-from marka@drugs.dv.isc.org)
Message-Id: <200909142310.n8ENAGw1001342@drugs.dv.isc.org>
To: Iljitsch van Beijnum <iljitsch@muada.com>
From: Mark Andrews <marka@isc.org>
References: <A09ECC61-E8CB-430B-A891-53902BEA083D@muada.com> <a7c8d0a30909100630y32e30024s68d17487612ebd37@mail.gmail.com> <74AA3C18-B735-4020-9FEB-B1ABBED1ACFF@muada.com> <39C363776A4E8C4A94691D2BD9D1C9A1066249A1@XCH-NW-7V2.nw.nos.boeing.com> <D42C5920-C7D5-40E6-99A4-A26DE139746A@muada.com> <a7c8d0a30909112304v6023d610n883220b8843582fd@mail.gmail.com> <1491EEEF-ED8E-46B7-9FDD-20DD305A0399@muada.com> <a7c8d0a30909132106i4dca4867kcfb3baa706bcb022@mail.gmail.com> <D8EFA55D-1077-4CFF-9ED7-56F4995F5DCE@muada.com> 
In-reply-to: Your message of "Mon, 14 Sep 2009 09:45:23 +0200." <D8EFA55D-1077-4CFF-9ED7-56F4995F5DCE@muada.com> 
Date: Tue, 15 Sep 2009 09:10:16 +1000
Sender: marka@isc.org
Cc: "Templin, Fred L" <Fred.L.Templin@boeing.com>, Behave WG <behave@ietf.org>, Zhen Cao <caozhenpku@gmail.com>
Subject: Re: [BEHAVE] 64 MTU and fragmentation handling
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/mail-archive/web/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>
X-List-Received-Date: Mon, 14 Sep 2009 23:09:49 -0000

In message <D8EFA55D-1077-4CFF-9ED7-56F4995F5DCE@muada.com>, Iljitsch van Beijn
um writes:
> On 14 Sep 2009, at 6:06 , Zhen Cao wrote:
> 
> >> In an earlier version of my text I took this into account, but  
> >> since then I
> >> have changed my mind: I don't think it's worth the trouble to do  
> >> this. The
> >> common situation will be for all the systems involved to have 1500- 
> >> byte
> >> MTUs. In that case, the IPv6 host will advertise a 1440-byte MSS
> 
> > For TCP, yes, For UDP, it is really a problem.
> 
> But since UDP doesn't have an MSS option, how do you propose to solve  
> this?
> 
> As long as UDP packets are sent with DF=0 there shouldn't be too much  
> of a problem.
> 
> However, I've seen a root DNS server send UDP DNS packets with DF=1 a  
> few years ago... Since in IPv4 the OS doesn't do path MTU discovery  
> and unless I'm very much mistaken, neither does DNS server software,  
> this is a big problem if the DNS server sends a packet larger than the  
> path MTU.

Which apart from on Solaris the nameserver can turn off.  When I
noticed this brokeness on the part of the kernel I modified named
to turn DF off on UDP sockets on all platforms where there was a
per socket api to do this.  Other nameserver vendors should also
be aware of this by now.

Now there are two question.

1. Do we need to provided a Advanced Socket API for IPv4 that includes
   this?

2. Do we need to do a "DF and UDP, by default, Considered Harmful" RFC?

Mark

> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From phdgang@gmail.com  Mon Sep 14 18:18:59 2009
Return-Path: <phdgang@gmail.com>
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 04F0B3A695D for <behave@core3.amsl.com>; Mon, 14 Sep 2009 18:18:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.074
X-Spam-Level: 
X-Spam-Status: No, score=-0.074 tagged_above=-999 required=5 tests=[AWL=0.074,  BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_CHARSET_FARAWAY=2.45]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qHAZ9oY2E1lq for <behave@core3.amsl.com>; Mon, 14 Sep 2009 18:18:58 -0700 (PDT)
Received: from mail-px0-f181.google.com (mail-px0-f181.google.com [209.85.216.181]) by core3.amsl.com (Postfix) with ESMTP id EF8E23A696F for <behave@ietf.org>; Mon, 14 Sep 2009 18:18:57 -0700 (PDT)
Received: by pxi11 with SMTP id 11so2722989pxi.17 for <behave@ietf.org>; Mon, 14 Sep 2009 18:19:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=bbatnEFUnowZxQS9IWBxXxm0arhvhHWBUUBYYAnP8Xg=; b=ngYx4qJoKtwskBGZ17qRGj20Yh7/Z5nVDrToPA9wtfyPTh3/nW43un3VixqMRbOh+1 LTTqCYgfYd2Ce5QJooAnb/nOB+C0NIR3AZpZEijyntHL4Qpjgv8/gK1p8H8ObvpBg1KM ixJ+RSnc+a/zYkjn+fNy5QyG2sZ++miLezNwQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=DaUDpXBjX05MIIMXqc2I/MpnUlz1MGfjACJOgh453YFIRCwV0cl376DATIQuZaW0No JzGitpTsJJYzAvEwRHavRCIrd45c0Ve0ej6p+yll3hAwt0AOu5sP6ZQsr7Wtv89j30Yu 3F/9+qIutClKn9w8sfPdf4ZR82SAZDDFcdguI=
MIME-Version: 1.0
Received: by 10.114.163.26 with SMTP id l26mr12550810wae.173.1252977580560;  Mon, 14 Sep 2009 18:19:40 -0700 (PDT)
In-Reply-To: <36ba02b00909141038i1611b5d6ide4fd96157ed2bc8@mail.gmail.com>
References: <4AA7730F.6040602@cernet.edu.cn> <36ba02b00909141038i1611b5d6ide4fd96157ed2bc8@mail.gmail.com>
Date: Tue, 15 Sep 2009 09:19:40 +0800
Message-ID: <36ba02b00909141819q662e8c97v28d73236a3236013@mail.gmail.com>
From: Chen Gang <phdgang@gmail.com>
To: Xing Li <xing@cernet.edu.cn>
Content-Type: multipart/alternative; boundary=00504502f62399d2de04739393de
Cc: congxiao <congxiao@cernet.edu.cn>, Behave WG <behave@ietf.org>, Fred Baker <fred@cisco.com>
Subject: Re: [BEHAVE] version 01 of xlate
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/mail-archive/web/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>
X-List-Received-Date: Tue, 15 Sep 2009 01:18:59 -0000

--00504502f62399d2de04739393de
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: quoted-printable

Hello Xing,

The comments may be attached to the wrong mail threads.
Sorry about that.
Please ignore it.



Best Regards

Gang



2009/9/15 Chen Gang <phdgang@gmail.com>

> Hello Xing,
>
> I have observed that you have also updated dual-stack implmentation,
> IPv4-only and IPv6-only definition. For my understanding, these three ter=
ms
> are basic adjectives and can be used to describe a host, which will appea=
r
> in several BEHAVE scenarios.
>
> However, for the purpose of describing all cases of a host implmentation,
> three adjectives is appearantly not enough. For example, IVI can be used =
in
> scenario 1 and 2. Especially, in scenario 1, can I call IVI host located =
in
> an IPv6 network as IPv6-only host or dual-stack host? No, since it has
> double IVI appproach, in which the functions of the first IVI translator =
is
> patched into the end systemthe, and it has IPv4-based application softwar=
e
> and IPv6/IPv4 enable system stack, IPv6 routing and address. Similar
> examples will be appreared in many cases.
>
> So, I suggest to add a new sort of adjective to deal with this problem. W=
e
> could define a general terms to cover various IPv4/IPv6 implementations.
> Like following:
>
> IPvX-adapted-IPvY implmentation: in this context, comprises an IPvX/IPvY
> enabled end system stack, IPvX applications plus IPvY routing and address=
 in
> the network.  It implies that two application instances are capable of
> communicating using IPvY by some sort of tranlations mechanisms to
> accomodate IPvY environments.
>
> The definition may need more works, but this sort of definition could fil=
l
> in a omission in current framework defintions.
>
> Thanks for your attantion.
>
>
> Best Regards
>
> Gang
>
>
>
> 2009/9/9 Xing Li <xing@cernet.edu.cn>
>
> Hi, All,
>>
>> Based on Dave's comment, the discussions in the mailing list and the
>> meeting notes of IETF75, the authors have made the modifications and
>> uploaded the 01 version of the IP/ICMP Translation Algorithm. Here are
>> some editorial notes.
>>
>> (1) Most of the grammar and spelling errors are corrected.
>> (2) Translating UDP over IPv4 (Sec. 2.2): Rewritten based on the
>> discussions on the mailing list.
>> (3) Transport-layer Header Translation (Sec. 2.5 and Sec 3.4): Reflected
>> the checksum neutral case.
>> (4) Translator sending ICMP error message: add the configuration
>> concerns in new sections (2.5 and 3.4).
>> (5) Translating ICMP extensions: add notes.
>> (6) Translating multicast packets: add notes.
>>
>> Please review this version and send your comments and suggestions.
>>
>> Regards,
>>
>> xing
>>
>>
>>
>>
>>
>> _______________________________________________
>> Behave mailing list
>> Behave@ietf.org
>> https://www.ietf.org/mailman/listinfo/behave
>>
>
>


--=20
=B3=C2=B8=D5
phdgang@gmail.com

--00504502f62399d2de04739393de
Content-Type: text/html; charset=GB2312
Content-Transfer-Encoding: quoted-printable

<div>Hello Xing,</div>
<div>&nbsp;</div>
<div>The comments may be attached to the wrong mail threads.</div>
<div>Sorry about that.</div>
<div>Please ignore it.</div>
<div>&nbsp;</div>
<div>&nbsp;</div>
<div>&nbsp;</div>
<div>Best Regards</div>
<div>&nbsp;</div>
<div>Gang</div>
<div><br><br>&nbsp;</div>
<div class=3D"gmail_quote">2009/9/15 Chen Gang <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:phdgang@gmail.com">phdgang@gmail.com</a>&gt;</span><br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>Hello Xing,</div>
<div>&nbsp;</div>
<div>I have observed that you have also updated dual-stack implmentation, I=
Pv4-only and IPv6-only definition. For my understanding, these three terms =
are basic adjectives and can be used to describe a host, which will appear =
in several BEHAVE scenarios.</div>

<div>&nbsp;</div>
<div>However, for the purpose of describing all cases of a host implmentati=
on, three adjectives is appearantly not enough. For example, IVI can be use=
d in scenario 1 and 2. Especially, in scenario 1, can I call IVI host locat=
ed in an IPv6 network as IPv6-only host or dual-stack host? No, since it ha=
s double IVI appproach, in which the functions of the first IVI translator =
is patched into the end systemthe, and it has IPv4-based application softwa=
re and IPv6/IPv4 enable system stack, IPv6 routing and address. Similar exa=
mples will be appreared in many cases.</div>

<div>&nbsp;</div>
<div>So, I suggest to add a new sort of adjective to deal with this problem=
. We could define a general terms to cover various IPv4/IPv6 implementation=
s. Like following:</div>
<div>&nbsp;</div>
<div>IPvX-adapted-IPvY implmentation: in this context, comprises an IPvX/IP=
vY enabled end system stack, IPvX applications plus IPvY routing and addres=
s in the network.&nbsp; It implies that two application instances are capab=
le of communicating using IPvY by some sort of tranlations mechanisms to ac=
comodate IPvY environments.</div>

<div><br>The definition may need more works, but this sort of definition co=
uld fill in a omission in current framework defintions.</div>
<div>&nbsp;</div>
<div>Thanks for your attantion.</div>
<div>&nbsp;</div>
<div>&nbsp;</div>
<div>Best Regards</div>
<div>&nbsp;</div>
<div>Gang</div>
<div><br><br>&nbsp;</div>
<div class=3D"gmail_quote">2009/9/9 Xing Li <span dir=3D"ltr">&lt;<a href=
=3D"mailto:xing@cernet.edu.cn" target=3D"_blank">xing@cernet.edu.cn</a>&gt;=
</span>=20
<div>
<div></div>
<div class=3D"h5"><br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hi, All,<br><br>Based on Dave&#3=
9;s comment, the discussions in the mailing list and the<br>meeting notes o=
f IETF75, the authors have made the modifications and<br>
uploaded the 01 version of the IP/ICMP Translation Algorithm. Here are<br>s=
ome editorial notes.<br><br>(1) Most of the grammar and spelling errors are=
 corrected.<br>(2) Translating UDP over IPv4 (Sec. 2.2): Rewritten based on=
 the<br>
discussions on the mailing list.<br>(3) Transport-layer Header Translation =
(Sec. 2.5 and Sec 3.4): Reflected<br>the checksum neutral case.<br>(4) Tran=
slator sending ICMP error message: add the configuration<br>concerns in new=
 sections (2.5 and 3.4).<br>
(5) Translating ICMP extensions: add notes.<br>(6) Translating multicast pa=
ckets: add notes.<br><br>Please review this version and send your comments =
and suggestions.<br><br>Regards,<br><br>xing<br><br><br><br><br><br>_______=
________________________________________<br>
Behave mailing list<br><a href=3D"mailto:Behave@ietf.org" target=3D"_blank"=
>Behave@ietf.org</a><br><a href=3D"https://www.ietf.org/mailman/listinfo/be=
have" target=3D"_blank">https://www.ietf.org/mailman/listinfo/behave</a><br=
></blockquote>
</div></div></div><br></blockquote></div><br><br clear=3D"all">
<div></div><br>-- <br>=B3=C2=B8=D5<br><a href=3D"mailto:phdgang@gmail.com">=
phdgang@gmail.com</a><br>

--00504502f62399d2de04739393de--

From phdgang@gmail.com  Mon Sep 14 18:22:12 2009
Return-Path: <phdgang@gmail.com>
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 EED0E3A6970 for <behave@core3.amsl.com>; Mon, 14 Sep 2009 18:22:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.303
X-Spam-Level: 
X-Spam-Status: No, score=-1.303 tagged_above=-999 required=5 tests=[AWL=1.295,  BAYES_00=-2.599, HTML_MESSAGE=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 2h-V8yz6fVSf for <behave@core3.amsl.com>; Mon, 14 Sep 2009 18:22:11 -0700 (PDT)
Received: from mail-pz0-f172.google.com (mail-pz0-f172.google.com [209.85.222.172]) by core3.amsl.com (Postfix) with ESMTP id DF6663A696F for <behave@ietf.org>; Mon, 14 Sep 2009 18:22:10 -0700 (PDT)
Received: by pzk2 with SMTP id 2so2996691pzk.19 for <behave@ietf.org>; Mon, 14 Sep 2009 18:22:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=Bj8wDRzn+MRgXCZGX9r0CGr1GoZMI0G2q03CFNaMUoc=; b=LNSgaJ8s5z6X/8NjZxyBGgUXJkf5wOVHFwadh80tCPQhIaD+3SFHtqzaRJulU9HfUl Sv7LhpQmD3p2cokCmbYJaZWlKnPJP2C5F51gRCPepnlXQfuvSXWZiO4gyCJ0OIYiZSAe 0rs9+JmqRzRlwmv8l8X6wnUj3R5AzeC4DM4Ks=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=W9h4iJ5tpuivoaEDEH967kaaZhYUch93LaL43Hzg3vqh1d5ufFDEIQftRg7uh/Ckv3 dZu1PevMgoBQdi6AI+2Q2DOxhzU2ly4IyygtctW6DCjLldskILfB+J0PW+WeV7Xm4Zw2 JfPRPIr14LU+vCXDWn1vcm/GcxnaJi2acsRWg=
MIME-Version: 1.0
Received: by 10.115.45.5 with SMTP id x5mr12581217waj.182.1252977772929; Mon,  14 Sep 2009 18:22:52 -0700 (PDT)
In-Reply-To: <4AA706C2.6020804@cernet.edu.cn>
References: <4AA706C2.6020804@cernet.edu.cn>
Date: Tue, 15 Sep 2009 09:22:52 +0800
Message-ID: <36ba02b00909141822m37c9239dy800f92c31f2b9a37@mail.gmail.com>
From: Chen Gang <phdgang@gmail.com>
To: Xing Li <xing@cernet.edu.cn>
Content-Type: multipart/alternative; boundary=0016e649bd941121df0473939fc9
Cc: congxiao <congxiao@cernet.edu.cn>, Behave WG <behave@ietf.org>, Fred Baker <fred@cisco.com>, Kevin Yin <kyin@cisco.com>
Subject: Re: [BEHAVE] draft-ietf-behave-v6v4-framework-01 uploaded
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/mail-archive/web/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>
X-List-Received-Date: Tue, 15 Sep 2009 01:22:12 -0000

--0016e649bd941121df0473939fc9
Content-Type: text/plain; charset=ISO-8859-1

Hello Xing,
I think it's a right place to attach the comments. Please kindly to review
it.

I have observed that you have also updated dual-stack implmentation,
IPv4-only and IPv6-only definition. For my understanding, these three terms
are basic adjectives and can be used to describe a host, which will appear
in several BEHAVE scenarios.

However, for the purpose of describing all cases of a host implmentation,
three adjectives is appearantly not enough. For example, IVI can be used in
scenario 1 and 2. Especially, in scenario 1, can I call IVI host located in
an IPv6 network as IPv6-only host or dual-stack host? No, since it has
double IVI appproach, in which the functions of the first IVI translator is
patched into the end systemthe, and it has IPv4-based application software
and IPv6/IPv4 enable system stack, IPv6 routing and address. Similar
examples will be appreared in many cases.

So, I suggest to add a new sort of adjective to deal with this problem. We
could define a general terms to cover various IPv4/IPv6 implementations.
Like following:

IPvX-adapted-IPvY implmentation: in this context, comprises an IPvX/IPvY
enabled end system stack, IPvX applications plus IPvY routing and address in
the network.  It implies that two application instances are capable of
communicating using IPvY by some sort of tranlations mechanisms to
accomodate IPvY environments.

The definition may need more works, but this sort of definition could fill
in a omission in current framework defintions.

Thanks for your attantion.


Best Regards

Gang

2009/9/9 Xing Li <xing@cernet.edu.cn>

> Hi, All,
>
> Based on Dave's comment, the discussions in the mailing list and the
> meeting notes of IETF75, the authors have made the modifications and
> uploaded the 01 version of the Framework for IPv4/IPv6 Translation. Here
> are some editorial notes.
>
> (1) Most of the grammar and spelling errors are corrected.
>
> (2) Terminology (Sec 1.2): Since the terminologies are not consistent in
> the current translation related documents. We will compile a list of the
> terminology and send to the behave@ietf.org to get the consensus before
> we modify the related documents.
>
> (3) Address Translation (Sec. 3.1.1, etc): The discussion will be move
> to the address format document and we will insert the conclusion in the
> framework document later.
>
> Please review this version and send your comments and suggestions, so we
> can edit the next version.
>
> Regards,
>
> xing
>
>
>
>
>
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>
>

--0016e649bd941121df0473939fc9
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div>Hello Xing,<br></div>
<div>I think it&#39;s a=A0right place to attach the comments. Please kindly=
 to review it.</div>
<div><br>I have observed that you have also updated dual-stack implmentatio=
n, IPv4-only and IPv6-only definition. For my understanding, these three te=
rms are basic adjectives and can be used to describe a host, which will app=
ear in several BEHAVE scenarios.<br>
=A0<br>However, for the purpose of describing all cases of a host implmenta=
tion, three adjectives is appearantly not enough. For example, IVI can be u=
sed in scenario 1 and 2. Especially, in scenario 1, can I call IVI host loc=
ated in an IPv6 network as IPv6-only host or dual-stack host? No, since it =
has double IVI appproach, in which the functions of the first IVI translato=
r is patched into the end systemthe, and it has IPv4-based application soft=
ware and IPv6/IPv4 enable system stack, IPv6 routing and address. Similar e=
xamples will be appreared in many cases.<br>
=A0<br>So, I suggest to add a new sort of adjective to deal with this probl=
em. We could define a general terms to cover various IPv4/IPv6 implementati=
ons. Like following:<br>=A0<br>IPvX-adapted-IPvY implmentation: in this con=
text, comprises an IPvX/IPvY enabled end system stack, IPvX applications pl=
us IPvY routing and address in the network.=A0 It implies that two applicat=
ion instances are capable of communicating using IPvY by some sort of tranl=
ations mechanisms to accomodate IPvY environments.</div>

<p>The definition may need more works, but this sort of definition could fi=
ll in a omission in current framework defintions.<br>=A0<br>Thanks for your=
 attantion.<br>=A0<br>=A0<br>Best Regards<br>=A0<br>Gang<br><br></p>
<div class=3D"gmail_quote">2009/9/9 Xing Li <span dir=3D"ltr">&lt;<a href=
=3D"mailto:xing@cernet.edu.cn">xing@cernet.edu.cn</a>&gt;</span><br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hi, All,<br><br>Based on Dave&#3=
9;s comment, the discussions in the mailing list and the<br>meeting notes o=
f IETF75, the authors have made the modifications and<br>
uploaded the 01 version of the Framework for IPv4/IPv6 Translation. Here<br=
>are some editorial notes.<br><br>(1) Most of the grammar and spelling erro=
rs are corrected.<br><br>(2) Terminology (Sec 1.2): Since the terminologies=
 are not consistent in<br>
the current translation related documents. We will compile a list of the<br=
>terminology and send to the <a href=3D"mailto:behave@ietf.org">behave@ietf=
.org</a> to get the consensus before<br>we modify the related documents.<br=
>
<br>(3) Address Translation (Sec. 3.1.1, etc): The discussion will be move<=
br>to the address format document and we will insert the conclusion in the<=
br>framework document later.<br><br>Please review this version and send you=
r comments and suggestions, so we<br>
can edit the next version.<br><br>Regards,<br><br>xing<br><br><br><br><br><=
br>_______________________________________________<br>Behave mailing list<b=
r><a href=3D"mailto:Behave@ietf.org">Behave@ietf.org</a><br><a href=3D"http=
s://www.ietf.org/mailman/listinfo/behave" target=3D"_blank">https://www.iet=
f.org/mailman/listinfo/behave</a><br>
<br clear=3D"all"></blockquote></div>
<div></div><br>

--0016e649bd941121df0473939fc9--

From brian.e.carpenter@gmail.com  Mon Sep 14 18:53:35 2009
Return-Path: <brian.e.carpenter@gmail.com>
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 E47143A683F for <behave@core3.amsl.com>; Mon, 14 Sep 2009 18:53:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.937
X-Spam-Level: 
X-Spam-Status: No, score=-0.937 tagged_above=-999 required=5 tests=[AWL=-1.352, BAYES_40=-0.185, J_CHICKENPOX_21=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 9iLBYBsfyaRj for <behave@core3.amsl.com>; Mon, 14 Sep 2009 18:53:35 -0700 (PDT)
Received: from mail-px0-f181.google.com (mail-px0-f181.google.com [209.85.216.181]) by core3.amsl.com (Postfix) with ESMTP id EB65A3A681C for <behave@ietf.org>; Mon, 14 Sep 2009 18:53:34 -0700 (PDT)
Received: by pxi11 with SMTP id 11so2740282pxi.17 for <behave@ietf.org>; Mon, 14 Sep 2009 18:54:20 -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:content-type :content-transfer-encoding; bh=enB6Sb4r53+El5cipbiWcjq5IFC3WPi6xp/vcSiuYPA=; b=lHVFxuDzYwqFol6yPxZwSxMaedO/bxj8UbKVMpsL+RA47O6Qr4mwfRmtF5nts7PSC3 VQaZKUPIdqZy9hVg328buMJ8mJgLwRVePHT34XogRSlautSAMhVGuiCoVAzKhdyJsF1W ueKJUISoBNGAeP62kDHAKrt3jVutTNIFABLSw=
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:content-type:content-transfer-encoding; b=ple8mN0ZuhHb3KgPwZS7SHFegbM3nWJb8M6TMLfj6L22QuCXhk9SmWOuRaNb5KY0R+ Z9+P8y88oMZ62BRaghxH5uVzdWp6HXq6tjrVsxKXsqeOY3rLd1PxSqNZfrGY6z/gP3NZ xRmvuB5vCzFvg/mNjL+MqpwfyUhMFK29tEoxU=
Received: by 10.114.30.7 with SMTP id d7mr12703100wad.30.1252979660786; Mon, 14 Sep 2009 18:54:20 -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 23sm948512pxi.13.2009.09.14.18.54.19 (version=SSLv3 cipher=RC4-MD5); Mon, 14 Sep 2009 18:54:20 -0700 (PDT)
Message-ID: <4AAEF3C1.2090502@gmail.com>
Date: Tue, 15 Sep 2009 13:54:09 +1200
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
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: DongJin Lee <dongjin@cs.auckland.ac.nz>
Subject: [BEHAVE] Actual data on UDP with/without checksum with/without fragmentation
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/mail-archive/web/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>
X-List-Received-Date: Tue, 15 Sep 2009 01:53:36 -0000

Hi,

A few weeks ago people were asking how much UDP/IPv4 traffic there
really is with or without checksums and with or without fragmentation.

Here are some actual data, kindly analysed by my colleague Dongjin Lee.
(He's in CC, but is not subscribed to the list.)

The first URL below is just the plots. The second one is a mini-report. We
may decide to beef up the report later.

The data are for a variety of network traces in a variety of years.
Dongjin has a disk full of traces that he used for his recently
completed Ph.D. The plots show cumulative distribution functions of
UDP/IPv4 bytes and packets vs port numbers for four cases:

CS=F, MF=F no checksum, not a fragment
CS=F, MF=T no checksum, fragment
CS=T, MF=F checksum, not a fragment
CS=T, MF=T checksum, fragment

You'll see an interesting variability - mainly CS=T, MF=F is above 97%,
but in a couple of traces CS=F, MF=F is above 99%.

CS=F, MF=T is the tricky one for a NAT64, I think. The highest value for
that is 0.20% of packets, on our campus in 2003. Typically, it's zero.

http://www.cs.auckland.ac.nz/~brian/UDP-CSMF-All-plots.pdf
http://www.cs.auckland.ac.nz/~brian/UDP-CSMF.pdf

    Brian

From marcelo@it.uc3m.es  Mon Sep 14 22:53:31 2009
Return-Path: <marcelo@it.uc3m.es>
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 4E4A73A68BB for <behave@core3.amsl.com>; Mon, 14 Sep 2009 22:53:31 -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 wWwpg+j21VpA for <behave@core3.amsl.com>; Mon, 14 Sep 2009 22:53:30 -0700 (PDT)
Received: from smtp03.uc3m.es (smtp03.uc3m.es [163.117.176.133]) by core3.amsl.com (Postfix) with ESMTP id 5469C3A677E for <behave@ietf.org>; Mon, 14 Sep 2009 22:53:30 -0700 (PDT)
Received: from marcelo-bagnulos-macbook-pro.local (37.pool85-59-201.dynamic.orange.es [85.59.201.37]) by smtp03.uc3m.es (Postfix) with ESMTP id 75EF172C075; Tue, 15 Sep 2009 07:54:14 +0200 (CEST)
Message-ID: <4AAF2C06.2020107@it.uc3m.es>
Date: Tue, 15 Sep 2009 07:54:14 +0200
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Christian Huitema <huitema@microsoft.com>
References: <4AA7730F.6040602@cernet.edu.cn>	<36ba02b00909141038i1611b5d6ide4fd96157ed2bc8@mail.gmail.com> <6B55F0F93C3E9D45AF283313B8D342BA20F54E47@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <6B55F0F93C3E9D45AF283313B8D342BA20F54E47@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-TM-AS-Product-Ver: IMSS-7.0.0.3116-5.6.0.1016-16888.003
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Security implications of protocol translation
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/mail-archive/web/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>
X-List-Received-Date: Tue, 15 Sep 2009 05:53:31 -0000

Christian Huitema escribió:
> Reading a couple drafts, I was wondering about the security aspects of protocol translation. 
>
> Take the IPv4 Internet to IPv6 network scenario. It differs from the "classic IPv4 NAT" in one great respect. While the IPv4 NAT mostly acts as the border between "the Internet" and "the private network", the v6-v4 NAT acts mostly as a bridge, not a border. The bridge can be accessed by the IPv4 Internet", as expected, but it could also be accessed from the IPv6 Internet, since we suppose connectivity between the IPv6 network and the IPv6 Internet. Accessibility from both sides clearly creates a different level of risk.
>
> Or take the scenario of stateless translators sitting on the Internet, and accessible by pretty much everybody. These are essentially alternate paths for reaching IPv4 or IPv6 hosts. It seems to me that such translators will have many of the security properties of "anonymous relays", such as for example 6to4 gateways. 
>
> I wonder how much of these security implications are already analyzed.
There has been some analysis of security, but i am not aware that the 
threat analysis that you are suggesting has been systematically done and 
documented. I think it may be worthwhile doing it.

Among the things that have been discussed are:

There has been quite a bit of analysis to unerstand how to make DNS64 
work with DNSSEC.

On the translators themselves, there has been agreement that the 
translators should not forward packets coming from the internet towards 
the internet. e.g. that a translator shoudl not forward an IPv6 packet 
coming from an off site source addressed to an IPv6 represetnation of 
and IPv4 destiantion that is also off site (the motivation for this was 
to avoid providing free transit to the rest of the IPv4 internet)

Interaction with IPsec and TLS has also been (mildly) done.

Then there is all the filtering capabilities of the nats that has 
certainly been taken into consideration and all the discussion about 
tracking seq numbers in tcp is ongoing.


Regards, marcelo

>  I would very much like to take this analysis into consideration before the next iteration of the address format draft.
>
> -- Christian Huitema
>
>
>
>
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>
>   


From lin.xiao@nsn.com  Mon Sep 14 23:10:13 2009
Return-Path: <lin.xiao@nsn.com>
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 DEC9C3A67FD for <behave@core3.amsl.com>; Mon, 14 Sep 2009 23:10:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.654
X-Spam-Level: 
X-Spam-Status: No, score=-2.654 tagged_above=-999 required=5 tests=[AWL=-0.055, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fQmouAlguyJw for <behave@core3.amsl.com>; Mon, 14 Sep 2009 23:10:11 -0700 (PDT)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [217.115.75.234]) by core3.amsl.com (Postfix) with ESMTP id 0B5C23A6803 for <behave@ietf.org>; Mon, 14 Sep 2009 23:10:10 -0700 (PDT)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id n8F6AMUu030359 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 15 Sep 2009 08:10:23 +0200
Received: from demuexc023.nsn-intra.net (demuexc023.nsn-intra.net [10.150.128.36]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id n8F6AKCD028502; Tue, 15 Sep 2009 08:10:22 +0200
Received: from CNBEEXC007.nsn-intra.net ([10.159.192.12]) by demuexc023.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 15 Sep 2009 08:10:14 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 15 Sep 2009 14:09:49 +0800
Message-ID: <5D84FDD8D5DC8646B9F73CF1EFD1BFA4BB88C0@CNBEEXC007.nsn-intra.net>
In-Reply-To: <4AA706C2.6020804@cernet.edu.cn>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BEHAVE] draft-ietf-behave-v6v4-framework-01 uploaded
Thread-Index: Acow7hreZjth744RT1+AEIrmS7KdpAEyNrSQ
From: "Xiao, Lin (NSN - CN/Beijing)" <lin.xiao@nsn.com>
To: "ext Xing Li" <xing@cernet.edu.cn>, "Behave WG" <behave@ietf.org>, "Kevin Yin" <kyin@cisco.com>
X-OriginalArrivalTime: 15 Sep 2009 06:10:14.0656 (UTC) FILETIME=[30C88000:01CA35CB]
Cc: congxiao <congxiao@cernet.edu.cn>, Fred Baker <fred@cisco.com>
Subject: Re: [BEHAVE] draft-ietf-behave-v6v4-framework-01 uploaded
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/mail-archive/web/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>
X-List-Received-Date: Tue, 15 Sep 2009 06:10:14 -0000

Hi Xing,

In Terminology (Sec 1.2), there is a term " IPv4-binding IPv6
addresses". Should we make sure the specific scenario that this term
could be used in? As far as I understand from the term description, this
kind of addresses are just native IPv6 addresses without any
relationship with IPv4 addresses until mapping is set up with certain
IPv4 addresses at NAT.  Do we really need such a term to describe the
IPv6 addresses before they get bound with IPv4 addresses at a NAT64? or
it can be used for the IPv6 addresses in the pool of NAT46? Could you
please give a clear definition on it for the term?

For "IPv4-embedded IPv6 addresses", it's easer to understand. But, It's
also better to put the translation directions as well as the
source/destination description of the addresses in the term definition.
e.g, "IPv4-embedded IPv6 addresses can be used either in source address
translation or in destination address translation or in both in both
NAT64 and NAT46 scenarios."

In RFC 2765, terms "IPv4-translatable IPv6 addresses" and IPv4- mapped
IPv6 addresses" are used. Should we abolish these term, or a clear
description for all the address types mentioned in the email would be
given?=20

Best Regards,
Lin



-----Original Message-----
From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On Behalf
Of ext Xing Li
Sent: Wednesday, September 09, 2009 9:37 AM
To: 'Behave WG'; Kevin Yin
Cc: congxiao; Xing Li; Fred Baker
Subject: [BEHAVE] draft-ietf-behave-v6v4-framework-01 uploaded

Hi, All,

Based on Dave's comment, the discussions in the mailing list and the
meeting notes of IETF75, the authors have made the modifications and
uploaded the 01 version of the Framework for IPv4/IPv6 Translation. Here
are some editorial notes.

(1) Most of the grammar and spelling errors are corrected.

(2) Terminology (Sec 1.2): Since the terminologies are not consistent in
the current translation related documents. We will compile a list of the
terminology and send to the behave@ietf.org to get the consensus before
we modify the related documents.

(3) Address Translation (Sec. 3.1.1, etc): The discussion will be move
to the address format document and we will insert the conclusion in the
framework document later.

Please review this version and send your comments and suggestions, so we
can edit the next version.

Regards,

xing





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

From zhouboyj@gmail.com  Mon Sep 14 23:32:25 2009
Return-Path: <zhouboyj@gmail.com>
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 5777C3A6982 for <behave@core3.amsl.com>; Mon, 14 Sep 2009 23:32:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.833
X-Spam-Level: 
X-Spam-Status: No, score=-1.833 tagged_above=-999 required=5 tests=[AWL=0.765,  BAYES_00=-2.599, HTML_MESSAGE=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 4v-zO9RI0WWr for <behave@core3.amsl.com>; Mon, 14 Sep 2009 23:32:24 -0700 (PDT)
Received: from mail-iw0-f200.google.com (mail-iw0-f200.google.com [209.85.223.200]) by core3.amsl.com (Postfix) with ESMTP id 781E63A67E3 for <behave@ietf.org>; Mon, 14 Sep 2009 23:32:24 -0700 (PDT)
Received: by iwn38 with SMTP id 38so301359iwn.31 for <behave@ietf.org>; Mon, 14 Sep 2009 23:33:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=2mqmfyEzy8AESrwB9AdaFbgGOPGYB9VrfRN+vP65Ezs=; b=h6FGibEsuqa+BYB05qbm/xEvvrBTQstqaptjP9oVxvnp8S50xx5fFTC1WXcbuN8cLr ipWp3Lf0ye/xq5RX1m8Y3iPWimaE9lwp4SPqYleVEl3XJF0d3bqhQ/32FOW2KJyxAhBi ocvP5ARvvOxAtnwn/cBMj5igXThYvWJqxCBZg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=qyNsKiVLOrMAVnKpzmyMdxXbLsJkeFu+bERvyOnKikP3VuMQJ4q3GZz7zBj2TfNXrb 27yiIOh3m1TjGD1cfDHjoNaKHeYwAM1ASkuosRGL9kW6/HN73SkNu4hB173MoWzvhJlS Y6XCBn419KF4UaocpSZYWuL/JRPs3A5Q791yc=
MIME-Version: 1.0
Received: by 10.231.25.29 with SMTP id x29mr15165768ibb.31.1252996388119; Mon,  14 Sep 2009 23:33:08 -0700 (PDT)
In-Reply-To: <038201ca3329$06870c70$c6f0200a@cisco.com>
References: <36a593230908232300m45a10136wce25d01ef8bac439@mail.gmail.com> <4A9B7BA1.6000807@cernet.edu.cn> <36a593230908310651kd76a383j28b845bb07ebba55@mail.gmail.com> <4AA9880E.3000007@cernet.edu.cn> <038201ca3329$06870c70$c6f0200a@cisco.com>
Date: Tue, 15 Sep 2009 14:33:07 +0800
Message-ID: <36a593230909142333h3ddfba97r89785044220548f4@mail.gmail.com>
From: bo zhou <zhouboyj@gmail.com>
To: Dan Wing <dwing@cisco.com>
Content-Type: multipart/alternative; boundary=00151773e7309e8ffd047397f4c1
Cc: denghui02@gmail.com, congxiao@cernet.edu.cn, behave@ietf.org, liu dapeng <maxpassion@gmail.com>, kyin@cisco.com, Xing Li <xing@cernet.edu.cn>, fred@cisco.com, phdgang@gmail.com
Subject: Re: [BEHAVE] Proposed text and comments for framework for IPv4/IPv6 translation
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/mail-archive/web/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>
X-List-Received-Date: Tue, 15 Sep 2009 06:32:25 -0000

--00151773e7309e8ffd047397f4c1
Content-Type: text/plain; charset=ISO-8859-1

Do you think we should avoid ALG, or ignore ALG inside framework?

Regards,

Bo

On Sat, Sep 12, 2009 at 5:44 AM, Dan Wing <dwing@cisco.com> wrote:

> On Thursday, September 10, 2009 4:13pm, Xing Li wrote:
>
> ...
> > >     [bo]About the ALG issue, we should state "all IP packet payload
> > >     included IP address need do ALG".
> >
> > Agree, if the end systems are in different address families.
>
> It is important to avoid ALG issues raised in
> http://tools.ietf.org/html/rfc4924#section-2.3
>
> -d
>
>


-- 
Regards,

Bo Zhou
China Mobile

--00151773e7309e8ffd047397f4c1
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div>Do you think we should avoid ALG, or ignore ALG inside framework?</div=
>
<div>=A0</div>
<div>Regards,</div>
<div>=A0</div>
<div>Bo <br><br></div>
<div class=3D"gmail_quote">On Sat, Sep 12, 2009 at 5:44 AM, Dan Wing <span =
dir=3D"ltr">&lt;<a href=3D"mailto:dwing@cisco.com">dwing@cisco.com</a>&gt;<=
/span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">On Thursday, September 10, 2009 =
4:13pm, Xing Li wrote:<br><br>...<br>
<div class=3D"im">&gt; &gt; =A0 =A0 [bo]About the ALG issue, we should stat=
e &quot;all IP packet payload<br>&gt; &gt; =A0 =A0 included IP address need=
 do ALG&quot;.<br>&gt;<br>&gt; Agree, if the end systems are in different a=
ddress families.<br>
<br></div>It is important to avoid ALG issues raised in<br><a href=3D"http:=
//tools.ietf.org/html/rfc4924#section-2.3" target=3D"_blank">http://tools.i=
etf.org/html/rfc4924#section-2.3</a><br><font color=3D"#888888"><br>-d<br><=
br>
</font></blockquote></div><br><br clear=3D"all">
<div></div><br>-- <br>Regards,<br><br>Bo Zhou<br>China Mobile<br>

--00151773e7309e8ffd047397f4c1--

From zhouboyj@gmail.com  Mon Sep 14 23:40:08 2009
Return-Path: <zhouboyj@gmail.com>
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 065713A685D for <behave@core3.amsl.com>; Mon, 14 Sep 2009 23:40:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.881
X-Spam-Level: 
X-Spam-Status: No, score=-1.881 tagged_above=-999 required=5 tests=[AWL=0.717,  BAYES_00=-2.599, HTML_MESSAGE=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 H5daIn3Qx0JE for <behave@core3.amsl.com>; Mon, 14 Sep 2009 23:40:06 -0700 (PDT)
Received: from mail-iw0-f200.google.com (mail-iw0-f200.google.com [209.85.223.200]) by core3.amsl.com (Postfix) with ESMTP id 399263A67E3 for <behave@ietf.org>; Mon, 14 Sep 2009 23:40:06 -0700 (PDT)
Received: by iwn38 with SMTP id 38so303032iwn.31 for <behave@ietf.org>; Mon, 14 Sep 2009 23:40:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=9goUD8mkoK3uiTxLRVdUQzyFDbXoP3ta/A8n8pjBQHc=; b=ST6+/XqccaTQzIOG2tgAh64ePAN+UIgmDZDh3Acmg/qQqK6rGFl8ZnIQcHmC8A/bCK vaagN30Du1962vBD/DRgG7bAepoqY9YEzESKvEOkI6tNMYPiJr4Tj9LhuPR+fBpA/gJp GnkzYDMhK22mm8s5W/sKlh6V6EqNiBhHRlDCw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=uDp+Y4WG1GbI9GH5fe8q0gQTM0MyyxOVQqV7IQonUuvP/Ms/K31seryUUxAKvFWWif Tu8bRnzHCF1+ZOrLGRX4GxXKkYVa45+vHkaJPnnzQJArjA9QC+2mx25ZubRjDxebm44+ a3arHoyZVSWDgvPXbNA9NRm10E+zvJyIUSKe4=
MIME-Version: 1.0
Received: by 10.231.121.164 with SMTP id h36mr15124452ibr.9.1252996849176;  Mon, 14 Sep 2009 23:40:49 -0700 (PDT)
In-Reply-To: <E4561B14EE2A3E4E9D478EBFB5416E1B1CC5667B@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com>
References: <36a593230908232300m45a10136wce25d01ef8bac439@mail.gmail.com> <4A9B7BA1.6000807@cernet.edu.cn> <36a593230908310651kd76a383j28b845bb07ebba55@mail.gmail.com> <4AA9880E.3000007@cernet.edu.cn> <36a593230909102302k5df1fcfsda08e38e0068bb38@mail.gmail.com> <4AAAD9D7.6080904@gmail.com> <E4561B14EE2A3E4E9D478EBFB5416E1B1CC5667B@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com>
Date: Tue, 15 Sep 2009 14:40:49 +0800
Message-ID: <36a593230909142340o66cc8549ge797ccaac5c1e7e7@mail.gmail.com>
From: bo zhou <zhouboyj@gmail.com>
To: Dave Thaler <dthaler@microsoft.com>
Content-Type: multipart/alternative; boundary=0016e64606ca19925a04739810b3
Cc: "denghui02@gmail.com" <denghui02@gmail.com>, "congxiao@cernet.edu.cn" <congxiao@cernet.edu.cn>, "behave@ietf.org" <behave@ietf.org>, liu dapeng <maxpassion@gmail.com>, "kyin@cisco.com" <kyin@cisco.com>, Xing Li <xing@cernet.edu.cn>, "fred@cisco.com" <fred@cisco.com>, "phdgang@gmail.com" <phdgang@gmail.com>
Subject: Re: [BEHAVE] Proposed text and comments for framework for IPv4/IPv6 translation
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/mail-archive/web/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>
X-List-Received-Date: Tue, 15 Sep 2009 06:40:08 -0000

--0016e64606ca19925a04739810b3
Content-Type: text/plain; charset=ISO-8859-1

I am confused.
For example: The google servers has located inside the AT&T network. then a
AT&T customer try to visit www.google.com and access the google server which
located inside the AT&T network. Shall we say this customer access Internet
or network?

Regards,

Bo Zhou

On Sat, Sep 12, 2009 at 7:44 AM, Dave Thaler <dthaler@microsoft.com> wrote:

> One distinction, which isn't always precise but is probably useful is
> that "a network" is often managed by a common organization, whereas
> the "Internet" is certainly not.  Hence a scenario with "a network"
> implies the operators of that network can unilaterally do something
> to enable that scenario.
>
> -Dave
>
> -----Original Message-----
> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On Behalf
> Of Brian E Carpenter
> Sent: Friday, September 11, 2009 4:15 PM
> To: bo zhou
> Cc: denghui02@gmail.com; congxiao@cernet.edu.cn; behave@ietf.org; liu
> dapeng; kyin@cisco.com; Xing Li; fred@cisco.com; phdgang@gmail.com
> Subject: Re: [BEHAVE] Proposed text and comments for framework for
> IPv4/IPv6 translation
>
> On 2009-09-11 18:02, bo zhou wrote:
> ...
> >>> [bo] Sorry, I cannot find any words in Sec.1.2 to define the difference
> >>> between network and Internet.
> >>>
> >>  An IPv4 network:  A specific network that has an IPv4-only
> >>     deployment.  This could be an enterprise's IPv4-only network or an
> >>     ISP's IPv4-only network.  The size of an IPv4 network is
> >>     relatively small comparing to the global IPv4 Internet.
> >>
> >> The key words are: "A specific network" and "relatively small comparing
> to
> >> the global IPv4 Internet".
> >
> >       [bo] From aboved words, i have feeling that the difference between
> > network and Internet is SIZE only. I am not sure the size is the major
> thing
> > to distinguish between the network and Internet, Is there any equipment,
> > like NAT, inside the network can help us distinguish between network and
> > Internet?
>
> I think the honest answer is no. The variations of how addressing realms
> are separated from each other are so great that I can't see any
> mathematically precise way to define them.
>
> Operationally, we can perhaps define the point of separation as anywhere
> that it is decided to put a translation device. But that doesn't help
> anybody to decide where such a point is. I think the definition quoted
> above is as good as it can be.
>
>    Brian
>  _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>
>


-- 
Regards,

Bo Zhou
China Mobile

--0016e64606ca19925a04739810b3
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div>I am confused. </div>
<div>For example: The google servers has=A0located inside the AT&amp;T netw=
ork. then a AT&amp;T customer try to=A0visit <a href=3D"http://www.google.c=
om/">www.google.com</a>=A0and access the google server which located inside=
 the AT&amp;T network. Shall we say this customer=A0access Internet or netw=
ork?</div>

<div>=A0</div>
<div>Regards,</div>
<div>=A0</div>
<div>Bo Zhou<br><br></div>
<div class=3D"gmail_quote">On Sat, Sep 12, 2009 at 7:44 AM, Dave Thaler <sp=
an dir=3D"ltr">&lt;<a href=3D"mailto:dthaler@microsoft.com">dthaler@microso=
ft.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">One distinction, which isn&#39;t=
 always precise but is probably useful is<br>that &quot;a network&quot; is =
often managed by a common organization, whereas<br>
the &quot;Internet&quot; is certainly not. =A0Hence a scenario with &quot;a=
 network&quot;<br>implies the operators of that network can unilaterally do=
 something<br>to enable that scenario.<br><font color=3D"#888888"><br>-Dave=
<br>
</font>
<div>
<div></div>
<div class=3D"h5"><br>-----Original Message-----<br>From: <a href=3D"mailto=
:behave-bounces@ietf.org">behave-bounces@ietf.org</a> [mailto:<a href=3D"ma=
ilto:behave-bounces@ietf.org">behave-bounces@ietf.org</a>] On Behalf Of Bri=
an E Carpenter<br>
Sent: Friday, September 11, 2009 4:15 PM<br>To: bo zhou<br>Cc: <a href=3D"m=
ailto:denghui02@gmail.com">denghui02@gmail.com</a>; <a href=3D"mailto:congx=
iao@cernet.edu.cn">congxiao@cernet.edu.cn</a>; <a href=3D"mailto:behave@iet=
f.org">behave@ietf.org</a>; liu dapeng; <a href=3D"mailto:kyin@cisco.com">k=
yin@cisco.com</a>; Xing Li; <a href=3D"mailto:fred@cisco.com">fred@cisco.co=
m</a>; <a href=3D"mailto:phdgang@gmail.com">phdgang@gmail.com</a><br>
Subject: Re: [BEHAVE] Proposed text and comments for framework for IPv4/IPv=
6 translation<br><br>On 2009-09-11 18:02, bo zhou wrote:<br>...<br>&gt;&gt;=
&gt; [bo] Sorry, I cannot find any words in Sec.1.2 to define the differenc=
e<br>
&gt;&gt;&gt; between network and Internet.<br>&gt;&gt;&gt;<br>&gt;&gt; =A0A=
n IPv4 network: =A0A specific network that has an IPv4-only<br>&gt;&gt; =A0=
 =A0 deployment. =A0This could be an enterprise&#39;s IPv4-only network or =
an<br>
&gt;&gt; =A0 =A0 ISP&#39;s IPv4-only network. =A0The size of an IPv4 networ=
k is<br>&gt;&gt; =A0 =A0 relatively small comparing to the global IPv4 Inte=
rnet.<br>&gt;&gt;<br>&gt;&gt; The key words are: &quot;A specific network&q=
uot; and &quot;relatively small comparing to<br>
&gt;&gt; the global IPv4 Internet&quot;.<br>&gt;<br>&gt; =A0 =A0 =A0 [bo] F=
rom aboved words, i have feeling that the difference between<br>&gt; networ=
k and Internet is SIZE only. I am not sure the size is the major thing<br>&=
gt; to distinguish between the network and Internet, Is there any equipment=
,<br>
&gt; like NAT, inside the network can help us distinguish between network a=
nd<br>&gt; Internet?<br><br>I think the honest answer is no. The variations=
 of how addressing realms<br>are separated from each other are so great tha=
t I can&#39;t see any<br>
mathematically precise way to define them.<br><br>Operationally, we can per=
haps define the point of separation as anywhere<br>that it is decided to pu=
t a translation device. But that doesn&#39;t help<br>anybody to decide wher=
e such a point is. I think the definition quoted<br>
above is as good as it can be.<br><br>=A0 =A0Brian<br></div></div>
<div>
<div></div>
<div class=3D"h5">_______________________________________________<br>Behave=
 mailing list<br><a href=3D"mailto:Behave@ietf.org">Behave@ietf.org</a><br>=
<a href=3D"https://www.ietf.org/mailman/listinfo/behave" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/behave</a><br>
<br></div></div></blockquote></div><br><br clear=3D"all">
<div></div><br>-- <br>Regards,<br><br>Bo Zhou<br>China Mobile<br>

--0016e64606ca19925a04739810b3--

From xing@cernet.edu.cn  Tue Sep 15 01:46:25 2009
Return-Path: <xing@cernet.edu.cn>
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 C41D228B797 for <behave@core3.amsl.com>; Tue, 15 Sep 2009 01:46:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.772
X-Spam-Level: 
X-Spam-Status: No, score=0.772 tagged_above=-999 required=5 tests=[AWL=0.675,  BAYES_00=-2.599, FH_HAS_XAIMC=2.696]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZCB2ljm78QiU for <behave@core3.amsl.com>; Tue, 15 Sep 2009 01:46:25 -0700 (PDT)
Received: from cernet.edu.cn (sea.net.edu.cn [202.112.3.66]) by core3.amsl.com (Postfix) with SMTP id 12BE23A6AD0 for <behave@ietf.org>; Tue, 15 Sep 2009 01:46:23 -0700 (PDT)
Received: from [59.66.24.75]([59.66.24.75]) by cernet.edu.cn(AIMC 3.2.0.0) with SMTP id jm04aafd429; Tue, 15 Sep 2009 16:47:07 +0800
Message-ID: <4AAF5485.1050701@cernet.edu.cn>
Date: Tue, 15 Sep 2009 16:47:01 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Christian Huitema <huitema@microsoft.com>
References: <4AA7730F.6040602@cernet.edu.cn>	<36ba02b00909141038i1611b5d6ide4fd96157ed2bc8@mail.gmail.com> <6B55F0F93C3E9D45AF283313B8D342BA20F54E47@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <6B55F0F93C3E9D45AF283313B8D342BA20F54E47@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-AIMC-AUTH: xing
X-AIMC-MAILFROM: xing@cernet.edu.cn
X-AIMC-Msg-ID: w6pg3nWB
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Security implications of protocol translation
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/mail-archive/web/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>
X-List-Received-Date: Tue, 15 Sep 2009 08:46:25 -0000

Christian Huitema 写道:
> Reading a couple drafts, I was wondering about the security aspects of protocol translation. 
>
> Take the IPv4 Internet to IPv6 network scenario. It differs from the "classic IPv4 NAT" in one great respect. While the IPv4 NAT mostly acts as the border between "the Internet" and "the private network", the v6-v4 NAT acts mostly as a bridge, not a border. The bridge can be accessed by the IPv4 Internet", as expected, but it could also be accessed from the IPv6 Internet, since we suppose connectivity between the IPv6 network and the IPv6 Internet. Accessibility from both sides clearly creates a different level of risk.
>
> Or take the scenario of stateless translators sitting on the Internet, and accessible by pretty much everybody. These are essentially alternate paths for reaching IPv4 or IPv6 hosts. It seems to me that such translators will have many of the security properties of "anonymous relays", such as for example 6to4 gateways. 
>   

We have done some analysis for the stateless translator.

An IPv6 host in administrative domain B may send the packets to the 
stateless translator in administrative domain A. Since the source 
address of the packets is not a IPv4-mapped address in domain A, the 
translator will drop the packets.

xing

> I wonder how much of these security implications are already analyzed. I would very much like to take this analysis into consideration before the next iteration of the address format draft.
>
> -- Christian Huitema
>
>
>
>
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>
>
>   


From caozhenpku@gmail.com  Tue Sep 15 06:29:48 2009
Return-Path: <caozhenpku@gmail.com>
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 5A25E3A6407 for <behave@core3.amsl.com>; Tue, 15 Sep 2009 06:29:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.46
X-Spam-Level: 
X-Spam-Status: No, score=-2.46 tagged_above=-999 required=5 tests=[AWL=0.139,  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 gqPKlC53UUz4 for <behave@core3.amsl.com>; Tue, 15 Sep 2009 06:29:47 -0700 (PDT)
Received: from mail-vw0-f201.google.com (mail-vw0-f201.google.com [209.85.212.201]) by core3.amsl.com (Postfix) with ESMTP id 6E94F3A684F for <behave@ietf.org>; Tue, 15 Sep 2009 06:29:47 -0700 (PDT)
Received: by vws39 with SMTP id 39so2524318vws.29 for <behave@ietf.org>; Tue, 15 Sep 2009 06:30:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=v4wmuLZ8w2opbcqaaj3LS54Te+f4kG+74UqJu+wxD68=; b=Mod27c31h6aASDhk0fgUl2IT+NrsgjDRS2ABDF7lpBVMfSa1JNIcXTLHbetEOzSsVN CEc4CcSdSBVcGOqZwjp4ngViVfQmI6uDreVp2U5IPFB4RSlTNsZEvvbv1GRmNjgEybWo M2cM+01PzMW6lB1/mJsOfN5LFExodn/yKQnkU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=q6TUxc6V6OWcTVBNSbBA2aUc2XdvfSWaE6yuuYGAVtN1GZjv0ZWwd8id1ffftYpWx3 molsHHabaejMCarUmgt00kWryq+iDyfmvHt9E7YmNoJF0Ive1ke1kn+J/qlVjkdpATfz 2CKG6BpfafLBXzzQnkIHQXTCtnnbN6GwTGV7o=
MIME-Version: 1.0
Received: by 10.220.68.155 with SMTP id v27mr10388605vci.32.1253021428269;  Tue, 15 Sep 2009 06:30:28 -0700 (PDT)
Date: Tue, 15 Sep 2009 21:30:28 +0800
Message-ID: <a7c8d0a30909150630i29d535bbhf3089fdfecffa328@mail.gmail.com>
From: Zhen Cao <caozhenpku@gmail.com>
To: marcelo bagnulo braun <marcelo@it.uc3m.es>, Iljitsch van Beijnum <iljitsch@muada.com>, Behave WG <behave@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Subject: [BEHAVE] Comments on NAT64 draft
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/mail-archive/web/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>
X-List-Received-Date: Tue, 15 Sep 2009 13:29:48 -0000

Dear Authors and all,

I have some comments on the NAT64 draft, especially on Section.7 of
MTU and fragmentation. Thanks for any clarification.

1) Sec.7.1.1 talks about the PMTU in IPv6 to IPv4 translation, and it states:
           When a NAT64 translates "packet too big" messages from IPv6
to IPv4, it adjusts the advertised MTU to the minimum of the original
advertised MTU + 20, the NAT64's MTU on the IPv6 side + 20 and the
NAT64's MTU on the IPv4 side.

>From my understanding, when some IPv6 router reports a MTU 1500, the
effective MTU for IPv4 networks is actually 1480. So the "+20" should
be "-20" instead. What's more, if DF=0 in the IPv4 packet, the
effective MTU for IPv4 is 1472, considering the 8-byte place for
fragment header.

2) If the above is right, it also applies to the discussion in
Sec.7.1.2 similarly. The "-20" should be "+20" instead.

3) Sec.7.2.2 talks about the fragmentation issues from IPv6 to IPv4,
and it states:
           In the IPv6-to-IPv4 direction, there is no need to map a
fragment to the session it belongs to in order to translate the
fragment.

If there is only one ipv4 address available for ipv6-to-ipv4
translation, the above is true. However, NAT64 is a device with at
least one ipv6 interface and at least one ipv4 interface. If there are
more than one ipv4 address and the not-the-first fragment arrives
first, it does not know how to translate the packet.

Thanks again.

Best regards,
Zhen

From huitema@microsoft.com  Tue Sep 15 07:10:31 2009
Return-Path: <huitema@microsoft.com>
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 551EF3A6818 for <behave@core3.amsl.com>; Tue, 15 Sep 2009 07:10:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.535
X-Spam-Level: 
X-Spam-Status: No, score=-10.535 tagged_above=-999 required=5 tests=[AWL=0.064, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bAkuRd7VOKxL for <behave@core3.amsl.com>; Tue, 15 Sep 2009 07:10:30 -0700 (PDT)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.215]) by core3.amsl.com (Postfix) with ESMTP id 941923A6811 for <behave@ietf.org>; Tue, 15 Sep 2009 07:10:30 -0700 (PDT)
Received: from TK5EX14HUBC101.redmond.corp.microsoft.com (157.54.7.153) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.176.0; Tue, 15 Sep 2009 07:11:17 -0700
Received: from TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com (157.54.71.68) by TK5EX14HUBC101.redmond.corp.microsoft.com (157.54.7.153) with Microsoft SMTP Server id 14.0.639.20; Tue, 15 Sep 2009 07:11:17 -0700
Received: from TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com ([169.254.3.19]) by TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.68]) with mapi; Tue, 15 Sep 2009 07:11:16 -0700
From: Christian Huitema <huitema@microsoft.com>
To: marcelo bagnulo braun <marcelo@it.uc3m.es>
Thread-Topic: [BEHAVE] Security implications of protocol translation
Thread-Index: AQHKNckZMF3GDtqt2kuK6ErD8Y/t95DXsFRQ
Date: Tue, 15 Sep 2009 14:11:14 +0000
Message-ID: <6B55F0F93C3E9D45AF283313B8D342BA20F557D0@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
References: <4AA7730F.6040602@cernet.edu.cn> <36ba02b00909141038i1611b5d6ide4fd96157ed2bc8@mail.gmail.com> <6B55F0F93C3E9D45AF283313B8D342BA20F54E47@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <4AAF2C06.2020107@it.uc3m.es>
In-Reply-To: <4AAF2C06.2020107@it.uc3m.es>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Security implications of protocol translation
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/mail-archive/web/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>
X-List-Received-Date: Tue, 15 Sep 2009 14:10:31 -0000

> On the translators themselves, there has been agreement that the
> translators should not forward packets coming from the internet towards
> the internet. e.g. that a translator shoudl not forward an IPv6 packet
> coming from an off site source addressed to an IPv6 represetnation of
> and IPv4 destiantion that is also off site (the motivation for this was
> to avoid providing free transit to the rest of the IPv4 internet)

How does a translator what is in-site and what is off-site?

Besides, that is not completely sufficient. In some proposals, the IPv4 sou=
rce address can be algorithmically derived from the IPv6 source address. In=
 that case, an attacker can use the translation service to originate packet=
s from pretty much any IPv4 source address. What is the protection?

-- Christian Huitema




From marcelo@it.uc3m.es  Tue Sep 15 07:26:01 2009
Return-Path: <marcelo@it.uc3m.es>
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 5AB563A6A2D for <behave@core3.amsl.com>; Tue, 15 Sep 2009 07:26:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.561
X-Spam-Level: 
X-Spam-Status: No, score=-6.561 tagged_above=-999 required=5 tests=[AWL=0.038,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f8j93S58NWVy for <behave@core3.amsl.com>; Tue, 15 Sep 2009 07:26:00 -0700 (PDT)
Received: from smtp03.uc3m.es (smtp03.uc3m.es [163.117.176.133]) by core3.amsl.com (Postfix) with ESMTP id 31DA43A6811 for <behave@ietf.org>; Tue, 15 Sep 2009 07:25:59 -0700 (PDT)
Received: from marcelo-bagnulos-macbook-pro.local (wlap005.it.uc3m.es [163.117.139.108]) by smtp03.uc3m.es (Postfix) with ESMTP id AB1DC7F29AC; Tue, 15 Sep 2009 16:26:45 +0200 (CEST)
Message-ID: <4AAFA425.7040706@it.uc3m.es>
Date: Tue, 15 Sep 2009 16:26:45 +0200
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Christian Huitema <huitema@microsoft.com>
References: <4AA7730F.6040602@cernet.edu.cn>	<36ba02b00909141038i1611b5d6ide4fd96157ed2bc8@mail.gmail.com> <6B55F0F93C3E9D45AF283313B8D342BA20F54E47@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <4AAF2C06.2020107@it.uc3m.es> <6B55F0F93C3E9D45AF283313B8D342BA20F557D0@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <6B55F0F93C3E9D45AF283313B8D342BA20F557D0@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-TM-AS-Product-Ver: IMSS-7.0.0.3116-5.6.0.1016-16888.006
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Security implications of protocol translation
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/mail-archive/web/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>
X-List-Received-Date: Tue, 15 Sep 2009 14:26:01 -0000

Christian Huitema escribió:
>> On the translators themselves, there has been agreement that the
>> translators should not forward packets coming from the internet towards
>> the internet. e.g. that a translator shoudl not forward an IPv6 packet
>> coming from an off site source addressed to an IPv6 represetnation of
>> and IPv4 destiantion that is also off site (the motivation for this was
>> to avoid providing free transit to the rest of the IPv4 internet)
>>     
>
> How does a translator what is in-site and what is off-site?
>   

right, i was just thinking about that,

So, in the statefull case, it is simple i think.

the border routers must not accept any incoming packet containing a 
destination address that contains the IPv6 prefix used to represent IPv4 
addresses.
So, if the WK prefix is used, the border router must filter all incoming 
packet containing the WK prefix in the destiantion address. The same if 
the LIR is used.

This works, cause none of the IPv6 addresses assigned to internal hosts 
contain the prefix used by the statefull translator.

With the stateless translator is more complicated, i think. since the 
same prefix can be used to make representation of external hosts and to 
assign internal hosts, then the filtenring needs to be done based on the 
embedded IPv4 address, which may require per IPv4 prefix filter 
configuration the border routers, which may be more complicated, but i 
think it is feasible...


> Besides, that is not completely sufficient. In some proposals, the IPv4 source address can be algorithmically derived from the IPv6 source address. In that case, an attacker can use the translation service to originate packets from pretty much any IPv4 source address. What is the protection?
>
>   
Right.
In the statefull case, this is not an issue since the source address is 
selected form the IPv4 pool of the nat64.
In the stateless case, we need some protection against that, i agree.
If we use the filters i mentioned above, based on the IPv4 prefix. then 
the off site attackers are prevented, agree?
So the problem is how can we deal with the on site attackers that want 
to spoof an address.
I think this is quite similar to the non natted situation. I mean, a 
host connected tot he internet can spoof any source address. The 
standard way to deal with this is to use ingress filters. So the ISP 
providing IPv4 access will need to configure ingress filters, so that 
the translator can only originate packets witht he source address that 
belong to the site.

So, summarizing, if we configure filters in border routers, we can 
prevent off site attackers, for both the state full and stateless 
translators (we need more fine grained filters for the stateless case, 
but still seems feasoble imho)

If we have these filters in place, on site attackers can still use the 
stateless translator to spoof source addresses. AFAICT, this is similar 
to what any IPv4 site can do today and this can be handled by the ISP of 
the site putting ingress filters in place.

Am i missing something?

Regards, marcelo


> -- Christian Huitema
>
>
>
>
>   


From iljitsch@muada.com  Tue Sep 15 07:36:45 2009
Return-Path: <iljitsch@muada.com>
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 1EE0B3A6B2A for <behave@core3.amsl.com>; Tue, 15 Sep 2009 07:36:45 -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 ZG9NiHpREYnv for <behave@core3.amsl.com>; Tue, 15 Sep 2009 07:36:44 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2]) by core3.amsl.com (Postfix) with ESMTP id 12F003A6B27 for <behave@ietf.org>; Tue, 15 Sep 2009 07:36:43 -0700 (PDT)
Received: from [IPv6:2001:720:410:100f:223:32ff:fec4:ba94] ([IPv6:2001:720:410:100f:223:32ff:fec4:ba94]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id n8FEbMJF081595 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 15 Sep 2009 16:37:22 +0200 (CEST) (envelope-from iljitsch@muada.com)
Mime-Version: 1.0 (Apple Message framework v1076)
Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <a7c8d0a30909150630i29d535bbhf3089fdfecffa328@mail.gmail.com>
Date: Tue, 15 Sep 2009 16:37:26 +0200
Content-Transfer-Encoding: 7bit
Message-Id: <7CB993A6-829C-46CC-A74C-7DBF7CFE88C6@muada.com>
References: <a7c8d0a30909150630i29d535bbhf3089fdfecffa328@mail.gmail.com>
To: Zhen Cao <caozhenpku@gmail.com>
X-Mailer: Apple Mail (2.1076)
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Comments on NAT64 draft
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/mail-archive/web/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>
X-List-Received-Date: Tue, 15 Sep 2009 14:36:45 -0000

On 15 Sep 2009, at 15:30 , Zhen Cao wrote:

> 1) Sec.7.1.1 talks about the PMTU in IPv6 to IPv4 translation, and  
> it states:
>           When a NAT64 translates "packet too big" messages from IPv6
> to IPv4, it adjusts the advertised MTU to the minimum of the original
> advertised MTU + 20, the NAT64's MTU on the IPv6 side + 20 and the
> NAT64's MTU on the IPv4 side.

> From my understanding, when some IPv6 router reports a MTU 1500, the
> effective MTU for IPv4 networks is actually 1480. So the "+20" should
> be "-20" instead.

Right. I think I was confusing the direction of the packet flows here.

> What's more, if DF=0 in the IPv4 packet, the
> effective MTU for IPv4 is 1472, considering the 8-byte place for
> fragment header.

Yes, if an IPv4 host is sending packets with DF=1 that are larger than  
what can be handled on the IPv6 part of the path and then switches to  
sending packets with DF=0, it then needs to use a path MTU that is 8  
bytes smaller than was the case with DF=1. However, hosts typically  
send packets that are all DF=0, in which case we won't be sending back  
any packet too big messages, or all with DF=1, in which case the host  
should adapt to the reported path MTU so there is no need for  
fragmentation.

> 2) If the above is right, it also applies to the discussion in
> Sec.7.1.2 similarly. The "-20" should be "+20" instead.

Right.

> 3) Sec.7.2.2 talks about the fragmentation issues from IPv6 to IPv4,
> and it states:
>           In the IPv6-to-IPv4 direction, there is no need to map a
> fragment to the session it belongs to in order to translate the
> fragment.

> If there is only one ipv4 address available for ipv6-to-ipv4
> translation, the above is true. However, NAT64 is a device with at
> least one ipv6 interface and at least one ipv4 interface. If there are
> more than one ipv4 address and the not-the-first fragment arrives
> first, it does not know how to translate the packet.

Not sure if we already discuss this in the draft, but we don't want  
the situation where a translator uses different IPv4 addresses for  
translating different sessions from the same IPv6 host because it  
breaks STUN.

Thanks for the comments,

Iljitsch

From huitema@microsoft.com  Tue Sep 15 07:41:55 2009
Return-Path: <huitema@microsoft.com>
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 070A63A6A35 for <behave@core3.amsl.com>; Tue, 15 Sep 2009 07:41:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.543
X-Spam-Level: 
X-Spam-Status: No, score=-10.543 tagged_above=-999 required=5 tests=[AWL=0.056, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wZ5F4Yb-2orc for <behave@core3.amsl.com>; Tue, 15 Sep 2009 07:41:53 -0700 (PDT)
Received: from smtp.microsoft.com (mailc.microsoft.com [131.107.115.214]) by core3.amsl.com (Postfix) with ESMTP id BFB6C28C0D6 for <behave@ietf.org>; Tue, 15 Sep 2009 07:41:52 -0700 (PDT)
Received: from TK5EX14MLTC104.redmond.corp.microsoft.com (157.54.79.159) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.2.176.0; Tue, 15 Sep 2009 07:42:39 -0700
Received: from TK5EX14MLTW651.wingroup.windeploy.ntdev.microsoft.com (157.54.71.39) by TK5EX14MLTC104.redmond.corp.microsoft.com (157.54.79.159) with Microsoft SMTP Server id 14.0.639.20; Tue, 15 Sep 2009 07:42:39 -0700
Received: from TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com ([169.254.3.19]) by TK5EX14MLTW651.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.39]) with mapi; Tue, 15 Sep 2009 07:42:39 -0700
From: Christian Huitema <huitema@microsoft.com>
To: marcelo bagnulo braun <marcelo@it.uc3m.es>
Thread-Topic: [BEHAVE] Security implications of protocol translation
Thread-Index: AQHKNckZMF3GDtqt2kuK6ErD8Y/t95DXsFRQgAB6jID//420oA==
Date: Tue, 15 Sep 2009 14:42:37 +0000
Message-ID: <6B55F0F93C3E9D45AF283313B8D342BA20F55829@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
References: <4AA7730F.6040602@cernet.edu.cn> <36ba02b00909141038i1611b5d6ide4fd96157ed2bc8@mail.gmail.com> <6B55F0F93C3E9D45AF283313B8D342BA20F54E47@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <4AAF2C06.2020107@it.uc3m.es> <6B55F0F93C3E9D45AF283313B8D342BA20F557D0@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <4AAFA425.7040706@it.uc3m.es>
In-Reply-To: <4AAFA425.7040706@it.uc3m.es>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Security implications of protocol translation
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/mail-archive/web/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>
X-List-Received-Date: Tue, 15 Sep 2009 14:41:55 -0000

> So, summarizing, if we configure filters in border routers, we can
> prevent off site attackers, for both the state full and stateless
> translators (we need more fine grained filters for the stateless case,
> but still seems feasoble imho)

I really don't think we can assume more than basic filters in most site rou=
ters. The lower common denominator seems to be egress filtering. That is, s=
ites will only accept incoming packets that are bound to the site's prefix,=
 will normally not accept incoming packets whose source address belongs to =
that prefix, and will not allow outgoing packets whose source address does =
not belong to the site prefix.

> If we have these filters in place, on site attackers can still use the
> stateless translator to spoof source addresses. AFAICT, this is similar
> to what any IPv4 site can do today and this can be handled by the ISP of
> the site putting ingress filters in place.
>
> Am i missing something?

I think we have to assume egress filtering, as described above, and not req=
uire specific filters. Certainly not filters that attempt to dissect the ho=
st part of an address. The technology we design should work with such basic=
 filters, and should not add extra risks.

-- Christian Huitema




From iljitsch@muada.com  Tue Sep 15 07:52:23 2009
Return-Path: <iljitsch@muada.com>
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 A781C3A67EA for <behave@core3.amsl.com>; Tue, 15 Sep 2009 07:52:23 -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 yoWdjVlfw1+s for <behave@core3.amsl.com>; Tue, 15 Sep 2009 07:52:23 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2]) by core3.amsl.com (Postfix) with ESMTP id 87A803A679C for <behave@ietf.org>; Tue, 15 Sep 2009 07:52:22 -0700 (PDT)
Received: from [IPv6:2001:720:410:100f:223:32ff:fec4:ba94] ([IPv6:2001:720:410:100f:223:32ff:fec4:ba94]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id n8FEr2Lx081762 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 15 Sep 2009 16:53:02 +0200 (CEST) (envelope-from iljitsch@muada.com)
Mime-Version: 1.0 (Apple Message framework v1076)
Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <6B55F0F93C3E9D45AF283313B8D342BA20F557D0@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
Date: Tue, 15 Sep 2009 16:53:06 +0200
Content-Transfer-Encoding: 7bit
Message-Id: <AA0F118A-5883-451C-B2B5-1EE72895B2A4@muada.com>
References: <4AA7730F.6040602@cernet.edu.cn> <36ba02b00909141038i1611b5d6ide4fd96157ed2bc8@mail.gmail.com> <6B55F0F93C3E9D45AF283313B8D342BA20F54E47@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <4AAF2C06.2020107@it.uc3m.es> <6B55F0F93C3E9D45AF283313B8D342BA20F557D0@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
To: Christian Huitema <huitema@microsoft.com>
X-Mailer: Apple Mail (2.1076)
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Security implications of protocol translation
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/mail-archive/web/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>
X-List-Received-Date: Tue, 15 Sep 2009 14:52:23 -0000

On 15 Sep 2009, at 16:11 , Christian Huitema wrote:

> How does a translator what is in-site and what is off-site?

The same way any proxy or relay does: with a set of policy restriction  
rules.

> Besides, that is not completely sufficient. In some proposals, the  
> IPv4 source address can be algorithmically derived from the IPv6  
> source address. In that case, an attacker can use the translation  
> service to originate packets from pretty much any IPv4 source  
> address. What is the protection?

Since when are you protected against anything on the internet?

The case where an IPv4 host sets up a connection through a stateful  
NAT64 is similar to having a host on the outside set up a connection  
through a NAT44: if there is already some state, the packets will flow  
towards the internal/IPv6 host that created the state (case 1). If  
there is no state the translator doesn't know where to send the  
packets so they are dropped (case 2).

I see no reason for alarm in case 1 because presumably, the same IPv4  
host could have sent the same packet to the IPv6 host over IPv6 if the  
IPv4 host were dual stack. There is certainly no reason for alarm in  
case 2 because the packet don't get anywhere.

In case 1 it would be suboptimal if the packets flowed towards hosts  
that are not users of the NAT64 in question, but again, the same  
packets could have been sent by any IPv6 host. This is true for both  
the stateful and stateless case. IPv6 hosts wouldn't recognize the  
packets coming from the IPv4 world if a RIR prefix is used but the  
level of obfuscation is limited because the IPv4 address is still in  
there.

All in all, I don't see a problem as long as people don't treat any  
address ranges involved in the translation as "internal" or "trusted".  
(Which you really shouldn't do to begin with, addresses are easily  
faked in many circumstances.)

From kyin@cisco.com  Tue Sep 15 00:25:31 2009
Return-Path: <kyin@cisco.com>
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 A47EB3A690F for <behave@core3.amsl.com>; Tue, 15 Sep 2009 00:25:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.799
X-Spam-Level: 
X-Spam-Status: No, score=-2.799 tagged_above=-999 required=5 tests=[AWL=0.800,  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 i1OugwHj3Fvn for <behave@core3.amsl.com>; Tue, 15 Sep 2009 00:25:30 -0700 (PDT)
Received: from syd-iport-2.cisco.com (syd-iport-2.cisco.com [64.104.193.197]) by core3.amsl.com (Postfix) with ESMTP id E85EA3A6931 for <behave@ietf.org>; Tue, 15 Sep 2009 00:25:29 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEAGferkoKS+ej/2dsb2JhbADEFIhMAY8pBYQXgVtkiCo
X-IronPort-AV: E=Sophos;i="4.44,388,1249257600"; d="scan'208";a="57894571"
Received: from hkg-dkim-2.cisco.com ([10.75.231.163]) by syd-iport-2.cisco.com with ESMTP; 15 Sep 2009 07:26: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 n8F7QCvX022614;  Tue, 15 Sep 2009 15:26: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.14.3) with ESMTP id n8F7Q9Ij019521; Tue, 15 Sep 2009 07:26:12 GMT
Received: from xmb-hkg-413.apac.cisco.com ([64.104.123.85]) by xbh-hkg-411.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 15 Sep 2009 15:25:36 +0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 15 Sep 2009 15:25:35 +0800
Message-ID: <E0E45D06F7DB404FA9C6DC47A904717F068A0392@xmb-hkg-413.apac.cisco.com>
In-Reply-To: <5D84FDD8D5DC8646B9F73CF1EFD1BFA4BB88C0@CNBEEXC007.nsn-intra.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BEHAVE] draft-ietf-behave-v6v4-framework-01 uploaded
Thread-Index: Acow7hreZjth744RT1+AEIrmS7KdpAEyNrSQAAeNomA=
References: <4AA706C2.6020804@cernet.edu.cn> <5D84FDD8D5DC8646B9F73CF1EFD1BFA4BB88C0@CNBEEXC007.nsn-intra.net>
From: "Kevin Yin (kyin)" <kyin@cisco.com>
To: "Xiao, Lin (NSN - CN/Beijing)" <lin.xiao@nsn.com>, "ext Xing Li" <xing@cernet.edu.cn>, "Behave WG" <behave@ietf.org>
X-OriginalArrivalTime: 15 Sep 2009 07:25:36.0574 (UTC) FILETIME=[B80E6DE0:01CA35D5]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2992; t=1252999573; x=1253863573; c=relaxed/simple; s=hkgdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=kyin@cisco.com; z=From:=20=22Kevin=20Yin=20(kyin)=22=20<kyin@cisco.com> |Subject:=20RE=3A=20[BEHAVE]=20draft-ietf-behave-v6v4-frame work-01=20uploaded |Sender:=20; bh=hn+lew3hUrtwyuVJ86ajrfECR/6aJG0gg73apuEHXAg=; b=lojln1+xfmzF4jqgniytB7taFFYFyllweBHS6vsK8Ke9NXmnzsjs55tVpx 826tEb0UW5MqpAP6WFsqUOKosLgUgsc86rnk6nTz+D344DhXjGfKSM8vEgZb vwPrF/sXe+7O9JKIGiSj5e3KDiJ7WK7iLWFem/S3PuIThz7bd3EvA=;
Authentication-Results: hkg-dkim-2; header.From=kyin@cisco.com; dkim=pass ( sig from cisco.com/hkgdkim2001 verified; ); 
X-Mailman-Approved-At: Tue, 15 Sep 2009 08:26:07 -0700
Cc: congxiao <congxiao@cernet.edu.cn>, "Fred Baker \(fred\)" <fred@cisco.com>
Subject: Re: [BEHAVE] draft-ietf-behave-v6v4-framework-01 uploaded
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/mail-archive/web/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>
X-List-Received-Date: Tue, 15 Sep 2009 07:25:31 -0000

Yes, those are exactly terminologies in reviewing and
will be re-defined in mailist for discussion. Stay tuned.  =20

Thanks

Kevin Yin=20


-----Original Message-----
From: Xiao, Lin (NSN - CN/Beijing) [mailto:lin.xiao@nsn.com]=20
Sent: Tuesday, September 15, 2009 2:10 PM
To: ext Xing Li; Behave WG; Kevin Yin (kyin)
Cc: congxiao; Fred Baker (fred)
Subject: RE: [BEHAVE] draft-ietf-behave-v6v4-framework-01 uploaded

Hi Xing,

In Terminology (Sec 1.2), there is a term " IPv4-binding IPv6
addresses". Should we make sure the specific scenario that this term
could be used in? As far as I understand from the term description, this
kind of addresses are just native IPv6 addresses without any
relationship with IPv4 addresses until mapping is set up with certain
IPv4 addresses at NAT.  Do we really need such a term to describe the
IPv6 addresses before they get bound with IPv4 addresses at a NAT64? or
it can be used for the IPv6 addresses in the pool of NAT46? Could you
please give a clear definition on it for the term?

For "IPv4-embedded IPv6 addresses", it's easer to understand. But, It's
also better to put the translation directions as well as the
source/destination description of the addresses in the term definition.
e.g, "IPv4-embedded IPv6 addresses can be used either in source address
translation or in destination address translation or in both in both
NAT64 and NAT46 scenarios."

In RFC 2765, terms "IPv4-translatable IPv6 addresses" and IPv4- mapped
IPv6 addresses" are used. Should we abolish these term, or a clear
description for all the address types mentioned in the email would be
given?=20

Best Regards,
Lin



-----Original Message-----
From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On Behalf
Of ext Xing Li
Sent: Wednesday, September 09, 2009 9:37 AM
To: 'Behave WG'; Kevin Yin
Cc: congxiao; Xing Li; Fred Baker
Subject: [BEHAVE] draft-ietf-behave-v6v4-framework-01 uploaded

Hi, All,

Based on Dave's comment, the discussions in the mailing list and the
meeting notes of IETF75, the authors have made the modifications and
uploaded the 01 version of the Framework for IPv4/IPv6 Translation. Here
are some editorial notes.

(1) Most of the grammar and spelling errors are corrected.

(2) Terminology (Sec 1.2): Since the terminologies are not consistent in
the current translation related documents. We will compile a list of the
terminology and send to the behave@ietf.org to get the consensus before
we modify the related documents.

(3) Address Translation (Sec. 3.1.1, etc): The discussion will be move
to the address format document and we will insert the conclusion in the
framework document later.

Please review this version and send your comments and suggestions, so we
can edit the next version.

Regards,

xing





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

From peter.livesey@tandberg.com  Mon Sep 14 09:16:57 2009
Return-Path: <peter.livesey@tandberg.com>
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 C2AA528C138 for <behave@core3.amsl.com>; Mon, 14 Sep 2009 09:16:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.11
X-Spam-Level: 
X-Spam-Status: No, score=-5.11 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, 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 LM3DCTUop8E4 for <behave@core3.amsl.com>; Mon, 14 Sep 2009 09:16:56 -0700 (PDT)
Received: from mail169.messagelabs.com (mail169.messagelabs.com [85.158.138.179]) by core3.amsl.com (Postfix) with SMTP id 34ADA28C142 for <behave@ietf.org>; Mon, 14 Sep 2009 09:16:52 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: peter.livesey@tandberg.com
X-Msg-Ref: server-14.tower-169.messagelabs.com!1252945052!32670804!12
X-StarScan-Version: 6.1.3; banners=-,-,-
X-Originating-IP: [62.70.2.252]
Received: (qmail 23886 invoked from network); 14 Sep 2009 16:17:35 -0000
Received: from unknown (HELO OSLEXCP11.eu.tandberg.int) (62.70.2.252) by server-14.tower-169.messagelabs.com with SMTP; 14 Sep 2009 16:17:35 -0000
Received: from oslexcp2.eu.tandberg.int ([10.47.136.30]) by OSLEXCP11.eu.tandberg.int with Microsoft SMTPSVC(6.0.3790.3959); Mon, 14 Sep 2009 18:16:43 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 14 Sep 2009 18:17:13 +0200
Message-ID: <C67BCA34F23E804199B464EAF3BE55DF06439A68@oslexcp2.eu.tandberg.int>
In-Reply-To: <4AAE68BF.2030401@acm.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BEHAVE] Discusses regarding security mechanism usage for TURN
Thread-Index: Aco1VJoWXyl0X9kRRMWTChd6b7v+PgAATKgg
From: "Peter Livesey" <peter.livesey@tandberg.com>
To: "Behave WG" <behave@ietf.org>
X-OriginalArrivalTime: 14 Sep 2009 16:16:43.0848 (UTC) FILETIME=[C004CC80:01CA3556]
X-Mailman-Approved-At: Tue, 15 Sep 2009 08:26:19 -0700
Subject: Re: [BEHAVE] Discusses regarding security mechanism usage for TURN
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/mail-archive/web/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>
X-List-Received-Date: Mon, 14 Sep 2009 16:18:09 -0000

It's only an *Internet* protocol if it has many implementations which
are widely used. If people/vendors are reluctant to implement it until
the drafts become a RFC then delaying it over a MUST/SHOULD seems self
defeating.

If it's a SHOULD then vendors can decide if their implementations make
it a MUST by always challenging  or leave it up to the administrators of
their equipment to decide (via configuration), based on the deployment
case.

=20
-----Original Message-----
From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On Behalf
Of Marc Petit-Huguenin
Sent: 14 September 2009 17:01
To: matthew@matthew.at
Cc: Behave WG; Tim Polk
Subject: Re: [BEHAVE] Discusses regarding security mechanism usage for
TURN

Matthew Kaufman wrote:
> Magnus Westerlund wrote:
>> ...
>> So if I understand this correctly, this deployment is exactly such a
one
>> that will be vulnerable to the security threats. You have some TURN
>> servers operated by Adobe, they are located in the Internet as viewed
>> from the client perspective. Thus, they are not fulfilling even the
>> exception case for using security based on TURN server policies with
>> restricting the location of the clients to the internal domain.
>>
>> So running without security in this case do leave TURN wide open to
the
>> threats listed in the security consideration.
>> ...
>> =20
>> Well, the argument is operational and does not appear to me to take
the
>> security issues with TURN itself into consideration.
>>
>> Am I misunderstanding the deployment in the flash case?
>>
>>  =20
> Yes. The deployment in the Flash case is *not* that Adobe provides
> public TURN servers for use by Flash Player. Rather, Adobe has made it
> possible for corporate IT departments to deploy Flash Player along
with
> a static configuration file which points them at a TURN server
operated
> by that IT department which is only accessible from the inside network
> and which can only initiate sessions towards outside addresses. The
TURN
> server is secured and operated in parallel with an equally
> unauthenticated-but-secured HTTP proxy.

IT department can deploy whatever they want, with whatever security
level they
want on an inside network.  But TURN, which is an *Internet* protocol,
must be
secure.

I fully support Magnus text.

--=20
Marc Petit-Huguenin
Personal email: marc@petit-huguenin.org
Professional email: petithug@acm.org
Blog: http://blog.marc.petit-huguenin.org
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave

From caozhenpku@gmail.com  Tue Sep 15 08:39:53 2009
Return-Path: <caozhenpku@gmail.com>
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 351453A6B54 for <behave@core3.amsl.com>; Tue, 15 Sep 2009 08:39:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.467
X-Spam-Level: 
X-Spam-Status: No, score=-2.467 tagged_above=-999 required=5 tests=[AWL=0.132,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5-4v0QBalSZT for <behave@core3.amsl.com>; Tue, 15 Sep 2009 08:39:52 -0700 (PDT)
Received: from mail-vw0-f201.google.com (mail-vw0-f201.google.com [209.85.212.201]) by core3.amsl.com (Postfix) with ESMTP id D50EE3A6B48 for <behave@ietf.org>; Tue, 15 Sep 2009 08:39:41 -0700 (PDT)
Received: by vws39 with SMTP id 39so2648134vws.29 for <behave@ietf.org>; Tue, 15 Sep 2009 08:40:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=3TS6AQet+E+nc414KMWjgqLYdaCruxf/MIgqVkBDi1k=; b=bdGx8pw6cJwFQAxdqm1vKyfinUW3ZrXASHDtDVPBcuaKPAPcn8Sk/nQ2vjOLv7rKdR tUgyRU7jMTPmY7NB2Qj28U/6MOOZNKQ5uq7hJ6HgrsNXmciNY3yFC6XdjBLllGV8BQn1 S8d3ImHf4Bl5NDrqygi6r9orimNupv01s03Go=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=juagfAnns6Zpj6KJWD6s42nDozw8lujgXpHUJFiBjNG1lMyJSAErlZDkY4YNBr8U6n FaYjFtuF/B7kHzEtQGWlHVtNeLXPLkW8hML//hJijfJJbnCu4wR3cnDXjr3ZxTB4C7lM X7BZfVYriv3senvuAcVBqFhg5ifqCY61jEylE=
MIME-Version: 1.0
Received: by 10.220.89.77 with SMTP id d13mr10683105vcm.91.1253029123293; Tue,  15 Sep 2009 08:38:43 -0700 (PDT)
In-Reply-To: <7CB993A6-829C-46CC-A74C-7DBF7CFE88C6@muada.com>
References: <a7c8d0a30909150630i29d535bbhf3089fdfecffa328@mail.gmail.com> <7CB993A6-829C-46CC-A74C-7DBF7CFE88C6@muada.com>
Date: Tue, 15 Sep 2009 23:38:42 +0800
Message-ID: <a7c8d0a30909150838s230397d9r3cbffb5df6097b76@mail.gmail.com>
From: Zhen Cao <caozhenpku@gmail.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Comments on NAT64 draft
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/mail-archive/web/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>
X-List-Received-Date: Tue, 15 Sep 2009 15:39:53 -0000

On Tue, Sep 15, 2009 at 10:37 PM, Iljitsch van Beijnum
<iljitsch@muada.com> wrote:
> On 15 Sep 2009, at 15:30 , Zhen Cao wrote:
>
>> 1) Sec.7.1.1 talks about the PMTU in IPv6 to IPv4 translation, and it
>> states:
>> =A0 =A0 =A0 =A0 =A0When a NAT64 translates "packet too big" messages fro=
m IPv6
>> to IPv4, it adjusts the advertised MTU to the minimum of the original
>> advertised MTU + 20, the NAT64's MTU on the IPv6 side + 20 and the
>> NAT64's MTU on the IPv4 side.
>
>> From my understanding, when some IPv6 router reports a MTU 1500, the
>> effective MTU for IPv4 networks is actually 1480. So the "+20" should
>> be "-20" instead.
>
> Right. I think I was confusing the direction of the packet flows here.
>
>> What's more, if DF=3D0 in the IPv4 packet, the
>> effective MTU for IPv4 is 1472, considering the 8-byte place for
>> fragment header.
>
> Yes, if an IPv4 host is sending packets with DF=3D1 that are larger than =
what
> can be handled on the IPv6 part of the path and then switches to sending
> packets with DF=3D0, it then needs to use a path MTU that is 8 bytes smal=
ler
> than was the case with DF=3D1. However, hosts typically send packets that=
 are
> all DF=3D0, in which case we won't be sending back any packet too big
> messages, or all with DF=3D1, in which case the host should adapt to the
> reported path MTU so there is no need for fragmentation.

Understand, thanks.

>
>> 2) If the above is right, it also applies to the discussion in
>> Sec.7.1.2 similarly. The "-20" should be "+20" instead.
>
> Right.
>
>> 3) Sec.7.2.2 talks about the fragmentation issues from IPv6 to IPv4,
>> and it states:
>> =A0 =A0 =A0 =A0 =A0In the IPv6-to-IPv4 direction, there is no need to ma=
p a
>> fragment to the session it belongs to in order to translate the
>> fragment.
>
>> If there is only one ipv4 address available for ipv6-to-ipv4
>> translation, the above is true. However, NAT64 is a device with at
>> least one ipv6 interface and at least one ipv4 interface. If there are
>> more than one ipv4 address and the not-the-first fragment arrives
>> first, it does not know how to translate the packet.
>
> Not sure if we already discuss this in the draft, but we don't want the
> situation where a translator uses different IPv4 addresses for translatin=
g
> different sessions from the same IPv6 host because it breaks STUN.

I am not talking about the one ipv6 mapping to multiple ipv4
addresses, and am assuming one ipv6 host maps to one ipv4 address.

If an in-the-middle fragmented packet arrives, we cannot create the
mapping entry from <Y', y> to <T, t>. Do you mean just translate it
first and wait for the first fragment to fill in the entry?

>
> Thanks for the comments,
>
> Iljitsch
>

From iljitsch@muada.com  Tue Sep 15 08:46:40 2009
Return-Path: <iljitsch@muada.com>
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 F39963A6BA7 for <behave@core3.amsl.com>; Tue, 15 Sep 2009 08:46:39 -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 yysV-19brnXV for <behave@core3.amsl.com>; Tue, 15 Sep 2009 08:46:39 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2]) by core3.amsl.com (Postfix) with ESMTP id B56473A6BA3 for <behave@ietf.org>; Tue, 15 Sep 2009 08:46:38 -0700 (PDT)
Received: from [IPv6:2001:720:410:100f:223:32ff:fec4:ba94] ([IPv6:2001:720:410:100f:223:32ff:fec4:ba94]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id n8FFlHbi082274 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 15 Sep 2009 17:47:17 +0200 (CEST) (envelope-from iljitsch@muada.com)
Mime-Version: 1.0 (Apple Message framework v1076)
Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <a7c8d0a30909150838s230397d9r3cbffb5df6097b76@mail.gmail.com>
Date: Tue, 15 Sep 2009 17:47:21 +0200
Content-Transfer-Encoding: 7bit
Message-Id: <273D4852-D26C-497E-A034-2C3EE4908660@muada.com>
References: <a7c8d0a30909150630i29d535bbhf3089fdfecffa328@mail.gmail.com> <7CB993A6-829C-46CC-A74C-7DBF7CFE88C6@muada.com> <a7c8d0a30909150838s230397d9r3cbffb5df6097b76@mail.gmail.com>
To: Zhen Cao <caozhenpku@gmail.com>
X-Mailer: Apple Mail (2.1076)
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Comments on NAT64 draft
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/mail-archive/web/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>
X-List-Received-Date: Tue, 15 Sep 2009 15:46:40 -0000

On 15 Sep 2009, at 17:38 , Zhen Cao wrote:

>> Not sure if we already discuss this in the draft, but we don't want  
>> the
>> situation where a translator uses different IPv4 addresses for  
>> translating
>> different sessions from the same IPv6 host because it breaks STUN.

> I am not talking about the one ipv6 mapping to multiple ipv4
> addresses, and am assuming one ipv6 host maps to one ipv4 address.

Well, in that case there is no problem with the translation of  
fragments without reassembly or setting up state, right?

> If an in-the-middle fragmented packet arrives, we cannot create the
> mapping entry from <Y', y> to <T, t>. Do you mean just translate it
> first and wait for the first fragment to fill in the entry?

I assume Y' = the IPv6 source address, y = the source port, T is the  
destination address and t the destination port.

You are right that it won't be possible to map a non-first fragment to  
a session because it could match multiple sessions. However, we can  
still translate it as long as we know the IPv4 source address that we  
need to use. The IPv4 destination address can be derived from the IPv6  
destination address. The only thing we need for the translation is  
addresses and an identifier value that is the same for all fragments.

From petithug@acm.org  Tue Sep 15 13:01:43 2009
Return-Path: <petithug@acm.org>
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 8F99428C25D for <behave@core3.amsl.com>; Tue, 15 Sep 2009 13:01:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.335
X-Spam-Level: 
X-Spam-Status: No, score=-101.335 tagged_above=-999 required=5 tests=[AWL=-0.559, BAYES_05=-1.11, 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 qgkCjPpTHvSk for <behave@core3.amsl.com>; Tue, 15 Sep 2009 13:01:42 -0700 (PDT)
Received: from server.implementers.org (server.implementers.org [69.55.225.91]) by core3.amsl.com (Postfix) with ESMTP id 6EBE928C258 for <behave@ietf.org>; Tue, 15 Sep 2009 13:01:42 -0700 (PDT)
Received: by server.implementers.org (Postfix, from userid 1001) id EC0BADBCC08A; Tue, 15 Sep 2009 20:02:28 +0000 (UTC)
Received: from [192.168.2.3] (server.implementers.org [127.0.0.1]) by server.implementers.org (Postfix) with ESMTPA id 9A989DBCC088; Tue, 15 Sep 2009 20:02:18 +0000 (UTC)
Message-ID: <4AAFF2C5.1010103@acm.org>
Date: Tue, 15 Sep 2009 13:02:13 -0700
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla-Thunderbird 2.0.0.22 (X11/20090701)
MIME-Version: 1.0
To: Peter Livesey <peter.livesey@tandberg.com>
References: <C67BCA34F23E804199B464EAF3BE55DF06439A68@oslexcp2.eu.tandberg.int>
In-Reply-To: <C67BCA34F23E804199B464EAF3BE55DF06439A68@oslexcp2.eu.tandberg.int>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Discusses regarding security mechanism usage for TURN
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/mail-archive/web/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>
X-List-Received-Date: Tue, 15 Sep 2009 20:01:43 -0000

Peter Livesey wrote:
> It's only an *Internet* protocol if it has many implementations which
> are widely used. If people/vendors are reluctant to implement it until
> the drafts become a RFC then delaying it over a MUST/SHOULD seems self
> defeating.
> 
> If it's a SHOULD then vendors can decide if their implementations make
> it a MUST by always challenging  or leave it up to the administrators of
> their equipment to decide (via configuration), based on the deployment
> case.

Most software developers will use anything they can to not implement stuff, and
for them SHOULD = do not bother.  I saw it happen so many time that it is not
funny anymore.  Making it configurable is OK but having two different products,
one for the Internet and another for the walled gardens is even better.  The
important part is been able to blame the sysadmins when bad things _will_ happen.

So far I didn't see one single use case where a TURN server on the *Internet*
would need disabled authentication.

> 
>  
> -----Original Message-----
> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On Behalf
> Of Marc Petit-Huguenin
> Sent: 14 September 2009 17:01
> To: matthew@matthew.at
> Cc: Behave WG; Tim Polk
> Subject: Re: [BEHAVE] Discusses regarding security mechanism usage for
> TURN
> 
> Matthew Kaufman wrote:
>> Magnus Westerlund wrote:
>>> ...
>>> So if I understand this correctly, this deployment is exactly such a
> one
>>> that will be vulnerable to the security threats. You have some TURN
>>> servers operated by Adobe, they are located in the Internet as viewed
>>> from the client perspective. Thus, they are not fulfilling even the
>>> exception case for using security based on TURN server policies with
>>> restricting the location of the clients to the internal domain.
>>>
>>> So running without security in this case do leave TURN wide open to
> the
>>> threats listed in the security consideration.
>>> ...
>>>  
>>> Well, the argument is operational and does not appear to me to take
> the
>>> security issues with TURN itself into consideration.
>>>
>>> Am I misunderstanding the deployment in the flash case?
>>>
>>>   
>> Yes. The deployment in the Flash case is *not* that Adobe provides
>> public TURN servers for use by Flash Player. Rather, Adobe has made it
>> possible for corporate IT departments to deploy Flash Player along
> with
>> a static configuration file which points them at a TURN server
> operated
>> by that IT department which is only accessible from the inside network
>> and which can only initiate sessions towards outside addresses. The
> TURN
>> server is secured and operated in parallel with an equally
>> unauthenticated-but-secured HTTP proxy.
> 
> IT department can deploy whatever they want, with whatever security
> level they
> want on an inside network.  But TURN, which is an *Internet* protocol,
> must be
> secure.
> 
> I fully support Magnus text.
> 


-- 
Marc Petit-Huguenin
Personal email: marc@petit-huguenin.org
Professional email: petithug@acm.org
Blog: http://blog.marc.petit-huguenin.org

From simon.perreault@viagenie.ca  Tue Sep 15 13:15:33 2009
Return-Path: <simon.perreault@viagenie.ca>
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 E451028C1F3 for <behave@core3.amsl.com>; Tue, 15 Sep 2009 13:15:33 -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.075,  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 OZZqwrjqmQTH for <behave@core3.amsl.com>; Tue, 15 Sep 2009 13:15:33 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by core3.amsl.com (Postfix) with ESMTP id A536D28C1A3 for <behave@ietf.org>; Tue, 15 Sep 2009 13:15:32 -0700 (PDT)
Received: by jazz.viagenie.ca (Postfix, from userid 8) id 0512529E1614; Tue, 15 Sep 2009 16:16:20 -0400 (EDT)
Received: from ringo.viagenie.ca (ringo.viagenie.ca [IPv6:2620:0:230:c000::67]) by jazz.viagenie.ca (Postfix) with ESMTP id EEF7A29E1610; Tue, 15 Sep 2009 16:16:19 -0400 (EDT)
From: Simon Perreault <simon.perreault@viagenie.ca>
Organization: =?iso-8859-1?q?Viag=E9nie?=
To: behave@ietf.org
Date: Tue, 15 Sep 2009 16:16:16 -0400
User-Agent: KMail/1.12.0 (Linux/2.6.30.5-43.fc11.x86_64; KDE/4.3.0; x86_64; ; )
References: <C67BCA34F23E804199B464EAF3BE55DF06439A68@oslexcp2.eu.tandberg.int> <4AAFF2C5.1010103@acm.org>
In-Reply-To: <4AAFF2C5.1010103@acm.org>
MIME-Version: 1.0
Content-Type: Text/Plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <200909151616.16445.simon.perreault@viagenie.ca>
Cc: Peter Livesey <peter.livesey@tandberg.com>
Subject: Re: [BEHAVE] Discusses regarding security mechanism usage for TURN
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/mail-archive/web/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>
X-List-Received-Date: Tue, 15 Sep 2009 20:15:34 -0000

The proposed text doesn't talk about what needs to be implemented, it talks 
about what goes on the wire.

I'd be fine with a MUST implement, SHOULD use.

The proposed text says MUST implement, MUST use.


On Tuesday 15 September 2009 16:02:13 Marc Petit-Huguenin wrote:
> So far I didn't see one single use case where a TURN server on the
> *Internet* would need disabled authentication.

           +-------<Internet>-----------+
           |                            |
        +-----+                 +-------------+
--------| NAT |-----------------| TURN server |------------------------
        +-----+                 +-------------+
           |                            |
           +-----<Private network>------+

Authentication is not needed on the private side. It is pointless to mandate 
it.

If the proposed text's "MUST use" only applies to the Internet side, it needs 
to be more explicit.

Simon
-- 
DNS64 open-source   --> http://ecdysis.viagenie.ca
STUN/TURN server    --> http://numb.viagenie.ca
vCard 4.0           --> http://www.vcarddav.org

From petithug@acm.org  Tue Sep 15 13:50:15 2009
Return-Path: <petithug@acm.org>
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 02CD03A6ADE for <behave@core3.amsl.com>; Tue, 15 Sep 2009 13:50:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.009
X-Spam-Level: 
X-Spam-Status: No, score=-102.009 tagged_above=-999 required=5 tests=[AWL=0.256, 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 nAt0NY1CVpZv for <behave@core3.amsl.com>; Tue, 15 Sep 2009 13:50:14 -0700 (PDT)
Received: from server.implementers.org (server.implementers.org [69.55.225.91]) by core3.amsl.com (Postfix) with ESMTP id 06F953A6AB7 for <behave@ietf.org>; Tue, 15 Sep 2009 13:50:13 -0700 (PDT)
Received: by server.implementers.org (Postfix, from userid 1001) id 5E2DD6C984BE; Tue, 15 Sep 2009 20:51:01 +0000 (UTC)
Received: from [192.168.2.3] (server.implementers.org [127.0.0.1]) by server.implementers.org (Postfix) with ESMTPA id 906216C984B6; Tue, 15 Sep 2009 20:50:59 +0000 (UTC)
Message-ID: <4AAFFE2D.2030805@acm.org>
Date: Tue, 15 Sep 2009 13:50:53 -0700
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla-Thunderbird 2.0.0.22 (X11/20090701)
MIME-Version: 1.0
To: Simon Perreault <simon.perreault@viagenie.ca>
References: <C67BCA34F23E804199B464EAF3BE55DF06439A68@oslexcp2.eu.tandberg.int> <4AAFF2C5.1010103@acm.org> <200909151616.16445.simon.perreault@viagenie.ca>
In-Reply-To: <200909151616.16445.simon.perreault@viagenie.ca>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Peter Livesey <peter.livesey@tandberg.com>, behave@ietf.org
Subject: Re: [BEHAVE] Discusses regarding security mechanism usage for TURN
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/mail-archive/web/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>
X-List-Received-Date: Tue, 15 Sep 2009 20:50:15 -0000

Simon Perreault wrote:
> The proposed text doesn't talk about what needs to be implemented, it talks 
> about what goes on the wire.
> 
> I'd be fine with a MUST implement, SHOULD use.
> 
> The proposed text says MUST implement, MUST use.
> 
> 
> On Tuesday 15 September 2009 16:02:13 Marc Petit-Huguenin wrote:
>> So far I didn't see one single use case where a TURN server on the
>> *Internet* would need disabled authentication.
> 
>            +-------<Internet>-----------+
>            |                            |
>         +-----+                 +-------------+
> --------| NAT |-----------------| TURN server |------------------------
>         +-----+                 +-------------+
>            |                            |
>            +-----<Private network>------+
> 
> Authentication is not needed on the private side. It is pointless to mandate 
> it.
> 
> If the proposed text's "MUST use" only applies to the Internet side, it needs 
> to be more explicit.

Well, your diagram shows that the TURN server is not on the Internet so why an
Internet protocol should apply to it?  At best it is an Internet host (the side
connected to the Internet), and should follow RFC 1122 but not much more can be
said about this.

I would add that the TURN spec specifically talk about a TURN server with the
two sides on the Internet:

"This relay typically sits in the public Internet and relays packets between two
hosts that both sit behind NATs."

Some people probably have a need for a "TURN" server that works like your
diagram, but it should defined be, IMO, in a different spec (or better, a
different SDO).


-- 
Marc Petit-Huguenin
Personal email: marc@petit-huguenin.org
Professional email: petithug@acm.org
Blog: http://blog.marc.petit-huguenin.org

From matthew@matthew.at  Tue Sep 15 14:18:20 2009
Return-Path: <matthew@matthew.at>
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 B18023A6812 for <behave@core3.amsl.com>; Tue, 15 Sep 2009 14:18:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.91
X-Spam-Level: 
X-Spam-Status: No, score=-0.91 tagged_above=-999 required=5 tests=[AWL=0.520,  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 HL8GrWIdStk5 for <behave@core3.amsl.com>; Tue, 15 Sep 2009 14:18:20 -0700 (PDT)
Received: from where.matthew.at (where.matthew.at [198.202.199.1]) by core3.amsl.com (Postfix) with ESMTP id 021473A68EE for <behave@ietf.org>; Tue, 15 Sep 2009 14:18:20 -0700 (PDT)
Received: from [10.10.155.2] (unknown [10.10.155.2]) by where.matthew.at (Postfix) with ESMTP id EEA8B148074; Tue, 15 Sep 2009 14:19:05 -0700 (PDT)
Message-ID: <4AB004C9.1070708@matthew.at>
Date: Tue, 15 Sep 2009 14:19:05 -0700
From: Matthew Kaufman <matthew@matthew.at>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Marc Petit-Huguenin <petithug@acm.org>
References: <C67BCA34F23E804199B464EAF3BE55DF06439A68@oslexcp2.eu.tandberg.int>	<4AAFF2C5.1010103@acm.org>	<200909151616.16445.simon.perreault@viagenie.ca> <4AAFFE2D.2030805@acm.org>
In-Reply-To: <4AAFFE2D.2030805@acm.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Peter Livesey <peter.livesey@tandberg.com>, behave@ietf.org
Subject: Re: [BEHAVE] Discusses regarding security mechanism usage for TURN
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/mail-archive/web/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>
X-List-Received-Date: Tue, 15 Sep 2009 21:18:20 -0000

Marc Petit-Huguenin wrote:
> Simon Perreault wrote:
>   
>> The proposed text doesn't talk about what needs to be implemented, it talks 
>> about what goes on the wire.
>>
>> I'd be fine with a MUST implement, SHOULD use.
>>
>> The proposed text says MUST implement, MUST use.
>>
>>
>> On Tuesday 15 September 2009 16:02:13 Marc Petit-Huguenin wrote:
>>     
>>> So far I didn't see one single use case where a TURN server on the
>>> *Internet* would need disabled authentication.
>>>       
>>            +-------<Internet>-----------+
>>            |                            |
>>         +-----+                 +-------------+
>> --------| NAT |-----------------| TURN server |------------------------
>>         +-----+                 +-------------+
>>            |                            |
>>            +-----<Private network>------+
>>
>> Authentication is not needed on the private side. It is pointless to mandate 
>> it.
>>
>> If the proposed text's "MUST use" only applies to the Internet side, it needs 
>> to be more explicit.
>>     
>
> Well, your diagram shows that the TURN server is not on the Internet so why an
> Internet protocol should apply to it?  At best it is an Internet host (the side
> connected to the Internet), and should follow RFC 1122 but not much more can be
> said about this.
>
> I would add that the TURN spec specifically talk about a TURN server with the
> two sides on the Internet:
>
> "This relay typically sits in the public Internet and relays packets between two
> hosts that both sit behind NATs."
>
> Some people probably have a need for a "TURN" server that works like your
> diagram, but it should defined be, IMO, in a different spec (or better, a
> different SDO).
>
>
>   

BEHAVE's charter is to work on NAT traversal. TURN has the opportunity 
to be a fairly general UDP-over-UDP relay protocol usable for NAT 
traversal in both the "TURN server on public Internet" and "TURN server 
sitting in parallel with non-compliant NAT" cases. Or, by requiring 
"MUST" here, TURN can be made less applicable for the latter case.

If we wanted to ignore everything that isn't "on the public Internet", 
then I suppose BEHAVE wouldn't have any work to do, as everything behind 
a NAT isn't. I think you may be confusing "the public Internet" and 
"those networks over which IETF-standardized protocols might run", as 
the latter is a much larger scope, and most definitely within both 
IETF's scope and the BEHAVE WG's charter.

Matthew Kaufman

From petithug@acm.org  Tue Sep 15 14:54:48 2009
Return-Path: <petithug@acm.org>
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 A62CC28C11F for <behave@core3.amsl.com>; Tue, 15 Sep 2009 14:54:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.038
X-Spam-Level: 
X-Spam-Status: No, score=-102.038 tagged_above=-999 required=5 tests=[AWL=0.227, 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 gbgEQyZ2T-Ui for <behave@core3.amsl.com>; Tue, 15 Sep 2009 14:54:47 -0700 (PDT)
Received: from server.implementers.org (server.implementers.org [69.55.225.91]) by core3.amsl.com (Postfix) with ESMTP id AF4C43A67D8 for <behave@ietf.org>; Tue, 15 Sep 2009 14:54:47 -0700 (PDT)
Received: by server.implementers.org (Postfix, from userid 1001) id C4E8EDBCC08A; Tue, 15 Sep 2009 21:55:33 +0000 (UTC)
Received: from [192.168.2.3] (server.implementers.org [127.0.0.1]) by server.implementers.org (Postfix) with ESMTPA id 09D67DBCC088; Tue, 15 Sep 2009 21:55:29 +0000 (UTC)
Message-ID: <4AB00D4A.40108@acm.org>
Date: Tue, 15 Sep 2009 14:55:22 -0700
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla-Thunderbird 2.0.0.22 (X11/20090701)
MIME-Version: 1.0
To: matthew@matthew.at
References: <C67BCA34F23E804199B464EAF3BE55DF06439A68@oslexcp2.eu.tandberg.int>	<4AAFF2C5.1010103@acm.org>	<200909151616.16445.simon.perreault@viagenie.ca> <4AAFFE2D.2030805@acm.org> <4AB004C9.1070708@matthew.at>
In-Reply-To: <4AB004C9.1070708@matthew.at>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Peter Livesey <peter.livesey@tandberg.com>, behave@ietf.org
Subject: Re: [BEHAVE] Discusses regarding security mechanism usage for TURN
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/mail-archive/web/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>
X-List-Received-Date: Tue, 15 Sep 2009 21:54:48 -0000

Matthew Kaufman wrote:
> Marc Petit-Huguenin wrote:
>> Simon Perreault wrote:
>>  
>>> The proposed text doesn't talk about what needs to be implemented, it
>>> talks about what goes on the wire.
>>>
>>> I'd be fine with a MUST implement, SHOULD use.
>>>
>>> The proposed text says MUST implement, MUST use.
>>>
>>>
>>> On Tuesday 15 September 2009 16:02:13 Marc Petit-Huguenin wrote:
>>>    
>>>> So far I didn't see one single use case where a TURN server on the
>>>> *Internet* would need disabled authentication.
>>>>       
>>>            +-------<Internet>-----------+
>>>            |                            |
>>>         +-----+                 +-------------+
>>> --------| NAT |-----------------| TURN server |------------------------
>>>         +-----+                 +-------------+
>>>            |                            |
>>>            +-----<Private network>------+
>>>
>>> Authentication is not needed on the private side. It is pointless to
>>> mandate it.
>>>
>>> If the proposed text's "MUST use" only applies to the Internet side,
>>> it needs to be more explicit.
>>>     
>>
>> Well, your diagram shows that the TURN server is not on the Internet
>> so why an
>> Internet protocol should apply to it?  At best it is an Internet host
>> (the side
>> connected to the Internet), and should follow RFC 1122 but not much
>> more can be
>> said about this.
>>
>> I would add that the TURN spec specifically talk about a TURN server
>> with the
>> two sides on the Internet:
>>
>> "This relay typically sits in the public Internet and relays packets
>> between two
>> hosts that both sit behind NATs."
>>
>> Some people probably have a need for a "TURN" server that works like your
>> diagram, but it should defined be, IMO, in a different spec (or better, a
>> different SDO).
>>
>>
>>   
> 
> BEHAVE's charter is to work on NAT traversal. 
> TURN has the opportunity
> to be a fairly general UDP-over-UDP relay protocol usable for NAT
> traversal in both the "TURN server on public Internet" and "TURN server
> sitting in parallel with non-compliant NAT" cases. Or, by requiring
> "MUST" here, TURN can be made less applicable for the latter case.

Then call NRUT the version of TURN that does not do authentication, and I will
have no other objection.

> 
> If we wanted to ignore everything that isn't "on the public Internet",
> then I suppose BEHAVE wouldn't have any work to do, as everything behind
> a NAT isn't. I think you may be confusing "the public Internet" and
> "those networks over which IETF-standardized protocols might run", as
> the latter is a much larger scope, and most definitely within both
> IETF's scope and the BEHAVE WG's charter.

I am not confusing anything, and "public Internet" is a pleonasm.

Your computer is no more connected to the Internet than the faucet in my kitchen
is connected to the Almaden Reservoir.

-- 
Marc Petit-Huguenin
Personal email: marc@petit-huguenin.org
Professional email: petithug@acm.org
Blog: http://blog.marc.petit-huguenin.org

From petithug@acm.org  Tue Sep 15 16:20:20 2009
Return-Path: <petithug@acm.org>
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 B29013A682C for <behave@core3.amsl.com>; Tue, 15 Sep 2009 16:20:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.061
X-Spam-Level: 
X-Spam-Status: No, score=-102.061 tagged_above=-999 required=5 tests=[AWL=0.204, 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 H0H77GRHfnMn for <behave@core3.amsl.com>; Tue, 15 Sep 2009 16:20:20 -0700 (PDT)
Received: from server.implementers.org (server.implementers.org [69.55.225.91]) by core3.amsl.com (Postfix) with ESMTP id 0AA8C3A67F1 for <behave@ietf.org>; Tue, 15 Sep 2009 16:20:20 -0700 (PDT)
Received: by server.implementers.org (Postfix, from userid 1001) id 0D9AF6C984BC; Tue, 15 Sep 2009 23:21:07 +0000 (UTC)
Received: from [192.168.2.3] (server.implementers.org [127.0.0.1]) by server.implementers.org (Postfix) with ESMTPA id 103AB6C984B6; Tue, 15 Sep 2009 23:21:04 +0000 (UTC)
Message-ID: <4AB0215F.1080407@acm.org>
Date: Tue, 15 Sep 2009 16:21:03 -0700
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla-Thunderbird 2.0.0.22 (X11/20090701)
MIME-Version: 1.0
To: Simon Perreault <simon.perreault@viagenie.ca>
References: <C67BCA34F23E804199B464EAF3BE55DF06439A68@oslexcp2.eu.tandberg.int> <4AAFF2C5.1010103@acm.org> <200909151616.16445.simon.perreault@viagenie.ca>
In-Reply-To: <200909151616.16445.simon.perreault@viagenie.ca>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Peter Livesey <peter.livesey@tandberg.com>, behave@ietf.org
Subject: Re: [BEHAVE] Discusses regarding security mechanism usage for TURN
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/mail-archive/web/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>
X-List-Received-Date: Tue, 15 Sep 2009 23:20:20 -0000

OK, let's be practical.  What about saying that if the client request comes from
a non RFC 1918 IP address, the request MUST be authenticated? (and adding the
equivalent for IPv6).

Simon Perreault wrote:
> The proposed text doesn't talk about what needs to be implemented, it talks 
> about what goes on the wire.
> 
> I'd be fine with a MUST implement, SHOULD use.
> 
> The proposed text says MUST implement, MUST use.
> 
> 
> On Tuesday 15 September 2009 16:02:13 Marc Petit-Huguenin wrote:
>> So far I didn't see one single use case where a TURN server on the
>> *Internet* would need disabled authentication.
> 
>            +-------<Internet>-----------+
>            |                            |
>         +-----+                 +-------------+
> --------| NAT |-----------------| TURN server |------------------------
>         +-----+                 +-------------+
>            |                            |
>            +-----<Private network>------+
> 
> Authentication is not needed on the private side. It is pointless to mandate 
> it.
> 
> If the proposed text's "MUST use" only applies to the Internet side, it needs 
> to be more explicit.
> 
> Simon


-- 
Marc Petit-Huguenin
Personal email: marc@petit-huguenin.org
Professional email: petithug@acm.org
Blog: http://blog.marc.petit-huguenin.org

From marc.blanchet@viagenie.ca  Tue Sep 15 16:30:16 2009
Return-Path: <marc.blanchet@viagenie.ca>
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 37B2A3A6AA1 for <behave@core3.amsl.com>; Tue, 15 Sep 2009 16:30:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.95
X-Spam-Level: 
X-Spam-Status: No, score=-1.95 tagged_above=-999 required=5 tests=[AWL=0.650,  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 6WkTuPEpMsMb for <behave@core3.amsl.com>; Tue, 15 Sep 2009 16:30:14 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by core3.amsl.com (Postfix) with ESMTP id 290D73A6405 for <behave@ietf.org>; Tue, 15 Sep 2009 16:30:14 -0700 (PDT)
Received: by jazz.viagenie.ca (Postfix, from userid 8) id 6A01429E1610; Tue, 15 Sep 2009 19:31:01 -0400 (EDT)
Message-ID: <4AB023B3.2010009@viagenie.ca>
Date: Tue, 15 Sep 2009 19:30:59 -0400
From: Marc Blanchet <marc.blanchet@viagenie.ca>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Marc Petit-Huguenin <petithug@acm.org>
References: <C67BCA34F23E804199B464EAF3BE55DF06439A68@oslexcp2.eu.tandberg.int>	<4AAFF2C5.1010103@acm.org>	<200909151616.16445.simon.perreault@viagenie.ca> <4AB0215F.1080407@acm.org>
In-Reply-To: <4AB0215F.1080407@acm.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: Peter Livesey <peter.livesey@tandberg.com>, behave@ietf.org
Subject: Re: [BEHAVE] Discusses regarding security mechanism usage for TURN
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/mail-archive/web/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>
X-List-Received-Date: Tue, 15 Sep 2009 23:30:16 -0000

Marc Petit-Huguenin a écrit :
> OK, let's be practical.  What about saying that if the client request comes from
> a non RFC 1918 IP address, the request MUST be authenticated? (and adding the
> equivalent for IPv6).

the problem with this proposal is that the source IP address does not 
tell if you are on public or private or ... These days, broadband 
providers are deploying RFC1918 to the subscribers... In fact, I think 
the wording should instead be related to the deployment scenario. This 
is not the first case in IETF for this kind of scenarios. I'm sure we 
can borrow some text from other protocols on this.

Marc.

> 
> Simon Perreault wrote:
>> The proposed text doesn't talk about what needs to be implemented, it talks 
>> about what goes on the wire.
>>
>> I'd be fine with a MUST implement, SHOULD use.
>>
>> The proposed text says MUST implement, MUST use.
>>
>>
>> On Tuesday 15 September 2009 16:02:13 Marc Petit-Huguenin wrote:
>>> So far I didn't see one single use case where a TURN server on the
>>> *Internet* would need disabled authentication.
>>            +-------<Internet>-----------+
>>            |                            |
>>         +-----+                 +-------------+
>> --------| NAT |-----------------| TURN server |------------------------
>>         +-----+                 +-------------+
>>            |                            |
>>            +-----<Private network>------+
>>
>> Authentication is not needed on the private side. It is pointless to mandate 
>> it.
>>
>> If the proposed text's "MUST use" only applies to the Internet side, it needs 
>> to be more explicit.
>>
>> Simon
> 
> 


From petithug@acm.org  Tue Sep 15 16:46:32 2009
Return-Path: <petithug@acm.org>
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 365233A690C for <behave@core3.amsl.com>; Tue, 15 Sep 2009 16:46:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.079
X-Spam-Level: 
X-Spam-Status: No, score=-102.079 tagged_above=-999 required=5 tests=[AWL=0.186, 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 DsDnxy0RBXzV for <behave@core3.amsl.com>; Tue, 15 Sep 2009 16:46:31 -0700 (PDT)
Received: from server.implementers.org (server.implementers.org [69.55.225.91]) by core3.amsl.com (Postfix) with ESMTP id 5BD983A681B for <behave@ietf.org>; Tue, 15 Sep 2009 16:46:31 -0700 (PDT)
Received: by server.implementers.org (Postfix, from userid 1001) id 359766C984BC; Tue, 15 Sep 2009 23:47:19 +0000 (UTC)
Received: from [192.168.2.3] (server.implementers.org [127.0.0.1]) by server.implementers.org (Postfix) with ESMTPA id 6CB236C984B6; Tue, 15 Sep 2009 23:47:17 +0000 (UTC)
Message-ID: <4AB02784.8060604@acm.org>
Date: Tue, 15 Sep 2009 16:47:16 -0700
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla-Thunderbird 2.0.0.22 (X11/20090701)
MIME-Version: 1.0
To: Marc Blanchet <marc.blanchet@viagenie.ca>
References: <C67BCA34F23E804199B464EAF3BE55DF06439A68@oslexcp2.eu.tandberg.int>	<4AAFF2C5.1010103@acm.org>	<200909151616.16445.simon.perreault@viagenie.ca> <4AB0215F.1080407@acm.org> <4AB023B3.2010009@viagenie.ca>
In-Reply-To: <4AB023B3.2010009@viagenie.ca>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Cc: Peter Livesey <peter.livesey@tandberg.com>, behave@ietf.org
Subject: Re: [BEHAVE] Discusses regarding security mechanism usage for TURN
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/mail-archive/web/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>
X-List-Received-Date: Tue, 15 Sep 2009 23:46:32 -0000

Marc Blanchet wrote:
> Marc Petit-Huguenin a écrit :
>> OK, let's be practical.  What about saying that if the client request
>> comes from
>> a non RFC 1918 IP address, the request MUST be authenticated? (and
>> adding the
>> equivalent for IPv6).
> 
> the problem with this proposal is that the source IP address does not
> tell if you are on public or private or ... These days, broadband
> providers are deploying RFC1918 to the subscribers...

I am not sure to understand why this scenario would be a problem.  If the TURN
server is outside the provider's network, then there will be authentication.  If
inside, then no authentication but it is fine because this is all the provider's
customers.  Or is there something I missed?

> In fact, I think
> the wording should instead be related to the deployment scenario. This
> is not the first case in IETF for this kind of scenarios. I'm sure we
> can borrow some text from other protocols on this.
> 

And in fact I just realized that a TURN client (on a private or public network)
that succeed to connect to a TURN server on a public network without
authentication should better disconnect immediately.  I do not want my customers
to be investigated when the TURN server will be seized to find who is using it
to anonymously stream illegal stuff.

-- 
Marc Petit-Huguenin
Personal email: marc@petit-huguenin.org
Professional email: petithug@acm.org
Blog: http://blog.marc.petit-huguenin.org

From dwing@cisco.com  Tue Sep 15 17:15:12 2009
Return-Path: <dwing@cisco.com>
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 8722A3A65A6 for <behave@core3.amsl.com>; Tue, 15 Sep 2009 17:15:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[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 IeD8rJNlCxW8 for <behave@core3.amsl.com>; Tue, 15 Sep 2009 17:15:11 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id AA0813A67A3 for <behave@ietf.org>; Tue, 15 Sep 2009 17:15:11 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqgEAJfLr0qrR7MV/2dsb2JhbACLErtgiEwBkDEFhBc
X-IronPort-AV: E=Sophos;i="4.44,393,1249257600"; d="scan'208";a="389507500"
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-6.cisco.com with ESMTP; 16 Sep 2009 00:15:58 +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 n8G0FwBP011431 for <behave@ietf.org>; Tue, 15 Sep 2009 17:15:58 -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.14.3) with ESMTP id n8G0Fwgg008654 for <behave@ietf.org>; Wed, 16 Sep 2009 00:15:58 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 15 Sep 2009 17:15:57 -0700
Received: from dwingwxp01 ([10.32.240.198]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 15 Sep 2009 17:15:57 -0700
From: "Dan Wing" <dwing@cisco.com>
To: <behave@ietf.org>
Date: Tue, 15 Sep 2009 17:15:57 -0700
Message-ID: <0c5f01ca3662$dd2e1480$c6f0200a@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Aco2Ytz5xvQTNmuVR3GcIq4C0rU9mw==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-OriginalArrivalTime: 16 Sep 2009 00:15:57.0693 (UTC) FILETIME=[DD0F1AD0:01CA3662]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=295; t=1253060158; x=1253924158; 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=20teleconference,=20Wednesday,=20Septem ber=2016,=207am-9am=20Pacific=20Time |Sender:=20; bh=74x7Kg8pyUsd+Fc8+e0DO5kENA0IsyGN2GeK9k7XyLk=; b=N5zkxJQmD5x2blLDGn63hBXQtQyMvr6bDgw+tSlZEoKLgKb4J9kb3LAxB/ Xs26MVxD353bX8bxUd9doqm1GV3VAHxzZ3mCkaRy0kzj8vsbXVTM410NlJgi xQr2GfWKsJ5Yt1GXC67y8O/rNpozyshnqmvcBz3eMV/zO0XpXXVBE=;
Authentication-Results: sj-dkim-1; header.From=dwing@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; ); 
Subject: [BEHAVE] Interim teleconference, Wednesday, September 16, 7am-9am Pacific 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/mail-archive/web/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>
X-List-Received-Date: Wed, 16 Sep 2009 00:15:12 -0000

We are having another interim teleconference tomorrow morning focused on 6/4
translation.  We have asked document authors to provide a list of open issues
for their documents.

Agenda and dialin information is available at:
  http://trac.tools.ietf.org/wg/behave/trac/wiki/WikiStart

-d


From marc.blanchet@viagenie.ca  Tue Sep 15 18:00:46 2009
Return-Path: <marc.blanchet@viagenie.ca>
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 E660B3A6A94 for <behave@core3.amsl.com>; Tue, 15 Sep 2009 18:00:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.167
X-Spam-Level: 
X-Spam-Status: No, score=-2.167 tagged_above=-999 required=5 tests=[AWL=0.433,  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 OAfROftDRoNN for <behave@core3.amsl.com>; Tue, 15 Sep 2009 18:00:46 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by core3.amsl.com (Postfix) with ESMTP id 02D413A681A for <behave@ietf.org>; Tue, 15 Sep 2009 18:00:45 -0700 (PDT)
Received: by jazz.viagenie.ca (Postfix, from userid 8) id 0479A29E1612; Tue, 15 Sep 2009 21:01:31 -0400 (EDT)
Message-ID: <4AB038E2.2070403@viagenie.ca>
Date: Tue, 15 Sep 2009 21:01:22 -0400
From: Marc Blanchet <marc.blanchet@viagenie.ca>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Marc Petit-Huguenin <petithug@acm.org>
References: <C67BCA34F23E804199B464EAF3BE55DF06439A68@oslexcp2.eu.tandberg.int>	<4AAFF2C5.1010103@acm.org>	<200909151616.16445.simon.perreault@viagenie.ca> <4AB0215F.1080407@acm.org> <4AB023B3.2010009@viagenie.ca> <4AB02784.8060604@acm.org>
In-Reply-To: <4AB02784.8060604@acm.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: Peter Livesey <peter.livesey@tandberg.com>, behave@ietf.org
Subject: Re: [BEHAVE] Discusses regarding security mechanism usage for TURN
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/mail-archive/web/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>
X-List-Received-Date: Wed, 16 Sep 2009 01:00:47 -0000

Marc Petit-Huguenin a écrit :
> Marc Blanchet wrote:
>> Marc Petit-Huguenin a écrit :
>>> OK, let's be practical.  What about saying that if the client request
>>> comes from
>>> a non RFC 1918 IP address, the request MUST be authenticated? (and
>>> adding the
>>> equivalent for IPv6).
>> the problem with this proposal is that the source IP address does not
>> tell if you are on public or private or ... These days, broadband
>> providers are deploying RFC1918 to the subscribers...
> 
> I am not sure to understand why this scenario would be a problem.

What I'm just saying is that the assumption that a type of IP address 
(RFC1918 or non-RFC1918) does not tell you anything about the location 
of the node. Therefore, one can not use this criteria for deciding to 
use or not to use authentication.

Marc.


>  If the TURN
> server is outside the provider's network, then there will be authentication.  If
> inside, then no authentication but it is fine because this is all the provider's
> customers.  Or is there something I missed?
> 
>> In fact, I think
>> the wording should instead be related to the deployment scenario. This
>> is not the first case in IETF for this kind of scenarios. I'm sure we
>> can borrow some text from other protocols on this.
>>
> 
> And in fact I just realized that a TURN client (on a private or public network)
> that succeed to connect to a TURN server on a public network without
> authentication should better disconnect immediately.  I do not want my customers
> to be investigated when the TURN server will be seized to find who is using it
> to anonymously stream illegal stuff.
> 


From xing@cernet.edu.cn  Tue Sep 15 18:17:47 2009
Return-Path: <xing@cernet.edu.cn>
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 4C7CF3A65A6 for <behave@core3.amsl.com>; Tue, 15 Sep 2009 18:17:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.758
X-Spam-Level: 
X-Spam-Status: No, score=0.758 tagged_above=-999 required=5 tests=[AWL=0.661,  BAYES_00=-2.599, FH_HAS_XAIMC=2.696]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m5RCYYbdQ+c0 for <behave@core3.amsl.com>; Tue, 15 Sep 2009 18:17:46 -0700 (PDT)
Received: from cernet.edu.cn (sea.net.edu.cn [202.112.3.66]) by core3.amsl.com (Postfix) with SMTP id CDE273A6825 for <behave@ietf.org>; Tue, 15 Sep 2009 18:17:45 -0700 (PDT)
Received: from [10.140.95.191]([117.136.0.184]) by cernet.edu.cn(AIMC 3.2.0.0) with SMTP id jm104ab04a31; Wed, 16 Sep 2009 09:18:31 +0800
Message-ID: <4AB039D1.7080808@cernet.edu.cn>
Date: Wed, 16 Sep 2009 09:05:21 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: "Xiao, Lin (NSN - CN/Beijing)" <lin.xiao@nsn.com>
References: <5D84FDD8D5DC8646B9F73CF1EFD1BFA4BB88C0@CNBEEXC007.nsn-intra.net>
In-Reply-To: <5D84FDD8D5DC8646B9F73CF1EFD1BFA4BB88C0@CNBEEXC007.nsn-intra.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-AIMC-AUTH: xing
X-AIMC-MAILFROM: xing@cernet.edu.cn
X-AIMC-Msg-ID: tIPKjnWB
Cc: Xing Li <xing@cernet.edu.cn>, congxiao <congxiao@cernet.edu.cn>, Behave WG <behave@ietf.org>, Fred Baker <fred@cisco.com>, Kevin Yin <kyin@cisco.com>
Subject: Re: [BEHAVE] draft-ietf-behave-v6v4-framework-01 uploaded
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/mail-archive/web/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>
X-List-Received-Date: Wed, 16 Sep 2009 01:17:47 -0000

Xiao, Lin (NSN - CN/Beijing) 写道:
> Hi Xing,
>
> In Terminology (Sec 1.2), there is a term " IPv4-binding IPv6
> addresses". Should we make sure the specific scenario that this term
> could be used in? As far as I understand from the term description, this
> kind of addresses are just native IPv6 addresses without any
> relationship with IPv4 addresses until mapping is set up with certain
> IPv4 addresses at NAT.  Do we really need such a term to describe the
> IPv6 addresses before they get bound with IPv4 addresses at a NAT64? or
> it can be used for the IPv6 addresses in the pool of NAT46? Could you
> please give a clear definition on it for the term?
>   
This kind of addresses is defined as "IPv6 addresses assigned to IPv6 
hosts", which is used for "Represent IPv6 addresses in IPv4". In the 
stateless mode, such IPv6 addresses are algorithmically mapped to IPv4. 
In the stateful translation, such IPv6 addresses bind to the IPv4 
addresses dynamically. We need terms to describe these cases.
> For "IPv4-embedded IPv6 addresses", it's easer to understand. But, It's
> also better to put the translation directions as well as the
> source/destination description of the addresses in the term definition.
> e.g, "IPv4-embedded IPv6 addresses can be used either in source address
> translation or in destination address translation or in both in both
> NAT64 and NAT46 scenarios."
>   

This kind of address is defined as "IPv6 addresses used to represent 
IPv4 hosts", which is used for "Represent IPv4 address in IPv6". Both in 
stateless mode and the stateful mode, such IPv4 addresses are 
algorithmically mapped to IPv6.

Concerning the directions, we are discussing in 
draft-ietf-behave-v6v4-xlate-01
> In RFC 2765, terms "IPv4-translatable IPv6 addresses" and IPv4- mapped
> IPv6 addresses" are used. Should we abolish these term, or a clear
> description for all the address types mentioned in the email would be
> given? 
>   
We may use some of these terms based on the consensus.

regards,

xing


> Best Regards,
> Lin
>
>
>
> -----Original Message-----
> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On Behalf
> Of ext Xing Li
> Sent: Wednesday, September 09, 2009 9:37 AM
> To: 'Behave WG'; Kevin Yin
> Cc: congxiao; Xing Li; Fred Baker
> Subject: [BEHAVE] draft-ietf-behave-v6v4-framework-01 uploaded
>
> Hi, All,
>
> Based on Dave's comment, the discussions in the mailing list and the
> meeting notes of IETF75, the authors have made the modifications and
> uploaded the 01 version of the Framework for IPv4/IPv6 Translation. Here
> are some editorial notes.
>
> (1) Most of the grammar and spelling errors are corrected.
>
> (2) Terminology (Sec 1.2): Since the terminologies are not consistent in
> the current translation related documents. We will compile a list of the
> terminology and send to the behave@ietf.org to get the consensus before
> we modify the related documents.
>
> (3) Address Translation (Sec. 3.1.1, etc): The discussion will be move
> to the address format document and we will insert the conclusion in the
> framework document later.
>
> Please review this version and send your comments and suggestions, so we
> can edit the next version.
>
> Regards,
>
> xing
>
>
>
>
>
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>
>
>   



From xing@cernet.edu.cn  Tue Sep 15 18:17:50 2009
Return-Path: <xing@cernet.edu.cn>
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 31B033A6832 for <behave@core3.amsl.com>; Tue, 15 Sep 2009 18:17:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.626
X-Spam-Level: 
X-Spam-Status: No, score=0.626 tagged_above=-999 required=5 tests=[AWL=0.529,  BAYES_00=-2.599, FH_HAS_XAIMC=2.696]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 876MemZZuFSo for <behave@core3.amsl.com>; Tue, 15 Sep 2009 18:17:49 -0700 (PDT)
Received: from cernet.edu.cn (sea.net.edu.cn [202.112.3.66]) by core3.amsl.com (Postfix) with SMTP id B23FD3A6825 for <behave@ietf.org>; Tue, 15 Sep 2009 18:17:48 -0700 (PDT)
Received: from [10.140.95.191]([117.136.0.184]) by cernet.edu.cn(AIMC 3.2.0.0) with SMTP id jm104ab04a35; Wed, 16 Sep 2009 09:18:35 +0800
Message-ID: <4AB03B61.7080004@cernet.edu.cn>
Date: Wed, 16 Sep 2009 09:12:01 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Chen Gang <phdgang@gmail.com>
References: <4AA706C2.6020804@cernet.edu.cn> <36ba02b00909141822m37c9239dy800f92c31f2b9a37@mail.gmail.com>
In-Reply-To: <36ba02b00909141822m37c9239dy800f92c31f2b9a37@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-AIMC-AUTH: xing
X-AIMC-MAILFROM: xing@cernet.edu.cn
X-AIMC-Msg-ID: tJTKjnWB
Cc: Xing Li <xing@cernet.edu.cn>, congxiao <congxiao@cernet.edu.cn>, Behave WG <behave@ietf.org>, Fred Baker <fred@cisco.com>, Kevin Yin <kyin@cisco.com>
Subject: Re: [BEHAVE] draft-ietf-behave-v6v4-framework-01 uploaded
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/mail-archive/web/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>
X-List-Received-Date: Wed, 16 Sep 2009 01:17:50 -0000

Chen Gang 写道:
> Hello Xing,
> I think it's a right place to attach the comments. Please kindly to 
> review it.
>
> I have observed that you have also updated dual-stack implmentation, 
> IPv4-only and IPv6-only definition. For my understanding, these three 
> terms are basic adjectives and can be used to describe a host, which 
> will appear in several BEHAVE scenarios.
>
> However, for the purpose of describing all cases of a host 
> implmentation, three adjectives is appearantly not enough. For 
> example, IVI can be used in scenario 1 and 2. Especially, in scenario 
> 1, can I call IVI host located in an IPv6 network as IPv6-only host or 
> dual-stack host? No, since it has double IVI appproach, in which the 
> functions of the first IVI translator is patched into the end 
> systemthe, and it has IPv4-based application software and IPv6/IPv4 
> enable system stack, IPv6 routing and address. Similar examples will 
> be appreared in many cases.

We believe it is easier to describe the general mode as

(1) IPv4 ---- xlate ----- IPv6

If multiple translators are involved

(2) IPv4 ---- xlate1----IPv6----xlate2---IPv4

It can be decoupled as two (1)s cascading.

regards,

xing


>
> So, I suggest to add a new sort of adjective to deal with this 
> problem. We could define a general terms to cover various IPv4/IPv6 
> implementations. Like following:
>
> IPvX-adapted-IPvY implmentation: in this context, comprises an 
> IPvX/IPvY enabled end system stack, IPvX applications plus IPvY 
> routing and address in the network. It implies that two application 
> instances are capable of communicating using IPvY by some sort of 
> tranlations mechanisms to accomodate IPvY environments.
>
> The definition may need more works, but this sort of definition could 
> fill in a omission in current framework defintions.
>
> Thanks for your attantion.
>
>
> Best Regards
>
> Gang
>
> 2009/9/9 Xing Li <xing@cernet.edu.cn <mailto:xing@cernet.edu.cn>>
>
>     Hi, All,
>
>     Based on Dave's comment, the discussions in the mailing list and the
>     meeting notes of IETF75, the authors have made the modifications and
>     uploaded the 01 version of the Framework for IPv4/IPv6
>     Translation. Here
>     are some editorial notes.
>
>     (1) Most of the grammar and spelling errors are corrected.
>
>     (2) Terminology (Sec 1.2): Since the terminologies are not
>     consistent in
>     the current translation related documents. We will compile a list
>     of the
>     terminology and send to the behave@ietf.org
>     <mailto:behave@ietf.org> to get the consensus before
>     we modify the related documents.
>
>     (3) Address Translation (Sec. 3.1.1, etc): The discussion will be move
>     to the address format document and we will insert the conclusion
>     in the
>     framework document later.
>
>     Please review this version and send your comments and suggestions,
>     so we
>     can edit the next version.
>
>     Regards,
>
>     xing
>
>
>
>
>
>     _______________________________________________
>     Behave mailing list
>     Behave@ietf.org <mailto:Behave@ietf.org>
>     https://www.ietf.org/mailman/listinfo/behave
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>   



From caozhenpku@gmail.com  Tue Sep 15 18:45:32 2009
Return-Path: <caozhenpku@gmail.com>
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 8179A3A6B3D for <behave@core3.amsl.com>; Tue, 15 Sep 2009 18:45:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.474
X-Spam-Level: 
X-Spam-Status: No, score=-2.474 tagged_above=-999 required=5 tests=[AWL=0.125,  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 cVOg5zpQJgK4 for <behave@core3.amsl.com>; Tue, 15 Sep 2009 18:45:31 -0700 (PDT)
Received: from mail-vw0-f201.google.com (mail-vw0-f201.google.com [209.85.212.201]) by core3.amsl.com (Postfix) with ESMTP id 72A8E3A6935 for <behave@ietf.org>; Tue, 15 Sep 2009 18:45:31 -0700 (PDT)
Received: by vws39 with SMTP id 39so2992707vws.29 for <behave@ietf.org>; Tue, 15 Sep 2009 18:46:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=BBBwLZr1evg3XkEcz01x7tb6tTfadwgc/yMzWROjAU4=; b=wTlvwXAu2NJIdzyNTW9D+FFg7+ZA+X3IwdCkrE5eFluYvDnI3Tvwe/8Pv48RIVg0N+ C9Fio4n7QIFaR8NZa+aStMhxyUjfcne/pw1huCshqo7llBYsKgFDGUNr44qQuuwajZZC mTbyxveHzjhd3Ex1a/IsGDUmJS8Dm2OXvN/Bw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=cAJs+JeVWO5Qx/Ypn/CxxC0abvI21CU+EqvJ/kA+EwsgSk+njyvUoWfpfg+NXwBcFJ Jp8Kg/Rwuq2CF25MBvMta4zWznNiwoTU0yr2kIyB23rHatvbvXwEHHp3lrEC+FbOKXns +80ovAKHfW5G0xkbpw1zPLeNUVeiAFuCiqZtE=
MIME-Version: 1.0
Received: by 10.220.108.102 with SMTP id e38mr11513106vcp.71.1253065576273;  Tue, 15 Sep 2009 18:46:16 -0700 (PDT)
In-Reply-To: <273D4852-D26C-497E-A034-2C3EE4908660@muada.com>
References: <a7c8d0a30909150630i29d535bbhf3089fdfecffa328@mail.gmail.com> <7CB993A6-829C-46CC-A74C-7DBF7CFE88C6@muada.com> <a7c8d0a30909150838s230397d9r3cbffb5df6097b76@mail.gmail.com> <273D4852-D26C-497E-A034-2C3EE4908660@muada.com>
Date: Wed, 16 Sep 2009 09:46:13 +0800
Message-ID: <a7c8d0a30909151846w6f85cc67je3774c93e298f2e1@mail.gmail.com>
From: Zhen Cao <caozhenpku@gmail.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Comments on NAT64 draft
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/mail-archive/web/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>
X-List-Received-Date: Wed, 16 Sep 2009 01:45:32 -0000

On Tue, Sep 15, 2009 at 11:47 PM, Iljitsch van Beijnum
<iljitsch@muada.com> wrote:
> On 15 Sep 2009, at 17:38 , Zhen Cao wrote:
>
>>> Not sure if we already discuss this in the draft, but we don't want the
>>> situation where a translator uses different IPv4 addresses for
>>> translating
>>> different sessions from the same IPv6 host because it breaks STUN.
>
>> I am not talking about the one ipv6 mapping to multiple ipv4
>> addresses, and am assuming one ipv6 host maps to one ipv4 address.
>
> Well, in that case there is no problem with the translation of fragments
> without reassembly or setting up state, right?
>
>> If an in-the-middle fragmented packet arrives, we cannot create the
>> mapping entry from <Y', y> to <T, t>. Do you mean just translate it
>> first and wait for the first fragment to fill in the entry?
>
> I assume Y' = the IPv6 source address, y = the source port, T is the
> destination address and t the destination port.
>
> You are right that it won't be possible to map a non-first fragment to a
> session because it could match multiple sessions. However, we can still
> translate it as long as we know the IPv4 source address that we need to use.
> The IPv4 destination address can be derived from the IPv6 destination
> address. The only thing we need for the translation is addresses and an
> identifier value that is the same for all fragments.
>

Let me explain my concerns further. Here, Y' = the IPv6 source
address, y = the source port; T= the translated IPv4 address on NAT64
and t the translated port on NAT64. (consistent with Sec.1.2.2
presentation). Multiple Y' may reuse the same IPv4 address T.

For example, if an ipv6 datagram has two fragments, frag1 and frag2.

a) if frag1 arrives at the NAT64 first (it includes the port number),
the NAT will choose an IPv4 address T and port t for translation and
creates an mapping entry from <Y', y> to <T, t>. When frag2 arrives
later, it  knows how to translate by querying the mapping table.

b) if frag2 arrives at the NAT64 first (it does NOT include the port
number), the NAT has not yet created the mapping entry  <Y', y> to <T,
t>.  How to translate this frag2 in this case?

Thanks,
Zhen

From caozhenpku@gmail.com  Tue Sep 15 19:09:06 2009
Return-Path: <caozhenpku@gmail.com>
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 EEB1128C141 for <behave@core3.amsl.com>; Tue, 15 Sep 2009 19:09:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.48
X-Spam-Level: 
X-Spam-Status: No, score=-2.48 tagged_above=-999 required=5 tests=[AWL=0.119,  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 sK82wqsu1u3H for <behave@core3.amsl.com>; Tue, 15 Sep 2009 19:09:05 -0700 (PDT)
Received: from mail-vw0-f201.google.com (mail-vw0-f201.google.com [209.85.212.201]) by core3.amsl.com (Postfix) with ESMTP id 1098B28C11F for <behave@ietf.org>; Tue, 15 Sep 2009 19:09:04 -0700 (PDT)
Received: by vws39 with SMTP id 39so3002847vws.29 for <behave@ietf.org>; Tue, 15 Sep 2009 19:09:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=0dFLxZyVBDXA6txTNeqnfC9hFCJMTw65tg3SuXrJA9E=; b=LDJktQLWT2Qj8tqLPbFD1csLb2gzAzRbfguwN/R7MyqbuaOHywSAKHy0R71nAbie+s SSUpqr1fU/KW1GHpGtoKwOTpuvWNlGVvlYPDnveS2pieBMpKNILHSl7rQdXxfnfJSwmi MfFgnIjItN1XXrhIiWCPUHqq1gmvQEsSqCbDQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=ciSZBZB8k5FWj6WAHEMm3vwiaiKbSmbDwbQPzCUeJw+UvLmsMFFu8GkUBFp8QE7NkB P9IzCNX67K4j6UMk5Dz76Wj0pjE1vhdN7s20iP0bNhtmYuatib8hSA+qKxg8yvx5F39N OPjeKWv04rR1RAtirRJmh98eBISraTSm9Nwg4=
MIME-Version: 1.0
Received: by 10.220.79.11 with SMTP id n11mr11681482vck.95.1253066989555; Tue,  15 Sep 2009 19:09:49 -0700 (PDT)
In-Reply-To: <4AA7730F.6040602@cernet.edu.cn>
References: <4AA7730F.6040602@cernet.edu.cn>
Date: Wed, 16 Sep 2009 10:09:49 +0800
Message-ID: <a7c8d0a30909151909y68a1c6e8i39e48a3f0f45abd8@mail.gmail.com>
From: Zhen Cao <caozhenpku@gmail.com>
To: Xing Li <xing@cernet.edu.cn>
Content-Type: text/plain; charset=ISO-8859-1
Cc: congxiao <congxiao@cernet.edu.cn>, Behave WG <behave@ietf.org>, Fred Baker <fred@cisco.com>
Subject: Re: [BEHAVE] version 01 of xlate
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/mail-archive/web/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>
X-List-Received-Date: Wed, 16 Sep 2009 02:09:06 -0000

Hi Xing,

According to the title 'IP/ICMP Translation' (no transport port
inside), my first impression about the document is that it should only
talks about stateless translation. Going over the document, i find the
description on stateful case nearly resort to the nat64 document.
Maybe i did not catch up with the work group concerns on working on
both stateless and stateful in one document?

Thanks,
Zhen

On Wed, Sep 9, 2009 at 5:19 PM, Xing Li <xing@cernet.edu.cn> wrote:
> Hi, All,
>
> Based on Dave's comment, the discussions in the mailing list and the
> meeting notes of IETF75, the authors have made the modifications and
> uploaded the 01 version of the IP/ICMP Translation Algorithm. Here are
> some editorial notes.
>
> (1) Most of the grammar and spelling errors are corrected.
> (2) Translating UDP over IPv4 (Sec. 2.2): Rewritten based on the
> discussions on the mailing list.
> (3) Transport-layer Header Translation (Sec. 2.5 and Sec 3.4): Reflected
> the checksum neutral case.
> (4) Translator sending ICMP error message: add the configuration
> concerns in new sections (2.5 and 3.4).
> (5) Translating ICMP extensions: add notes.
> (6) Translating multicast packets: add notes.
>
> Please review this version and send your comments and suggestions.
>
> Regards,
>
> xing
>
>
>
>
>
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>

From phdgang@gmail.com  Tue Sep 15 19:24:35 2009
Return-Path: <phdgang@gmail.com>
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 0D88B3A67F7 for <behave@core3.amsl.com>; Tue, 15 Sep 2009 19:24:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.137
X-Spam-Level: 
X-Spam-Status: No, score=-0.137 tagged_above=-999 required=5 tests=[AWL=0.011,  BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_CHARSET_FARAWAY=2.45]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NTLodIrBOstx for <behave@core3.amsl.com>; Tue, 15 Sep 2009 19:24:33 -0700 (PDT)
Received: from mail-px0-f202.google.com (mail-px0-f202.google.com [209.85.216.202]) by core3.amsl.com (Postfix) with ESMTP id C9D503A6883 for <behave@ietf.org>; Tue, 15 Sep 2009 19:24:33 -0700 (PDT)
Received: by pxi40 with SMTP id 40so3731937pxi.5 for <behave@ietf.org>; Tue, 15 Sep 2009 19:25:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=i2aZf5bVD+tjK1I1NpavYVIkLmd9lmbBrxIF3V4aWcc=; b=d5KwQFz0Cz5o49gDan5+MXGVer9hyi/YMgpstbWY/Y+GVP4PgepyeTYs1zFZlYM5KM xQA3umx+u1e2IIao7Wo+ELNZ09yPwUiJSfdCpr53TiYKGzCbjWe3Qj/bp+IPPwmemHc2 n5fV43APfptEm1i44u8Ss/ME8194GlonXEgnU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=HmlUOyMXbCzcd1aZHlOPzozeyk9ASjfmR/6Y1ww6ehN3jtlDEfIMsprPs3nCFGolq5 nThtBfI18ciaLqC4mpVEmD0B3ycsbxZRQHaZALCATwSgmthwk2bXdoKKBHyjATxba+MZ Ul3jhUoWIdXsLH6ij4VfiJgzBmpmBwt6C6phw=
MIME-Version: 1.0
Received: by 10.114.162.38 with SMTP id k38mr15117562wae.138.1253067919255;  Tue, 15 Sep 2009 19:25:19 -0700 (PDT)
In-Reply-To: <4AB03B61.7080004@cernet.edu.cn>
References: <4AA706C2.6020804@cernet.edu.cn> <36ba02b00909141822m37c9239dy800f92c31f2b9a37@mail.gmail.com> <4AB03B61.7080004@cernet.edu.cn>
Date: Wed, 16 Sep 2009 10:25:19 +0800
Message-ID: <36ba02b00909151925l72fc32d7o2489bb2893b32f44@mail.gmail.com>
From: Chen Gang <phdgang@gmail.com>
To: Xing Li <xing@cernet.edu.cn>
Content-Type: multipart/alternative; boundary=00504502f60d34ed970473a89ce7
Cc: congxiao <congxiao@cernet.edu.cn>, Behave WG <behave@ietf.org>, Fred Baker <fred@cisco.com>, Kevin Yin <kyin@cisco.com>
Subject: Re: [BEHAVE] draft-ietf-behave-v6v4-framework-01 uploaded
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/mail-archive/web/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>
X-List-Received-Date: Wed, 16 Sep 2009 02:24:35 -0000

--00504502f60d34ed970473a89ce7
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: quoted-printable

2009/9/16 Xing Li <xing@cernet.edu.cn>

> Chen Gang =D0=B4=B5=C0:
>
>> Hello Xing,
>> I think it's a right place to attach the comments. Please kindly to revi=
ew
>> it.
>>
>> I have observed that you have also updated dual-stack implmentation,
>> IPv4-only and IPv6-only definition. For my understanding, these three te=
rms
>> are basic adjectives and can be used to describe a host, which will appe=
ar
>> in several BEHAVE scenarios.
>>
>> However, for the purpose of describing all cases of a host implmentation=
,
>> three adjectives is appearantly not enough. For example, IVI can be used=
 in
>> scenario 1 and 2. Especially, in scenario 1, can I call IVI host located=
 in
>> an IPv6 network as IPv6-only host or dual-stack host? No, since it has
>> double IVI appproach, in which the functions of the first IVI translator=
 is
>> patched into the end systemthe, and it has IPv4-based application softwa=
re
>> and IPv6/IPv4 enable system stack, IPv6 routing and address. Similar
>> examples will be appreared in many cases.
>>
>
> We believe it is easier to describe the general mode as
>
> (1) IPv4 ---- xlate ----- IPv6
>
> If multiple translators are involved
>
> (2) IPv4 ---- xlate1----IPv6----xlate2---IPv4
>
> It can be decoupled as two (1)s cascading.
>
> regards,
>
> xing
>


For multiple translators, I guess the following case can't match the number
(2) cascading model:

"A more interesting scenario is to integrate the functions of the first IVI
translator into the end system.  In this case, the application software is
IPv4 based and there is no need to have ALG support in the IVI translator
when it is communicating with IPv4 hosts."

Looking forward to your reply!

Thanks

Gang


>
>
>> So, I suggest to add a new sort of adjective to deal with this problem. =
We
>> could define a general terms to cover various IPv4/IPv6 implementations.
>> Like following:
>>
>> IPvX-adapted-IPvY implmentation: in this context, comprises an IPvX/IPvY
>> enabled end system stack, IPvX applications plus IPvY routing and addres=
s in
>> the network. It implies that two application instances are capable of
>> communicating using IPvY by some sort of tranlations mechanisms to
>> accomodate IPvY environments.
>>
>> The definition may need more works, but this sort of definition could fi=
ll
>> in a omission in current framework defintions.
>>
>> Thanks for your attantion.
>>
>>
>> Best Regards
>>
>> Gang
>>
>> 2009/9/9 Xing Li <xing@cernet.edu.cn <mailto:xing@cernet.edu.cn>>
>>
>>    Hi, All,
>>
>>    Based on Dave's comment, the discussions in the mailing list and the
>>    meeting notes of IETF75, the authors have made the modifications and
>>    uploaded the 01 version of the Framework for IPv4/IPv6
>>    Translation. Here
>>    are some editorial notes.
>>
>>    (1) Most of the grammar and spelling errors are corrected.
>>
>>    (2) Terminology (Sec 1.2): Since the terminologies are not
>>    consistent in
>>    the current translation related documents. We will compile a list
>>    of the
>>    terminology and send to the behave@ietf.org
>>    <mailto:behave@ietf.org> to get the consensus before
>>    we modify the related documents.
>>
>>    (3) Address Translation (Sec. 3.1.1, etc): The discussion will be mov=
e
>>    to the address format document and we will insert the conclusion
>>    in the
>>    framework document later.
>>
>>    Please review this version and send your comments and suggestions,
>>    so we
>>    can edit the next version.
>>
>>    Regards,
>>
>>    xing
>>
>>
>>
>>
>>
>>    _______________________________________________
>>    Behave mailing list
>>    Behave@ietf.org <mailto:Behave@ietf.org>
>>    https://www.ietf.org/mailman/listinfo/behave
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Behave mailing list
>> Behave@ietf.org
>> https://www.ietf.org/mailman/listinfo/behave
>>
>>
>
>
>

--00504502f60d34ed970473a89ce7
Content-Type: text/html; charset=GB2312
Content-Transfer-Encoding: quoted-printable

<br><br>
<div class=3D"gmail_quote">2009/9/16 Xing Li <span dir=3D"ltr">&lt;<a href=
=3D"mailto:xing@cernet.edu.cn">xing@cernet.edu.cn</a>&gt;</span><br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Chen Gang =D0=B4=B5=C0:=20
<div class=3D"im"><br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hello Xing,<br>I think it&#39;s =
a right place to attach the comments. Please kindly to review it.<br><br>I =
have observed that you have also updated dual-stack implmentation, IPv4-onl=
y and IPv6-only definition. For my understanding, these three terms are bas=
ic adjectives and can be used to describe a host, which will appear in seve=
ral BEHAVE scenarios.<br>
<br>However, for the purpose of describing all cases of a host implmentatio=
n, three adjectives is appearantly not enough. For example, IVI can be used=
 in scenario 1 and 2. Especially, in scenario 1, can I call IVI host locate=
d in an IPv6 network as IPv6-only host or dual-stack host? No, since it has=
 double IVI appproach, in which the functions of the first IVI translator i=
s patched into the end systemthe, and it has IPv4-based application softwar=
e and IPv6/IPv4 enable system stack, IPv6 routing and address. Similar exam=
ples will be appreared in many cases.<br>
</blockquote><br></div>We believe it is easier to describe the general mode=
 as<br><br>(1) IPv4 ---- xlate ----- IPv6<br><br>If multiple translators ar=
e involved<br><br>(2) IPv4 ---- xlate1----IPv6----xlate2---IPv4<br><br>
It can be decoupled as two (1)s cascading.<br><br>regards,<br><br>xing<br><=
/blockquote>
<div>&nbsp;</div>
<div>&nbsp;</div>
<div>For multiple translators, I guess the following case can&#39;t match t=
he number (2) cascading model:</div>
<div>&nbsp;</div>
<div>&quot;<font color=3D"#ff0000">A more interesting scenario is to integr=
ate the functions of the first IVI translator into the end system.&nbsp; In=
 this case, the application software is IPv4 based and there is no need to =
have ALG support in the IVI translator when it is communicating with IPv4&n=
bsp;hosts</font>.&quot;</div>

<div>&nbsp;</div>
<div>Looking forward to your reply!</div>
<div>&nbsp;</div>
<div>Thanks</div>
<div>&nbsp;</div>
<div>Gang<br></div>
<div>&nbsp;</div>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div class=3D"im"><br>So, I suggest to add a new sort of adjective to deal =
with this problem. We could define a general terms to cover various IPv4/IP=
v6 implementations. Like following:<br><br>IPvX-adapted-IPvY implmentation:=
 in this context, comprises an IPvX/IPvY enabled end system stack, IPvX app=
lications plus IPvY routing and address in the network. It implies that two=
 application instances are capable of communicating using IPvY by some sort=
 of tranlations mechanisms to accomodate IPvY environments.<br>
<br>The definition may need more works, but this sort of definition could f=
ill in a omission in current framework defintions.<br><br>Thanks for your a=
ttantion.<br><br><br>Best Regards<br><br>Gang<br><br></div>2009/9/9 Xing Li=
 &lt;<a href=3D"mailto:xing@cernet.edu.cn" target=3D"_blank">xing@cernet.ed=
u.cn</a> &lt;mailto:<a href=3D"mailto:xing@cernet.edu.cn" target=3D"_blank"=
>xing@cernet.edu.cn</a>&gt;&gt;=20
<div class=3D"im"><br><br>&nbsp; &nbsp;Hi, All,<br><br>&nbsp; &nbsp;Based o=
n Dave&#39;s comment, the discussions in the mailing list and the<br>&nbsp;=
 &nbsp;meeting notes of IETF75, the authors have made the modifications and=
<br>&nbsp; &nbsp;uploaded the 01 version of the Framework for IPv4/IPv6<br>
&nbsp; &nbsp;Translation. Here<br>&nbsp; &nbsp;are some editorial notes.<br=
><br>&nbsp; &nbsp;(1) Most of the grammar and spelling errors are corrected=
.<br><br>&nbsp; &nbsp;(2) Terminology (Sec 1.2): Since the terminologies ar=
e not<br>&nbsp; &nbsp;consistent in<br>&nbsp; &nbsp;the current translation=
 related documents. We will compile a list<br>
&nbsp; &nbsp;of the<br>&nbsp; &nbsp;terminology and send to the <a href=3D"=
mailto:behave@ietf.org" target=3D"_blank">behave@ietf.org</a><br></div>&nbs=
p; &nbsp;&lt;mailto:<a href=3D"mailto:behave@ietf.org" target=3D"_blank">be=
have@ietf.org</a>&gt; to get the consensus before=20
<div class=3D"im"><br>&nbsp; &nbsp;we modify the related documents.<br><br>=
&nbsp; &nbsp;(3) Address Translation (Sec. 3.1.1, etc): The discussion will=
 be move<br>&nbsp; &nbsp;to the address format document and we will insert =
the conclusion<br>&nbsp; &nbsp;in the<br>
&nbsp; &nbsp;framework document later.<br><br>&nbsp; &nbsp;Please review th=
is version and send your comments and suggestions,<br>&nbsp; &nbsp;so we<br=
>&nbsp; &nbsp;can edit the next version.<br><br>&nbsp; &nbsp;Regards,<br><b=
r>&nbsp; &nbsp;xing<br><br><br><br><br><br>&nbsp; &nbsp;___________________=
____________________________<br>
&nbsp; &nbsp;Behave mailing list<br></div>&nbsp; &nbsp;<a href=3D"mailto:Be=
have@ietf.org" target=3D"_blank">Behave@ietf.org</a> &lt;mailto:<a href=3D"=
mailto:Behave@ietf.org" target=3D"_blank">Behave@ietf.org</a>&gt;=20
<div class=3D"im"><br>&nbsp; &nbsp;<a href=3D"https://www.ietf.org/mailman/=
listinfo/behave" target=3D"_blank">https://www.ietf.org/mailman/listinfo/be=
have</a><br><br><br></div>-------------------------------------------------=
-----------------------=20
<div class=3D"im"><br><br>_______________________________________________<b=
r>Behave mailing list<br><a href=3D"mailto:Behave@ietf.org" target=3D"_blan=
k">Behave@ietf.org</a><br><a href=3D"https://www.ietf.org/mailman/listinfo/=
behave" target=3D"_blank">https://www.ietf.org/mailman/listinfo/behave</a><=
br>
&nbsp;<br></div></blockquote><br><br></blockquote></div><br>

--00504502f60d34ed970473a89ce7--

From xing@cernet.edu.cn  Tue Sep 15 21:43:57 2009
Return-Path: <xing@cernet.edu.cn>
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 9FD3B3A659B for <behave@core3.amsl.com>; Tue, 15 Sep 2009 21:43:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.688
X-Spam-Level: 
X-Spam-Status: No, score=0.688 tagged_above=-999 required=5 tests=[AWL=0.591,  BAYES_00=-2.599, FH_HAS_XAIMC=2.696]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uoCbNOLrYAy0 for <behave@core3.amsl.com>; Tue, 15 Sep 2009 21:43:56 -0700 (PDT)
Received: from cernet.edu.cn (sea.net.edu.cn [202.112.3.66]) by core3.amsl.com (Postfix) with SMTP id 076DF3A688F for <behave@ietf.org>; Tue, 15 Sep 2009 21:43:55 -0700 (PDT)
Received: from [59.66.24.75]([59.66.24.75]) by cernet.edu.cn(AIMC 3.2.0.0) with SMTP id jm124ab07a85; Wed, 16 Sep 2009 12:44:42 +0800
Message-ID: <4AB05E3F.20406@cernet.edu.cn>
Date: Wed, 16 Sep 2009 11:40:47 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Zhen Cao <caozhenpku@gmail.com>
References: <4AA7730F.6040602@cernet.edu.cn> <a7c8d0a30909151909y68a1c6e8i39e48a3f0f45abd8@mail.gmail.com>
In-Reply-To: <a7c8d0a30909151909y68a1c6e8i39e48a3f0f45abd8@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-AIMC-AUTH: xing
X-AIMC-MAILFROM: xing@cernet.edu.cn
X-AIMC-Msg-ID: tOmXmnWB
Cc: congxiao <congxiao@cernet.edu.cn>, Behave WG <behave@ietf.org>, Fred Baker <fred@cisco.com>
Subject: Re: [BEHAVE] version 01 of xlate
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/mail-archive/web/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>
X-List-Received-Date: Wed, 16 Sep 2009 04:43:57 -0000

Zhen Cao 写道:
> Hi Xing,
>
> According to the title 'IP/ICMP Translation' (no transport port
> inside), my first impression about the document is that it should only
> talks about stateless translation. Going over the document, i find the
> description on stateful case nearly resort to the nat64 document.
> Maybe i did not catch up with the work group concerns on working on
> both stateless and stateful in one document?
>   

Please see the framework document, this was WG's decision.
(1) The title of RFC2765 is SIIT, but the title of this document is IIT (-:
(2) The details of the transport layer table maintenance is discussed in 
xlate-staful

xing

> Thanks,
> Zhen
>
> On Wed, Sep 9, 2009 at 5:19 PM, Xing Li <xing@cernet.edu.cn> wrote:
>   
>> Hi, All,
>>
>> Based on Dave's comment, the discussions in the mailing list and the
>> meeting notes of IETF75, the authors have made the modifications and
>> uploaded the 01 version of the IP/ICMP Translation Algorithm. Here are
>> some editorial notes.
>>
>> (1) Most of the grammar and spelling errors are corrected.
>> (2) Translating UDP over IPv4 (Sec. 2.2): Rewritten based on the
>> discussions on the mailing list.
>> (3) Transport-layer Header Translation (Sec. 2.5 and Sec 3.4): Reflected
>> the checksum neutral case.
>> (4) Translator sending ICMP error message: add the configuration
>> concerns in new sections (2.5 and 3.4).
>> (5) Translating ICMP extensions: add notes.
>> (6) Translating multicast packets: add notes.
>>
>> Please review this version and send your comments and suggestions.
>>
>> Regards,
>>
>> xing
>>
>>
>>
>>
>>
>> _______________________________________________
>> 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 huitema@microsoft.com  Tue Sep 15 22:07:32 2009
Return-Path: <huitema@microsoft.com>
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 B473E3A6969 for <behave@core3.amsl.com>; Tue, 15 Sep 2009 22:07:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.549
X-Spam-Level: 
X-Spam-Status: No, score=-10.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 08rImWfmKmfy for <behave@core3.amsl.com>; Tue, 15 Sep 2009 22:07:32 -0700 (PDT)
Received: from smtp.microsoft.com (mailc.microsoft.com [131.107.115.214]) by core3.amsl.com (Postfix) with ESMTP id E99413A695E for <behave@ietf.org>; Tue, 15 Sep 2009 22:07:31 -0700 (PDT)
Received: from TK5EX14MLTC101.redmond.corp.microsoft.com (157.54.79.178) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.2.176.0; Tue, 15 Sep 2009 22:08:20 -0700
Received: from TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com (157.54.71.68) by TK5EX14MLTC101.redmond.corp.microsoft.com (157.54.79.178) with Microsoft SMTP Server id 14.0.639.20; Tue, 15 Sep 2009 22:08:20 -0700
Received: from TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com ([169.254.3.19]) by TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.68]) with mapi; Tue, 15 Sep 2009 22:08:19 -0700
From: Christian Huitema <huitema@microsoft.com>
To: Dan Wing <dwing@cisco.com>, 'Zhen Cao' <caozhenpku@gmail.com>
Thread-Topic: [BEHAVE] Stateless translation definition
Thread-Index: AQHKMIsybcWCH8YWoEKIqxHLFB4kG5DNVEWAgAIlMACAAAeMgIAAj48AgACPtACACBNR8A==
Date: Wed, 16 Sep 2009 05:08:18 +0000
Message-ID: <6B55F0F93C3E9D45AF283313B8D342BA20F59D61@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
References: <a7c8d0a30909080645t342f7bd7udfc553c0303f25ff@mail.gmail.com> <09f701ca30a0$01e90730$c5f0200a@cisco.com> <a7c8d0a30909091804j368a8a6fr4ee1b75eb7081559@mail.gmail.com> <073801ca31b6$60299ff0$c6f0200a@cisco.com> <a7c8d0a30909100304w69593812o29778ad80f28451c@mail.gmail.com> <004701ca3246$015ea5c0$c6f0200a@cisco.com>
In-Reply-To: <004701ca3246$015ea5c0$c6f0200a@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: 'Behave WG' <behave@ietf.org>
Subject: Re: [BEHAVE] Stateless translation definition
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/mail-archive/web/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>
X-List-Received-Date: Wed, 16 Sep 2009 05:07:32 -0000

> Looking at the diagram in
> http://tools.ietf.org/html/draft-huang-pnat-host-ipv6-01#section-2 and
> reading
> the PNAT44COM definition in that section, the conclusion I reach is that
> it
> can be done statelessly if both of these are true:
>=20
>  1. each IPv6 host consumes one IPv4 address in the PNAT64 device;
>     this allows a stateless, algorithmic mapping on the PNAT64 device
>     similar to what is described in the IVI drafts and in
>     http://tools.ietf.org/html/draft-ietf-behave-address-format-
> 00#section-2.3
>=20
> and
>  2. there are only routable, non-overlapping IPv4 addresses on
>     the IPv4 site.
>=20
> But if either of those are false, there needs to be per-flow state
> somewhere.

I think the "stateless translation" can have two definitions. The least res=
trictive one is what Dan just described: when it is possible to allocate an=
 IPv4 address to the IPv6 host. The domain of application is very limited, =
because there are not enough 32 bits IPv4 addresses to map every 128 bit IP=
v6 address. I can see one application: when we want an IPv6 host to be visi=
ble, for example as a web server, by IPv4 hosts.

The more restrictive is an operational definition. A translation is statele=
ss if two different translators, presented with the same packets, would per=
form exactly the same translation. This is even more restrictive, because i=
t requires that every NAT can interpret the IPv6 source and destination add=
ress and translate them to the same pair of IPv4 addresses.

By the way, even the least restrictive definition implies that stateless tr=
anslation is very much a specialty product, and cannot be used as a general=
 solution for providing IPv6 networks with connectivity to the IPv4 Interne=
t.

-- Christian Huitema





From xing@cernet.edu.cn  Tue Sep 15 22:43:40 2009
Return-Path: <xing@cernet.edu.cn>
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 D47163A67EC for <behave@core3.amsl.com>; Tue, 15 Sep 2009 22:43:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.538
X-Spam-Level: 
X-Spam-Status: No, score=0.538 tagged_above=-999 required=5 tests=[AWL=0.441,  BAYES_00=-2.599, FH_HAS_XAIMC=2.696]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gnNBRLzivWSK for <behave@core3.amsl.com>; Tue, 15 Sep 2009 22:43:38 -0700 (PDT)
Received: from cernet.edu.cn (sea.net.edu.cn [202.112.3.66]) by core3.amsl.com (Postfix) with SMTP id A99D83A67AF for <behave@ietf.org>; Tue, 15 Sep 2009 22:43:37 -0700 (PDT)
Received: from [10.140.107.49]([117.136.0.188]) by cernet.edu.cn(AIMC 3.2.0.0) with SMTP id jm54ab08880; Wed, 16 Sep 2009 13:44:22 +0800
Message-ID: <4AB079D5.1010404@cernet.edu.cn>
Date: Wed, 16 Sep 2009 13:38:29 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: marcelo bagnulo braun <marcelo@it.uc3m.es>
References: <4AA7730F.6040602@cernet.edu.cn>	<36ba02b00909141038i1611b5d6ide4fd96157ed2bc8@mail.gmail.com>	<6B55F0F93C3E9D45AF283313B8D342BA20F54E47@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>	<4AAF2C06.2020107@it.uc3m.es>	<6B55F0F93C3E9D45AF283313B8D342BA20F557D0@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <4AAFA425.7040706@it.uc3m.es>
In-Reply-To: <4AAFA425.7040706@it.uc3m.es>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-AIMC-AUTH: xing
X-AIMC-MAILFROM: xing@cernet.edu.cn
X-AIMC-Msg-ID: tU6TnnWB
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Security implications of protocol translation
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/mail-archive/web/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>
X-List-Received-Date: Wed, 16 Sep 2009 05:43:40 -0000

marcelo bagnulo braun 写道:
> Christian Huitema escribió:
>>> On the translators themselves, there has been agreement that the
>>> translators should not forward packets coming from the internet towards
>>> the internet. e.g. that a translator shoudl not forward an IPv6 packet
>>> coming from an off site source addressed to an IPv6 represetnation of
>>> and IPv4 destiantion that is also off site (the motivation for this was
>>> to avoid providing free transit to the rest of the IPv4 internet)
>>
>> How does a translator what is in-site and what is off-site?
>
> right, i was just thinking about that,
>
> So, in the statefull case, it is simple i think.
>
> the border routers must not accept any incoming packet containing a 
> destination address that contains the IPv6 prefix used to represent 
> IPv4 addresses.
> So, if the WK prefix is used, the border router must filter all 
> incoming packet containing the WK prefix in the destiantion address. 
> The same if the LIR is used.
>
> This works, cause none of the IPv6 addresses assigned to internal 
> hosts contain the prefix used by the statefull translator.
>
> With the stateless translator is more complicated, i think. since the 
> same prefix can be used to make representation of external hosts and 
> to assign internal hosts, then the filtenring needs to be done based 
> on the embedded IPv4 address, which may require per IPv4 prefix filter 
> configuration the border routers, which may be more complicated, but i 
> think it is feasible...

the stateless translator can just simple drop the packets, if they are
not the IPv4-mapped source addresses in the administrative domain.

>
>
>> Besides, that is not completely sufficient. In some proposals, the 
>> IPv4 source address can be algorithmically derived from the IPv6 
>> source address. In that case, an attacker can use the translation 
>> service to originate packets from pretty much any IPv4 source 
>> address. What is the protection?
>>
> Right.
> In the statefull case, this is not an issue since the source address 
> is selected form the IPv4 pool of the nat64.
> In the stateless case, we need some protection against that, i agree.
> If we use the filters i mentioned above, based on the IPv4 prefix. 
> then the off site attackers are prevented, agree?
> So the problem is how can we deal with the on site attackers that want 
> to spoof an address.
> I think this is quite similar to the non natted situation. I mean, a 
> host connected tot he internet can spoof any source address. The 
> standard way to deal with this is to use ingress filters. So the ISP 
> providing IPv4 access will need to configure ingress filters, so that 
> the translator can only originate packets witht he source address that 
> belong to the site.
>
> So, summarizing, if we configure filters in border routers, we can 
> prevent off site attackers, for both the state full and stateless 
> translators (we need more fine grained filters for the stateless case, 
> but still seems feasoble imho)
>
> If we have these filters in place, on site attackers can still use the 
> stateless translator to spoof source addresses. AFAICT, this is 
> similar to what any IPv4 site can do today and this can be handled by 
> the ISP of the site putting ingress filters in place.

(repeat) the stateless translator can just simple drop the packets, if 
they are
not the IPv4-mapped source addresses in the administrative domain.

xing

>
> Am i missing something?
>
> Regards, marcelo
>
>
>> -- Christian Huitema
>>
>>
>>
>>
>
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>
>




From xing@cernet.edu.cn  Tue Sep 15 22:44:10 2009
Return-Path: <xing@cernet.edu.cn>
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 076C03A67EE for <behave@core3.amsl.com>; Tue, 15 Sep 2009 22:44:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.475
X-Spam-Level: 
X-Spam-Status: No, score=0.475 tagged_above=-999 required=5 tests=[AWL=0.378,  BAYES_00=-2.599, FH_HAS_XAIMC=2.696]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wtJ9zprgVNiu for <behave@core3.amsl.com>; Tue, 15 Sep 2009 22:44:09 -0700 (PDT)
Received: from cernet.edu.cn (sea.net.edu.cn [202.112.3.66]) by core3.amsl.com (Postfix) with SMTP id 728AA3A67EC for <behave@ietf.org>; Tue, 15 Sep 2009 22:43:45 -0700 (PDT)
Received: from [10.140.107.49]([117.136.0.188]) by cernet.edu.cn(AIMC 3.2.0.0) with SMTP id jmb4ab08888; Wed, 16 Sep 2009 13:44:30 +0800
Message-ID: <4AB07A6E.4040602@cernet.edu.cn>
Date: Wed, 16 Sep 2009 13:41:02 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Iljitsch van Beijnum <iljitsch@muada.com>
References: <4AA7730F.6040602@cernet.edu.cn>	<36ba02b00909141038i1611b5d6ide4fd96157ed2bc8@mail.gmail.com>	<6B55F0F93C3E9D45AF283313B8D342BA20F54E47@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>	<4AAF2C06.2020107@it.uc3m.es>	<6B55F0F93C3E9D45AF283313B8D342BA20F557D0@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <AA0F118A-5883-451C-B2B5-1EE72895B2A4@muada.com>
In-Reply-To: <AA0F118A-5883-451C-B2B5-1EE72895B2A4@muada.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-AIMC-AUTH: xing
X-AIMC-MAILFROM: xing@cernet.edu.cn
X-AIMC-Msg-ID: t1eTnnWB
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Security implications of protocol translation
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/mail-archive/web/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>
X-List-Received-Date: Wed, 16 Sep 2009 05:44:10 -0000

Iljitsch van Beijnum 写道:
> On 15 Sep 2009, at 16:11 , Christian Huitema wrote:
>
>> How does a translator what is in-site and what is off-site?
>
> The same way any proxy or relay does: with a set of policy restriction 
> rules.
>
>> Besides, that is not completely sufficient. In some proposals, the 
>> IPv4 source address can be algorithmically derived from the IPv6 
>> source address. In that case, an attacker can use the translation 
>> service to originate packets from pretty much any IPv4 source 
>> address. What is the protection?
>
> Since when are you protected against anything on the internet?
>
> The case where an IPv4 host sets up a connection through a stateful 
> NAT64 is similar to having a host on the outside set up a connection 
> through a NAT44: if there is already some state, the packets will flow 
> towards the internal/IPv6 host that created the state (case 1). If 
> there is no state the translator doesn't know where to send the 
> packets so they are dropped (case 2).
>
> I see no reason for alarm in case 1 because presumably, the same IPv4 
> host could have sent the same packet to the IPv6 host over IPv6 if the 
> IPv4 host were dual stack. There is certainly no reason for alarm in 
> case 2 because the packet don't get anywhere.
>
> In case 1 it would be suboptimal if the packets flowed towards hosts 
> that are not users of the NAT64 in question, but again, the same 
> packets could have been sent by any IPv6 host. This is true for both 
> the stateful and stateless case. IPv6 hosts wouldn't recognize the 
> packets coming from the IPv4 world if a RIR prefix is used but the 
> level of obfuscation is limited because the IPv4 address is still in 
> there.
>
> All in all, I don't see a problem as long as people don't treat any 
> address ranges involved in the translation as "internal" or "trusted". 
> (Which you really shouldn't do to begin with, addresses are easily 
> faked in many circumstances.)

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



From marcelo@it.uc3m.es  Wed Sep 16 00:26:31 2009
Return-Path: <marcelo@it.uc3m.es>
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 452E53A6863 for <behave@core3.amsl.com>; Wed, 16 Sep 2009 00:26:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.562
X-Spam-Level: 
X-Spam-Status: No, score=-6.562 tagged_above=-999 required=5 tests=[AWL=0.037,  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 2fIb2PLawS48 for <behave@core3.amsl.com>; Wed, 16 Sep 2009 00:26:30 -0700 (PDT)
Received: from smtp02.uc3m.es (smtp02.uc3m.es [163.117.176.132]) by core3.amsl.com (Postfix) with ESMTP id 20B5D3A6841 for <behave@ietf.org>; Wed, 16 Sep 2009 00:26:29 -0700 (PDT)
Received: from marcelo-bagnulos-macbook-pro.local (wlap005.it.uc3m.es [163.117.139.108]) by smtp02.uc3m.es (Postfix) with ESMTP id 068466C1021; Wed, 16 Sep 2009 09:27:17 +0200 (CEST)
Message-ID: <4AB09354.80105@it.uc3m.es>
Date: Wed, 16 Sep 2009 09:27:16 +0200
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Xing Li <xing@cernet.edu.cn>
References: <4AA7730F.6040602@cernet.edu.cn>	<36ba02b00909141038i1611b5d6ide4fd96157ed2bc8@mail.gmail.com>	<6B55F0F93C3E9D45AF283313B8D342BA20F54E47@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <4AAF5485.1050701@cernet.edu.cn>
In-Reply-To: <4AAF5485.1050701@cernet.edu.cn>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-TM-AS-Product-Ver: IMSS-7.0.0.3116-5.6.0.1016-16890.003
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Security implications of protocol translation
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/mail-archive/web/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>
X-List-Received-Date: Wed, 16 Sep 2009 07:26:31 -0000

Xing Li escribió:
> Christian Huitema 写道:
>> Reading a couple drafts, I was wondering about the security aspects 
>> of protocol translation.
>> Take the IPv4 Internet to IPv6 network scenario. It differs from the 
>> "classic IPv4 NAT" in one great respect. While the IPv4 NAT mostly 
>> acts as the border between "the Internet" and "the private network", 
>> the v6-v4 NAT acts mostly as a bridge, not a border. The bridge can 
>> be accessed by the IPv4 Internet", as expected, but it could also be 
>> accessed from the IPv6 Internet, since we suppose connectivity 
>> between the IPv6 network and the IPv6 Internet. Accessibility from 
>> both sides clearly creates a different level of risk.
>>
>> Or take the scenario of stateless translators sitting on the 
>> Internet, and accessible by pretty much everybody. These are 
>> essentially alternate paths for reaching IPv4 or IPv6 hosts. It seems 
>> to me that such translators will have many of the security properties 
>> of "anonymous relays", such as for example 6to4 gateways.   
>
> We have done some analysis for the stateless translator.
>
> An IPv6 host in administrative domain B may send the packets to the 
> stateless translator in administrative domain A. Since the source 
> address of the packets is not a IPv4-mapped address in domain A, the 
> translator will drop the packets.
right, this is another way of doing it.
the filtering can either be configured in the ingress routers of the 
site or in the translator itself.

Regards, marcelo


>
>
> xing
>
>> I wonder how much of these security implications are already 
>> analyzed. I would very much like to take this analysis into 
>> consideration before the next iteration of the address format draft.
>>
>> -- Christian Huitema
>>
>>
>>
>>
>> _______________________________________________
>> 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 marcelo@it.uc3m.es  Wed Sep 16 00:30:34 2009
Return-Path: <marcelo@it.uc3m.es>
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 49C293A6976 for <behave@core3.amsl.com>; Wed, 16 Sep 2009 00:30:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.563
X-Spam-Level: 
X-Spam-Status: No, score=-6.563 tagged_above=-999 required=5 tests=[AWL=0.036,  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 DRriL1voiB3Y for <behave@core3.amsl.com>; Wed, 16 Sep 2009 00:30:26 -0700 (PDT)
Received: from smtp02.uc3m.es (smtp02.uc3m.es [163.117.176.132]) by core3.amsl.com (Postfix) with ESMTP id E29593A6975 for <behave@ietf.org>; Wed, 16 Sep 2009 00:30:20 -0700 (PDT)
Received: from marcelo-bagnulos-macbook-pro.local (wlap005.it.uc3m.es [163.117.139.108]) by smtp02.uc3m.es (Postfix) with ESMTP id 674186BA79C; Wed, 16 Sep 2009 09:31:06 +0200 (CEST)
Message-ID: <4AB0943A.90605@it.uc3m.es>
Date: Wed, 16 Sep 2009 09:31:06 +0200
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Christian Huitema <huitema@microsoft.com>
References: <4AA7730F.6040602@cernet.edu.cn>	<36ba02b00909141038i1611b5d6ide4fd96157ed2bc8@mail.gmail.com> <6B55F0F93C3E9D45AF283313B8D342BA20F54E47@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <4AAF2C06.2020107@it.uc3m.es> <6B55F0F93C3E9D45AF283313B8D342BA20F557D0@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <4AAFA425.7040706@it.uc3m.es> <6B55F0F93C3E9D45AF283313B8D342BA20F55829@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <6B55F0F93C3E9D45AF283313B8D342BA20F55829@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-TM-AS-Product-Ver: IMSS-7.0.0.3116-5.6.0.1016-16890.003
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Security implications of protocol translation
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/mail-archive/web/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>
X-List-Received-Date: Wed, 16 Sep 2009 07:30:34 -0000

Christian Huitema escribió:
>> So, summarizing, if we configure filters in border routers, we can
>> prevent off site attackers, for both the state full and stateless
>> translators (we need more fine grained filters for the stateless case,
>> but still seems feasoble imho)
>>     
>
> I really don't think we can assume more than basic filters in most site routers. The lower common denominator seems to be egress filtering. That is, sites will only accept incoming packets that are bound to the site's prefix, will normally not accept incoming packets whose source address belongs to that prefix, and will not allow outgoing packets whose source address does not belong to the site prefix.
>   
So, this will solve the issue for the case the translator is using the 
WK prefix, correct?
The case of the LIR prefix would not be covered by this, since the LIR 
prefix is part of the site's prefix. Would xing's configuration of 
filters int he trnaslator itself would seem acceptable to you? I mean, 
in that case, the filters are configured in the translator itself, so 
that it doesn't forward any packet with a source address coming from a 
source address that doesn't belong to a local host i.e. the translator 
verifies the embedded IPv4 prefix.

Regards, marcelo


>   
>> If we have these filters in place, on site attackers can still use the
>> stateless translator to spoof source addresses. AFAICT, this is similar
>> to what any IPv4 site can do today and this can be handled by the ISP of
>> the site putting ingress filters in place.
>>
>> Am i missing something?
>>     
>
> I think we have to assume egress filtering, as described above, and not require specific filters. Certainly not filters that attempt to dissect the host part of an address. The technology we design should work with such basic filters, and should not add extra risks.
>
> -- Christian Huitema
>
>
>
>
>   


From xing@cernet.edu.cn  Wed Sep 16 01:40:21 2009
Return-Path: <xing@cernet.edu.cn>
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 1E59E3A6841 for <behave@core3.amsl.com>; Wed, 16 Sep 2009 01:40:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.428
X-Spam-Level: 
X-Spam-Status: No, score=0.428 tagged_above=-999 required=5 tests=[AWL=0.331,  BAYES_00=-2.599, FH_HAS_XAIMC=2.696]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ebw5yGXfuYEk for <behave@core3.amsl.com>; Wed, 16 Sep 2009 01:40:20 -0700 (PDT)
Received: from cernet.edu.cn (sea.net.edu.cn [202.112.3.66]) by core3.amsl.com (Postfix) with SMTP id 938323A68DE for <behave@ietf.org>; Wed, 16 Sep 2009 01:40:18 -0700 (PDT)
Received: from [10.140.165.181]([117.136.0.188]) by cernet.edu.cn(AIMC 3.2.0.0) with SMTP id jm164ab0b1d5; Wed, 16 Sep 2009 16:40:43 +0800
Message-ID: <4AB0A353.8060407@cernet.edu.cn>
Date: Wed, 16 Sep 2009 16:35:31 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: marcelo bagnulo braun <marcelo@it.uc3m.es>
References: <4AA7730F.6040602@cernet.edu.cn>	<36ba02b00909141038i1611b5d6ide4fd96157ed2bc8@mail.gmail.com>	<6B55F0F93C3E9D45AF283313B8D342BA20F54E47@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <4AAF5485.1050701@cernet.edu.cn> <4AB09354.80105@it.uc3m.es>
In-Reply-To: <4AB09354.80105@it.uc3m.es>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-AIMC-AUTH: xing
X-AIMC-MAILFROM: xing@cernet.edu.cn
X-AIMC-Msg-ID: tRLEqnWB
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Security implications of protocol translation
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/mail-archive/web/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>
X-List-Received-Date: Wed, 16 Sep 2009 08:40:21 -0000

marcelo bagnulo braun 写道:
> Xing Li escribió:
>> Christian Huitema 写道:
>>> Reading a couple drafts, I was wondering about the security aspects 
>>> of protocol translation.
>>> Take the IPv4 Internet to IPv6 network scenario. It differs from the 
>>> "classic IPv4 NAT" in one great respect. While the IPv4 NAT mostly 
>>> acts as the border between "the Internet" and "the private network", 
>>> the v6-v4 NAT acts mostly as a bridge, not a border. The bridge can 
>>> be accessed by the IPv4 Internet", as expected, but it could also be 
>>> accessed from the IPv6 Internet, since we suppose connectivity 
>>> between the IPv6 network and the IPv6 Internet. Accessibility from 
>>> both sides clearly creates a different level of risk.
>>>
>>> Or take the scenario of stateless translators sitting on the 
>>> Internet, and accessible by pretty much everybody. These are 
>>> essentially alternate paths for reaching IPv4 or IPv6 hosts. It 
>>> seems to me that such translators will have many of the security 
>>> properties of "anonymous relays", such as for example 6to4 gateways.   
>>
>> We have done some analysis for the stateless translator.
>>
>> An IPv6 host in administrative domain B may send the packets to the 
>> stateless translator in administrative domain A. Since the source 
>> address of the packets is not a IPv4-mapped address in domain A, the 
>> translator will drop the packets.
> right, this is another way of doing it.
> the filtering can either be configured in the ingress routers of the 
> site or in the translator itself.

agree. xing

>
> Regards, marcelo
>
>
>>
>>
>> xing
>>
>>> I wonder how much of these security implications are already 
>>> analyzed. I would very much like to take this analysis into 
>>> consideration before the next iteration of the address format draft.
>>>
>>> -- Christian Huitema
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> 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 magnus.westerlund@ericsson.com  Wed Sep 16 02:56:02 2009
Return-Path: <magnus.westerlund@ericsson.com>
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 C64753A6AD3 for <behave@core3.amsl.com>; Wed, 16 Sep 2009 02:56:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.517
X-Spam-Level: 
X-Spam-Status: No, score=-5.517 tagged_above=-999 required=5 tests=[AWL=0.732,  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 gn9+0zV9ffc9 for <behave@core3.amsl.com>; Wed, 16 Sep 2009 02:56:02 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62]) by core3.amsl.com (Postfix) with ESMTP id 861493A69BA for <behave@ietf.org>; Wed, 16 Sep 2009 02:56:01 -0700 (PDT)
X-AuditID: c1b4fb3e-b7b2cae000005a8f-43-4ab0b660e245
Received: from esealmw128.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw4.ericsson.se (Symantec Mail Security) with SMTP id B1.0E.23183.F56B0BA4; Wed, 16 Sep 2009 11:56:48 +0200 (CEST)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.170]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 16 Sep 2009 11:56:26 +0200
Received: from [147.214.183.250] ([147.214.183.250]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 16 Sep 2009 11:56:25 +0200
Message-ID: <4AB0B649.4080906@ericsson.com>
Date: Wed, 16 Sep 2009 11:56:25 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Dave Thaler <dthaler@microsoft.com>
References: <4A6D9D29.2050901@ericsson.com> <4AADED78.7010905@ericsson.com> <E4561B14EE2A3E4E9D478EBFB5416E1B1CC70457@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <E4561B14EE2A3E4E9D478EBFB5416E1B1CC70457@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-OriginalArrivalTime: 16 Sep 2009 09:56:25.0421 (UTC) FILETIME=[F400A7D0:01CA36B3]
X-Brightmail-Tracker: AAAAAA==
Cc: Tim Polk <tim.polk@nist.gov>, Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Discusses regarding security mechanism usage for TURN
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/mail-archive/web/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>
X-List-Received-Date: Wed, 16 Sep 2009 09:56:02 -0000

Dave Thaler skrev:
> Magnus Westerlund writes:
>> NEW:
>>    [RFC5389] specifies a Long-Term Credential mechanism for STUN.  TURN
>>    servers and clients MUST implement this mechanism.  The server MUST
>>    demand that all requests from the client be authenticated using this
>>    mechanism, or that a equally strong or stronger mechanism for client
>>    authentication is used. One such mechanism is TLS, if using client
>>    and server certificates that actually identify the parties, i.e. no
>>    self-signed certificates.  The client MUST always be prepared to
>>    authenticate requests use the Long-Term Credential mechanism if
>>    required.
> 
> IF we go with MUST, then I disagree with the phrasing
> " if using client and server certificates that actually identify 
> the parties, i.e. no self-signed certificates"
> My understanding is that whether the certificates are self-signed or 
> signed by someone else is irrelevant.  What is relevant is whether they're
> signed by something that the server trusts.  The server can certainly
> be configured to trust a specific self-signed cert.
> 
> Suggest "if using client certificates that the server trusts" or
> equivalent wording, if the decision is to go with the proposed new text.

Yes, I think that is a better wording. No problem with such a change
from my perspective.

Cheers

Magnus Westerlund

IETF Transport Area Director
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------

From iljitsch@muada.com  Wed Sep 16 02:56:27 2009
Return-Path: <iljitsch@muada.com>
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 B846E3A6AD7 for <behave@core3.amsl.com>; Wed, 16 Sep 2009 02:56:27 -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 b-iLAO+nKJYH for <behave@core3.amsl.com>; Wed, 16 Sep 2009 02:56:26 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2]) by core3.amsl.com (Postfix) with ESMTP id 8C14A3A6AC4 for <behave@ietf.org>; Wed, 16 Sep 2009 02:56:26 -0700 (PDT)
Received: from [IPv6:2001:720:410:100f:223:32ff:fec4:ba94] ([IPv6:2001:720:410:100f:223:32ff:fec4:ba94]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id n8G9v53X088441 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 16 Sep 2009 11:57:05 +0200 (CEST) (envelope-from iljitsch@muada.com)
Mime-Version: 1.0 (Apple Message framework v1076)
Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <a7c8d0a30909151846w6f85cc67je3774c93e298f2e1@mail.gmail.com>
Date: Wed, 16 Sep 2009 11:57:09 +0200
Content-Transfer-Encoding: 7bit
Message-Id: <C37FF658-CF1A-4106-ABD9-2DB18B97B2CF@muada.com>
References: <a7c8d0a30909150630i29d535bbhf3089fdfecffa328@mail.gmail.com> <7CB993A6-829C-46CC-A74C-7DBF7CFE88C6@muada.com> <a7c8d0a30909150838s230397d9r3cbffb5df6097b76@mail.gmail.com> <273D4852-D26C-497E-A034-2C3EE4908660@muada.com> <a7c8d0a30909151846w6f85cc67je3774c93e298f2e1@mail.gmail.com>
To: Zhen Cao <caozhenpku@gmail.com>
X-Mailer: Apple Mail (2.1076)
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Comments on NAT64 draft
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/mail-archive/web/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>
X-List-Received-Date: Wed, 16 Sep 2009 09:56:27 -0000

On 16 Sep 2009, at 3:46 , Zhen Cao wrote:

> a) if frag1 arrives at the NAT64 first (it includes the port number),
> the NAT will choose an IPv4 address T and port t for translation and
> creates an mapping entry from <Y', y> to <T, t>. When frag2 arrives
> later, it  knows how to translate by querying the mapping table.

Right. Suppose the following mapping table:

1: TCP 2001::abc/1025, 1000::10.0.0.1/80 -> 192.0.2.1/16000, 10.0.0.1/80
2: TCP 2001::abc/1026, 1000::172.16.0.255/993 -> 192.0.2.1/16001,  
172.16.0.255/993
3: TCP 2001::bdf/1025, 1000::10.0.0.1/80 -> 192.0.2.45/16002,  
10.0.0.1/80
4: TCP 2001::abc/1027, 1000::10.0.0.1/80 -> 192.0.2.1/16003, 10.0.0.1/80

If the fragment has TCP, src=2001::abc/1025, dst=1000::10.0.0.1/80 the  
mapping query will provide a hit on mapping 1, so this works.

> b) if frag2 arrives at the NAT64 first (it does NOT include the port
> number), the NAT has not yet created the mapping entry  <Y', y> to <T,
> t>.  How to translate this frag2 in this case?

In this case the mapping lookup will be done on the addresses and  
protocol only, so a lookup for TCP, src=2001::abc, dst=1000::10.0.0.1  
will match both 1 and 4. However, this is not a problem, because the  
only information needed for the translation is the translated source  
address 192.0.2.1, which is the same for both mappings so the  
ambiguity is irrelevant.

The only problematic case is one where there is no match because this  
is the first packet (and a non-first fragment). In that case the  
fragment must be dropped, because a mapping can't be created without  
port numbers.

From magnus.westerlund@ericsson.com  Wed Sep 16 04:04:48 2009
Return-Path: <magnus.westerlund@ericsson.com>
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 E371B3A6941 for <behave@core3.amsl.com>; Wed, 16 Sep 2009 04:04:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.527
X-Spam-Level: 
X-Spam-Status: No, score=-5.527 tagged_above=-999 required=5 tests=[AWL=0.722,  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 NpW9u7AccdRq for <behave@core3.amsl.com>; Wed, 16 Sep 2009 04:04:47 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60]) by core3.amsl.com (Postfix) with ESMTP id 6ACA93A68EB for <behave@ietf.org>; Wed, 16 Sep 2009 04:04:47 -0700 (PDT)
X-AuditID: c1b4fb3c-b7b6eae000001984-5f-4ab0c67a6396
Received: from esealmw126.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw3.ericsson.se (Symantec Mail Security) with SMTP id E1.9B.06532.A76C0BA4; Wed, 16 Sep 2009 13:05:30 +0200 (CEST)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.174]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 16 Sep 2009 13:05:29 +0200
Received: from [147.214.183.250] ([147.214.183.250]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 16 Sep 2009 13:05:29 +0200
Message-ID: <4AB0C679.7070605@ericsson.com>
Date: Wed, 16 Sep 2009 13:05:29 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: matthew@matthew.at
References: <4A6D9D29.2050901@ericsson.com> <4AAE67F5.1040003@matthew.at>
In-Reply-To: <4AAE67F5.1040003@matthew.at>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-OriginalArrivalTime: 16 Sep 2009 11:05:29.0864 (UTC) FILETIME=[9A487880:01CA36BD]
X-Brightmail-Tracker: AAAAAA==
Cc: Tim Polk <tim.polk@nist.gov>, Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Discusses regarding security mechanism usage for TURN
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/mail-archive/web/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>
X-List-Received-Date: Wed, 16 Sep 2009 11:04:49 -0000

Hi Matthew,

Tim and Cullen can you please comment also.

I think you have me convinced about the placement on the border of an
enterprise domain and only serve internal requests. I can't answer for
the other ADs. Cullen has raised concerns that the document isn't well
structured to describe this usage in good way.

Can you propose how to implement this deployment scenario in the
document such that is made clear the following:

- Only in this specific deployment may it be ok to not use individual
authentication.
- What requirements it puts on the TURN server when it comes to usage.
In other words, what messages MUST be comming from the internal side and
 how to determine that.

Best Regards

Magnus


Matthew Kaufman skrev:
> And to second what Hadriel Kaplan asked,...
> 
> Magnus Westerlund wrote:
>> The main usage of TURN will be with publicly reachable
>> relays. In most cases located outside of firewalls belonging to
>> companies, governmental agencies, private homes, etc. These firewalls
>> needs to have a certain trust in TURN so that they allow TURN to pass
>> through. The security vulnerabilities that exist with TURN if
>> authentication is not used, will prevent that trust to exist. 
> 
> I don't understand this argument at all. There are only a few firewall
> configurations that matter:
> 
> 1) Deciding whether or not to enable outbound access from my client PCs
> to the TURN port generally.
> 
> In this case, I need to decide if I'm ok with my PC users initiating UDP
> sessions to a service that I may not control at all. Having TURN
> long-term-credentials mandatory makes no difference here, because an
> evil TURN server could just let anyone in... or it might not even run
> TURN but instead run some other evil protocol.
> 
> I also need to decide if I'm ok with my PC users using such a thing to
> get traffic relayed back to them... but then I have that same problem
> when I let them use HTTP to get to the outside world.
> 
> 2) Deciding whether or not to enable outbound access from my client PCs
> to a *specific* TURN server (port and IP address).
> 
> In this case, I need to decide if I'm ok with my PC users initiating UDP
> sessions to a specific server which I then need to trust. I trust this
> best if it is in a DMZ that I control so that I can prevent
> externally-initiated traffic from coming to the TURN port/address, but I
> might for whatever reason need to trust one that is out on the wild
> Internet. That's not as safe, and so then I need to consider whether its
> operator is or is not running it in a relatively safe manner, and
> long-term credentials is something I might expect them to have turned on.
> 
> 3) Deciding whether or not to enable inbound access to a TURN server I
> am running.
> 
> In this case, I'm the provider of a TURN server accessible to other
> hosts that I don't control. Relaying traffic costs me money, so I need
> to do everything possible to make sure that I control who uses the
> server. Of course I'll enable long-term credentials. I'll also turn on a
> whole lot of logging, do traffic shaping, set up alerts for suspicious
> traffic patterns, etc. If I'm an IT department, I never open a port up
> without a full security analysis of the system I'm providing access to,
> so there's not really any way the port is getting opened without the
> server being set up properly first.
> 
> 
> None of these use cases is made safer by *requiring* long-term
> credential authentication, or any authentication. In use case 1, once
> you've allowed your clients out, they might be connecting to *anything*,
> and you don't really care if the server gets abused. In use case 2,
> you've still let your clients out and it still isn't really your problem
> if the server gets misused by others. In use case 3, you're the
> responsible operator of the server and so you already need to be fully
> aware of the risks of running such a thing in whatever mode you've
> configured it in.
> 
> The reality is that most firewalls will be configured to let UDP
> sessions initiated from inside go to the outside, on all ports, and a
> few (run by paranoid IT departments, as opposed to being freebies that
> come with home gateways) will be configured to let *no* UDP sessions
> initiated from inside to go to the outside. The latter ones may make
> exceptions for specific ports, but TURN's advertised ability to be used
> as a way for people to get back to the originating host will make that
> one of the less-likely exceptions... and mandatory authentication
> doesn't solve the problem they're worried about at all.
> 
> Matthew Kaufman
> 


-- 

Magnus Westerlund

IETF Transport Area Director
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------

From remi.despres@free.fr  Wed Sep 16 04:57:49 2009
Return-Path: <remi.despres@free.fr>
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 334913A697C; Wed, 16 Sep 2009 04:57:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.777
X-Spam-Level: 
X-Spam-Status: No, score=-1.777 tagged_above=-999 required=5 tests=[AWL=0.172,  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 sIljS9WX2PDI; Wed, 16 Sep 2009 04:57:48 -0700 (PDT)
Received: from smtp6-g21.free.fr (smtp6-g21.free.fr [212.27.42.6]) by core3.amsl.com (Postfix) with ESMTP id 2C1E73A6986; Wed, 16 Sep 2009 04:57:45 -0700 (PDT)
Received: from smtp6-g21.free.fr (localhost [127.0.0.1]) by smtp6-g21.free.fr (Postfix) with ESMTP id 2915DE0814D; Wed, 16 Sep 2009 13:58:29 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by smtp6-g21.free.fr (Postfix) with ESMTP id 00F67E0819A; Wed, 16 Sep 2009 13:58:26 +0200 (CEST)
In-Reply-To: <000701ca303b$3bc26600$d40c6f0a@china.huawei.com>
References: <000701ca303b$3bc26600$d40c6f0a@china.huawei.com>
Mime-Version: 1.0 (Apple Message framework v753.1)
Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed
Message-Id: <40B3335A-DF89-4036-A6E3-5DC20CE782C4@free.fr>
Content-Transfer-Encoding: quoted-printable
From: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
Date: Wed, 16 Sep 2009 13:58:25 +0200
To: Xu Xiaohu <xuxh@huawei.com>
X-Mailer: Apple Mail (2.753.1)
Cc: softwires@ietf.org, "'Templin, Fred L'" <Fred.L.Templin@boeing.com>, 'Behave WG' <behave@ietf.org>
Subject: Re: [BEHAVE] [Softwires] Some Thought about the Automatic Tunnel Address
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/mail-archive/web/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>
X-List-Received-Date: Wed, 16 Sep 2009 11:57:49 -0000

Le 8 sept. 09 =E0 06:17, Xu Xiaohu a =E9crit :

>> I floated the idea of a /96 for ISATAP during either an
>> intarea or ipv6 meeting several years ago (can't remember
>> which) but there was no uptake. Looking back, I don't see
>> any advantages, and in fact it goes against the model in
>> which IPv6 addresses beginning with other than '000' use
>> a 64-bit prefix.
>
> What's the real purpose of the above model (IPv6 addresses =20
> beginning with
> other than '000' use a 64-bit prefix)? Can somebody help explain it?

Xu,

I had the view that this statement badly needed a reliable =20
justification, and argued about it.

But it now happens that the study about routing-loop attacks =20
documented last August by Gabi Nakibly, in www.ops.ietf.org/lists/=20
v6ops/v6ops.2009/msg00601, leads IMHO to such a justification.

I tried to explain all this in www.ietf.org/mail-archive/web/behave/=20
current/msg06816.
You may find relevant to this discussion.

Regards,
RD



From caozhenpku@gmail.com  Wed Sep 16 06:07:08 2009
Return-Path: <caozhenpku@gmail.com>
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 D9A513A69E8 for <behave@core3.amsl.com>; Wed, 16 Sep 2009 06:07:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.485
X-Spam-Level: 
X-Spam-Status: No, score=-2.485 tagged_above=-999 required=5 tests=[AWL=0.114,  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 ebY+tEKc2pzw for <behave@core3.amsl.com>; Wed, 16 Sep 2009 06:07:08 -0700 (PDT)
Received: from mail-vw0-f201.google.com (mail-vw0-f201.google.com [209.85.212.201]) by core3.amsl.com (Postfix) with ESMTP id F26983A6819 for <behave@ietf.org>; Wed, 16 Sep 2009 06:07:07 -0700 (PDT)
Received: by vws39 with SMTP id 39so3240250vws.29 for <behave@ietf.org>; Wed, 16 Sep 2009 06:07:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=Y6UsMQ1we7BBTalVwuvqYuIHs5qFKePBuI2Wr5L4XD4=; b=aCUEO4PdsW8IAcsNw5RTSy45vXjFu4kunR5dORuseijYf7NQqzv9c6Q4QyPy+5gKAC hz6esCuMjLJ9vZKOaqmkCCRmktdUIRVMRECjRd2ElzR/USCvNIzJV6OXazlS+bSGhlie 3UgdVkOZoT18DpGsumFAjoBHI2sjp0tCQHMFg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=XC5NEdYsVYLQKkmH71aop4y2SCTx01iJkZsLiTaJuW/e+TbloiXNdu/+W/W6QQjJMA KjX8i4UinBvH4nlmH5D1whbdkQhn+pE1ThFw6NfB0pNbTGq8y/p0iov9abicltVpAprU oi/PzyJWEw5kjYesR6NQf9c5orwwHRTjC6RAI=
MIME-Version: 1.0
Received: by 10.220.69.15 with SMTP id x15mr1428241vci.73.1253106474273; Wed,  16 Sep 2009 06:07:54 -0700 (PDT)
In-Reply-To: <C37FF658-CF1A-4106-ABD9-2DB18B97B2CF@muada.com>
References: <a7c8d0a30909150630i29d535bbhf3089fdfecffa328@mail.gmail.com> <7CB993A6-829C-46CC-A74C-7DBF7CFE88C6@muada.com> <a7c8d0a30909150838s230397d9r3cbffb5df6097b76@mail.gmail.com> <273D4852-D26C-497E-A034-2C3EE4908660@muada.com> <a7c8d0a30909151846w6f85cc67je3774c93e298f2e1@mail.gmail.com> <C37FF658-CF1A-4106-ABD9-2DB18B97B2CF@muada.com>
Date: Wed, 16 Sep 2009 21:07:54 +0800
Message-ID: <a7c8d0a30909160607l1209993ajae733d2dc116532b@mail.gmail.com>
From: Zhen Cao <caozhenpku@gmail.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Comments on NAT64 draft
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/mail-archive/web/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>
X-List-Received-Date: Wed, 16 Sep 2009 13:07:08 -0000

On Wed, Sep 16, 2009 at 5:57 PM, Iljitsch van Beijnum
<iljitsch@muada.com> wrote:
> On 16 Sep 2009, at 3:46 , Zhen Cao wrote:
>
>> a) if frag1 arrives at the NAT64 first (it includes the port number),
>> the NAT will choose an IPv4 address T and port t for translation and
>> creates an mapping entry from <Y', y> to <T, t>. When frag2 arrives
>> later, it =A0knows how to translate by querying the mapping table.
>
> Right. Suppose the following mapping table:
>
> 1: TCP 2001::abc/1025, 1000::10.0.0.1/80 -> 192.0.2.1/16000, 10.0.0.1/80
> 2: TCP 2001::abc/1026, 1000::172.16.0.255/993 -> 192.0.2.1/16001,
> 172.16.0.255/993
> 3: TCP 2001::bdf/1025, 1000::10.0.0.1/80 -> 192.0.2.45/16002, 10.0.0.1/80
> 4: TCP 2001::abc/1027, 1000::10.0.0.1/80 -> 192.0.2.1/16003, 10.0.0.1/80
>
> If the fragment has TCP, src=3D2001::abc/1025, dst=3D1000::10.0.0.1/80 th=
e
> mapping query will provide a hit on mapping 1, so this works.
>
>> b) if frag2 arrives at the NAT64 first (it does NOT include the port
>> number), the NAT has not yet created the mapping entry =A0<Y', y> to <T,
>> t>. =A0How to translate this frag2 in this case?
>
> In this case the mapping lookup will be done on the addresses and protoco=
l
> only, so a lookup for TCP, src=3D2001::abc, dst=3D1000::10.0.0.1 will mat=
ch both
> 1 and 4. However, this is not a problem, because the only information nee=
ded
> for the translation is the translated source address 192.0.2.1, which is =
the
> same for both mappings so the ambiguity is irrelevant.
>
> The only problematic case is one where there is no match because this is =
the
> first packet (and a non-first fragment). In that case the fragment must b=
e
> dropped, because a mapping can't be created without port numbers.

Yes, that's what i meant. I forgot to mention it is the first packet
in the flow. But the NAT may wait for the first frag to arrive?
Anyway, do we need to define this behavior explicitly in the draft?

From iljitsch@muada.com  Wed Sep 16 06:15:05 2009
Return-Path: <iljitsch@muada.com>
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 9F3113A6A1E for <behave@core3.amsl.com>; Wed, 16 Sep 2009 06:15:05 -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 9wafza73xI92 for <behave@core3.amsl.com>; Wed, 16 Sep 2009 06:15:05 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2]) by core3.amsl.com (Postfix) with ESMTP id 781CC3A6A02 for <behave@ietf.org>; Wed, 16 Sep 2009 06:15:04 -0700 (PDT)
Received: from [IPv6:2001:720:410:100f:223:32ff:fec4:ba94] ([IPv6:2001:720:410:100f:223:32ff:fec4:ba94]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id n8GDFiea089693 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 16 Sep 2009 15:15:45 +0200 (CEST) (envelope-from iljitsch@muada.com)
Mime-Version: 1.0 (Apple Message framework v1076)
Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <a7c8d0a30909160607l1209993ajae733d2dc116532b@mail.gmail.com>
Date: Wed, 16 Sep 2009 15:15:48 +0200
Content-Transfer-Encoding: 7bit
Message-Id: <519DB330-54FD-4163-91A8-DF81290A10B5@muada.com>
References: <a7c8d0a30909150630i29d535bbhf3089fdfecffa328@mail.gmail.com> <7CB993A6-829C-46CC-A74C-7DBF7CFE88C6@muada.com> <a7c8d0a30909150838s230397d9r3cbffb5df6097b76@mail.gmail.com> <273D4852-D26C-497E-A034-2C3EE4908660@muada.com> <a7c8d0a30909151846w6f85cc67je3774c93e298f2e1@mail.gmail.com> <C37FF658-CF1A-4106-ABD9-2DB18B97B2CF@muada.com> <a7c8d0a30909160607l1209993ajae733d2dc116532b@mail.gmail.com>
To: Zhen Cao <caozhenpku@gmail.com>
X-Mailer: Apple Mail (2.1076)
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Comments on NAT64 draft
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/mail-archive/web/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>
X-List-Received-Date: Wed, 16 Sep 2009 13:15:05 -0000

On 16 Sep 2009, at 15:07 , Zhen Cao wrote:

>> The only problematic case is one where there is no match because  
>> this is the
>> first packet (and a non-first fragment). In that case the fragment  
>> must be
>> dropped, because a mapping can't be created without port numbers.

> Yes, that's what i meant. I forgot to mention it is the first packet
> in the flow. But the NAT may wait for the first frag to arrive?
> Anyway, do we need to define this behavior explicitly in the draft?

With TCP this can't realistically happen because the initial SYN is  
small enough to fit in any reasonable MTU.

With UDP it could happen. I guess if you ALWAYS get reordering and  
ALWAYS throw away the non-initial fragment of a first packet then  
there will be trouble with protocols like the DNS that send single  
packet transactions, because those will then consistently fail.

Any ideas from implementers? Is it problematic to have to buffer and  
reassemble UDP fragments that don't match any state in the v6->v4  
direction?

(Fortunately we don't have to do this in the v4->v6 direction, where  
denial of service attacks are a bigger risk, because new sessions  
aren't set up in this direction.)

From remi.despres@free.fr  Wed Sep 16 06:27:01 2009
Return-Path: <remi.despres@free.fr>
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 AD8BB3A69F8 for <behave@core3.amsl.com>; Wed, 16 Sep 2009 06:27:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.884
X-Spam-Level: 
X-Spam-Status: No, score=-0.884 tagged_above=-999 required=5 tests=[AWL=-0.735, BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_13=0.6, J_CHICKENPOX_19=0.6, J_CHICKENPOX_62=0.6, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cCqgkdhEU4fp for <behave@core3.amsl.com>; Wed, 16 Sep 2009 06:27:00 -0700 (PDT)
Received: from smtp6-g21.free.fr (smtp6-g21.free.fr [212.27.42.6]) by core3.amsl.com (Postfix) with ESMTP id 97F203A6896 for <behave@ietf.org>; Wed, 16 Sep 2009 06:26:59 -0700 (PDT)
Received: from smtp6-g21.free.fr (localhost [127.0.0.1]) by smtp6-g21.free.fr (Postfix) with ESMTP id 98BDBE080F0; Wed, 16 Sep 2009 15:27:43 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by smtp6-g21.free.fr (Postfix) with ESMTP id 35862E0812E; Wed, 16 Sep 2009 15:27:40 +0200 (CEST)
In-Reply-To: <36a593230909010933u657b573dgb56e59273dc9ce82@mail.gmail.com>
References: <095E4E4E-F4F5-4FFD-95D5-4D6C05608124@free.fr> <36a593230909010929j14f04b09i8deb0237f412de32@mail.gmail.com> <36a593230909010933u657b573dgb56e59273dc9ce82@mail.gmail.com>
Mime-Version: 1.0 (Apple Message framework v753.1)
Content-Type: text/plain; charset=WINDOWS-1252; delsp=yes; format=flowed
Message-Id: <831EF201-6BC6-49A6-B979-24AD71F5D7D7@free.fr>
Content-Transfer-Encoding: quoted-printable
From: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
Date: Wed, 16 Sep 2009 15:27:38 +0200
To: bo zhou <zhouboyj@gmail.com>
X-Mailer: Apple Mail (2.753.1)
Cc: Xing Li <xing@cernet.edu.cn>, Behave WG <behave@ietf.org>, Fred Baker <fred@cisco.com>, dthaler@microsoft.com
Subject: Re: [BEHAVE] IPv4-only and IPv6-only definitions
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/mail-archive/web/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>
X-List-Received-Date: Wed, 16 Sep 2009 13:27:01 -0000

Bo,

Apologies for the late answer.

Le 1 sept. 09 =E0 18:33, bo zhou a =E9crit :

>
> I think the  IP endpoint shall be defined combining with four aspects:
> a. the application type installed on the endpoint,
> b.the IP family stack supported by the endpoint
> c.the IP family routing assigned by a network
> d.available IP family connectivity

I don't see why you find d necessary: if an IPvX address is =20
available, the host can work in IPvX and cannot be considered IPvY-only.

> If the IPvX only endpoint is only focus on 6/4 translation =20
> framework, I agree with Remi that its connection traverses an IPv6/=20
> IPv4 translator. However, in general, we need not define IPvX only =20
> endpoint traverses translator.

You are right.
It's better to determine if an endpoint is IPvX-only independently =20
from other endpoints.

We have though to face that an endpoint that is IPv4/IPv6 as a =20
connection initiator may be IPv4-only as a connection acceptor =20
because it's only advertised address is IPv4.

Criteria that determine IP families of an endpoint (IPv4-only, IPv6-=20
only, or IPv4/IPv6) would then be:
a. IP families of the application
b. IP families of the host stack
c. IP families of assigned addresses
d. as a connection acceptor, IP families of advertised addresses

Regards,
RD


>
> Futrhermore, we can predict there should be some "endpoint" cannot =20
> easy to define as IPvX/Y only endpoint. for example:
> IPv4-inherited IPv6 host comprises an IPv4/IPv6 enabled end system =20
> dual-stack plus IPv6 routing in the network, IPv4/IPv6 applications =20=

> installed on the host. It implies two application instances with =20
> installed IPv4/IPv6 applications are capable of communication using =20=

> IPv6 =96 they have IPv4/IPv6 dual-stack, network support including =20
> routing in IPv6, IPv4/IPv6 applications can communicate with IPv4/=20
> IPv6 hosts respectively.
> Regards,
>
> Bo Zhou
>
>
> On Tue, Sep 1, 2009 at 6:40 PM, R=E9mi Despr=E9s =
<remi.despres@free.fr> =20
> wrote:
> Dave,
>
> I also also think that the current definition of IPv6-only needs =20
> more work.
>
> Here is an approach which, in my understanding, would improve the =20
> situation.
> (Whereas you introduced "connected", as an adjective for =20
> applications, it introduces "connections", and more precisely =20
> connection "endpoints" as objects that can be IPv6-only at one end =20
> and IPv4-only at the other end.)
>
>
> 1. The definition would become(in substance):
> "IPvX-only endpoint: In a connection that traverses an IPv6/IPv4 =20
> translator, the endpoint that works in IPvX. Reasons for this may =20
> be that: (1) its application is IPvX-only (not IPvY capable); (2) =20
> its node is IPvX-only (not IPvY-enabled); (3) if the endpoint is =20
> connection initiator, all known addresses of the other endpoint are =20=

> IPvX (and translatable to IPvY); if the endpoint is connection =20
> acceptor, all of its addresses known by other endpoint are IPvY =20
> (translatable to IPvX)."
>
> 2. In the text, IPv6-only entities that contain connection =20
> endpoints ("systems", "devices", "equipment", "nodes") would be =20
> renamed "IPv6-only endpoints".
>
> Regards,
> RD
>
>
> Le 1 sept. 09 =E0 00:54, Dave Thaler a =E9crit :
>
> "IPv6-only" is an adjective and can be used to describe a network,
> a host, or an application.
>
> The text in the framework doc says:
>   IPv6-only:  An IPv6-only implementation, in this context, comprises
>      an IPv6 enabled end system stack plus routing in the network.  It
>      implies that two application instances are capable of
>      communicating using IPv6, but not IPv4 - they have an IPv6 stack,
>      addresses, and network support including routing in IPv6, but =20
> some
>      element is missing that prevents communication with IPv4 hosts.
>
> One problem with the above is that it confuses whether it's an =20
> adjective,
> or a term "IPv6-only implementation" or an "IPv6-only end system" or
> an "IPv6-only application"
> ...
> I think people would expect that an IP-version agnostic application =20=

> would be "IPv4-capable" but not necessarily "IPv4-connected".
>
>
>
>
>
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>
>
>
> --=20
> Regards,
>
> Bo Zhou
> China Mobile
>
>
>
> --=20
> Regards,
>
> Bo Zhou
> China Mobile


From iljitsch@muada.com  Wed Sep 16 06:48:19 2009
Return-Path: <iljitsch@muada.com>
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 250133A6A64 for <behave@core3.amsl.com>; Wed, 16 Sep 2009 06:48: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=[AWL=0.000, 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 zJv5ZMFKA2KJ for <behave@core3.amsl.com>; Wed, 16 Sep 2009 06:47:59 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2]) by core3.amsl.com (Postfix) with ESMTP id B04873A6A21 for <behave@ietf.org>; Wed, 16 Sep 2009 06:47:58 -0700 (PDT)
Received: from [IPv6:2001:720:410:100f:223:32ff:fec4:ba94] ([IPv6:2001:720:410:100f:223:32ff:fec4:ba94]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id n8GDmcwB089859 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <behave@ietf.org>; Wed, 16 Sep 2009 15:48:38 +0200 (CEST) (envelope-from iljitsch@muada.com)
From: Iljitsch van Beijnum <iljitsch@muada.com>
Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Date: Wed, 16 Sep 2009 15:48:43 +0200
Message-Id: <096B047D-DDB9-4890-A75C-50B9244A4AA9@muada.com>
To: Behave WG <behave@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1076)
X-Mailer: Apple Mail (2.1076)
Subject: [BEHAVE] IPvX-only meaningless?
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/mail-archive/web/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>
X-List-Received-Date: Wed, 16 Sep 2009 13:48:19 -0000

Does it make sense to spend many cycles on exploring what IPv4-only or  
IPv6-only really means?

In order to be able to communicate over a certain protocol, both ends  
need to have:

1. a network stack that supports the protocol and is enabled
2. an address for the protocol
3. a route to the correspondent's address
4. the ability to find the correspondent's address

And that for both ends, so 8 yes/no combinations = 256 permutations  
per IP version.

(Note that 4 is usually the DNS but it can also be a BitTorrent  
tracker or a SIP server or something like that.)

In only very few circumstances all four are limited to one protocol.  
Does it make sense to single out that unusual case?

A more common case will be that some of the steps can handle a given  
protocol, but others can't.

From cb.list6@gmail.com  Wed Sep 16 06:52:38 2009
Return-Path: <cb.list6@gmail.com>
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 73E763A6A22 for <behave@core3.amsl.com>; Wed, 16 Sep 2009 06:52:38 -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 0z7SNBrehk-g for <behave@core3.amsl.com>; Wed, 16 Sep 2009 06:52:37 -0700 (PDT)
Received: from mail-px0-f202.google.com (mail-px0-f202.google.com [209.85.216.202]) by core3.amsl.com (Postfix) with ESMTP id A47D93A6877 for <behave@ietf.org>; Wed, 16 Sep 2009 06:52:37 -0700 (PDT)
Received: by pxi40 with SMTP id 40so4095512pxi.5 for <behave@ietf.org>; Wed, 16 Sep 2009 06:53:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=i8isk2jHT1GVS4StCwX6MHy7VJACLcas3/LOAjrONIw=; b=md5QX437cx+Y/uPUpbFwcHn/ft4KoS7k3OzmbPYL1H1dQxIdWGEvjTR0jkEsm5S6sj u6dUS7ga6VBShWoGdo+Yu+ol5s/XujnXVZ8+FNiBym4s5IAYG59kVsFvZ+P/GSfv4bNA pkXM7HVAtKd0Q49bKfMHb5FsRGrM4ohn2GF9o=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=bf/IxgXSzFsn2EJf5bbcRaBNgOInNJirzVFnhgEjZBHtT+1Ct/9INCmYyuzMl3W2UG rH4BdgtdqMJCpT2s//Wf9/ut4gS3JppHjfR8eizsYx8ZnOKNe0stzF+dTNqf6PTtmA0M FzcqwS40jH4bT5y/aX4yyuRVAiy9XpuiFz7ss=
MIME-Version: 1.0
Received: by 10.142.67.7 with SMTP id p7mr626488wfa.251.1253109203015; Wed, 16  Sep 2009 06:53:23 -0700 (PDT)
In-Reply-To: <519DB330-54FD-4163-91A8-DF81290A10B5@muada.com>
References: <a7c8d0a30909150630i29d535bbhf3089fdfecffa328@mail.gmail.com> <7CB993A6-829C-46CC-A74C-7DBF7CFE88C6@muada.com> <a7c8d0a30909150838s230397d9r3cbffb5df6097b76@mail.gmail.com> <273D4852-D26C-497E-A034-2C3EE4908660@muada.com> <a7c8d0a30909151846w6f85cc67je3774c93e298f2e1@mail.gmail.com> <C37FF658-CF1A-4106-ABD9-2DB18B97B2CF@muada.com> <a7c8d0a30909160607l1209993ajae733d2dc116532b@mail.gmail.com> <519DB330-54FD-4163-91A8-DF81290A10B5@muada.com>
Date: Wed, 16 Sep 2009 06:53:22 -0700
Message-ID: <bcff0fba0909160653s59990a8al3cd29d12dab14095@mail.gmail.com>
From: Cameron Byrne <cb.list6@gmail.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Behave WG <behave@ietf.org>, Zhen Cao <caozhenpku@gmail.com>
Subject: Re: [BEHAVE] Comments on NAT64 draft
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/mail-archive/web/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>
X-List-Received-Date: Wed, 16 Sep 2009 13:52:38 -0000

On Wed, Sep 16, 2009 at 6:15 AM, Iljitsch van Beijnum
<iljitsch@muada.com> wrote:
> On 16 Sep 2009, at 15:07 , Zhen Cao wrote:
>
>>> The only problematic case is one where there is no match because this is
>>> the
>>> first packet (and a non-first fragment). In that case the fragment must
>>> be
>>> dropped, because a mapping can't be created without port numbers.
>
>> Yes, that's what i meant. I forgot to mention it is the first packet
>> in the flow. But the NAT may wait for the first frag to arrive?
>> Anyway, do we need to define this behavior explicitly in the draft?
>
> With TCP this can't realistically happen because the initial SYN is small
> enough to fit in any reasonable MTU.
>
> With UDP it could happen. I guess if you ALWAYS get reordering and ALWAYS
> throw away the non-initial fragment of a first packet then there will be
> trouble with protocols like the DNS that send single packet transactions,
> because those will then consistently fail.
>
> Any ideas from implementers? Is it problematic to have to buffer and
> reassemble UDP fragments that don't match any state in the v6->v4 direction?

According to RFC 4787 Requirement 14, a NAT MUST accommodate this out
of order fragment situation.

>
> (Fortunately we don't have to do this in the v4->v6 direction, where denial
> of service attacks are a bigger risk, because new sessions aren't set up in
> this direction.)
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>

From huitema@microsoft.com  Wed Sep 16 06:55:22 2009
Return-Path: <huitema@microsoft.com>
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 72AC63A6A35 for <behave@core3.amsl.com>; Wed, 16 Sep 2009 06:55:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.554
X-Spam-Level: 
X-Spam-Status: No, score=-10.554 tagged_above=-999 required=5 tests=[AWL=0.045, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L9WPwqDlfA-i for <behave@core3.amsl.com>; Wed, 16 Sep 2009 06:55:21 -0700 (PDT)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.214]) by core3.amsl.com (Postfix) with ESMTP id 967C53A69F6 for <behave@ietf.org>; Wed, 16 Sep 2009 06:55:21 -0700 (PDT)
Received: from TK5EX14MLTC102.redmond.corp.microsoft.com (157.54.79.180) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.2.176.0; Wed, 16 Sep 2009 06:56:11 -0700
Received: from TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com (157.54.71.68) by TK5EX14MLTC102.redmond.corp.microsoft.com (157.54.79.180) with Microsoft SMTP Server id 14.0.639.20; Wed, 16 Sep 2009 06:56:10 -0700
Received: from TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com ([169.254.3.19]) by TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.68]) with mapi; Wed, 16 Sep 2009 06:56:12 -0700
From: Christian Huitema <huitema@microsoft.com>
To: Xing Li <xing@cernet.edu.cn>, marcelo bagnulo braun <marcelo@it.uc3m.es>
Thread-Topic: [BEHAVE] Security implications of protocol translation
Thread-Index: AQHKNckZMF3GDtqt2kuK6ErD8Y/t95DXsFRQgAB6jICAAP69gIAAD6tw
Date: Wed, 16 Sep 2009 13:56:09 +0000
Message-ID: <6B55F0F93C3E9D45AF283313B8D342BA20F5A151@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
References: <4AA7730F.6040602@cernet.edu.cn> <36ba02b00909141038i1611b5d6ide4fd96157ed2bc8@mail.gmail.com> <6B55F0F93C3E9D45AF283313B8D342BA20F54E47@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <4AAF2C06.2020107@it.uc3m.es> <6B55F0F93C3E9D45AF283313B8D342BA20F557D0@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <4AAFA425.7040706@it.uc3m.es> <4AB079D5.1010404@cernet.edu.cn>
In-Reply-To: <4AB079D5.1010404@cernet.edu.cn>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Security implications of protocol translation
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/mail-archive/web/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>
X-List-Received-Date: Wed, 16 Sep 2009 13:55:22 -0000

PiA+IFdpdGggdGhlIHN0YXRlbGVzcyB0cmFuc2xhdG9yIGlzIG1vcmUgY29tcGxpY2F0ZWQsIGkg
dGhpbmsuIHNpbmNlIHRoZQ0KPiA+IHNhbWUgcHJlZml4IGNhbiBiZSB1c2VkIHRvIG1ha2UgcmVw
cmVzZW50YXRpb24gb2YgZXh0ZXJuYWwgaG9zdHMgYW5kDQo+ID4gdG8gYXNzaWduIGludGVybmFs
IGhvc3RzLCB0aGVuIHRoZSBmaWx0ZW5yaW5nIG5lZWRzIHRvIGJlIGRvbmUgYmFzZWQNCj4gPiBv
biB0aGUgZW1iZWRkZWQgSVB2NCBhZGRyZXNzLCB3aGljaCBtYXkgcmVxdWlyZSBwZXIgSVB2NCBw
cmVmaXggZmlsdGVyDQo+ID4gY29uZmlndXJhdGlvbiB0aGUgYm9yZGVyIHJvdXRlcnMsIHdoaWNo
IG1heSBiZSBtb3JlIGNvbXBsaWNhdGVkLCBidXQgaQ0KPiA+IHRoaW5rIGl0IGlzIGZlYXNpYmxl
Li4uDQo+IA0KPiB0aGUgc3RhdGVsZXNzIHRyYW5zbGF0b3IgY2FuIGp1c3Qgc2ltcGxlIGRyb3Ag
dGhlIHBhY2tldHMsIGlmIHRoZXkgYXJlDQo+IG5vdCB0aGUgSVB2NC1tYXBwZWQgc291cmNlIGFk
ZHJlc3NlcyBpbiB0aGUgYWRtaW5pc3RyYXRpdmUgZG9tYWluLg0KDQpCdXQgZG9lc24ndCB0aGF0
IHJlcXVpcmUgc29tZSBhbW91bnQgb2Ygc3RhdGU/DQoNClN1cHBvc2UgdGhlIHRyYW5zbGF0b3Ig
aXMgbWFuYWdlZCBieSBhbiBJU1AsIGZvciB0aGUgc2VydmljZSBvZiBpdHMgY3VzdG9tZXJzLiBU
aGUgSVNQIG5ldHdvcmsgc2VydmVzIGEgbGFyZ2UgbnVtYmVyIG9mIGN1c3RvbWVycy4gSW4gbm9y
bWFsIElQdjYgcHJhY3RpY2UsIHRoZSBJU1AgaGFzIGFzc2lnbmVkIGFuIElQdjYgcHJlZml4IHRv
IGVhY2ggb2YgdGhlc2UgY3VzdG9tZXJzLiBUaGUgSVNQIHdhbnRzIHRvIHByb3ZpZGUgYSBzdGFi
bGUgSVB2NCBhZGRyZXNzIHRvIHNvbWUgaG9zdHMgb2YgdGhlc2UgY3VzdG9tZXJzLCB0aHJvdWdo
IGEgdHJhbnNsYXRpb24gc2VydmljZS4gT2J2aW91c2x5LCB0aGUgSVNQIGNhbm5vdCBwcm92aWRl
IHN0YWJsZSBJUHY0IGFkZHJlc3NlcyB0byBlYWNoIG9mIGhpcyBjdXN0b21lcnMsIGJlY2F1c2Ug
dGhlcmUgYXJlIGp1c3Qgbm90IGVub3VnaCBhZGRyZXNzZXMuDQoNCklmIEkgdW5kZXJzdGFuZCBj
b3JyZWN0bHksIHRoaXMgaXMgYSB0YXJnZXQgZGVwbG95bWVudCBmb3IgdGhlIHN0YXRlbGVzcyB0
cmFuc2xhdGlvbiBzZXJ2aWNlLiBUaGUgaG9zdHMgdG8gd2hpY2ggc3RhYmxlIElQdjQgYWRkcmVz
c2VzIGhhdmUgYmVlbiBhc3NpZ25lZCB3aWxsIGJlIGNvbmZpZ3VyZWQgd2l0aCBhbiBJUHY0IHRy
YW5zbGF0YWJsZSBJUHY0IGFkZHJlc3MuIFRoZSBJU1AgdHJhbnNsYXRvciB3aWxsIGFwcGx5IHN0
YXRlbGVzcyB0cmFuc2xhdGlvbiB3aGVuIHRoZSBvdXRnb2luZyBhZGRyZXNzIHNvdXJjZSBpcyBh
IHRyYW5zbGF0YWJsZSBhZGRyZXNzLCBzdGF0ZWZ1bCB0cmFuc2xhdGlvbiB3aGVuIGl0IGlzIG5v
dC4gDQoNCkxldCdzIGFzc3VtZSB0aGF0IHRoZSBjdXN0b21lciBzaXRlIHJvdXRlcnMgcGVyZm9y
bSBlZ3Jlc3MgZmlsdGVyaW5nLCB3aGljaCBpcyBnZW5lcmFsbHkgbWFuZGF0ZWQgYnkgb3RoZXIg
c2VjdXJpdHkgY29uc2lkZXJhdGlvbi4gV2UgaGF2ZSB0d28gcG9zc2liaWxpdGllcyB0aGVuOg0K
DQoxKSBBbGwgc291cmNlIGFkZHJlc3Nlcywgd2hldGhlciBJUHY0IHRyYW5zbGF0YWJsZSBvciBu
b3QsIG11c3QgYmUgYXNzaWduZWQgb3V0IG9mIHRoZSBJUHY2IHByZWZpeCBhc3NpZ25lZCBieSB0
aGUgSVNQIHRvIHRoZSBjdXN0b21lciBzaXRlOw0KDQoyKSBJUHY2IHRyYW5zbGF0YWJsZSBhZGRy
ZXNzZXMgdXNlIGEgc3BlY2lhbCBwcmVmaXgsIGRpZmZlcmVudCBmcm9tIHRoYXQgb2YgdGhlIGN1
c3RvbWVyIHNpdGUuDQoNCkZyYW5rbHksIEkgZG9uJ3QgdGhpbmsgdGhhdCB0aGUgc2Vjb25kIGNh
c2UgaXMgbWFuYWdlYWJsZS4gSXQgaW1wbGllcyBzcGVjaWFsIGNvbmZpZ3VyYXRpb24gaW4gbXVs
dGlwbGUgcm91dGVycywgaS5lLiBwdXNoaW5nIGFuZCBtYW5hZ2luZyBhIGxvdCBvZiBzdGF0ZSBp
bmZvcm1hdGlvbiwgd2hpY2ggc2VlbXMgdG8gZGVmZWF0IHRoZSB3aG9sZSBpZGVhIG9mIHN0YXRl
bGVzcyB0cmFuc2xhdGlvbi4gU28sIEkgd2lsbCBhc3N1bWUgdGhhdCB3ZSB1c2UgdGhlIGZpcnN0
IHZhcmlhdGlvbiwgaW4gd2hpY2ggdHJhbnNsYXRhYmxlIGFkZHJlc3NlcyBhcmUgZ2VuZXJhdGVk
IG91dCBvZiB0aGUgY3VzdG9tZXIgcHJlZml4ZXMuIFRoaXMgbWVhbnMgdGhhdCB0cmFuc2xhdGFi
bGUgYWRkcmVzc2VzIHdpbGwgb25seSBkaWZmZXIgZnJvbSB0aGUgcmVndWxhciBhZGRyZXNzZXMg
YnkgdGhlIHN0cnVjdHVyZSBvZiB0aGUgaG9zdCBpZGVudGlmaWVyLg0KDQpJZiB0aGF0IGlzIHRo
ZSBjYXNlLCBpZiB0cmFuc2xhdGFibGUgYWRkcmVzc2VzIG9ubHkgZGlmZmVyIGZyb20gdGhlIHJl
Z3VsYXIgYWRkcmVzc2VzIGJ5IHRoZSBzdHJ1Y3R1cmUgb2YgdGhlIGhvc3QgaWRlbnRpZmllciwg
aG93IGRvZXMgdGhlIHRyYW5zbGF0b3IgdmVyaWZ5IHRoYXQgY3VzdG9tZXIgQSBpcyBub3QgYXR0
ZW1wdGluZyB0byB1c2UgYW4gSVB2NCBhZGRyZXNzIGFzc2lnbmVkIHRvIGN1c3RvbWVyIEI/DQoN
Ci0tIENocmlzdGlhbiBIdWl0ZW1hDQoNCg0KDQo=

From xing@cernet.edu.cn  Wed Sep 16 06:56:56 2009
Return-Path: <xing@cernet.edu.cn>
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 F2E6828C0FA for <behave@core3.amsl.com>; Wed, 16 Sep 2009 06:56:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.847
X-Spam-Level: *
X-Spam-Status: No, score=1.847 tagged_above=-999 required=5 tests=[AWL=-0.700,  BAYES_00=-2.599, FH_HAS_XAIMC=2.696, MIME_CHARSET_FARAWAY=2.45]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BgLcvVg4J0R4 for <behave@core3.amsl.com>; Wed, 16 Sep 2009 06:56:55 -0700 (PDT)
Received: from cernet.edu.cn (sea.net.edu.cn [202.112.3.66]) by core3.amsl.com (Postfix) with SMTP id 469C028C0F8 for <behave@ietf.org>; Wed, 16 Sep 2009 06:56:53 -0700 (PDT)
Received: from [59.66.24.75]([59.66.24.75]) by cernet.edu.cn(AIMC 3.2.0.0) with SMTP id jm104ab0fc1c; Wed, 16 Sep 2009 21:57:37 +0800
Message-ID: <4AB0EECA.4070104@cernet.edu.cn>
Date: Wed, 16 Sep 2009 21:57:30 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Chen Gang <phdgang@gmail.com>
References: <4AA706C2.6020804@cernet.edu.cn>	<36ba02b00909141822m37c9239dy800f92c31f2b9a37@mail.gmail.com>	<4AB03B61.7080004@cernet.edu.cn> <36ba02b00909151925l72fc32d7o2489bb2893b32f44@mail.gmail.com>
In-Reply-To: <36ba02b00909151925l72fc32d7o2489bb2893b32f44@mail.gmail.com>
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: 8bit
X-AIMC-AUTH: xing
X-AIMC-MAILFROM: xing@cernet.edu.cn
X-AIMC-Msg-ID: tOrAvnWB
Cc: congxiao <congxiao@cernet.edu.cn>, Behave WG <behave@ietf.org>, Fred Baker <fred@cisco.com>, Kevin Yin <kyin@cisco.com>
Subject: Re: [BEHAVE] draft-ietf-behave-v6v4-framework-01 uploaded
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/mail-archive/web/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>
X-List-Received-Date: Wed, 16 Sep 2009 13:56:56 -0000

Chen Gang дµÀ:
>
>
>
>     We believe it is easier to describe the general mode as
>
>     (1) IPv4 ---- xlate ----- IPv6
>
>     If multiple translators are involved
>
>     (2) IPv4 ---- xlate1----IPv6----xlate2---IPv4
>
>     It can be decoupled as two (1)s cascading.
>
>     regards,
>
>     xing
>
> For multiple translators, I guess the following case can't match the
> number (2) cascading model:
> "A more interesting scenario is to integrate the functions of the
> first IVI translator into the end system. In this case, the
> application software is IPv4 based and there is no need to have ALG
> support in the IVI translator when it is communicating with IPv4 hosts."

how about

(2) IPv4 ---- xlate1----IPv6----xlate2---(IPv4/IPv6)

xing

> Looking forward to your reply!
> Thanks
> Gang
>
>
>
>         So, I suggest to add a new sort of adjective to deal with this
>         problem. We could define a general terms to cover various
>         IPv4/IPv6 implementations. Like following:
>
>         IPvX-adapted-IPvY implmentation: in this context, comprises an
>         IPvX/IPvY enabled end system stack, IPvX applications plus
>         IPvY routing and address in the network. It implies that two
>         application instances are capable of communicating using IPvY
>         by some sort of tranlations mechanisms to accomodate IPvY
>         environments.
>
>         The definition may need more works, but this sort of
>         definition could fill in a omission in current framework
>         defintions.
>
>         Thanks for your attantion.
>
>
>         Best Regards
>
>         Gang
>
>         2009/9/9 Xing Li <xing@cernet.edu.cn
>         <mailto:xing@cernet.edu.cn> <mailto:xing@cernet.edu.cn
>         <mailto:xing@cernet.edu.cn>>>
>
>
>         Hi, All,
>
>         Based on Dave's comment, the discussions in the mailing list
>         and the
>         meeting notes of IETF75, the authors have made the
>         modifications and
>         uploaded the 01 version of the Framework for IPv4/IPv6
>         Translation. Here
>         are some editorial notes.
>
>         (1) Most of the grammar and spelling errors are corrected.
>
>         (2) Terminology (Sec 1.2): Since the terminologies are not
>         consistent in
>         the current translation related documents. We will compile a list
>         of the
>         terminology and send to the behave@ietf.org
>         <mailto:behave@ietf.org>
>         <mailto:behave@ietf.org <mailto:behave@ietf.org>> to get the
>         consensus before
>
>         we modify the related documents.
>
>         (3) Address Translation (Sec. 3.1.1, etc): The discussion will
>         be move
>         to the address format document and we will insert the conclusion
>         in the
>         framework document later.
>
>         Please review this version and send your comments and suggestions,
>         so we
>         can edit the next version.
>
>         Regards,
>
>         xing
>
>
>
>
>
>         _______________________________________________
>         Behave mailing list
>         Behave@ietf.org <mailto:Behave@ietf.org>
>         <mailto:Behave@ietf.org <mailto:Behave@ietf.org>>
>
>         https://www.ietf.org/mailman/listinfo/behave
>
>
>         ------------------------------------------------------------------------
>
>
>
>         _______________________________________________
>         Behave mailing list
>         Behave@ietf.org <mailto:Behave@ietf.org>
>         https://www.ietf.org/mailman/listinfo/behave
>
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>   


From teemu.savolainen@nokia.com  Wed Sep 16 07:53:57 2009
Return-Path: <teemu.savolainen@nokia.com>
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 518093A682C for <behave@core3.amsl.com>; Wed, 16 Sep 2009 07:53:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.998
X-Spam-Level: 
X-Spam-Status: No, score=-5.998 tagged_above=-999 required=5 tests=[AWL=0.601,  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 66Guo4EnXQfC for <behave@core3.amsl.com>; Wed, 16 Sep 2009 07:53:56 -0700 (PDT)
Received: from mgw-mx06.nokia.com (smtp.nokia.com [192.100.122.233]) by core3.amsl.com (Postfix) with ESMTP id 0A0693A69CD for <behave@ietf.org>; Wed, 16 Sep 2009 07:53:55 -0700 (PDT)
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213]) by mgw-mx06.nokia.com (Switch-3.3.3/Switch-3.3.3) with ESMTP id n8GEsO1j014292; Wed, 16 Sep 2009 17:54:28 +0300
Received: from vaebh104.NOE.Nokia.com ([10.160.244.30]) by esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 16 Sep 2009 17:54:39 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.8]) by vaebh104.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 16 Sep 2009 17:54:28 +0300
Received: from NOK-EUMSG-01.mgdnok.nokia.com ([65.54.30.106]) by nok-am1mhub-04.mgdnok.nokia.com ([65.54.30.8]) with mapi; Wed, 16 Sep 2009 16:54:30 +0200
From: <teemu.savolainen@nokia.com>
To: <dthaler@microsoft.com>
Date: Wed, 16 Sep 2009 16:53:09 +0200
Thread-Topic: Comments on draft-denis-icmpv6-generation-for-teredo-00
Thread-Index: AcoKOIZyuTOrxeI5S+iI1NyOBmBztwAoFXsAABTsSWAK67NXAA==
Message-ID: <18034D4D7FE9AE48BF19AB1B0EF2729F3EEDFAA191@NOK-EUMSG-01.mgdnok.nokia.com>
References: <E4561B14EE2A3E4E9D478EBFB5416E1B1256B7@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com> <200907221029.47246.remi.denis-courmont@nokia.com> <E4561B14EE2A3E4E9D478EBFB5416E1B1285FB@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <E4561B14EE2A3E4E9D478EBFB5416E1B1285FB@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 16 Sep 2009 14:54:28.0286 (UTC) FILETIME=[97054DE0:01CA36DD]
X-Nokia-AV: Clean
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Comments on draft-denis-icmpv6-generation-for-teredo-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/mail-archive/web/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>
X-List-Received-Date: Wed, 16 Sep 2009 14:53:57 -0000

Hi Dave, behave,

We've updated this draft based on received feedback: http://www.ietf.org/id=
/draft-denis-icmpv6-generation-for-teredo-01.txt

1) We tried to tackle this by adding more text clarifying reply generation =
MUST only be done if middlebox is certainly on the return path and also cla=
rification that host-specific relay function could otherwise break.

2) We'd like more clarification on this: how discovery is made easier when =
compared to attacker just sending ICMPv6 Echo Requests to various IPv6 peer=
s out there?=20

3) Yes, but blindly responding might make middlebox act as reflector on som=
e attacks - i.e. there should be some sanity in ICMPv6 echo reply generatio=
n. Then again, this is about the same for any host/server and from that poi=
nt of view useless to have in this document? Therefore we are consider drop=
ping that piece of text out.

4) Right, but which one is worse: false negative or false positive reply of=
 peer's liveness? The ICMPv6 anyway only tells the peer's lower layers are =
alive, but nothing about application layer stuff.=20

We also added some text on CGA.

Best regards,

	Teemu

>-----Original Message-----
>From: ext Dave Thaler [mailto:dthaler@microsoft.com]=20
>Sent: 23 July, 2009 03:36
>To: Denis-Courmont Remi (Nokia-D/Helsinki)
>Cc: Savolainen Teemu (Nokia-D-MSW/Tampere); Behave WG
>Subject: RE: Comments on draft-denis-icmpv6-generation-for-teredo-00
>
>I forwarded the doc to our Teredo implementers and have some=20
>additional feedback from them to pass along.
>
>1) The option for "Forced ICMPv6 Echo Reply generation for clients"
>mentioned in 2.1 is especially problematic in that it breaks=20
>the concept of a host-specific relay (a dual-stack host that=20
>is acting as a relay for itself).
>
>2) A security consideration is that this draft makes discovery=20
>of Teredo relays much easier for an attacker, when then makes=20
>it easier to mount attacks against them.
>
>3) Section 5 talks about rate limiting.  If you rate limit,=20
>then you limit the usefulness because communication won't be=20
>established.
>
>4) There are applications that consider ping replies as an=20
>indicator of liveness (e.g., when picking which IP address to=20
>use among a set, or whatever else).  Spoofing echo responses=20
>will cause such apps to have expected behavior.
>
>
>> -----Original Message-----
>> From: R=E9mi Denis-Courmont [mailto:remi.denis-courmont@nokia.com]
>> Sent: Wednesday, July 22, 2009 12:30 AM
>> To: Dave Thaler
>> Cc: Savolainen Teemu (Nokia-D-MSW/Tampere); Behave WG
>> Subject: Re: Comments on draft-denis-icmpv6-generation-for-teredo-00
>>
>> On Tuesday 21 July 2009 22:22:02 ext Dave Thaler wrote:
>> > Section 2.2 talks about translators sending (spoofed) echo replies=20
>> > by default. However, if the translator is not guaranteed to be on=20
>> > the
>> reverse
>> > path, e.g. in the case of multiple stateless translators, this is=20
>> > dangerous. At minimum, the SHALL's need to be constrained to cases
>> where
>> > the translator is guaranteed to be on the reverse path.
>>
>> I don't disagree that a clarification would be good.
>>
>> However, I think it depends on how "a" translator is=20
>defined. I think=20
>> we can all agree that there has to be translation in both=20
>paths. Then=20
>> it depends whether one thinks of the translator as an abstract whole=20
>> system or as a physical box between wires.
>>
>> Indeed, if the inbound and outbound boxes are distinct, stateless,=20
>> unable to communicate with one another *and* topologically separate,=20
>> there is a problem.
>>
>> > Section 2.3 states that firewalls SHOULD send (spoofed)=20
>echo replies=20
>> > to Teredo addresses.  This is again too strong.  If the firewall=20
>> > would block incoming unsolicited packets from Teredo clients, then=20
>> > it shouldn't send echo replies.  At minimum, the SHOULD=20
>needs to be=20
>> > constrained to a case where it would actually allow=20
>packets through=20
>> > from that address.
>>
>> Right.
>>
>> --
>> R=E9mi Denis-Courmont
>> Nokia Devices R&D, Maemo Software, Helsinki
>>
>
>=

From iljitsch@muada.com  Wed Sep 16 09:19:25 2009
Return-Path: <iljitsch@muada.com>
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 46CCA3A687D for <behave@core3.amsl.com>; Wed, 16 Sep 2009 09:19:25 -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 QP+f1+fbLQQ0 for <behave@core3.amsl.com>; Wed, 16 Sep 2009 09:19:24 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2]) by core3.amsl.com (Postfix) with ESMTP id 1A28B3A681F for <behave@ietf.org>; Wed, 16 Sep 2009 09:19:23 -0700 (PDT)
Received: from [IPv6:2001:720:410:100f:223:32ff:fec4:ba94] ([IPv6:2001:720:410:100f:223:32ff:fec4:ba94]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id n8GGK2S4090846 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 16 Sep 2009 18:20:03 +0200 (CEST) (envelope-from iljitsch@muada.com)
From: Iljitsch van Beijnum <iljitsch@muada.com>
Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Date: Wed, 16 Sep 2009 18:20:07 +0200
Message-Id: <CC03EB36-4761-4FF7-8220-FC9C0D4AB9B6@muada.com>
To: Dan Wing <dwing@cisco.com>
Mime-Version: 1.0 (Apple Message framework v1076)
X-Mailer: Apple Mail (2.1076)
Cc: Behave WG <behave@ietf.org>
Subject: [BEHAVE] Try EPSV or PASV first
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/mail-archive/web/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>
X-List-Received-Date: Wed, 16 Sep 2009 16:19:25 -0000

Dan,

Any chance of running another test case on the set of FTP servers again?

It looks like at least some FTP servers respond with the remote (from  
the server's persective) IP address to the STAT command.  
Unfortunately, not the Microsoft FTP server.

So if the server mentions an IPv4 address in its login banner or in  
response to STAT, do PASV. If it mentions an IPv6 address, do EPSV.

Server administrators could then simply put an IP address in the  
banner to trigger the desired behavior.

Another hint could be the structure of the IPv6 address: if bits 64 -  
95 are 0:0 or 0:ffff (or whatever else we settle on) that could  
indicate that the destination goes through a translator.

But I would really like to be at least somewhat conservative here and  
not break regular IPv6 operation just so we can talk to a handful of  
broken IPv4 servers a bit faster.

From fluffy@cisco.com  Wed Sep 16 10:24:37 2009
Return-Path: <fluffy@cisco.com>
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 C6CB23A69C8 for <behave@core3.amsl.com>; Wed, 16 Sep 2009 10:24:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.519
X-Spam-Level: 
X-Spam-Status: No, score=-106.519 tagged_above=-999 required=5 tests=[AWL=0.080, 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 teALZ49Pyy-K for <behave@core3.amsl.com>; Wed, 16 Sep 2009 10:24:37 -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 19C523A692E for <behave@ietf.org>; Wed, 16 Sep 2009 10:24:37 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEAIe8sEqrR7O6/2dsb2JhbADGd4hMAZBZBYIsgWs
X-IronPort-AV: E=Sophos;i="4.44,399,1249257600"; d="scan'208";a="242784382"
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-1.cisco.com with ESMTP; 16 Sep 2009 17:25:26 +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 n8GHPQ8e030939;  Wed, 16 Sep 2009 10:25:26 -0700
Received: from [10.73.129.66] ([10.21.77.19]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id n8GHPOWi004485; Wed, 16 Sep 2009 17:25:25 GMT
Message-Id: <DEC650B6-6380-41CD-9049-DE87D3D3CD55@cisco.com>
From: Cullen Jennings <fluffy@cisco.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
In-Reply-To: <4AADED78.7010905@ericsson.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Wed, 16 Sep 2009 10:51:33 -0600
References: <4A6D9D29.2050901@ericsson.com> <4AADED78.7010905@ericsson.com>
X-Mailer: Apple Mail (2.936)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=804; t=1253121926; x=1253985926; 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[BEHAVE]=20Discusses=20regarding=20secu rity=20mechanism=20usage=20for=20TURN |Sender:=20; bh=y1+L5KiBscOELQQB3g9OnElr8N9NoTMrYNpTtjhoL9w=; b=grcwMSeAaJevqz/shtusEZARgCMvSx1jRtPbx9WSqFJZ87Wn3gwAhX4KzI wYMt8yme5o3xEcKt/p4r5tfs7gNOrtcEozm2AUNmr/8dKrMueUQDl7IDgwPE Pmvdq3ynre;
Authentication-Results: sj-dkim-2; header.From=fluffy@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; ); 
Cc: Tim Polk <tim.polk@nist.gov>, Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Discusses regarding security mechanism usage for TURN
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/mail-archive/web/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>
X-List-Received-Date: Wed, 16 Sep 2009 17:24:37 -0000

On Sep 14, 2009, at 1:15 , Magnus Westerlund wrote:

> NEW:
>    [RFC5389] specifies a Long-Term Credential mechanism for STUN.   
> TURN
>    servers and clients MUST implement this mechanism.  The server MUST
>    demand that all requests from the client be authenticated using  
> this
>    mechanism, or that a equally strong or stronger mechanism for  
> client
>    authentication is used. One such mechanism is TLS, if using client
>    and server certificates that actually identify the parties, i.e. no
>    self-signed certificates.  The client MUST always be prepared to
>    authenticate requests use the Long-Term Credential mechanism if
>    required.
>
> Cullen and Tim, does this text satisfies your discusses?

That would solve my concern.

Cullen <in my AD role>



From xing@cernet.edu.cn  Wed Sep 16 18:33:12 2009
Return-Path: <xing@cernet.edu.cn>
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 A33E43A683D for <behave@core3.amsl.com>; Wed, 16 Sep 2009 18:33:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.692
X-Spam-Level: 
X-Spam-Status: No, score=0.692 tagged_above=-999 required=5 tests=[AWL=0.595,  BAYES_00=-2.599, FH_HAS_XAIMC=2.696]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YVpiy2HWmHzD for <behave@core3.amsl.com>; Wed, 16 Sep 2009 18:33:11 -0700 (PDT)
Received: from cernet.edu.cn (sea.net.edu.cn [202.112.3.66]) by core3.amsl.com (Postfix) with SMTP id E5A1A3A6A61 for <behave@ietf.org>; Wed, 16 Sep 2009 18:33:09 -0700 (PDT)
Received: from [59.66.24.75]([59.66.24.75]) by cernet.edu.cn(AIMC 3.2.0.0) with SMTP id jm54ab1b0d6; Thu, 17 Sep 2009 09:33:59 +0800
Message-ID: <4AB191F3.9040305@cernet.edu.cn>
Date: Thu, 17 Sep 2009 09:33:39 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Christian Huitema <huitema@microsoft.com>
References: <4AA7730F.6040602@cernet.edu.cn>	<36ba02b00909141038i1611b5d6ide4fd96157ed2bc8@mail.gmail.com>	<6B55F0F93C3E9D45AF283313B8D342BA20F54E47@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>	<4AAF2C06.2020107@it.uc3m.es>	<6B55F0F93C3E9D45AF283313B8D342BA20F557D0@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <4AAFA425.7040706@it.uc3m.es> <4AB079D5.1010404@cernet.edu.cn> <6B55F0F93C3E9D45AF283313B8D342BA20F5A151@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <6B55F0F93C3E9D45AF283313B8D342BA20F5A151@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-AIMC-AUTH: xing
X-AIMC-MAILFROM: xing@cernet.edu.cn
X-AIMC-Msg-ID: NqlsFoWB
Cc: Xing Li <xing@cernet.edu.cn>, Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Security implications of protocol translation
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/mail-archive/web/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>
X-List-Received-Date: Thu, 17 Sep 2009 01:33:12 -0000

Christian Huitema 写道:
>>> With the stateless translator is more complicated, i think. since the
>>> same prefix can be used to make representation of external hosts and
>>> to assign internal hosts, then the filtenring needs to be done based
>>> on the embedded IPv4 address, which may require per IPv4 prefix filter
>>> configuration the border routers, which may be more complicated, but i
>>> think it is feasible...
>>>       
>> the stateless translator can just simple drop the packets, if they are
>> not the IPv4-mapped source addresses in the administrative domain.
>>     
>
> But doesn't that require some amount of state?
>
> Suppose the translator is managed by an ISP, for the service of its customers. The ISP network serves a large number of customers. In normal IPv6 practice, the ISP has assigned an IPv6 prefix to each of these customers. The ISP wants to provide a stable IPv4 address to some hosts of these customers, through a translation service. Obviously, the ISP cannot provide stable IPv4 addresses to each of his customers, because there are just not enough addresses.
>
> If I understand correctly, this is a target deployment for the stateless translation service. The hosts to which stable IPv4 addresses have been assigned will be configured with an IPv4 translatable IPv4 address. The ISP translator will apply stateless translation when the outgoing address source is a translatable address, stateful translation when it is not. 
>
> Let's assume that the customer site routers perform egress filtering, which is generally mandated by other security consideration. We have two possibilities then:
>
> 1) All source addresses, whether IPv4 translatable or not, must be assigned out of the IPv6 prefix assigned by the ISP to the customer site;
>
> 2) IPv6 translatable addresses use a special prefix, different from that of the customer site.
>
> Frankly, I don't think that the second case is manageable. It implies special configuration in multiple routers, i.e. pushing and managing a lot of state information, which seems to defeat the whole idea of stateless translation. So, I will assume that we use the first variation, in which translatable addresses are generated out of the customer prefixes. This means that translatable addresses will only differ from the regular addresses by the structure of the host identifier.
>
> If that is the case, if translatable addresses only differ from the regular addresses by the structure of the host identifier, how does the translator verify that customer A is not attempting to use an IPv4 address assigned to customer B?
>   

how about configure uRPF in the stateless translator?  xing
> -- Christian Huitema
>
>
>
>   


From xuxh@huawei.com  Wed Sep 16 20:16:51 2009
Return-Path: <xuxh@huawei.com>
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 1E01828C181; Wed, 16 Sep 2009 20:16:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.675
X-Spam-Level: *
X-Spam-Status: No, score=1.675 tagged_above=-999 required=5 tests=[AWL=1.270,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  J_CHICKENPOX_13=0.6, MIME_8BIT_HEADER=0.3, 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 jqcyIp17ilZl; Wed, 16 Sep 2009 20:16:50 -0700 (PDT)
Received: from szxga04-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id DC8733A68B4; Wed, 16 Sep 2009 20:16:49 -0700 (PDT)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KQ300MTCIH6HF@szxga04-in.huawei.com>; Thu, 17 Sep 2009 11:17:30 +0800 (CST)
Received: from huawei.com ([172.24.1.33]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KQ300DI6IH6V6@szxga04-in.huawei.com>; Thu, 17 Sep 2009 11:17:30 +0800 (CST)
Received: from HUAWEIE75F8F11 ([10.111.12.212]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KQ300E8OIH56N@szxml06-in.huawei.com>; Thu, 17 Sep 2009 11:17:30 +0800 (CST)
Date: Thu, 17 Sep 2009 11:17:29 +0800
From: Xu Xiaohu <xuxh@huawei.com>
In-reply-to: <40B3335A-DF89-4036-A6E3-5DC20CE782C4@free.fr>
To: =?iso-8859-1?Q?'R=E9mi_Despr=E9s'?= <remi.despres@free.fr>
Message-id: <002601ca3745$63c8b710$d40c6f0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
Thread-index: Aco2xR3OoAivq8xQTcqESrgDudvpFwAfVoQQ
Cc: softwires@ietf.org, "'Templin, Fred L'" <Fred.L.Templin@boeing.com>, 'Behave WG' <behave@ietf.org>
Subject: Re: [BEHAVE] [Softwires] Some Thought about the Automatic TunnelAddress
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/mail-archive/web/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>
X-List-Received-Date: Thu, 17 Sep 2009 03:16:51 -0000

Hi Remi,

> > What's the real purpose of the above model (IPv6 addresses
> > beginning with
> > other than '000' use a 64-bit prefix)? Can somebody help explain it?
> 
> Xu,
> 
> I had the view that this statement badly needed a reliable
> justification, and argued about it.
> 
> But it now happens that the study about routing-loop attacks
> documented last August by Gabi Nakibly, in www.ops.ietf.org/lists/
> v6ops/v6ops.2009/msg00601, leads IMHO to such a justification.
> 
> I tried to explain all this in www.ietf.org/mail-archive/web/behave/
> current/msg06816.
> You may find relevant to this discussion.

Thanks for your reply. 

In your msg
(http://www.ietf.org/mail-archive/web/behave/current/msg06816.html), you
said "... Suffice it to say that a 6to4 relay router may need, to be safe,
to look at IPv4 addresses that are embedded in ISATAP IPv6 addresses. In the
above example, if the 6to4 relay router sees that the IPv4 embedded address
in the IPv6 destination is its own IPv4 address 192.88.99.1, it can discard
the packet and thus prevent the loop". However, I feel this is not a good
idea for a 6to4 router to check the ISATAP address. In fact, the
routing-loop attack can be easily avoided by using a private IPv4 address,
rather that a public IPv4 address as the ISATAP tunnel endpoint address on
the ISATAP router.

Hence, I don't think the routing-loop attack prevention is a justification
for the "IID-format constraint".

Best wishes,
Xiaohu

NOTE: The following is quoted from Remi's msg
(http://www.ietf.org/mail-archive/web/behave/current/msg06816.html)
******************************************************************
ROUTING-LOOP ATTACK PROTECTION AND ITS IMPLICATION ON IPV6 ADDRESS FORMATS 


In a mail of Aug 17 (www.ops.ietf.org/lists/v6ops/v6ops.2009/ msg00601),
Gabi Nakibly documented a new type of attack: the "routing loop" attack.
With it, some packets can be repeatedly retransmitted between two ISATAP
routers, or between an ISATAP router and a 6to4 relay router. 


For a brief illustration of one instance of the the attack, here is an
example: 

+-------------------------------------------------------+
| IPv6                   IPv6 packet                    |
|Internet        dst6:  2002:198.16.9.9::1              |
|                src6:  2001:db8:1::200:5efe:192.88.99.1|
|                                           |           |
|                                           V           |
|          .--------------->--------------. |           |
|         /                                \|           |
+--------+----------------------------------+-----------+
         |                                  |
  2001:db8:1::/48                       2002::/16
    +---------+                        +---------+
    | ISATAP  |                        |  6to4   |
    +---------+                        +---------+
    198.16.9.9                         192.88.99.1
         |                                  |
+--------+---------+                        |
| IPv4   ^         |                        |
| site   ^         |                        |
|        ^         |                        V
|        ^         |                        |
+--------+---------+                        |
    198.16.9.0/24                           |
         |                                  |
         |                                  |
+--------+----------------------------------+-----------+
| IPv4    \                                /            |
|internet  '----------------<-------------'             |
|                 IPv6 in IPv4 packet                   |
|                  dst4: 198.16.9.9                     |
|                  src4: 192.88.99.1                    |
|                                                       |
+--------+----------------------------------+-----------+



Detailed protection mechanisms against these attacks are being discussed on
the v6ops and 6man lists, in particular with Gabi Nakibly, Fred Templin, and
Christian Huitema, and are out of scope here. Suffice it to say that a 6to4
relay router may need, to be safe, to look at IPv4 addresses that are
embedded in ISATAP IPv6 addresses. In the above example, if the 6to4 relay
router sees that the IPv4 embedded address in the IPv6 destination is its
own IPv4 address 192.88.99.1, it can discard the packet and thus prevent the
loop. 


Now, IPv4 addresses embedded in ISATAP addresses can be reliably detected
ONLY if non-ISATAP addresses NEVER have 200:5efe::/32 in their octets 8 to
15. If some mappable-only address would have this pattern, there could be a
slight but real possibility that an intermediate 6to4 relay would discard
packets sent to this address. 


This is, in my understanding, a sufficient technical reason for the
IID-format constraint to apply to all IPv6 addresses (with or without real
IID). 


Regards,
RD


*****************************************************************


From brian.e.carpenter@gmail.com  Wed Sep 16 21:17:38 2009
Return-Path: <brian.e.carpenter@gmail.com>
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 3AFEB3A6405 for <behave@core3.amsl.com>; Wed, 16 Sep 2009 21:17:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.206
X-Spam-Level: 
X-Spam-Status: No, score=-2.206 tagged_above=-999 required=5 tests=[AWL=0.393,  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 ucErNO-N7Xpu for <behave@core3.amsl.com>; Wed, 16 Sep 2009 21:17:37 -0700 (PDT)
Received: from mail-pz0-f171.google.com (mail-pz0-f171.google.com [209.85.222.171]) by core3.amsl.com (Postfix) with ESMTP id 5A2283A6843 for <behave@ietf.org>; Wed, 16 Sep 2009 21:17:37 -0700 (PDT)
Received: by pzk1 with SMTP id 1so2363705pzk.13 for <behave@ietf.org>; Wed, 16 Sep 2009 21:18:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=gGfZqPWQZOx4uoYJvKvsYsC3G9FS3p+kfJqaoAgJmgs=; b=LBESZJJZPYhUSZeqZnYf4eOeZ4my8BHSXPSA1TMENsSjVXZZv3N/gatziLJsT5qe27 wDoHq+Dax0s1LBOo3jw41/lMk9wbma9DP1ujXupUFE/6MuH31dhFa38UoeX5uUkCXyv/ PpFVpem5Q2U78ItzFyNTQ3xHHTAJS1I3oiHJ4=
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=nLwc7YHOBCkUVcKtZOoZstVYJFpr6VLMn28R1Gh13A2cjGJXOC30BTRZu+QtASMyZO tCwYvXvwPlSJdPH8PYtavQumvXo9UC1PsOUGFBj13ySqH6uQMxM70UawPWSX84AKbLnk ZX7a+XZyx/KF1eTvAdz6ztunt6rnAJdJ6s29k=
Received: by 10.114.49.14 with SMTP id w14mr17605824waw.219.1253161104287; Wed, 16 Sep 2009 21:18:24 -0700 (PDT)
Received: from ?10.1.1.4? (118-92-192-43.dsl.dyn.ihug.co.nz [118.92.192.43]) by mx.google.com with ESMTPS id 23sm1657226pzk.4.2009.09.16.21.18.21 (version=SSLv3 cipher=RC4-MD5); Wed, 16 Sep 2009 21:18:23 -0700 (PDT)
Message-ID: <4AB1B88A.6080109@gmail.com>
Date: Thu, 17 Sep 2009 16:18:18 +1200
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: Cameron Byrne <cb.list6@gmail.com>
References: <a7c8d0a30909150630i29d535bbhf3089fdfecffa328@mail.gmail.com>	<7CB993A6-829C-46CC-A74C-7DBF7CFE88C6@muada.com>	<a7c8d0a30909150838s230397d9r3cbffb5df6097b76@mail.gmail.com>	<273D4852-D26C-497E-A034-2C3EE4908660@muada.com>	<a7c8d0a30909151846w6f85cc67je3774c93e298f2e1@mail.gmail.com>	<C37FF658-CF1A-4106-ABD9-2DB18B97B2CF@muada.com>	<a7c8d0a30909160607l1209993ajae733d2dc116532b@mail.gmail.com>	<519DB330-54FD-4163-91A8-DF81290A10B5@muada.com> <bcff0fba0909160653s59990a8al3cd29d12dab14095@mail.gmail.com>
In-Reply-To: <bcff0fba0909160653s59990a8al3cd29d12dab14095@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Behave WG <behave@ietf.org>, Zhen Cao <caozhenpku@gmail.com>
Subject: Re: [BEHAVE] Comments on NAT64 draft
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/mail-archive/web/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>
X-List-Received-Date: Thu, 17 Sep 2009 04:17:38 -0000

On 2009-09-17 01:53, Cameron Byrne wrote:
> On Wed, Sep 16, 2009 at 6:15 AM, Iljitsch van Beijnum
> <iljitsch@muada.com> wrote:
>> On 16 Sep 2009, at 15:07 , Zhen Cao wrote:
>>
>>>> The only problematic case is one where there is no match because this is
>>>> the
>>>> first packet (and a non-first fragment). In that case the fragment must
>>>> be
>>>> dropped, because a mapping can't be created without port numbers.
>>> Yes, that's what i meant. I forgot to mention it is the first packet
>>> in the flow. But the NAT may wait for the first frag to arrive?
>>> Anyway, do we need to define this behavior explicitly in the draft?
>> With TCP this can't realistically happen because the initial SYN is small
>> enough to fit in any reasonable MTU.
>>
>> With UDP it could happen. I guess if you ALWAYS get reordering and ALWAYS
>> throw away the non-initial fragment of a first packet then there will be
>> trouble with protocols like the DNS that send single packet transactions,
>> because those will then consistently fail.
>>
>> Any ideas from implementers? Is it problematic to have to buffer and
>> reassemble UDP fragments that don't match any state in the v6->v4 direction?
> 
> According to RFC 4787 Requirement 14, a NAT MUST accommodate this out
> of order fragment situation.

This seems extreme; I wonder why it wasn't a SHOULD. However,
that's a BCP for IPv4-IPv4 NATs "as described in [RFC2663]."
We can decide independently for NAT64, but Iljitsch has asked the
right question: how big a deal is this for implementors?

    Brian

> 
>> (Fortunately we don't have to do this in the v4->v6 direction, where denial
>> of service attacks are a bigger risk, because new sessions aren't set up in
>> this direction.)
>> _______________________________________________
>> 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 zhangdong_rh@huaweisymantec.com  Wed Sep 16 22:04:00 2009
Return-Path: <zhangdong_rh@huaweisymantec.com>
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 9BAC73A6814 for <behave@core3.amsl.com>; Wed, 16 Sep 2009 22:04:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.152
X-Spam-Level: 
X-Spam-Status: No, score=-1.152 tagged_above=-999 required=5 tests=[AWL=1.446,  BAYES_00=-2.599, HTML_MESSAGE=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 s9s42j6NbNel for <behave@core3.amsl.com>; Wed, 16 Sep 2009 22:03:59 -0700 (PDT)
Received: from mta1.huaweisymantec.com (mta1.huaweisymantec.com [218.17.155.14]) by core3.amsl.com (Postfix) with ESMTP id 9B4503A6405 for <behave@ietf.org>; Wed, 16 Sep 2009 22:03:59 -0700 (PDT)
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_zS6D62f4mygS0EWXt/2pdQ)"
Received: from hstml01-in.huaweisymantec.com ([172.26.3.41]) by hstga01-in.huaweisymantec.com (Sun Java(tm) System Messaging Server 6.3-8.03 (built Apr 24 2009; 32bit)) with ESMTP id <0KQ3000MBNFGAB80@hstga01-in.huaweisymantec.com> for behave@ietf.org; Thu, 17 Sep 2009 13:04:29 +0800 (CST)
Received: from z90001956 ([10.27.154.76]) by hstml01-in.huaweisymantec.com (Sun Java(tm) System Messaging Server 6.3-8.03 (built Apr 24 2009; 32bit)) with ESMTPA id <0KQ3003D0NFFTK10@hstml01-in.huaweisymantec.com> for behave@ietf.org; Thu, 17 Sep 2009 13:04:28 +0800 (CST)
Date: Thu, 17 Sep 2009 13:04:27 +0800
From: Dong Zhang <zhangdong_rh@huaweisymantec.com>
To: syl <syl@pec.etri.re.kr>, mkshin <mkshin@pec.etri.re.kr>, yjkim <yjkim@pec.etri.re.kr>, "erik.nordmark" <erik.nordmark@sun.com>,  alain_durand <alain_durand@cable.comcast.com>
Message-id: <200909171304274151915@huaweisymantec.com>
X-Mailer: Foxmail 6, 10, 201, 20 [cn]
Cc: behave <behave@ietf.org>
Subject: [BEHAVE] Question for BIA(RFC3338)
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/mail-archive/web/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>
X-List-Received-Date: Thu, 17 Sep 2009 05:04:00 -0000

This is a multi-part message in MIME format.

--Boundary_(ID_zS6D62f4mygS0EWXt/2pdQ)
Content-type: text/plain; charset=gb2312
Content-transfer-encoding: 7BIT

Dear BIA's co-authors,

I am reading RFC3338. I have confusion.
In section 2.1 of RFC3338, it says:
   The main purposes of BIA are the same as BIS [BIS].  It makes IPv4
   applications communicate with IPv6 hosts without any modification of
   those IPv4 applications.  However, while BIS is for systems with no
   IPv6 stack, BIA is for systems with an IPv6 stack, but on which some
   applications are  not yet available on IPv6 and source code is not
   available preventing the application from being ported.

There is one word, "BIS is for systems with no IPv6 stack". I am confused.
BIS(RFC2767) defines a mechanism for dual stack hosts. And the dual stack 
hosts have IPv6 address. Meanwhile, they are able to send and receive IPv6
packets. I also check RFC1933, the reference of BIS. RFC1933 shows the 
definition of Dual IP Layer. It proves that "IPv6/IPv4 nodes have the ability 
to send and receive both IPv4 and IPv6 packets."

Hence, could anyone make the clarification? Sorry if I am missing something.
Thanks in advance.

B.R.
2009-09-17 



Dong Zhang

--Boundary_(ID_zS6D62f4mygS0EWXt/2pdQ)
Content-type: text/html; charset=gb2312
Content-transfer-encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=gb2312">
<META content="MSHTML 6.00.2900.3603" name=GENERATOR>
<STYLE>BLOCKQUOTE {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px; MARGIN-LEFT: 2em
}
OL {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
UL {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</STYLE>
</HEAD>
<BODY style="FONT-SIZE: 10pt; FONT-FAMILY: verdana">
<DIV><FONT face=Verdana size=2>Dear&nbsp;BIA's co-authors,</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV>I am reading RFC3338. I have confusion.</DIV>
<DIV>In section 2.1 of RFC3338, it says:</DIV>
<DIV>&nbsp;&nbsp; The main purposes of BIA are the same as BIS [BIS].&nbsp; It 
makes IPv4<BR>&nbsp;&nbsp; applications communicate with IPv6 hosts without any 
modification of<BR>&nbsp;&nbsp; those IPv4 applications.&nbsp; However, while 
BIS is for systems with no<BR>&nbsp;&nbsp; IPv6 stack, BIA is for systems with 
an IPv6 stack, but on which some<BR>&nbsp;&nbsp; applications are&nbsp; not yet 
available on IPv6 and source code is not<BR>&nbsp;&nbsp; available preventing 
the application from being ported.</DIV>
<DIV>&nbsp;</DIV>
<DIV>There is one word, "BIS is for systems with no IPv6 stack". I am 
confused.</DIV>
<DIV>BIS(RFC2767) defines a mechanism for dual stack hosts. And the dual stack 
</DIV>
<DIV>hosts have IPv6 address. Meanwhile, they are able to send and receive 
IPv6</DIV>
<DIV>packets. I also check RFC1933, the reference of BIS. RFC1933&nbsp;shows the 
</DIV>
<DIV>definition of Dual IP Layer.&nbsp;It proves that "IPv6/IPv4&nbsp;nodes have 
the ability </DIV>
<DIV>to send and receive both IPv4 and IPv6 packets."</DIV>
<DIV>&nbsp;</DIV>
<DIV>Hence, could anyone&nbsp;make&nbsp;the clarification? Sorry if I&nbsp;am 
missing something.</DIV>
<DIV>Thanks in&nbsp;advance.</DIV>
<DIV>&nbsp;</DIV>
<DIV>B.R.</DIV>
<DIV align=left><FONT face=Verdana color=#c0c0c0 size=2>2009-09-17 
</FONT></DIV><FONT face=Verdana size=2>
<HR style="WIDTH: 122px; HEIGHT: 2px" align=left SIZE=2>

<DIV><FONT face=Verdana color=#c0c0c0 size=2><SPAN>
<DIV>
<DIV><FONT face=Verdana><STRONG>Dong Zhang</STRONG></FONT></DIV>
<DIV><FONT face=Verdana><FONT face=Verdana><FONT 
color=#000000></FONT></FONT>&nbsp;</DIV></FONT></DIV></SPAN></FONT></DIV></FONT></BODY></HTML>

--Boundary_(ID_zS6D62f4mygS0EWXt/2pdQ)--

From huitema@microsoft.com  Wed Sep 16 22:08:51 2009
Return-Path: <huitema@microsoft.com>
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 996813A6814 for <behave@core3.amsl.com>; Wed, 16 Sep 2009 22:08:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.558
X-Spam-Level: 
X-Spam-Status: No, score=-10.558 tagged_above=-999 required=5 tests=[AWL=0.041, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qmdw2NWaJkgz for <behave@core3.amsl.com>; Wed, 16 Sep 2009 22:08:50 -0700 (PDT)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.214]) by core3.amsl.com (Postfix) with ESMTP id C76F53A67F0 for <behave@ietf.org>; Wed, 16 Sep 2009 22:08:50 -0700 (PDT)
Received: from TK5EX14MLTC103.redmond.corp.microsoft.com (157.54.79.174) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.2.176.0; Wed, 16 Sep 2009 22:09:41 -0700
Received: from TK5EX14MLTW651.wingroup.windeploy.ntdev.microsoft.com (157.54.71.39) by TK5EX14MLTC103.redmond.corp.microsoft.com (157.54.79.174) with Microsoft SMTP Server id 14.0.639.20; Wed, 16 Sep 2009 22:09:41 -0700
Received: from TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com ([169.254.3.19]) by TK5EX14MLTW651.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.39]) with mapi; Wed, 16 Sep 2009 22:09:41 -0700
From: Christian Huitema <huitema@microsoft.com>
To: Xing Li <xing@cernet.edu.cn>
Thread-Topic: [BEHAVE] Security implications of protocol translation
Thread-Index: AQHKNckZMF3GDtqt2kuK6ErD8Y/t95DXsFRQgAB6jICAAP69gIAAD6twgAE+QoD//8N50A==
Date: Thu, 17 Sep 2009 05:09:38 +0000
Message-ID: <6B55F0F93C3E9D45AF283313B8D342BA20F5C240@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
References: <4AA7730F.6040602@cernet.edu.cn> <36ba02b00909141038i1611b5d6ide4fd96157ed2bc8@mail.gmail.com> <6B55F0F93C3E9D45AF283313B8D342BA20F54E47@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <4AAF2C06.2020107@it.uc3m.es> <6B55F0F93C3E9D45AF283313B8D342BA20F557D0@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <4AAFA425.7040706@it.uc3m.es> <4AB079D5.1010404@cernet.edu.cn> <6B55F0F93C3E9D45AF283313B8D342BA20F5A151@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <4AB191F3.9040305@cernet.edu.cn>
In-Reply-To: <4AB191F3.9040305@cernet.edu.cn>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Security implications of protocol translation
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/mail-archive/web/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>
X-List-Received-Date: Thu, 17 Sep 2009 05:08:51 -0000

PiA+IElmIHRoYXQgaXMgdGhlIGNhc2UsIGlmIHRyYW5zbGF0YWJsZSBhZGRyZXNzZXMgb25seSBk
aWZmZXIgZnJvbSB0aGUNCj4gcmVndWxhciBhZGRyZXNzZXMgYnkgdGhlIHN0cnVjdHVyZSBvZiB0
aGUgaG9zdCBpZGVudGlmaWVyLCBob3cgZG9lcyB0aGUNCj4gdHJhbnNsYXRvciB2ZXJpZnkgdGhh
dCBjdXN0b21lciBBIGlzIG5vdCBhdHRlbXB0aW5nIHRvIHVzZSBhbiBJUHY0DQo+IGFkZHJlc3Mg
YXNzaWduZWQgdG8gY3VzdG9tZXIgQj8NCj4gPg0KPiANCj4gaG93IGFib3V0IGNvbmZpZ3VyZSB1
UlBGIGluIHRoZSBzdGF0ZWxlc3MgdHJhbnNsYXRvcj8gIFhpbmcNCg0KdVJQRiBpcyBhIGZvcm0g
b2YgaW5ncmVzcyBmaWx0ZXJpbmcuIE9mIGNvdXJzZSB5b3Ugc2hvdWxkIGVuYWJsZSB0aGF0LiBC
dXQgaXQgaXMgbm90IHN1ZmZpY2llbnQuIA0KDQpTdXBwb3NlIHRoYXQgY3VzdG9tZXIgQSBoYXMg
YW4gSVB2NiB0cmFuc2xhdGFibGUgYWRkcmVzcyBvZiB0aGUgZm9ybTogPElTUC1wcmVmaXg+OjxT
dWJuZXRBPjo8TWFnaWNBPjphLmEuYS5hLCB3aGVyZSBhLmEuYS5hIGlzIHRoZSBJUHY0IGFkZHJl
c3MgYXNzaWduZWQgYnkgdGhlIElTUCB0byBBIGFuZCAibWFnaWNBIiBpcyB0aGUgc3BlY2lhbCBz
YXVjZSB0aGF0IGRpc3Rpbmd1aXNoZXMgdHJhbnNsYXRhYmxlIGFkZHJlc3NlcyBhbmQgZW5hYmxl
cyBjaGVja3N1bSBuZXV0cmFsaXR5LiBDdXN0b21lciBCIG5vcm1hbGx5IHVzZXMgYWRkcmVzc2Vz
IG9mIHRoZSBmb3JtIDxJU1AtcHJlZml4Pjo8U3VibmV0Qj46PGhvc3QtSUQ+LiBPbmUgb2YgdGhl
IGhvc3RzIGF0IGN1c3RvbWVyIEIncyBzaXRlIGNvbmZpZ3VyZXMgYSBob3N0IElEIG9mIHRoZSBm
b3JtIDxNYWdpY0I+OmEuYS5hLmEgLS0gdXNpbmcgdGhlIGFwcHJvcHJpYXRlIG1hZ2ljLCBlLmcu
IHRvIG1hdGNoIGNoZWNrc3Vtcy4gDQoNCkN1c3RvbWVyIEIgY2FuIHNlbmQgc3Bvb2ZlZCBwYWNr
ZXRzIHdpdGggdGhlIHNvdXJjZSBhZGRyZXNzIDxJU1AtcHJlZml4Pjo8U3VibmV0Qj46PE1hZ2lj
Qj46YS5hLmEuYS4gVGhlc2UgcGFja2V0cyB3aWxsIGJlIGNvbnNpZGVyZWQgdmFsaWQgYnkgZWdy
ZXNzIGZpbHRlcmluZyBhbmQgdVJQRiBjaGVja3MsIGJlY2F1c2UgdGhleSBkbyBpbmRlZWQgY29t
ZSBmcm9tIHRoZSByaWdodCBwYXRoIGZvciA8SVNQLXByZWZpeD46PFN1Ym5ldEI+LiBXaWxsIHRo
ZSB0cmFuc2xhdG9yIGZvcndhcmQgdGhlc2UgcGFja2V0cyBhcyBvcmlnaW5hdGluZyBmcm9tIGFk
ZHJlc3MgPGEuYS5hLmE+PyBJZiBub3QsIGhvdyBkb2VzIHRoZSB0cmFuc2xhdG9yIGRlY2lkZSB0
aGF0IHRoZSBwYWNrZXRzIGZyb20gQiBhcmUgZXJyb25lb3VzPyBXaGF0IGluZm9ybWF0aW9uIGRv
ZXMgaXQgdXNlPw0KDQotLSBDaHJpc3RpYW4gSHVpdGVtYQ0KDQoNCg0K

From fernando.gont.netbook.win@gmail.com  Wed Sep 16 23:06:16 2009
Return-Path: <fernando.gont.netbook.win@gmail.com>
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 9207E3A6B3B for <behave@core3.amsl.com>; Wed, 16 Sep 2009 23:06:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.791
X-Spam-Level: 
X-Spam-Status: No, score=-2.791 tagged_above=-999 required=5 tests=[AWL=-0.192, 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 MbFsSDqkcpAA for <behave@core3.amsl.com>; Wed, 16 Sep 2009 23:06:15 -0700 (PDT)
Received: from mail-yw0-f118.google.com (mail-yw0-f118.google.com [209.85.211.118]) by core3.amsl.com (Postfix) with ESMTP id 0B93F28C117 for <behave@ietf.org>; Wed, 16 Sep 2009 23:06:14 -0700 (PDT)
Received: by ywh16 with SMTP id 16so898736ywh.31 for <behave@ietf.org>; Wed, 16 Sep 2009 23:07:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; bh=rmh7u0TwFwkMyA0rsUyd139VML7DDzeqyPZoAGaY0rw=; b=XOQSboaW+nXn3w8uaMhqSvLz9+lu/NJL/aiii+wOjmi2JEM8tKvlnhJSLXswnHPpqt /pydILp/U2AG9rGFwnmI5dHtRy8ivEvoZx/GzRwL6Zj7FLvWrINvL47mIwFxlOrDAmNu SqGt+tR2bbJZkuaXI4HzIjGvpqmqtD7vWo0ik=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:openpgp:content-type :content-transfer-encoding; b=hqTkYIwKndVFi09rXgkb5zot9VLDfF52SpOiLU2dJcfZQ+ahroyVyPd6i/vaygcnXT Soc0GLyDOssW8M/N17K5fJH7Br6MLLriBRT3fyDAuBdI0Mq4y+3pOcuxcfxpR/hqOUmc dKaOJWmCHEI/P4YAOzofiohKTfOx1P/mTBb00=
Received: by 10.91.3.40 with SMTP id f40mr158535agi.53.1253167623041; Wed, 16 Sep 2009 23:07:03 -0700 (PDT)
Received: from ?192.168.0.167? (129-130-17-190.fibertel.com.ar [190.17.130.129]) by mx.google.com with ESMTPS id 8sm370186agd.37.2009.09.16.23.06.59 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 16 Sep 2009 23:07:02 -0700 (PDT)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4AB1D1FA.3070507@gont.com.ar>
Date: Thu, 17 Sep 2009 03:06:50 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: marcelo bagnulo braun <marcelo@it.uc3m.es>
References: <4AA7730F.6040602@cernet.edu.cn>	<36ba02b00909141038i1611b5d6ide4fd96157ed2bc8@mail.gmail.com>	<6B55F0F93C3E9D45AF283313B8D342BA20F54E47@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <4AAF2C06.2020107@it.uc3m.es>
In-Reply-To: <4AAF2C06.2020107@it.uc3m.es>
X-Enigmail-Version: 0.95.7
OpenPGP: id=D076FFF1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Security implications of protocol translation
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/mail-archive/web/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>
X-List-Received-Date: Thu, 17 Sep 2009 06:06:16 -0000

marcelo bagnulo braun wrote:

> Then there is all the filtering capabilities of the nats that has
> certainly been taken into consideration and all the discussion about
> tracking seq numbers in tcp is ongoing.

FWIW, we had published an I-D
(http://www.gont.com.ar/drafts/nat-security/draft-gont-behave-nat-security-01.txt)
about security implications of NATs. The I-D has expired, but we are
working on a revision of it.

I presented this I-D back in November 2008 (in Minneapolis). Part of the
I-D is based on the assumption that you should rewrite some header
fields, as failure to do so might lead to interoperability problems that
were not present without the NAT (e.g., collisions of IP IDs if you
don't rewrite the IP ID, etc.). Unfortunately, it was my impression that
many participants ridiculed the discussion instead of thinking about the
issues we raised in our document. (Feedback is still appreciated!

To some extent, it all boils down to: from the external network, all
"connections" come from the same node. Therefore, from the external
network the header fields should look as if they the packets had really
been originated from the NAT (e.g., sequence numbers should look as if
they had been produced by RFC1948, etc.)

I have produced thorough discussion of TCP/IP security for UK CPNI:
TCP security:
http://www.cpni.gov.uk/Docs/tn-03-09-security-assessment-TCP.pdf
IP security: http://www.cpni.gov.uk/Docs/InternetProtocol.pdf

I still have to catch up with the new v6 work that is being produced....
but if you think I could be of help for any specific (existing or new)
document, please let me know.

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





From marcelo@it.uc3m.es  Thu Sep 17 00:09:48 2009
Return-Path: <marcelo@it.uc3m.es>
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 67B0C3A692F for <behave@core3.amsl.com>; Thu, 17 Sep 2009 00:09:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.564
X-Spam-Level: 
X-Spam-Status: No, score=-6.564 tagged_above=-999 required=5 tests=[AWL=0.035,  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 o25UqHl3Y6qw for <behave@core3.amsl.com>; Thu, 17 Sep 2009 00:09:47 -0700 (PDT)
Received: from smtp02.uc3m.es (smtp02.uc3m.es [163.117.176.132]) by core3.amsl.com (Postfix) with ESMTP id 489FE3A6957 for <behave@ietf.org>; Thu, 17 Sep 2009 00:09:46 -0700 (PDT)
Received: from marcelo-bagnulos-macbook-pro.local (wlap005.it.uc3m.es [163.117.139.108]) by smtp02.uc3m.es (Postfix) with ESMTP id 0DECF656AB2; Thu, 17 Sep 2009 09:10:34 +0200 (CEST)
Message-ID: <4AB1E0E9.2010704@it.uc3m.es>
Date: Thu, 17 Sep 2009 09:10:33 +0200
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Christian Huitema <huitema@microsoft.com>
References: <4AA7730F.6040602@cernet.edu.cn>	<36ba02b00909141038i1611b5d6ide4fd96157ed2bc8@mail.gmail.com>	<6B55F0F93C3E9D45AF283313B8D342BA20F54E47@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>	<4AAF2C06.2020107@it.uc3m.es>	<6B55F0F93C3E9D45AF283313B8D342BA20F557D0@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <4AAFA425.7040706@it.uc3m.es> <4AB079D5.1010404@cernet.edu.cn> <6B55F0F93C3E9D45AF283313B8D342BA20F5A151@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <4AB191F3.9040305@cernet.edu.cn> <6B55F0F93C3E9D45AF283313B8D342BA20F5C240@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <6B55F0F93C3E9D45AF283313B8D342BA20F5C240@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-TM-AS-Product-Ver: IMSS-7.0.0.3116-5.6.0.1016-16892.003
Cc: Behave WG <behave@ietf.org>, Xing Li <xing@cernet.edu.cn>
Subject: Re: [BEHAVE] Security implications of protocol translation
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/mail-archive/web/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>
X-List-Received-Date: Thu, 17 Sep 2009 07:09:48 -0000

Christian Huitema escribió:
>>> If that is the case, if translatable addresses only differ from the
>>>       
>> regular addresses by the structure of the host identifier, how does the
>> translator verify that customer A is not attempting to use an IPv4
>> address assigned to customer B?
>>     
>> how about configure uRPF in the stateless translator?  Xing
>>     
>
> uRPF is a form of ingress filtering. Of course you should enable that. But it is not sufficient. 
>
> Suppose that customer A has an IPv6 translatable address of the form: <ISP-prefix>:<SubnetA>:<MagicA>:a.a.a.a, where a.a.a.a is the IPv4 address assigned by the ISP to A and "magicA" is the special sauce that distinguishes translatable addresses and enables checksum neutrality. Customer B normally uses addresses of the form <ISP-prefix>:<SubnetB>:<host-ID>. One of the hosts at customer B's site configures a host ID of the form <MagicB>:a.a.a.a -- using the appropriate magic, e.g. to match checksums. 
>
>   
mmm, this is really not the configuration that i had in mind.
I mean, i always understood that we actually have a prefix to represent 
IPv4 addresses, as opposed to a magic token in the iid.

So, If the ISP is providing translation services, it will have a prefix 
that will be in the form of 
<ISP-prefix>:<subnet64>:<checksum-neutral-stuff>:a.a.a.a

So, the intra isp routing system will deliver the packets addressed to 
the <ISP-prefix>:<subnet64>::/n to the translator device.

I mean, if we use the magic token and all the IPv4 representations do 
not come from a common prefix, how does the routing system delivers the 
packets to to translator?

So, if we have this common prefix, the problem you mention is still 
present but in less degree i think.
An attacker in client B can spoof client A's source address. In order to 
cope with that, you need to be able to filter based on the IPv4 address, 
but you will need to route based on the IPv4 address in any case, to 
deliver the packets addressed to the IPv6 representation of the IPv4 
address assigned to  client A to the client A. So i think uRPF should 
still work.

Am i missing something?

regards, marcelo

> Customer B can send spoofed packets with the source address <ISP-prefix>:<SubnetB>:<MagicB>:a.a.a.a. These packets will be considered valid by egress filtering and uRPF checks, because they do indeed come from the right path for <ISP-prefix>:<SubnetB>. Will the translator forward these packets as originating from address <a.a.a.a>? If not, how does the translator decide that the packets from B are erroneous? What information does it use?
>
> -- Christian Huitema
>
>
>
>   


From iljitsch@muada.com  Thu Sep 17 01:34:55 2009
Return-Path: <iljitsch@muada.com>
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 03A943A68D4 for <behave@core3.amsl.com>; Thu, 17 Sep 2009 01:34: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=[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 9unBF8UhDAbF for <behave@core3.amsl.com>; Thu, 17 Sep 2009 01:34:54 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2]) by core3.amsl.com (Postfix) with ESMTP id AEFD43A69DD for <behave@ietf.org>; Thu, 17 Sep 2009 01:33:55 -0700 (PDT)
Received: from congres-229.telecom.tno.nl (congres-229.telecom.tno.nl [139.63.184.229]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id n8H8YaZn095889 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 17 Sep 2009 10:34:37 +0200 (CEST) (envelope-from iljitsch@muada.com)
Message-Id: <451B7D7E-9338-4130-AE51-540FAD3B7624@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: Fernando Gont <fernando@gont.com.ar>
In-Reply-To: <4AB1D1FA.3070507@gont.com.ar>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Thu, 17 Sep 2009 10:34:42 +0200
References: <4AA7730F.6040602@cernet.edu.cn>	<36ba02b00909141038i1611b5d6ide4fd96157ed2bc8@mail.gmail.com>	<6B55F0F93C3E9D45AF283313B8D342BA20F54E47@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <4AAF2C06.2020107@it.uc3m.es> <4AB1D1FA.3070507@gont.com.ar>
X-Mailer: Apple Mail (2.936)
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Security implications of protocol translation
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/mail-archive/web/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>
X-List-Received-Date: Thu, 17 Sep 2009 08:34:55 -0000

On 17 sep 2009, at 8:06, Fernando Gont wrote:

> To some extent, it all boils down to: from the external network, all
> "connections" come from the same node. Therefore, from the external
> network the header fields should look as if they the packets had  
> really
> been originated from the NAT (e.g., sequence numbers should look as if
> they had been produced by RFC1948, etc.)

Are you saying that a NAT64 should rewrite sequence numbers??

BTW, what happened last month in Holland?

Iljitsch

From remi.despres@free.fr  Thu Sep 17 01:39:39 2009
Return-Path: <remi.despres@free.fr>
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 D96333A67AD; Thu, 17 Sep 2009 01:39:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.756
X-Spam-Level: 
X-Spam-Status: No, score=-1.756 tagged_above=-999 required=5 tests=[AWL=0.193,  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 bYYxQc6rcZt4; Thu, 17 Sep 2009 01:39:39 -0700 (PDT)
Received: from smtp6-g21.free.fr (smtp6-g21.free.fr [212.27.42.6]) by core3.amsl.com (Postfix) with ESMTP id 36E6C3A68E6; Thu, 17 Sep 2009 01:39:36 -0700 (PDT)
Received: from smtp6-g21.free.fr (localhost [127.0.0.1]) by smtp6-g21.free.fr (Postfix) with ESMTP id 8E568E08067; Thu, 17 Sep 2009 10:40:22 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by smtp6-g21.free.fr (Postfix) with ESMTP id 018DEE08083; Thu, 17 Sep 2009 10:40:19 +0200 (CEST)
In-Reply-To: <002601ca3745$63c8b710$d40c6f0a@china.huawei.com>
References: <002601ca3745$63c8b710$d40c6f0a@china.huawei.com>
Mime-Version: 1.0 (Apple Message framework v753.1)
Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed
Message-Id: <57F95EAE-6705-4B8E-849F-3F35D7239EDD@free.fr>
Content-Transfer-Encoding: quoted-printable
From: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
Date: Thu, 17 Sep 2009 10:40:18 +0200
To: Xu Xiaohu <xuxh@huawei.com>
X-Mailer: Apple Mail (2.753.1)
Cc: softwires@ietf.org, "'Templin, Fred L'" <Fred.L.Templin@boeing.com>, 'Behave WG' <behave@ietf.org>
Subject: Re: [BEHAVE] [Softwires] Some Thought about the Automatic TunnelAddress
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/mail-archive/web/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>
X-List-Received-Date: Thu, 17 Sep 2009 08:39:39 -0000

Xu,

Thanks for you answer.
Further comment below.


Le 17 sept. 09 =E0 05:17, Xu Xiaohu a =E9crit :

> In your msg
> (http://www.ietf.org/mail-archive/web/behave/current/=20
> msg06816.html), you
> said "... Suffice it to say that a 6to4 relay router may need, to =20
> be safe,
> to look at IPv4 addresses that are embedded in ISATAP IPv6 =20
> addresses. In the
> above example, if the 6to4 relay router sees that the IPv4 embedded =20=

> address
> in the IPv6 destination is its own IPv4 address 192.88.99.1, it can =20=

> discard
> the packet and thus prevent the loop". However, I feel this is not =20
> a good
> idea for a 6to4 router to check the ISATAP address. In fact, the
> routing-loop attack can be easily avoided by using a private IPv4 =20
> address,
> rather that a public IPv4 address as the ISATAP tunnel endpoint =20
> address on
> the ISATAP router.

If the IPv4 address of an ISATAP router is private, the attack =20
scenario  below doesn't exists, YES.

But 5214 says in its introduction that "ISATAP enables automatic =20
tunneling whether global or private IPv4 addresses are used".
To prevent all routing-loop attacks, 6to4 relay routers should =20
therefore also deal with ISATAP routers that have global IPv4 addresses.

As a matter of facts, ISATAP can be useful with a global IPv4 address =20=

in a large private network that has enough global IPv4 addresses to =20
use them internally: this provides IPv6 connectivity to dual-stack =20
hosts that support ISATAP (e.g. with Windows or Linux AKAIK).


> Hence, I don't think the routing-loop attack prevention is a =20
> justification
> for the "IID-format constraint".

I also wish it would not have been a justification, but for the =20
reason above I believe it is one we have to live with :-(.

Did I miss anything?

Regards,
RD



> For a brief illustration of one instance of the the attack, here is an
> example:
>
> +-------------------------------------------------------+
> | IPv6                   IPv6 packet                    |
> |Internet        dst6:  2002:198.16.9.9::1              |
> |                src6:  2001:db8:1::200:5efe:192.88.99.1|
> |                                           |           |
> |                                           V           |
> |          .--------------->--------------. |           |
> |         /                                \|           |
> +--------+----------------------------------+-----------+
>          |                                  |
>   2001:db8:1::/48                       2002::/16
>     +---------+                        +---------+
>     | ISATAP  |                        |  6to4   |
>     +---------+                        +---------+
>     198.16.9.9                         192.88.99.1
>          |                                  |
> +--------+---------+                        |
> | IPv4   ^         |                        |
> | site   ^         |                        |
> |        ^         |                        V
> |        ^         |                        |
> +--------+---------+                        |
>     198.16.9.0/24                           |
>          |                                  |
>          |                                  |
> +--------+----------------------------------+-----------+
> | IPv4    \                                /            |
> |internet  '----------------<-------------'             |
> |                 IPv6 in IPv4 packet                   |
> |                  dst4: 198.16.9.9                     |
> |                  src4: 192.88.99.1                    |
> |                                                       |
> +--------+----------------------------------+-----------+
>

From xuxh@huawei.com  Thu Sep 17 02:30:27 2009
Return-Path: <xuxh@huawei.com>
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 9CEA13A6A12; Thu, 17 Sep 2009 02:30:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.347
X-Spam-Level: *
X-Spam-Status: No, score=1.347 tagged_above=-999 required=5 tests=[AWL=1.542,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  MIME_8BIT_HEADER=0.3, 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 Ntl28pH1ZjFX; Thu, 17 Sep 2009 02:30:25 -0700 (PDT)
Received: from szxga04-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id 805103A6997; Thu, 17 Sep 2009 02:30:25 -0700 (PDT)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KQ3005HYZNH46@szxga04-in.huawei.com>; Thu, 17 Sep 2009 17:28:29 +0800 (CST)
Received: from huawei.com ([172.24.1.33]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KQ30087AZNHF0@szxga04-in.huawei.com>; Thu, 17 Sep 2009 17:28:29 +0800 (CST)
Received: from HUAWEIE75F8F11 ([10.111.12.212]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KQ300EWNZNGDC@szxml06-in.huawei.com>; Thu, 17 Sep 2009 17:28:29 +0800 (CST)
Date: Thu, 17 Sep 2009 17:28:28 +0800
From: Xu Xiaohu <xuxh@huawei.com>
In-reply-to: <57F95EAE-6705-4B8E-849F-3F35D7239EDD@free.fr>
To: =?iso-8859-1?Q?'R=E9mi_Despr=E9s'?= <remi.despres@free.fr>
Message-id: <004201ca3779$373151b0$d40c6f0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
Thread-index: Aco3ctoyMEaJDrJLSNyPuRuvF2xwYgABSGMg
Cc: softwires@ietf.org, "'Templin, Fred L'" <Fred.L.Templin@boeing.com>, 'Behave WG' <behave@ietf.org>
Subject: Re: [BEHAVE] [Softwires] Some Thought about the Automatic TunnelAddress
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/mail-archive/web/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>
X-List-Received-Date: Thu, 17 Sep 2009 09:30:27 -0000

Hi Remi,

> But 5214 says in its introduction that "ISATAP enables automatic
> tunneling whether global or private IPv4 addresses are used".

Yes. However, to avoid the routing-loop attack, it'd better to use a private
address.

> To prevent all routing-loop attacks, 6to4 relay routers should
> therefore also deal with ISATAP routers that have global IPv4 addresses.
> 
> As a matter of facts, ISATAP can be useful with a global IPv4 address
> in a large private network that has enough global IPv4 addresses to
> use them internally: this provides IPv6 connectivity to dual-stack
> hosts that support ISATAP (e.g. with Windows or Linux AKAIK).

The site network could use public IPv4 address as long as the address used
as ISATAP tunnel endpoint on the ISATAP router is an address which is
unaccessible from the IPv4 Internet.

Xiaohu

> > Hence, I don't think the routing-loop attack prevention is a
> > justification
> > for the "IID-format constraint".
> 
> I also wish it would not have been a justification, but for the
> reason above I believe it is one we have to live with :-(.
> 
> Did I miss anything?
> 
> Regards,
> RD
> 
> 
> 
> > For a brief illustration of one instance of the the attack, here is an
> > example:
> >
> > +-------------------------------------------------------+
> > | IPv6                   IPv6 packet                    |
> > |Internet        dst6:  2002:198.16.9.9::1              |
> > |                src6:  2001:db8:1::200:5efe:192.88.99.1|
> > |                                           |           |
> > |                                           V           |
> > |          .--------------->--------------. |           |
> > |         /                                \|           |
> > +--------+----------------------------------+-----------+
> >          |                                  |
> >   2001:db8:1::/48                       2002::/16
> >     +---------+                        +---------+
> >     | ISATAP  |                        |  6to4   |
> >     +---------+                        +---------+
> >     198.16.9.9                         192.88.99.1
> >          |                                  |
> > +--------+---------+                        |
> > | IPv4   ^         |                        |
> > | site   ^         |                        |
> > |        ^         |                        V
> > |        ^         |                        |
> > +--------+---------+                        |
> >     198.16.9.0/24                           |
> >          |                                  |
> >          |                                  |
> > +--------+----------------------------------+-----------+
> > | IPv4    \                                /            |
> > |internet  '----------------<-------------'             |
> > |                 IPv6 in IPv4 packet                   |
> > |                  dst4: 198.16.9.9                     |
> > |                  src4: 192.88.99.1                    |
> > |                                                       |
> > +--------+----------------------------------+-----------+
> >


From remi.despres@free.fr  Thu Sep 17 03:11:47 2009
Return-Path: <remi.despres@free.fr>
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 D79273A6A9C; Thu, 17 Sep 2009 03:11:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.763
X-Spam-Level: 
X-Spam-Status: No, score=-1.763 tagged_above=-999 required=5 tests=[AWL=0.186,  BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tgSiLj-cqT7v; Thu, 17 Sep 2009 03:11:47 -0700 (PDT)
Received: from smtp6-g21.free.fr (smtp6-g21.free.fr [212.27.42.6]) by core3.amsl.com (Postfix) with ESMTP id 4E7173A69F7; Thu, 17 Sep 2009 03:11:44 -0700 (PDT)
Received: from smtp6-g21.free.fr (localhost [127.0.0.1]) by smtp6-g21.free.fr (Postfix) with ESMTP id F28F0E080AC; Thu, 17 Sep 2009 12:12:31 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by smtp6-g21.free.fr (Postfix) with ESMTP id EB98DE0814E; Thu, 17 Sep 2009 12:12:28 +0200 (CEST)
In-Reply-To: <004201ca3779$373151b0$d40c6f0a@china.huawei.com>
References: <004201ca3779$373151b0$d40c6f0a@china.huawei.com>
Mime-Version: 1.0 (Apple Message framework v753.1)
Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed
Message-Id: <47C266A3-F723-4D31-B56C-7F132A81E345@free.fr>
Content-Transfer-Encoding: quoted-printable
From: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
Date: Thu, 17 Sep 2009 12:12:27 +0200
To: Xu Xiaohu <xuxh@huawei.com>
X-Mailer: Apple Mail (2.753.1)
Cc: softwires@ietf.org, "'Templin, Fred L'" <Fred.L.Templin@boeing.com>, 'Behave WG' <behave@ietf.org>
Subject: Re: [BEHAVE] [Softwires] Some Thought about the Automatic TunnelAddress
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/mail-archive/web/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>
X-List-Received-Date: Thu, 17 Sep 2009 10:11:47 -0000

Le 17 sept. 09 =E0 11:28, Xu Xiaohu a =E9crit :

>> As a matter of facts, ISATAP can be useful with a global IPv4 address
>> in a large private network that has enough global IPv4 addresses to
>> use them internally: this provides IPv6 connectivity to dual-stack
>> hosts that support ISATAP (e.g. with Windows or Linux AKAIK).
>
> The site network could use public IPv4 address as long as the =20
> address used
> as ISATAP tunnel endpoint on the ISATAP router is an address which is
> unaccessible from the IPv4 Internet.

Yes.
I would also suggest to configure it this way.

But, one may want to protect the 6to4 relay WITHOUT assumptions that =20
go beyond what the ISATAP spec says (IMHO a legitimate objective).
For this, the proposed check can do the job.

BTW, are there scenarios you are interested in where having to =20
protect the 9th octet of IPv6 addresses is very annoying (I find it =20
annoying myself but, well, if we have to live with it let's accept it =20=

and proceed.)

Regards,
RD


>
> Xiaohu
>
>>> Hence, I don't think the routing-loop attack prevention is a
>>> justification
>>> for the "IID-format constraint".
>>
>> I also wish it would not have been a justification, but for the
>> reason above I believe it is one we have to live with :-(.
>>
>> Did I miss anything?
>>
>> Regards,
>> RD
>>
>>
>>
>>> For a brief illustration of one instance of the the attack, here =20
>>> is an
>>> example:
>>>
>>> +-------------------------------------------------------+
>>> | IPv6                   IPv6 packet                    |
>>> |Internet        dst6:  2002:198.16.9.9::1              |
>>> |                src6:  2001:db8:1::200:5efe:192.88.99.1|
>>> |                                           |           |
>>> |                                           V           |
>>> |          .--------------->--------------. |           |
>>> |         /                                \|           |
>>> +--------+----------------------------------+-----------+
>>>          |                                  |
>>>   2001:db8:1::/48                       2002::/16
>>>     +---------+                        +---------+
>>>     | ISATAP  |                        |  6to4   |
>>>     +---------+                        +---------+
>>>     198.16.9.9                         192.88.99.1
>>>          |                                  |
>>> +--------+---------+                        |
>>> | IPv4   ^         |                        |
>>> | site   ^         |                        |
>>> |        ^         |                        V
>>> |        ^         |                        |
>>> +--------+---------+                        |
>>>     198.16.9.0/24                           |
>>>          |                                  |
>>>          |                                  |
>>> +--------+----------------------------------+-----------+
>>> | IPv4    \                                /            |
>>> |internet  '----------------<-------------'             |
>>> |                 IPv6 in IPv4 packet                   |
>>> |                  dst4: 198.16.9.9                     |
>>> |                  src4: 192.88.99.1                    |
>>> |                                                       |
>>> +--------+----------------------------------+-----------+
>>>
>


From eric.burgey@orange-ftgroup.com  Thu Sep 17 07:44:42 2009
Return-Path: <eric.burgey@orange-ftgroup.com>
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 A9BCD3A688C; Thu, 17 Sep 2009 07:44: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_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 ySmVCzm103fL; Thu, 17 Sep 2009 07:44:41 -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 116D13A6808; Thu, 17 Sep 2009 07:44:40 -0700 (PDT)
Received: from ftrdmel0.rd.francetelecom.fr ([10.192.128.56]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 17 Sep 2009 16:45:08 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 17 Sep 2009 16:45:07 +0200
Message-ID: <08BA2C59E081884DB2AAE4A0BE9D6DC1629F33@ftrdmel0.rd.francetelecom.fr>
In-Reply-To: <57F95EAE-6705-4B8E-849F-3F35D7239EDD@free.fr>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BEHAVE] [Softwires] Some Thought about the AutomaticTunnelAddress
Thread-Index: Aco3coauTE1fkrVPRrG72UVQD5MnuAAMFF4w
References: <002601ca3745$63c8b710$d40c6f0a@china.huawei.com> <57F95EAE-6705-4B8E-849F-3F35D7239EDD@free.fr>
From: <eric.burgey@orange-ftgroup.com>
To: <remi.despres@free.fr>, <xuxh@huawei.com>
X-OriginalArrivalTime: 17 Sep 2009 14:45:08.0231 (UTC) FILETIME=[739D7170:01CA37A5]
Cc: softwires@ietf.org, Fred.L.Templin@boeing.com, behave@ietf.org
Subject: Re: [BEHAVE] [Softwires] Some Thought about the AutomaticTunnelAddress
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/mail-archive/web/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>
X-List-Received-Date: Thu, 17 Sep 2009 14:44:42 -0000

Hello,
Xu Xiaohu comment is right but probably be too much restrictive.
Excluding all public IPv4 addresses is too strict and not enough because =
it does not excludes 6 to 4 gateways between the local private network =
and the IPv6 network with a private IPv4 address.

ISATAP use an IPv6 operator prefix instead of a well known prefix, so it =
means that ISATAP is built to ensure IPv6 connectivity of IPv4 Islands =
inside an IPv6 network managed by a specific operator.
So the encapsulation of IPv6 packet into IPv4 done by the gateway must =
be restricted to IPv4 destination addresses managed by this operator =
(the ISATAP equipment operator) excluding all IPv4 addresses managed by =
this operator and allocated to ISATAP, 6 to 4 gateway or any other =
gateway between the IPv4 network and the IPv6 network like for example =
IVI-T gateways.


This limitation can be implemented through an access list in the ISATAP =
gateway, in IVI-T gateways or in any other gateway between the IPv4 =
network and the IPv6 network doing encapsulation of IPv6 packet, with a =
prefix allocated to an operator, in IPv4 packet.


	Eric BURGEY=20

-----Message d'origine-----
De=A0: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] De la =
part de R=E9mi Despr=E9s
Envoy=E9=A0: jeudi 17 septembre 2009 10:40
=C0=A0: Xu Xiaohu
Cc=A0: softwires@ietf.org; 'Templin, Fred L'; 'Behave WG'
Objet=A0: Re: [BEHAVE] [Softwires] Some Thought about the =
AutomaticTunnelAddress


Xu,

Thanks for you answer.
Further comment below.


Le 17 sept. 09 =E0 05:17, Xu Xiaohu a =E9crit :

> In your msg
> (http://www.ietf.org/mail-archive/web/behave/current/=20
> msg06816.html), you
> said "... Suffice it to say that a 6to4 relay router may need, to =20
> be safe,
> to look at IPv4 addresses that are embedded in ISATAP IPv6 =20
> addresses. In the
> above example, if the 6to4 relay router sees that the IPv4 embedded =20
> address
> in the IPv6 destination is its own IPv4 address 192.88.99.1, it can =20
> discard
> the packet and thus prevent the loop". However, I feel this is not =20
> a good
> idea for a 6to4 router to check the ISATAP address. In fact, the
> routing-loop attack can be easily avoided by using a private IPv4 =20
> address,
> rather that a public IPv4 address as the ISATAP tunnel endpoint =20
> address on
> the ISATAP router.

If the IPv4 address of an ISATAP router is private, the attack =20
scenario  below doesn't exists, YES.

But 5214 says in its introduction that "ISATAP enables automatic =20
tunneling whether global or private IPv4 addresses are used".
To prevent all routing-loop attacks, 6to4 relay routers should =20
therefore also deal with ISATAP routers that have global IPv4 addresses.

As a matter of facts, ISATAP can be useful with a global IPv4 address =20
in a large private network that has enough global IPv4 addresses to =20
use them internally: this provides IPv6 connectivity to dual-stack =20
hosts that support ISATAP (e.g. with Windows or Linux AKAIK).


> Hence, I don't think the routing-loop attack prevention is a =20
> justification
> for the "IID-format constraint".

I also wish it would not have been a justification, but for the =20
reason above I believe it is one we have to live with :-(.

Did I miss anything?

Regards,
RD



> For a brief illustration of one instance of the the attack, here is an
> example:
>
> +-------------------------------------------------------+
> | IPv6                   IPv6 packet                    |
> |Internet        dst6:  2002:198.16.9.9::1              |
> |                src6:  2001:db8:1::200:5efe:192.88.99.1|
> |                                           |           |
> |                                           V           |
> |          .--------------->--------------. |           |
> |         /                                \|           |
> +--------+----------------------------------+-----------+
>          |                                  |
>   2001:db8:1::/48                       2002::/16
>     +---------+                        +---------+
>     | ISATAP  |                        |  6to4   |
>     +---------+                        +---------+
>     198.16.9.9                         192.88.99.1
>          |                                  |
> +--------+---------+                        |
> | IPv4   ^         |                        |
> | site   ^         |                        |
> |        ^         |                        V
> |        ^         |                        |
> +--------+---------+                        |
>     198.16.9.0/24                           |
>          |                                  |
>          |                                  |
> +--------+----------------------------------+-----------+
> | IPv4    \                                /            |
> |internet  '----------------<-------------'             |
> |                 IPv6 in IPv4 packet                   |
> |                  dst4: 198.16.9.9                     |
> |                  src4: 192.88.99.1                    |
> |                                                       |
> +--------+----------------------------------+-----------+
>
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave

From fernando.gont.netbook.win@gmail.com  Thu Sep 17 09:41:26 2009
Return-Path: <fernando.gont.netbook.win@gmail.com>
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 0053B3A67D6 for <behave@core3.amsl.com>; Thu, 17 Sep 2009 09:41:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.784
X-Spam-Level: 
X-Spam-Status: No, score=-2.784 tagged_above=-999 required=5 tests=[AWL=-0.185, 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 mLIDJHDcT9dc for <behave@core3.amsl.com>; Thu, 17 Sep 2009 09:41:23 -0700 (PDT)
Received: from mail-yx0-f122.google.com (mail-yx0-f122.google.com [209.85.210.122]) by core3.amsl.com (Postfix) with ESMTP id A7E233A6978 for <behave@ietf.org>; Thu, 17 Sep 2009 09:41:22 -0700 (PDT)
Received: by yxe28 with SMTP id 28so21843yxe.19 for <behave@ietf.org>; Thu, 17 Sep 2009 09:42:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; bh=e5KvE1YSWwOL7nxCUpMUVwmYirmm/tiPI66NdvuRzjc=; b=E5mulScxiRbhnwODcbCeZsC6fl10XI+nJoVhY9AbdCeskoZNEzZl77kZCfok/8HxBC Qg03SVa9QysF0wltgJQGFYzooJpJBuLu725WkLsG5eb5koOY4oLeX+S1HB7BQojgwMeF EAFSDyBONc1LN1AFYm4TXKVW52sHZ/N6qFppc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:openpgp:content-type :content-transfer-encoding; b=kwasmcLnZfULOBMuYEGACePWuPC1FDFehC9UGDlShPBynXVmyjipxhJ1QlDaAlp61C ydHS4+jGfOUwfFkssvV4HLiknTby/YkoQTzGtRHpJwsjYFvhTMiPTCYyqi1wGrFz6kU9 X15wmB23kQkWrkG+LyVffLIlkBnf9SBJYfGXA=
Received: by 10.91.171.4 with SMTP id y4mr471098ago.116.1253205730996; Thu, 17 Sep 2009 09:42:10 -0700 (PDT)
Received: from ?192.168.0.167? (129-130-17-190.fibertel.com.ar [190.17.130.129]) by mx.google.com with ESMTPS id 7sm1265397agd.3.2009.09.17.09.42.08 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 17 Sep 2009 09:42:09 -0700 (PDT)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4AB266D4.50507@gont.com.ar>
Date: Thu, 17 Sep 2009 13:41:56 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Reinaldo Penno <rpenno@juniper.net>
References: <C6C54E63.36D5C%rpenno@juniper.net>
In-Reply-To: <C6C54E63.36D5C%rpenno@juniper.net>
X-Enigmail-Version: 0.95.7
OpenPGP: id=D076FFF1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Behave WG <behave@ietf.org>, Dan Wing <dwing@cisco.com>, Zhen Cao <caozhenpku@gmail.com>
Subject: Re: [BEHAVE] NAT64 and TCP processing (was Re: Comments todraft-ietf-behave-v6v4-xlate-stateful-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/mail-archive/web/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>
X-List-Received-Date: Thu, 17 Sep 2009 16:41:27 -0000

Reinaldo Penno wrote:

> No, in general the area where TCP, NAT44 and security intersect is very
> light on standards.

See the (currently expired) draft-gont-tcp-security I-D.

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






From Fred.L.Templin@boeing.com  Thu Sep 17 10:25:07 2009
Return-Path: <Fred.L.Templin@boeing.com>
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 EA25C28C2CA; Thu, 17 Sep 2009 10:25:07 -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.308,  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 zSRL+uBO8xeU; Thu, 17 Sep 2009 10:25:06 -0700 (PDT)
Received: from slb-smtpout-01.boeing.com (slb-smtpout-01.boeing.com [130.76.64.48]) by core3.amsl.com (Postfix) with ESMTP id D61D028C20A; Thu, 17 Sep 2009 10:25:06 -0700 (PDT)
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [130.247.48.231]) by slb-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id n8HHPdXp008102 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 17 Sep 2009 10:25:40 -0700 (PDT)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1]) by blv-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id n8HHPde6008006; Thu, 17 Sep 2009 10:25:39 -0700 (PDT)
Received: from XCH-NWHT-04.nw.nos.boeing.com (xch-nwht-04.nw.nos.boeing.com [130.247.64.250]) by blv-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id n8HHPd8b008003 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Thu, 17 Sep 2009 10:25:39 -0700 (PDT)
Received: from XCH-NW-15V.nw.nos.boeing.com ([130.247.25.104]) by XCH-NWHT-04.nw.nos.boeing.com ([130.247.64.250]) with mapi; Thu, 17 Sep 2009 10:25:39 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "eric.burgey@orange-ftgroup.com" <eric.burgey@orange-ftgroup.com>, "remi.despres@free.fr" <remi.despres@free.fr>, "xuxh@huawei.com" <xuxh@huawei.com>
Date: Thu, 17 Sep 2009 10:25:37 -0700
Thread-Topic: [BEHAVE] [Softwires] Some Thought about the AutomaticTunnelAddress
Thread-Index: Aco3coauTE1fkrVPRrG72UVQD5MnuAAMFF4wAAYPB4A=
Message-ID: <12F4112206976147A34FEC0277597CCF27A402C663@XCH-NW-15V.nw.nos.boeing.com>
References: <002601ca3745$63c8b710$d40c6f0a@china.huawei.com> <57F95EAE-6705-4B8E-849F-3F35D7239EDD@free.fr> <08BA2C59E081884DB2AAE4A0BE9D6DC1629F33@ftrdmel0.rd.francetelecom.fr>
In-Reply-To: <08BA2C59E081884DB2AAE4A0BE9D6DC1629F33@ftrdmel0.rd.francetelecom.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "softwires@ietf.org" <softwires@ietf.org>, "behave@ietf.org" <behave@ietf.org>
Subject: Re: [BEHAVE] [Softwires] Some Thought about the AutomaticTunnelAddress
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/mail-archive/web/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>
X-List-Received-Date: Thu, 17 Sep 2009 17:25:08 -0000

Eric,

The point is that ISATAP can be used with public IPv4
addresses (in which case the IPv6 address is constructed
as: "FOO::0200:5EFE:V4ADDR") and there is no guarantee
in that case that the ISATAP router is located behind an
ip-proto-41 nor ingress-filtering site border router. Plus,
I know of at least one major enterprise network that uses
public IPv4 addresses internally, and the network is much
too large to be covered by a single ISATAP link.

This discussion should probably by synchronized with the
one taking place on the v6ops, 6man and secdir lists.

Fred
fred.l.templin@boeing.com

> -----Original Message-----
> From: eric.burgey@orange-ftgroup.com [mailto:eric.burgey@orange-ftgroup.c=
om]
> Sent: Thursday, September 17, 2009 7:45 AM
> To: remi.despres@free.fr; xuxh@huawei.com
> Cc: softwires@ietf.org; Templin, Fred L; behave@ietf.org
> Subject: RE: [BEHAVE] [Softwires] Some Thought about the AutomaticTunnelA=
ddress
>=20
> Hello,
> Xu Xiaohu comment is right but probably be too much restrictive.
> Excluding all public IPv4 addresses is too strict and not enough because =
it does not excludes 6 to 4
> gateways between the local private network and the IPv6 network with a pr=
ivate IPv4 address.
>=20
> ISATAP use an IPv6 operator prefix instead of a well known prefix, so it =
means that ISATAP is built
> to ensure IPv6 connectivity of IPv4 Islands inside an IPv6 network manage=
d by a specific operator.
> So the encapsulation of IPv6 packet into IPv4 done by the gateway must be=
 restricted to IPv4
> destination addresses managed by this operator (the ISATAP equipment oper=
ator) excluding all IPv4
> addresses managed by this operator and allocated to ISATAP, 6 to 4 gatewa=
y or any other gateway
> between the IPv4 network and the IPv6 network like for example IVI-T gate=
ways.
>=20
>=20
> This limitation can be implemented through an access list in the ISATAP g=
ateway, in IVI-T gateways or
> in any other gateway between the IPv4 network and the IPv6 network doing =
encapsulation of IPv6
> packet, with a prefix allocated to an operator, in IPv4 packet.
>=20
>=20
> 	Eric BURGEY
>=20
> -----Message d'origine-----
> De=A0: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] De la par=
t de R=E9mi Despr=E9s
> Envoy=E9=A0: jeudi 17 septembre 2009 10:40
> =C0=A0: Xu Xiaohu
> Cc=A0: softwires@ietf.org; 'Templin, Fred L'; 'Behave WG'
> Objet=A0: Re: [BEHAVE] [Softwires] Some Thought about the AutomaticTunnel=
Address
>=20
>=20
> Xu,
>=20
> Thanks for you answer.
> Further comment below.
>=20
>=20
> Le 17 sept. 09 =E0 05:17, Xu Xiaohu a =E9crit :
>=20
> > In your msg
> > (http://www.ietf.org/mail-archive/web/behave/current/
> > msg06816.html), you
> > said "... Suffice it to say that a 6to4 relay router may need, to
> > be safe,
> > to look at IPv4 addresses that are embedded in ISATAP IPv6
> > addresses. In the
> > above example, if the 6to4 relay router sees that the IPv4 embedded
> > address
> > in the IPv6 destination is its own IPv4 address 192.88.99.1, it can
> > discard
> > the packet and thus prevent the loop". However, I feel this is not
> > a good
> > idea for a 6to4 router to check the ISATAP address. In fact, the
> > routing-loop attack can be easily avoided by using a private IPv4
> > address,
> > rather that a public IPv4 address as the ISATAP tunnel endpoint
> > address on
> > the ISATAP router.
>=20
> If the IPv4 address of an ISATAP router is private, the attack
> scenario  below doesn't exists, YES.
>=20
> But 5214 says in its introduction that "ISATAP enables automatic
> tunneling whether global or private IPv4 addresses are used".
> To prevent all routing-loop attacks, 6to4 relay routers should
> therefore also deal with ISATAP routers that have global IPv4 addresses.
>=20
> As a matter of facts, ISATAP can be useful with a global IPv4 address
> in a large private network that has enough global IPv4 addresses to
> use them internally: this provides IPv6 connectivity to dual-stack
> hosts that support ISATAP (e.g. with Windows or Linux AKAIK).
>=20
>=20
> > Hence, I don't think the routing-loop attack prevention is a
> > justification
> > for the "IID-format constraint".
>=20
> I also wish it would not have been a justification, but for the
> reason above I believe it is one we have to live with :-(.
>=20
> Did I miss anything?
>=20
> Regards,
> RD
>=20
>=20
>=20
> > For a brief illustration of one instance of the the attack, here is an
> > example:
> >
> > +-------------------------------------------------------+
> > | IPv6                   IPv6 packet                    |
> > |Internet        dst6:  2002:198.16.9.9::1              |
> > |                src6:  2001:db8:1::200:5efe:192.88.99.1|
> > |                                           |           |
> > |                                           V           |
> > |          .--------------->--------------. |           |
> > |         /                                \|           |
> > +--------+----------------------------------+-----------+
> >          |                                  |
> >   2001:db8:1::/48                       2002::/16
> >     +---------+                        +---------+
> >     | ISATAP  |                        |  6to4   |
> >     +---------+                        +---------+
> >     198.16.9.9                         192.88.99.1
> >          |                                  |
> > +--------+---------+                        |
> > | IPv4   ^         |                        |
> > | site   ^         |                        |
> > |        ^         |                        V
> > |        ^         |                        |
> > +--------+---------+                        |
> >     198.16.9.0/24                           |
> >          |                                  |
> >          |                                  |
> > +--------+----------------------------------+-----------+
> > | IPv4    \                                /            |
> > |internet  '----------------<-------------'             |
> > |                 IPv6 in IPv4 packet                   |
> > |                  dst4: 198.16.9.9                     |
> > |                  src4: 192.88.99.1                    |
> > |                                                       |
> > +--------+----------------------------------+-----------+
> >
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave

From rfc-editor@rfc-editor.org  Thu Sep 17 16:08:25 2009
Return-Path: <rfc-editor@rfc-editor.org>
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 49E203A6B1F; Thu, 17 Sep 2009 16:08:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.886
X-Spam-Level: 
X-Spam-Status: No, score=-16.886 tagged_above=-999 required=5 tests=[AWL=0.713, 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 o801-IDEl5Qr; Thu, 17 Sep 2009 16:08:24 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 85ED728C162; Thu, 17 Sep 2009 16:08:24 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id 372843256F6; Thu, 17 Sep 2009 16:08:49 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20090917230849.372843256F6@bosco.isi.edu>
Date: Thu, 17 Sep 2009 16:08:49 -0700 (PDT)
Cc: behave@ietf.org, rfc-editor@rfc-editor.org
Subject: [BEHAVE] BCP 150, RFC 5597 on Network Address Translation (NAT) Behavioral Requirements for the Datagram Congestion Control Protocol
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/mail-archive/web/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>
X-List-Received-Date: Thu, 17 Sep 2009 23:08:25 -0000

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

        BCP 150        
        RFC 5597

        Title:      Network Address Translation (NAT) Behavioral 
                    Requirements for the Datagram Congestion Control 
                    Protocol 
        Author:     R. Denis-Courmont
        Status:     Best Current Practice
        Date:       September 2009
        Mailbox:    rem@videolan.org
        Pages:      9
        Characters: 18933
        See Also:   BCP00150

        I-D Tag:    draft-ietf-behave-dccp-05.txt

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

This document defines a set of requirements for NATs handling the
Datagram Congestion Control Protocol (DCCP).  These requirements
allow DCCP applications, such as streaming applications, to operate
consistently, and they are very similar to the TCP requirements for
NATs, which have already been published by the IETF.  Ensuring that
NATs meet this set of requirements will greatly increase the
likelihood that applications using DCCP 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



From rpenno@juniper.net  Thu Sep 17 17:45:36 2009
Return-Path: <rpenno@juniper.net>
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 DE04C3A6B1F for <behave@core3.amsl.com>; Thu, 17 Sep 2009 17:45:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.414
X-Spam-Level: 
X-Spam-Status: No, score=-6.414 tagged_above=-999 required=5 tests=[AWL=0.185,  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 7LWHVam9pinG for <behave@core3.amsl.com>; Thu, 17 Sep 2009 17:45:35 -0700 (PDT)
Received: from exprod7og115.obsmtp.com (exprod7og115.obsmtp.com [64.18.2.217]) by core3.amsl.com (Postfix) with ESMTP id 4EA1C3A67A4 for <behave@ietf.org>; Thu, 17 Sep 2009 17:45:34 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob115.postini.com ([64.18.6.12]) with SMTP ID DSNKSrLYYqlVrr0toqtZPtaWrjt/j0zLsNro@postini.com; Thu, 17 Sep 2009 17:46:29 PDT
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.1.375.2; Thu, 17 Sep 2009 17:44:44 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Thu, 17 Sep 2009 20:44:43 -0400
From: Reinaldo Penno <rpenno@juniper.net>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Cameron Byrne <cb.list6@gmail.com>
Date: Thu, 17 Sep 2009 20:44:25 -0400
Thread-Topic: [BEHAVE] Comments on NAT64 draft
Thread-Index: Aco3TetCywnpWi7XSTuaq0eOOcoZXAAq0BCU
Message-ID: <C6D825F9.37F54%rpenno@juniper.net>
In-Reply-To: <4AB1B88A.6080109@gmail.com>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Behave WG <behave@ietf.org>, Zhen Cao <caozhenpku@gmail.com>
Subject: Re: [BEHAVE] Comments on NAT64 draft
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/mail-archive/web/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>
X-List-Received-Date: Fri, 18 Sep 2009 00:45:36 -0000

I do not think it is a big deal. The same is done today for NAT44 and such
knowledge/experience could be easily leveraged.

I know we can decide differently for NAT64, but the box that has been doing
NAT44 will (or could) be doing NAT64 for the same network; therefore 'look
and feel' as related to the original BEHAVE RFCs should be the same as much
as possible. This would make adoption and transition easier.

Thanks,

Reinaldo=20

On 9/16/09 9:18 PM, "Brian E Carpenter" <brian.e.carpenter@gmail.com> wrote=
:

> On 2009-09-17 01:53, Cameron Byrne wrote:
>> On Wed, Sep 16, 2009 at 6:15 AM, Iljitsch van Beijnum
>> <iljitsch@muada.com> wrote:
>>> On 16 Sep 2009, at 15:07 , Zhen Cao wrote:
>>>=20
>>>>> The only problematic case is one where there is no match because this=
 is
>>>>> the
>>>>> first packet (and a non-first fragment). In that case the fragment mu=
st
>>>>> be
>>>>> dropped, because a mapping can't be created without port numbers.
>>>> Yes, that's what i meant. I forgot to mention it is the first packet
>>>> in the flow. But the NAT may wait for the first frag to arrive?
>>>> Anyway, do we need to define this behavior explicitly in the draft?
>>> With TCP this can't realistically happen because the initial SYN is sma=
ll
>>> enough to fit in any reasonable MTU.
>>>=20
>>> With UDP it could happen. I guess if you ALWAYS get reordering and ALWA=
YS
>>> throw away the non-initial fragment of a first packet then there will b=
e
>>> trouble with protocols like the DNS that send single packet transaction=
s,
>>> because those will then consistently fail.
>>>=20
>>> Any ideas from implementers? Is it problematic to have to buffer and
>>> reassemble UDP fragments that don't match any state in the v6->v4 direc=
tion?
>>=20
>> According to RFC 4787 Requirement 14, a NAT MUST accommodate this out
>> of order fragment situation.
>=20
> This seems extreme; I wonder why it wasn't a SHOULD. However,
> that's a BCP for IPv4-IPv4 NATs "as described in [RFC2663]."
> We can decide independently for NAT64, but Iljitsch has asked the
> right question: how big a deal is this for implementors?
>=20
>     Brian
>=20
>>=20
>>> (Fortunately we don't have to do this in the v4->v6 direction, where de=
nial
>>> of service attacks are a bigger risk, because new sessions aren't set u=
p in
>>> this direction.)
>>> _______________________________________________
>>> Behave mailing list
>>> Behave@ietf.org
>>> https://www.ietf.org/mailman/listinfo/behave
>>>=20
>> _______________________________________________
>> Behave mailing list
>> Behave@ietf.org
>> https://www.ietf.org/mailman/listinfo/behave
>>=20
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave


From brian.e.carpenter@gmail.com  Thu Sep 17 18:15:39 2009
Return-Path: <brian.e.carpenter@gmail.com>
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 6577B3A686A for <behave@core3.amsl.com>; Thu, 17 Sep 2009 18:15:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.408
X-Spam-Level: 
X-Spam-Status: No, score=-2.408 tagged_above=-999 required=5 tests=[AWL=0.191,  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 l86d0bvulFDW for <behave@core3.amsl.com>; Thu, 17 Sep 2009 18:15:38 -0700 (PDT)
Received: from mail-px0-f173.google.com (mail-px0-f173.google.com [209.85.216.173]) by core3.amsl.com (Postfix) with ESMTP id 7AC543A686E for <behave@ietf.org>; Thu, 17 Sep 2009 18:15:38 -0700 (PDT)
Received: by pxi3 with SMTP id 3so470239pxi.31 for <behave@ietf.org>; Thu, 17 Sep 2009 18:16:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=V42nL6Fd0pOX6vkaT+gSnTAn2EBu4/KJf594UQsdIrs=; b=f4xIX7JlXTFCG5KvK3YU+dm0eaxQNUzqaBWUu/Y0doEKJSKwATXME65i51gk9ZpCu3 Bsn37mvUKPJ7MhuJQoMJ6ME+nH5uUT14pIDzYGZzD12n5onjsQGd3e2EyhPQ8YRn7SXv Ln91f0JY2D1XBzGczn0RoKpOA1Z22DO512ZTc=
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=JEJtovrDNO6f5V7Gw8cEGiBsF+k65e/sBlblFhOk5IUjUBWfTPikRhj9QJbcWshU7d 3mat/xsLBXeUs9gsJ+AfDHIJ2P9bklhhwMOBL2Zdza81T0eu5j1pVxrC8pSuUVtoT3Xf +M0PJVz+rxo/ICB167iJZh+fTo5wwYLS7BHno=
Received: by 10.114.18.29 with SMTP id 29mr1253453war.147.1253236588985; Thu, 17 Sep 2009 18:16:28 -0700 (PDT)
Received: from ?130.216.38.124? (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id 20sm243435pzk.1.2009.09.17.18.16.27 (version=SSLv3 cipher=RC4-MD5); Thu, 17 Sep 2009 18:16:28 -0700 (PDT)
Message-ID: <4AB2DF6E.7070308@gmail.com>
Date: Fri, 18 Sep 2009 13:16:30 +1200
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: Reinaldo Penno <rpenno@juniper.net>
References: <C6D825F9.37F54%rpenno@juniper.net>
In-Reply-To: <C6D825F9.37F54%rpenno@juniper.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Cameron Byrne <cb.list6@gmail.com>, Behave WG <behave@ietf.org>, Zhen Cao <caozhenpku@gmail.com>
Subject: Re: [BEHAVE] Comments on NAT64 draft
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/mail-archive/web/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>
X-List-Received-Date: Fri, 18 Sep 2009 01:15:39 -0000

Reinaldo,

In general terms I agree with you, but is there documented field experience?

I am concerned that even a small rate of out-of-order fragments could lead
to disproportionately high buffering requirements and a significant
performance hit, even disregarding a DOS scenario.

Regards
   Brian

On 2009-09-18 12:44, Reinaldo Penno wrote:
> I do not think it is a big deal. The same is done today for NAT44 and such
> knowledge/experience could be easily leveraged.
> 
> I know we can decide differently for NAT64, but the box that has been doing
> NAT44 will (or could) be doing NAT64 for the same network; therefore 'look
> and feel' as related to the original BEHAVE RFCs should be the same as much
> as possible. This would make adoption and transition easier.
> 
> Thanks,
> 
> Reinaldo 
> 
> On 9/16/09 9:18 PM, "Brian E Carpenter" <brian.e.carpenter@gmail.com> wrote:
> 
>> On 2009-09-17 01:53, Cameron Byrne wrote:
>>> On Wed, Sep 16, 2009 at 6:15 AM, Iljitsch van Beijnum
>>> <iljitsch@muada.com> wrote:
>>>> On 16 Sep 2009, at 15:07 , Zhen Cao wrote:
>>>>
>>>>>> The only problematic case is one where there is no match because this is
>>>>>> the
>>>>>> first packet (and a non-first fragment). In that case the fragment must
>>>>>> be
>>>>>> dropped, because a mapping can't be created without port numbers.
>>>>> Yes, that's what i meant. I forgot to mention it is the first packet
>>>>> in the flow. But the NAT may wait for the first frag to arrive?
>>>>> Anyway, do we need to define this behavior explicitly in the draft?
>>>> With TCP this can't realistically happen because the initial SYN is small
>>>> enough to fit in any reasonable MTU.
>>>>
>>>> With UDP it could happen. I guess if you ALWAYS get reordering and ALWAYS
>>>> throw away the non-initial fragment of a first packet then there will be
>>>> trouble with protocols like the DNS that send single packet transactions,
>>>> because those will then consistently fail.
>>>>
>>>> Any ideas from implementers? Is it problematic to have to buffer and
>>>> reassemble UDP fragments that don't match any state in the v6->v4 direction?
>>> According to RFC 4787 Requirement 14, a NAT MUST accommodate this out
>>> of order fragment situation.
>> This seems extreme; I wonder why it wasn't a SHOULD. However,
>> that's a BCP for IPv4-IPv4 NATs "as described in [RFC2663]."
>> We can decide independently for NAT64, but Iljitsch has asked the
>> right question: how big a deal is this for implementors?
>>
>>     Brian
>>
>>>> (Fortunately we don't have to do this in the v4->v6 direction, where denial
>>>> of service attacks are a bigger risk, because new sessions aren't set up in
>>>> this direction.)
>>>> _______________________________________________
>>>> 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 caozhenpku@gmail.com  Thu Sep 17 18:28:58 2009
Return-Path: <caozhenpku@gmail.com>
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 2B6233A6765 for <behave@core3.amsl.com>; Thu, 17 Sep 2009 18:28:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.49
X-Spam-Level: 
X-Spam-Status: No, score=-2.49 tagged_above=-999 required=5 tests=[AWL=0.109,  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 ts6MQibCFabW for <behave@core3.amsl.com>; Thu, 17 Sep 2009 18:28:57 -0700 (PDT)
Received: from mail-vw0-f201.google.com (mail-vw0-f201.google.com [209.85.212.201]) by core3.amsl.com (Postfix) with ESMTP id 4500D3A6811 for <behave@ietf.org>; Thu, 17 Sep 2009 18:28:57 -0700 (PDT)
Received: by vws39 with SMTP id 39so684499vws.29 for <behave@ietf.org>; Thu, 17 Sep 2009 18:29:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=EPmbVURVfhvymSgTGMIJAQjiCGlDiUHfpa+gBY2O/CM=; b=X8fIUsjeWGYSd0XBOdcBzTyvx20cX8Y1627UtKq5EdIleLKSt823/8PE+DgHHfFdfB ehzR8ScHNbGkvTXB6Pg2lexBhqqjh7IkgO9Bqi5xbY9Gqz8p62hCema8U0T7Z7R6ctS2 MYV4aHsLH4pnpS+aOlj0w0kqWp5nSSS/m7j0o=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=g0CtS0sTbg6deC+BvFZH/+r93XnfbuoRNgmF4OvLRUV8xgb/LMylYC02+HSl3E3hKq IMeCebP2pNJLDsWWSeXccR9QA3Fw1vrpKRXzE2V50ECspivgaWIazDCf+7/hjksGrNI9 XatvSSaqCXDG0dBXSRB5GcJ+rVEUYHHlcn95k=
MIME-Version: 1.0
Received: by 10.220.109.36 with SMTP id h36mr379078vcp.42.1253237386129; Thu,  17 Sep 2009 18:29:46 -0700 (PDT)
In-Reply-To: <4AB1B88A.6080109@gmail.com>
References: <a7c8d0a30909150630i29d535bbhf3089fdfecffa328@mail.gmail.com> <7CB993A6-829C-46CC-A74C-7DBF7CFE88C6@muada.com> <a7c8d0a30909150838s230397d9r3cbffb5df6097b76@mail.gmail.com> <273D4852-D26C-497E-A034-2C3EE4908660@muada.com> <a7c8d0a30909151846w6f85cc67je3774c93e298f2e1@mail.gmail.com> <C37FF658-CF1A-4106-ABD9-2DB18B97B2CF@muada.com> <a7c8d0a30909160607l1209993ajae733d2dc116532b@mail.gmail.com> <519DB330-54FD-4163-91A8-DF81290A10B5@muada.com> <bcff0fba0909160653s59990a8al3cd29d12dab14095@mail.gmail.com> <4AB1B88A.6080109@gmail.com>
Date: Fri, 18 Sep 2009 09:29:45 +0800
Message-ID: <a7c8d0a30909171829l673de518t228defb0248bd1e9@mail.gmail.com>
From: Zhen Cao <caozhenpku@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Cameron Byrne <cb.list6@gmail.com>, Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Comments on NAT64 draft
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/mail-archive/web/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>
X-List-Received-Date: Fri, 18 Sep 2009 01:28:58 -0000

>>> Any ideas from implementers? Is it problematic to have to buffer and
>>> reassemble UDP fragments that don't match any state in the v6->v4 direc=
tion?
>>
>> According to RFC 4787 Requirement 14, a NAT MUST accommodate this out
>> of order fragment situation.
>
> This seems extreme; I wonder why it wasn't a SHOULD. However,
> that's a BCP for IPv4-IPv4 NATs "as described in [RFC2663]."
> We can decide independently for NAT64, but Iljitsch has asked the
> right question: how big a deal is this for implementors?

It might not be a big problem for implementor, considering it only
hurts the first out-of-order fragmented packet of the flow. Also from
the statistics you provided several days before, fragmented UDP
packets counts to a very small percentage.

But changing the text in NAT64 is also not a big deal. We can analyze
this in the document a bit for the consideration of implementors. This
will do no harm and make the document as solid as possible.

>
> =A0 =A0Brian
>
>>
>>> (Fortunately we don't have to do this in the v4->v6 direction, where de=
nial
>>> of service attacks are a bigger risk, because new sessions aren't set u=
p in
>>> this direction.)
>>> _______________________________________________
>>> 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 dwing@cisco.com  Thu Sep 17 21:44:08 2009
Return-Path: <dwing@cisco.com>
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 A06DE3A6829 for <behave@core3.amsl.com>; Thu, 17 Sep 2009 21:44:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.449
X-Spam-Level: 
X-Spam-Status: No, score=-6.449 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, 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 qNX0FWGfb1IO for <behave@core3.amsl.com>; Thu, 17 Sep 2009 21:44:07 -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 5046D3A68AF for <behave@ietf.org>; Thu, 17 Sep 2009 21:43:49 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApsEAKOtskqrR7PE/2dsb2JhbACKbrBsiFABkCoFgjyBYIFd
X-IronPort-AV: E=Sophos;i="4.44,407,1249257600"; d="scan'208";a="243579475"
Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-1.cisco.com with ESMTP; 18 Sep 2009 04:44:42 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id n8I4igrr022136;  Thu, 17 Sep 2009 21:44:42 -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.14.3) with ESMTP id n8I4igSp024024; Fri, 18 Sep 2009 04:44:42 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 17 Sep 2009 21:44:42 -0700
Received: from dwingwxp01 ([10.32.240.198]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 17 Sep 2009 21:44:42 -0700
From: "Dan Wing" <dwing@cisco.com>
To: "'Christian Huitema'" <huitema@microsoft.com>
References: <4AA7730F.6040602@cernet.edu.cn><36ba02b00909141038i1611b5d6ide4fd96157ed2bc8@mail.gmail.com><6B55F0F93C3E9D45AF283313B8D342BA20F54E47@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com><4AAF2C06.2020107@it.uc3m.es><6B55F0F93C3E9D45AF283313B8D342BA20F557D0@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com><4AAFA425.7040706@it.uc3m.es> <4AB079D5.1010404@cernet.edu.cn><6B55F0F93C3E9D45AF283313B8D342BA20F5A151@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com><4AB191F3.9040305@cernet.edu.cn> <6B55F0F93C3E9D45AF283313B8D342BA20F5C240@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
Date: Thu, 17 Sep 2009 21:44:41 -0700
Message-ID: <028301ca381a$bcc47fe0$5da36b80@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AQHKNckZMF3GDtqt2kuK6ErD8Y/t95DXsFRQgAB6jICAAP69gIAAD6twgAE+QoD//8N50IABjcVg
In-Reply-To: <6B55F0F93C3E9D45AF283313B8D342BA20F5C240@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-OriginalArrivalTime: 18 Sep 2009 04:44:42.0285 (UTC) FILETIME=[BCE415D0:01CA381A]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2463; t=1253249082; x=1254113082; 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]=20Security=20implications=20of =20protocol=20translation |Sender:=20; bh=Y3/r4Qm5FY6Vw3snw69xWXA3dg6VITOHTm7cvIaAxS4=; b=RSXz3pZVlQx/KU5pzeho0uUblD7EGc8Wj1y2BvPE+YEN1Wqf33vadNYCRK 4Y31Cc21xVxyX1OxeIOYeMZdYFDzobOkQiO1kavOPROx7IIsnIfperXLos7X yFj384sx9J;
Authentication-Results: sj-dkim-4; header.From=dwing@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; ); 
Cc: 'Xing Li' <xing@cernet.edu.cn>, 'Behave WG' <behave@ietf.org>
Subject: Re: [BEHAVE] Security implications of protocol translation
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/mail-archive/web/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>
X-List-Received-Date: Fri, 18 Sep 2009 04:44:08 -0000

 

> -----Original Message-----
> From: behave-bounces@ietf.org 
> [mailto:behave-bounces@ietf.org] On Behalf Of Christian Huitema
> Sent: Wednesday, September 16, 2009 10:10 PM
> To: Xing Li
> Cc: Behave WG
> Subject: Re: [BEHAVE] Security implications of protocol translation
> 
> > > If that is the case, if translatable addresses only 
> differ from the
> > regular addresses by the structure of the host identifier, 
> how does the
> > translator verify that customer A is not attempting to use an IPv4
> > address assigned to customer B?
> > >
> > 
> > how about configure uRPF in the stateless translator?  Xing
> 
> uRPF is a form of ingress filtering. Of course you should 
> enable that. But it is not sufficient. 
> 
> Suppose that customer A has an IPv6 translatable address of 
> the form: <ISP-prefix>:<SubnetA>:<MagicA>:a.a.a.a, where 
> a.a.a.a is the IPv4 address assigned by the ISP to A and 
> "magicA" is the special sauce that distinguishes translatable 
> addresses and enables checksum neutrality. Customer B 
> normally uses addresses of the form 
> <ISP-prefix>:<SubnetB>:<host-ID>. One of the hosts at 
> customer B's site configures a host ID of the form 
> <MagicB>:a.a.a.a -- using the appropriate magic, e.g. to 
> match checksums. 
> 
> Customer B can send spoofed packets with the source address 
> <ISP-prefix>:<SubnetB>:<MagicB>:a.a.a.a. These packets will 
> be considered valid by egress filtering and uRPF checks, 
> because they do indeed come from the right path for 
> <ISP-prefix>:<SubnetB>. Will the translator forward these 
> packets as originating from address <a.a.a.a>? If not, how 
> does the translator decide that the packets from B are 
> erroneous? What information does it use?

I understand what you're describing now.  Thanks.

The translator would need to validate the incoming packet
by examing the a.a.a.a address and deciding if the
<ISP-prefix>:<SubnetB> is correct.  The translator can
validate it by using its same algorithm for IPv4-to-
IPv6 packets; if the translator receives an IPv4 packet
with IPv4 address a.a.a.a, it will algorithmically
prepend <ISP-Prefix>:<SubnetA>:<MagicB> to it.  The
translator can notice that the arriving packet has
a different subnet, and drop it.  This is akin to the
translator doing a uRPF check on the source address
of the IPv6 packet:  "would I send an IPv4 packet
to this same IPv6 destination".

-d


From huitema@microsoft.com  Thu Sep 17 22:14:20 2009
Return-Path: <huitema@microsoft.com>
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 2F92C3A69E8 for <behave@core3.amsl.com>; Thu, 17 Sep 2009 22:14:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.561
X-Spam-Level: 
X-Spam-Status: No, score=-10.561 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Va3oyzzhpDGN for <behave@core3.amsl.com>; Thu, 17 Sep 2009 22:14:19 -0700 (PDT)
Received: from smtp.microsoft.com (mail2.microsoft.com [131.107.115.215]) by core3.amsl.com (Postfix) with ESMTP id 36DA33A68F3 for <behave@ietf.org>; Thu, 17 Sep 2009 22:14:19 -0700 (PDT)
Received: from TK5EX14HUBC102.redmond.corp.microsoft.com (157.54.7.154) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.176.0; Thu, 17 Sep 2009 22:15:12 -0700
Received: from TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com (157.54.71.68) by TK5EX14HUBC102.redmond.corp.microsoft.com (157.54.7.154) with Microsoft SMTP Server id 14.0.639.20; Thu, 17 Sep 2009 22:15:11 -0700
Received: from TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com ([169.254.3.19]) by TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.68]) with mapi; Thu, 17 Sep 2009 22:15:11 -0700
From: Christian Huitema <huitema@microsoft.com>
To: Dan Wing <dwing@cisco.com>
Thread-Topic: [BEHAVE] Security implications of protocol translation
Thread-Index: AQHKNckZMF3GDtqt2kuK6ErD8Y/t95DXsFRQgAB6jICAAP69gIAAD6twgAE+QoD//8N50IABjcVggAADXDA=
Date: Fri, 18 Sep 2009 05:15:05 +0000
Message-ID: <6B55F0F93C3E9D45AF283313B8D342BA20F5E923@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
References: <4AA7730F.6040602@cernet.edu.cn><36ba02b00909141038i1611b5d6ide4fd96157ed2bc8@mail.gmail.com><6B55F0F93C3E9D45AF283313B8D342BA20F54E47@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com><4AAF2C06.2020107@it.uc3m.es><6B55F0F93C3E9D45AF283313B8D342BA20F557D0@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com><4AAFA425.7040706@it.uc3m.es> <4AB079D5.1010404@cernet.edu.cn><6B55F0F93C3E9D45AF283313B8D342BA20F5A151@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com><4AB191F3.9040305@cernet.edu.cn> <6B55F0F93C3E9D45AF283313B8D342BA20F5C240@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <028301ca381a$bcc47fe0$5da36b80@cisco.com>
In-Reply-To: <028301ca381a$bcc47fe0$5da36b80@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: 'Xing Li' <xing@cernet.edu.cn>, 'Behave WG' <behave@ietf.org>
Subject: Re: [BEHAVE] Security implications of protocol translation
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/mail-archive/web/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>
X-List-Received-Date: Fri, 18 Sep 2009 05:14:20 -0000

> > Customer B can send spoofed packets with the source address
> > <ISP-prefix>:<SubnetB>:<MagicB>:a.a.a.a. These packets will
> > be considered valid by egress filtering and uRPF checks,
> > because they do indeed come from the right path for
> > <ISP-prefix>:<SubnetB>. Will the translator forward these
> > packets as originating from address <a.a.a.a>? If not, how
> > does the translator decide that the packets from B are
> > erroneous? What information does it use?
>=20
> I understand what you're describing now.  Thanks.
>=20
> The translator would need to validate the incoming packet
> by examing the a.a.a.a address and deciding if the
> <ISP-prefix>:<SubnetB> is correct.  The translator can
> validate it by using its same algorithm for IPv4-to-
> IPv6 packets; if the translator receives an IPv4 packet
> with IPv4 address a.a.a.a, it will algorithmically
> prepend <ISP-Prefix>:<SubnetA>:<MagicB> to it.  The
> translator can notice that the arriving packet has
> a different subnet, and drop it.  This is akin to the
> translator doing a uRPF check on the source address
> of the IPv6 packet:  "would I send an IPv4 packet
> to this same IPv6 destination".

Yes, that will work. But lets now compare this stateless option to the alte=
rnative, a stateful translator with some configuration. Specifically, suppo=
se a stateful translator that manages a pool of IP addresses, and that is c=
onfigured to "reserve" some addresses in that pool to specific IPv6 hosts. =
The configuration option would be something like "map a.a.a.a to <ISP-Prefi=
x>:<SubnetA>:<HostId-A>."

Now, lets compare the amount of administrative overhead and routing overhea=
d:

1) At the translator: In the stateless case, the NAT is programmed to map "=
a.a.a.a" to "<ISP-Prefix>:<SubnetA>:<MagicA>:a.a.a.a"; In the stateful case=
, the NAT is programmed to map "a.a.a.a" to "<ISP-Prefix>:<SubnetA>:<HostID=
-A>". Basically the same cost.

2) At the host receiving the mapping: In the stateful case, the host manage=
s exactly one address, "<ISP-Prefix>:<SubnetA>:<HostID-A>"; In the stateles=
s case, the host has to be configured with two addresses, "<ISP-Prefix>:<Su=
bnetA>:<HostID-A>" and "<ISP-Prefix>:<SubnetA>:<MagicA>:a.a.a.a". Somewhat =
more complicated.

3) At intermediate routers: no configuration.

4) In the DNS: the host A has to be configured to publish the address a.a.a=
.a, in both cases.

>From an administrative point of view, it seems that the two solutions are a=
lmost equivalent, with a slightly lesser burden for the stateful scenario. =
The specification of the stateful is simpler, because it does not require a=
ny fancy addressing format, and can use whatever host ID structure is used =
in host A's subnet. In particular, A can use SEND.

-- Christian Huitema




From huitema@microsoft.com  Thu Sep 17 22:29:13 2009
Return-Path: <huitema@microsoft.com>
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 2A58A3A6A4E for <behave@core3.amsl.com>; Thu, 17 Sep 2009 22:29:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.564
X-Spam-Level: 
X-Spam-Status: No, score=-10.564 tagged_above=-999 required=5 tests=[AWL=0.035, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: 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-xn4vPwSeO3 for <behave@core3.amsl.com>; Thu, 17 Sep 2009 22:29:11 -0700 (PDT)
Received: from smtp.microsoft.com (mailb.microsoft.com [131.107.115.215]) by core3.amsl.com (Postfix) with ESMTP id 9DB3D3A6801 for <behave@ietf.org>; Thu, 17 Sep 2009 22:29:11 -0700 (PDT)
Received: from TK5EX14MLTC104.redmond.corp.microsoft.com (157.54.79.159) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.176.0; Thu, 17 Sep 2009 22:30:00 -0700
Received: from TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com (157.54.71.68) by TK5EX14MLTC104.redmond.corp.microsoft.com (157.54.79.159) with Microsoft SMTP Server id 14.0.639.20; Thu, 17 Sep 2009 22:29:59 -0700
Received: from TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com ([169.254.3.19]) by TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.68]) with mapi; Thu, 17 Sep 2009 22:29:59 -0700
From: Christian Huitema <huitema@microsoft.com>
To: Dan Wing <dwing@cisco.com>
Thread-Topic: [BEHAVE] Security implications of protocol translation
Thread-Index: AQHKNckZMF3GDtqt2kuK6ErD8Y/t95DXsFRQgAB6jICAAP69gIAAD6twgAE+QoD//8N50IABjcVggAADXDCAAAajsA==
Date: Fri, 18 Sep 2009 05:29:53 +0000
Message-ID: <6B55F0F93C3E9D45AF283313B8D342BA20F5E95A@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
References: <4AA7730F.6040602@cernet.edu.cn><36ba02b00909141038i1611b5d6ide4fd96157ed2bc8@mail.gmail.com><6B55F0F93C3E9D45AF283313B8D342BA20F54E47@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com><4AAF2C06.2020107@it.uc3m.es><6B55F0F93C3E9D45AF283313B8D342BA20F557D0@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com><4AAFA425.7040706@it.uc3m.es> <4AB079D5.1010404@cernet.edu.cn><6B55F0F93C3E9D45AF283313B8D342BA20F5A151@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com><4AB191F3.9040305@cernet.edu.cn> <6B55F0F93C3E9D45AF283313B8D342BA20F5C240@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <028301ca381a$bcc47fe0$5da36b80@cisco.com> <6B55F0F93C3E9D45AF283313B8D342BA20F5E923@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <6B55F0F93C3E9D45AF283313B8D342BA20F5E923@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: 'Behave WG' <behave@ietf.org>, 'Xing Li' <xing@cernet.edu.cn>
Subject: Re: [BEHAVE] Security implications of protocol translation
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/mail-archive/web/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>
X-List-Received-Date: Fri, 18 Sep 2009 05:29:13 -0000

> Now, lets compare the amount of administrative overhead and routing
> overhead:
>=20
> 1) At the translator: In the stateless case, the NAT is programmed to
> map "a.a.a.a" to "<ISP-Prefix>:<SubnetA>:<MagicA>:a.a.a.a"; In the
> stateful case, the NAT is programmed to map "a.a.a.a" to "<ISP-
> Prefix>:<SubnetA>:<HostID-A>". Basically the same cost.
>=20
>=20
> 2) At the host receiving the mapping: In the stateful case, the host
> manages exactly one address, "<ISP-Prefix>:<SubnetA>:<HostID-A>"; In the
> stateless case, the host has to be configured with two addresses, "<ISP-
> Prefix>:<SubnetA>:<HostID-A>" and "<ISP-
> Prefix>:<SubnetA>:<MagicA>:a.a.a.a". Somewhat more complicated.
>=20
> 3) At intermediate routers: no configuration.
>=20
> 4) In the DNS: the host A has to be configured to publish the address
> a.a.a.a, in both cases.
>=20
> From an administrative point of view, it seems that the two solutions
> are almost equivalent, with a slightly lesser burden for the stateful
> scenario. The specification of the stateful is simpler, because it does
> not require any fancy addressing format, and can use whatever host ID
> structure is used in host A's subnet. In particular, A can use SEND.

To be fair, Xing's stateless proposal solves the security burden in a diffe=
rent way. Instead of using "<ISP-Prefix>:<SubnetA>:<MagicA>:a.a.a.a", the m=
apped address would be <ISP-NAT-Prefix>:a.a.a.a:padding. The analysis of co=
nfiguration requirements would be:

1) At the translator: The translator is configured to map all addresses in =
the mapped range (say a.a.a.0/n) to the <ISP-NAT-Prefix>:a.a.a.a:padding. T=
he only required configuration is the range of address. There is no need to=
 configure individual addresses.

2) At the host receiving the mapping: the host has to be configured with tw=
o addresses, "<ISP-
Prefix>:<SubnetA>:<HostID-A>" and "<ISP-NAT-Prefix>:a.a.a.a:padding".=20
=20
3) At intermediate routers: all intermediate routers between host A and the=
 NAT need to install a route pointing the prefix "<ISP-NAT-Prefix>:a.a.a.a:=
:"/n towards the host A. The last hop router, serving the domain to which A=
 is attached, must be configured to relay these packets towards "<ISP-
Prefix>:<SubnetA>:<HostID-A>". All intermediate routers must implement some=
 form of egress filtering, to prevent spoofing of packets by the local NAT.

4) In the DNS: the host A has to be configured to publish the address a.a.a=
.a, in both cases.

This particular "stateless" solution does require a lesser administrative c=
ost in the NAT. However, there is a tradeoff. The administrative cost in th=
e intermediate routers is much higher. The solution trades a centralized ma=
nagement burden, in the NAT, for a distributed management burden, in the in=
termediate routers. I am not sure that this is the right tradeoff.

-- Christian Huitema




From marcelo@it.uc3m.es  Thu Sep 17 22:44:03 2009
Return-Path: <marcelo@it.uc3m.es>
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 F380F28C13D for <behave@core3.amsl.com>; Thu, 17 Sep 2009 22:44:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.526
X-Spam-Level: 
X-Spam-Status: No, score=-6.526 tagged_above=-999 required=5 tests=[AWL=0.073,  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 6whVVG90pLWV for <behave@core3.amsl.com>; Thu, 17 Sep 2009 22:44:01 -0700 (PDT)
Received: from smtp03.uc3m.es (smtp03.uc3m.es [163.117.176.133]) by core3.amsl.com (Postfix) with ESMTP id DAB5D3A6A80 for <behave@ietf.org>; Thu, 17 Sep 2009 22:44:00 -0700 (PDT)
Received: from marcelo-bagnulos-macbook-pro.local (29.pool85-53-129.dynamic.orange.es [85.53.129.29]) by smtp03.uc3m.es (Postfix) with ESMTP id B9B1A7F05A6; Fri, 18 Sep 2009 07:44:37 +0200 (CEST)
Message-ID: <4AB31E3D.7030207@it.uc3m.es>
Date: Fri, 18 Sep 2009 07:44:29 +0200
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Dan Wing <dwing@cisco.com>
References: <4AA7730F.6040602@cernet.edu.cn><36ba02b00909141038i1611b5d6ide4fd96157ed2bc8@mail.gmail.com><6B55F0F93C3E9D45AF283313B8D342BA20F54E47@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com><4AAF2C06.2020107@it.uc3m.es><6B55F0F93C3E9D45AF283313B8D342BA20F557D0@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com><4AAFA425.7040706@it.uc3m.es>	<4AB079D5.1010404@cernet.edu.cn><6B55F0F93C3E9D45AF283313B8D342BA20F5A151@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com><4AB191F3.9040305@cernet.edu.cn>	<6B55F0F93C3E9D45AF283313B8D342BA20F5C240@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <028301ca381a$bcc47fe0$5da36b80@cisco.com>
In-Reply-To: <028301ca381a$bcc47fe0$5da36b80@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-TM-AS-Product-Ver: IMSS-7.0.0.3116-5.6.0.1016-16894.003
Cc: 'Xing Li' <xing@cernet.edu.cn>, 'Behave WG' <behave@ietf.org>
Subject: Re: [BEHAVE] Security implications of protocol translation
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/mail-archive/web/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>
X-List-Received-Date: Fri, 18 Sep 2009 05:44:03 -0000

Dan Wing escribió:
>  
>
>   
>> -----Original Message-----
>> From: behave-bounces@ietf.org 
>> [mailto:behave-bounces@ietf.org] On Behalf Of Christian Huitema
>> Sent: Wednesday, September 16, 2009 10:10 PM
>> To: Xing Li
>> Cc: Behave WG
>> Subject: Re: [BEHAVE] Security implications of protocol translation
>>
>>     
>>>> If that is the case, if translatable addresses only 
>>>>         
>> differ from the
>>     
>>> regular addresses by the structure of the host identifier, 
>>>       
>> how does the
>>     
>>> translator verify that customer A is not attempting to use an IPv4
>>> address assigned to customer B?
>>>       
>>> how about configure uRPF in the stateless translator?  Xing
>>>       
>> uRPF is a form of ingress filtering. Of course you should 
>> enable that. But it is not sufficient. 
>>
>> Suppose that customer A has an IPv6 translatable address of 
>> the form: <ISP-prefix>:<SubnetA>:<MagicA>:a.a.a.a, where 
>> a.a.a.a is the IPv4 address assigned by the ISP to A and 
>> "magicA" is the special sauce that distinguishes translatable 
>> addresses and enables checksum neutrality. Customer B 
>> normally uses addresses of the form 
>> <ISP-prefix>:<SubnetB>:<host-ID>. One of the hosts at 
>> customer B's site configures a host ID of the form 
>> <MagicB>:a.a.a.a -- using the appropriate magic, e.g. to 
>> match checksums. 
>>
>> Customer B can send spoofed packets with the source address 
>> <ISP-prefix>:<SubnetB>:<MagicB>:a.a.a.a. These packets will 
>> be considered valid by egress filtering and uRPF checks, 
>> because they do indeed come from the right path for 
>> <ISP-prefix>:<SubnetB>. Will the translator forward these 
>> packets as originating from address <a.a.a.a>? If not, how 
>> does the translator decide that the packets from B are 
>> erroneous? What information does it use?
>>     
>
> I understand what you're describing now.  Thanks.
>
> The translator would need to validate the incoming packet
> by examing the a.a.a.a address and deciding if the
> <ISP-prefix>:<SubnetB> is correct.  The translator can
> validate it by using its same algorithm for IPv4-to-
> IPv6 packets; if the translator receives an IPv4 packet
> with IPv4 address a.a.a.a, it will algorithmically
> prepend <ISP-Prefix>:<SubnetA>:<MagicB> to it.  The
> translator can notice that the arriving packet has
> a different subnet, and drop it.  This is akin to the
> translator doing a uRPF check on the source address
> of the IPv6 packet:  "would I send an IPv4 packet
> to this same IPv6 destination".
>   

the translator would then be less "stateless" since it has to have a 
binding between IPv4 address and IPv6 prefix which i understnad must be 
manually configured

Regards, marcelo

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


From eric.burgey@orange-ftgroup.com  Fri Sep 18 07:33:35 2009
Return-Path: <eric.burgey@orange-ftgroup.com>
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 6B1F628C153; Fri, 18 Sep 2009 07:33:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.949
X-Spam-Level: 
X-Spam-Status: No, score=-2.949 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_13=0.6, 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 vqz4tfPGZVUG; Fri, 18 Sep 2009 07:33:34 -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 E96533A67AD; Fri, 18 Sep 2009 07:33:32 -0700 (PDT)
Received: from ftrdmel0.rd.francetelecom.fr ([10.192.128.56]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 18 Sep 2009 16:34:00 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 18 Sep 2009 16:33:58 +0200
Message-ID: <08BA2C59E081884DB2AAE4A0BE9D6DC162A3BE@ftrdmel0.rd.francetelecom.fr>
In-Reply-To: <12F4112206976147A34FEC0277597CCF27A402C663@XCH-NW-15V.nw.nos.boeing.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BEHAVE] [Softwires] Some Thought about the AutomaticTunnelAddress
Thread-Index: Aco3coauTE1fkrVPRrG72UVQD5MnuAAMFF4wAAYPB4AAKyOw0A==
References: <002601ca3745$63c8b710$d40c6f0a@china.huawei.com> <57F95EAE-6705-4B8E-849F-3F35D7239EDD@free.fr> <08BA2C59E081884DB2AAE4A0BE9D6DC1629F33@ftrdmel0.rd.francetelecom.fr> <12F4112206976147A34FEC0277597CCF27A402C663@XCH-NW-15V.nw.nos.boeing.com>
From: <eric.burgey@orange-ftgroup.com>
To: <Fred.L.Templin@boeing.com>
X-OriginalArrivalTime: 18 Sep 2009 14:34:00.0602 (UTC) FILETIME=[101717A0:01CA386D]
Cc: softwires@ietf.org, behave@ietf.org, xuxh@huawei.com
Subject: Re: [BEHAVE] [Softwires] Some Thought about the AutomaticTunnelAddress
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/mail-archive/web/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>
X-List-Received-Date: Fri, 18 Sep 2009 14:33:35 -0000

Thanks Fred,

Thanks Fred,
You are right it is difficult to protect tunnelling mechanism against =
spoofing attacks without ip-proto-41 and ingress filtering in site =
border router.
A major enterprise or an ISP may use more than one single ISATAP link.=20

But the point is, as you have written in chapter 4 of RFC 5214 ,
>"The domain of applicability for this technical specification is =
automatic >tunneling of IPv6 packets in IPv4 for ISATAP nodes within =
sites that >observe the security considerations found in this document, =
including host->to-router, router-to-host, and host-to-host automatic =
tunneling in certain >enterprise networks and 3GPP/3GPP2 wireless =
operator networks.  (Other >scenarios with a sufficient trust basis =
ensured by the mechanisms specified >in this document also fall   within =
this domain of applicability.)",
Automatic tunnelling must be limited to a "Site".

Even if I have not found a precise definition of a "Site" IMHO it means =
that there is an organisation able to create the trust inside the =
"Site". Such organisation is able to know all IPv4 addresses allocated =
to ISATAP router or all 6 to 4 router used to interconnect this site =
with internet and to prohibit automatic tunnelling between 2 ISATAP =
routers inside the "Site" or between an ISATAP router and 6 to 4 router =
inside the "Site".
So if these ISATAP-ISATAP or ISATAP-6_to_4 tunnels are prohibited inside =
the "Site", and if the automatic tunnelling process is limited to =
intra-site tunnels, I don't see how the loop described in REMI DESPRES =
mail can be closed in the IPv4 domain.


	Eric BURGEY

-----Message d'origine-----
De=A0: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]=20
Envoy=E9=A0: jeudi 17 septembre 2009 19:26
=C0=A0: BURGEY Eric RD-CORE-ISS; remi.despres@free.fr; xuxh@huawei.com
Cc=A0: softwires@ietf.org; behave@ietf.org
Objet=A0: RE: [BEHAVE] [Softwires] Some Thought about the =
AutomaticTunnelAddress

Eric,

The point is that ISATAP can be used with public IPv4
addresses (in which case the IPv6 address is constructed
as: "FOO::0200:5EFE:V4ADDR") and there is no guarantee
in that case that the ISATAP router is located behind an
ip-proto-41 nor ingress-filtering site border router. Plus,
I know of at least one major enterprise network that uses
public IPv4 addresses internally, and the network is much
too large to be covered by a single ISATAP link.

This discussion should probably by synchronized with the
one taking place on the v6ops, 6man and secdir lists.

Fred
fred.l.templin@boeing.com

> -----Original Message-----
> From: eric.burgey@orange-ftgroup.com =
[mailto:eric.burgey@orange-ftgroup.com]
> Sent: Thursday, September 17, 2009 7:45 AM
> To: remi.despres@free.fr; xuxh@huawei.com
> Cc: softwires@ietf.org; Templin, Fred L; behave@ietf.org
> Subject: RE: [BEHAVE] [Softwires] Some Thought about the =
AutomaticTunnelAddress
>=20
> Hello,
> Xu Xiaohu comment is right but probably be too much restrictive.
> Excluding all public IPv4 addresses is too strict and not enough =
because it does not excludes 6 to 4
> gateways between the local private network and the IPv6 network with a =
private IPv4 address.
>=20
> ISATAP use an IPv6 operator prefix instead of a well known prefix, so =
it means that ISATAP is built
> to ensure IPv6 connectivity of IPv4 Islands inside an IPv6 network =
managed by a specific operator.
> So the encapsulation of IPv6 packet into IPv4 done by the gateway must =
be restricted to IPv4
> destination addresses managed by this operator (the ISATAP equipment =
operator) excluding all IPv4
> addresses managed by this operator and allocated to ISATAP, 6 to 4 =
gateway or any other gateway
> between the IPv4 network and the IPv6 network like for example IVI-T =
gateways.
>=20
>=20
> This limitation can be implemented through an access list in the =
ISATAP gateway, in IVI-T gateways or
> in any other gateway between the IPv4 network and the IPv6 network =
doing encapsulation of IPv6
> packet, with a prefix allocated to an operator, in IPv4 packet.
>=20
>=20
> 	Eric BURGEY
>=20
> -----Message d'origine-----
> De=A0: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] De la =
part de R=E9mi Despr=E9s
> Envoy=E9=A0: jeudi 17 septembre 2009 10:40
> =C0=A0: Xu Xiaohu
> Cc=A0: softwires@ietf.org; 'Templin, Fred L'; 'Behave WG'
> Objet=A0: Re: [BEHAVE] [Softwires] Some Thought about the =
AutomaticTunnelAddress
>=20
>=20
> Xu,
>=20
> Thanks for you answer.
> Further comment below.
>=20
>=20
> Le 17 sept. 09 =E0 05:17, Xu Xiaohu a =E9crit :
>=20
> > In your msg
> > (http://www.ietf.org/mail-archive/web/behave/current/
> > msg06816.html), you
> > said "... Suffice it to say that a 6to4 relay router may need, to
> > be safe,
> > to look at IPv4 addresses that are embedded in ISATAP IPv6
> > addresses. In the
> > above example, if the 6to4 relay router sees that the IPv4 embedded
> > address
> > in the IPv6 destination is its own IPv4 address 192.88.99.1, it can
> > discard
> > the packet and thus prevent the loop". However, I feel this is not
> > a good
> > idea for a 6to4 router to check the ISATAP address. In fact, the
> > routing-loop attack can be easily avoided by using a private IPv4
> > address,
> > rather that a public IPv4 address as the ISATAP tunnel endpoint
> > address on
> > the ISATAP router.
>=20
> If the IPv4 address of an ISATAP router is private, the attack
> scenario  below doesn't exists, YES.
>=20
> But 5214 says in its introduction that "ISATAP enables automatic
> tunneling whether global or private IPv4 addresses are used".
> To prevent all routing-loop attacks, 6to4 relay routers should
> therefore also deal with ISATAP routers that have global IPv4 =
addresses.
>=20
> As a matter of facts, ISATAP can be useful with a global IPv4 address
> in a large private network that has enough global IPv4 addresses to
> use them internally: this provides IPv6 connectivity to dual-stack
> hosts that support ISATAP (e.g. with Windows or Linux AKAIK).
>=20
>=20
> > Hence, I don't think the routing-loop attack prevention is a
> > justification
> > for the "IID-format constraint".
>=20
> I also wish it would not have been a justification, but for the
> reason above I believe it is one we have to live with :-(.
>=20
> Did I miss anything?
>=20
> Regards,
> RD
>=20
>=20
>=20
> > For a brief illustration of one instance of the the attack, here is =
an
> > example:
> >
> > +-------------------------------------------------------+
> > | IPv6                   IPv6 packet                    |
> > |Internet        dst6:  2002:198.16.9.9::1              |
> > |                src6:  2001:db8:1::200:5efe:192.88.99.1|
> > |                                           |           |
> > |                                           V           |
> > |          .--------------->--------------. |           |
> > |         /                                \|           |
> > +--------+----------------------------------+-----------+
> >          |                                  |
> >   2001:db8:1::/48                       2002::/16
> >     +---------+                        +---------+
> >     | ISATAP  |                        |  6to4   |
> >     +---------+                        +---------+
> >     198.16.9.9                         192.88.99.1
> >          |                                  |
> > +--------+---------+                        |
> > | IPv4   ^         |                        |
> > | site   ^         |                        |
> > |        ^         |                        V
> > |        ^         |                        |
> > +--------+---------+                        |
> >     198.16.9.0/24                           |
> >          |                                  |
> >          |                                  |
> > +--------+----------------------------------+-----------+
> > | IPv4    \                                /            |
> > |internet  '----------------<-------------'             |
> > |                 IPv6 in IPv4 packet                   |
> > |                  dst4: 198.16.9.9                     |
> > |                  src4: 192.88.99.1                    |
> > |                                                       |
> > +--------+----------------------------------+-----------+
> >
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave

From Gurpreet.Virdi@microsoft.com  Thu Sep 17 13:24:27 2009
Return-Path: <Gurpreet.Virdi@microsoft.com>
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 C2D383A67F9 for <behave@core3.amsl.com>; Thu, 17 Sep 2009 13:24:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bizSmhzjNuTl for <behave@core3.amsl.com>; Thu, 17 Sep 2009 13:24:26 -0700 (PDT)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.215]) by core3.amsl.com (Postfix) with ESMTP id 9271C3A6921 for <behave@ietf.org>; Thu, 17 Sep 2009 13:24:26 -0700 (PDT)
Received: from TK5EX14HUBC102.redmond.corp.microsoft.com (157.54.7.154) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.176.0; Thu, 17 Sep 2009 13:25:09 -0700
Received: from TK5EX14MBXC122.redmond.corp.microsoft.com ([169.254.2.64]) by TK5EX14HUBC102.redmond.corp.microsoft.com ([157.54.7.154]) with mapi; Thu, 17 Sep 2009 13:25:09 -0700
From: Gurpreet Virdi <Gurpreet.Virdi@microsoft.com>
To: "teemu.savolainen@nokia.com" <teemu.savolainen@nokia.com>
Thread-Topic: Comments on draft-denis-icmpv6-generation-for-teredo-00
Thread-Index: AcoKOIZyuTOrxeI5S+iI1NyOBmBztwAoFXsAABTsSWAK67NXAAAJaP4QAAKnxIAAATwMwAALPMhg
Date: Thu, 17 Sep 2009 20:25:06 +0000
Message-ID: <21052BD84AD96A4E8749DAA4766A4747096FBED1@TK5EX14MBXC122.redmond.corp.microsoft.com>
References: <E4561B14EE2A3E4E9D478EBFB5416E1B1CC7A902@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com> <21052BD84AD96A4E8749DAA4766A4747096F99DF@TK5EX14MBXC122.redmond.corp.microsoft.com> <E4561B14EE2A3E4E9D478EBFB5416E1B1CC7AE58@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <E4561B14EE2A3E4E9D478EBFB5416E1B1CC7AE58@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Fri, 18 Sep 2009 09:04:51 -0700
Cc: Ali Turkoglu <alitu@microsoft.com>, "behave@ietf.org" <behave@ietf.org>, Dave Thaler <dthaler@microsoft.com>
Subject: Re: [BEHAVE] Comments on draft-denis-icmpv6-generation-for-teredo-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/mail-archive/web/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>
X-List-Received-Date: Thu, 17 Sep 2009 20:26:14 -0000

Hi Teemu,

I am part of the Teredo team at Microsoft and I had some comments about #1,=
 #2, #3 and #4 points you mention below. Here are my comments:

#1: The draft now says "Furthermore, the IPv6 firewall might not be on the =
return data path in which case generated ICMPv6 Echo Replies might break Te=
redo host-based relay feature.". This might seem a little confusing. See in=
 both the host-based relay features and non-host-based relay feature....the=
 firewall might be on the return data path. The difference is that in the h=
ost-based relay feature, the ICMPV6 Echo Reply packet hits the relay *befor=
e* hitting the IPV6 firewall (the host itself is the relay!!!). And in the =
non host-based relay feature, the ICMPV6 Echo Reply packet will hit the rel=
ay after hitting this IPV6 firewall. Hence, the host-based relay feature wi=
ll not work with this draft.

#2: Currently Teredo relay discovery only succeeds when the following condi=
tions are met
A) if the firewall on the peer machine exempts ICMPV6 Echo Request and
B) if the IPV6 address is a valid IPV6 address belonging to a peer machine =
that is up & running.

Now A is not common by default. In windows teredo clients, the time this is=
 most common is when the peer is a host-based relay and I will not talk abo=
ut it in detail, because you have already mentioned it in the draft as bein=
g one of the cases where the IPV6 firewall will not reply to pings.

Now B, requires that the attacker to guess your 128 bit IPV6 address correc=
tly.

But with this draft, Teredo relay discovery will now succeed even if the ab=
ove 2 conditions i.e. A & B are not met. So potentially an attacker could g=
o around sending pings to all sorts of address ranges and ping replies from=
 the IPV6 firewall in front of these machines will help in discovering Tere=
do relays around the world.=20

This can certainly be mitigated by taking measures like: the firewall shoul=
d only respond to ping requests that are destined to actual *active* IPV6 a=
ddresses behind the firewall.

#3: A windows teredo client will today re-do teredo relay discovery every 1=
5 seconds (3 retransmissions) for a non-TCP connection and for a TCP connec=
tion it will redo relay discovery (upto 3 retransmissions) when TCP fails t=
o confirms path reach-ability. If all 3 retransmissions don't end up gettin=
g a ping reply, the connection could potentially break. Hence, we have to b=
e very careful when rate limiting. A way to approach this problem could be =
that instead of rate limiting, if the traffic increases too much, packets s=
hould be forwarded to the end host and let the end host take care of it.

#4: Perhaps we need to collect data on key applications that rely on ping r=
eplies while choosing a destination address. The false positive can absolut=
ely have an adverse effect for example: take a TCP connection which will st=
art on the Teredo address and then fail after x seconds only after which th=
e next address in the list *might* be tried. X seconds might be too long in=
 terms of latency.

Thanks
Gurpreet
=20
> -----Original Message-----
> From: teemu.savolainen@nokia.com [mailto:teemu.savolainen@nokia.com]
> Sent: Wednesday, September 16, 2009 7:53 AM
> To: Dave Thaler
> Cc: behave@ietf.org
> Subject: RE: Comments on draft-denis-icmpv6-generation-for-teredo-00
>=20
> Hi Dave, behave,
>=20
> We've updated this draft based on received feedback:
> http://www.ietf.org/id/draft-denis-icmpv6-generation-for-teredo-01.txt
>=20
> 1) We tried to tackle this by adding more text clarifying reply
> generation MUST only be done if middlebox is certainly on the return
> path and also clarification that host-specific relay function could
> otherwise break.
>=20
> 2) We'd like more clarification on this: how discovery is made easier
> when compared to attacker just sending ICMPv6 Echo Requests to various
> IPv6 peers out there?
>=20
> 3) Yes, but blindly responding might make middlebox act as reflector on
> some attacks - i.e. there should be some sanity in ICMPv6 echo reply
> generation. Then again, this is about the same for any host/server and
> from that point of view useless to have in this document? Therefore we
> are consider dropping that piece of text out.
>=20
> 4) Right, but which one is worse: false negative or false positive
> reply of peer's liveness? The ICMPv6 anyway only tells the peer's lower
> layers are alive, but nothing about application layer stuff.
>=20
> We also added some text on CGA.
>=20
> Best regards,
>=20
> 	Teemu
>=20
> >-----Original Message-----
> >From: ext Dave Thaler [mailto:dthaler@microsoft.com]
> >Sent: 23 July, 2009 03:36
> >To: Denis-Courmont Remi (Nokia-D/Helsinki)
> >Cc: Savolainen Teemu (Nokia-D-MSW/Tampere); Behave WG
> >Subject: RE: Comments on draft-denis-icmpv6-generation-for-teredo-00
> >
> >I forwarded the doc to our Teredo implementers and have some
> >additional feedback from them to pass along.
> >
> >1) The option for "Forced ICMPv6 Echo Reply generation for clients"
> >mentioned in 2.1 is especially problematic in that it breaks
> >the concept of a host-specific relay (a dual-stack host that
> >is acting as a relay for itself).
> >
> >2) A security consideration is that this draft makes discovery
> >of Teredo relays much easier for an attacker, when then makes
> >it easier to mount attacks against them.
> >
> >3) Section 5 talks about rate limiting.  If you rate limit,
> >then you limit the usefulness because communication won't be
> >established.
> >
> >4) There are applications that consider ping replies as an
> >indicator of liveness (e.g., when picking which IP address to
> >use among a set, or whatever else).  Spoofing echo responses
> >will cause such apps to have expected behavior.
> >
> >
> >> -----Original Message-----
> >> From: R=E9mi Denis-Courmont [mailto:remi.denis-courmont@nokia.com]
> >> Sent: Wednesday, July 22, 2009 12:30 AM
> >> To: Dave Thaler
> >> Cc: Savolainen Teemu (Nokia-D-MSW/Tampere); Behave WG
> >> Subject: Re: Comments on draft-denis-icmpv6-generation-for-teredo-00
> >>
> >> On Tuesday 21 July 2009 22:22:02 ext Dave Thaler wrote:
> >> > Section 2.2 talks about translators sending (spoofed) echo replies
> >> > by default. However, if the translator is not guaranteed to be on
> >> > the
> >> reverse
> >> > path, e.g. in the case of multiple stateless translators, this is
> >> > dangerous. At minimum, the SHALL's need to be constrained to cases
> >> where
> >> > the translator is guaranteed to be on the reverse path.
> >>
> >> I don't disagree that a clarification would be good.
> >>
> >> However, I think it depends on how "a" translator is
> >defined. I think
> >> we can all agree that there has to be translation in both
> >paths. Then
> >> it depends whether one thinks of the translator as an abstract whole
> >> system or as a physical box between wires.
> >>
> >> Indeed, if the inbound and outbound boxes are distinct, stateless,
> >> unable to communicate with one another *and* topologically separate,
> >> there is a problem.
> >>
> >> > Section 2.3 states that firewalls SHOULD send (spoofed)
> >echo replies
> >> > to Teredo addresses.  This is again too strong.  If the firewall
> >> > would block incoming unsolicited packets from Teredo clients, then
> >> > it shouldn't send echo replies.  At minimum, the SHOULD
> >needs to be
> >> > constrained to a case where it would actually allow
> >packets through
> >> > from that address.
> >>
> >> Right.
> >>
> >> --
> >> R=E9mi Denis-Courmont
> >> Nokia Devices R&D, Maemo Software, Helsinki
> >>
> >
> >
>=20



From Fred.L.Templin@boeing.com  Fri Sep 18 10:22:10 2009
Return-Path: <Fred.L.Templin@boeing.com>
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 255C83A693F; Fri, 18 Sep 2009 10:22:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.695
X-Spam-Level: 
X-Spam-Status: No, score=-5.695 tagged_above=-999 required=5 tests=[AWL=0.304,  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 Je+GWCZipkjY; Fri, 18 Sep 2009 10:22:08 -0700 (PDT)
Received: from blv-smtpout-01.boeing.com (blv-smtpout-01.boeing.com [130.76.32.69]) by core3.amsl.com (Postfix) with ESMTP id B41A43A6AF6; Fri, 18 Sep 2009 10:22:08 -0700 (PDT)
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6]) by blv-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id n8IHMYfm014366 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 18 Sep 2009 10:22:35 -0700 (PDT)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id n8IHMXXr019627; Fri, 18 Sep 2009 12:22:33 -0500 (CDT)
Received: from XCH-NWHT-03.nw.nos.boeing.com (xch-nwht-03.nw.nos.boeing.com [130.247.71.23]) by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id n8IHMXib019608 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Fri, 18 Sep 2009 12:22:33 -0500 (CDT)
Received: from XCH-NW-15V.nw.nos.boeing.com ([130.247.25.104]) by XCH-NWHT-03.nw.nos.boeing.com ([130.247.71.23]) with mapi; Fri, 18 Sep 2009 10:22:32 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "eric.burgey@orange-ftgroup.com" <eric.burgey@orange-ftgroup.com>
Date: Fri, 18 Sep 2009 10:22:31 -0700
Thread-Topic: [BEHAVE] [Softwires] Some Thought about the AutomaticTunnelAddress
Thread-Index: Aco3coauTE1fkrVPRrG72UVQD5MnuAAMFF4wAAYPB4AAKyOw0AAF4qVQ
Message-ID: <12F4112206976147A34FEC0277597CCF27A4062166@XCH-NW-15V.nw.nos.boeing.com>
References: <002601ca3745$63c8b710$d40c6f0a@china.huawei.com> <57F95EAE-6705-4B8E-849F-3F35D7239EDD@free.fr> <08BA2C59E081884DB2AAE4A0BE9D6DC1629F33@ftrdmel0.rd.francetelecom.fr> <12F4112206976147A34FEC0277597CCF27A402C663@XCH-NW-15V.nw.nos.boeing.com> <08BA2C59E081884DB2AAE4A0BE9D6DC162A3BE@ftrdmel0.rd.francetelecom.fr>
In-Reply-To: <08BA2C59E081884DB2AAE4A0BE9D6DC162A3BE@ftrdmel0.rd.francetelecom.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "softwires@ietf.org" <softwires@ietf.org>, "behave@ietf.org" <behave@ietf.org>, "xuxh@huawei.com" <xuxh@huawei.com>
Subject: Re: [BEHAVE] [Softwires] Some Thought about the AutomaticTunnelAddress
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/mail-archive/web/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>
X-List-Received-Date: Fri, 18 Sep 2009 17:22:10 -0000

Hi Eric,

> -----Original Message-----
> From: eric.burgey@orange-ftgroup.com [mailto:eric.burgey@orange-ftgroup.c=
om]
> Sent: Friday, September 18, 2009 7:34 AM
> To: Templin, Fred L
> Cc: softwires@ietf.org; behave@ietf.org; remi.despres@free.fr; xuxh@huawe=
i.com
> Subject: RE: [BEHAVE] [Softwires] Some Thought about the AutomaticTunnelA=
ddress
>=20
> Thanks Fred,
>=20
> Thanks Fred,
> You are right it is difficult to protect tunnelling mechanism against spo=
ofing attacks without ip-
> proto-41 and ingress filtering in site border router.
> A major enterprise or an ISP may use more than one single ISATAP link.

OK.

> But the point is, as you have written in chapter 4 of RFC 5214 ,
> >"The domain of applicability for this technical specification is automat=
ic >tunneling of IPv6
> packets in IPv4 for ISATAP nodes within sites that >observe the security =
considerations found in this
> document, including host->to-router, router-to-host, and host-to-host aut=
omatic tunneling in certain
> >enterprise networks and 3GPP/3GPP2 wireless operator networks.  (Other >=
scenarios with a sufficient
> trust basis ensured by the mechanisms specified >in this document also fa=
ll   within this domain of
> applicability.)",
> Automatic tunnelling must be limited to a "Site".

The statement beginning: "Other scenarios with a sufficient
trust basis..." is the one to consider when the "site" we
are considering is the public Internet itself. The check
for '*::0200:5EFE:V4ADDR' updates this statement.

> Even if I have not found a precise definition of a "Site" IMHO it means t=
hat there is an organisation
> able to create the trust inside the "Site".

The "organization" in this case is the IANA that delegated
the public IPv4 addresses, along with the collective
administrative authorities of all BGP routers in the DFZ.
=20
> Such organisation is able to know all IPv4 addresses
> allocated to ISATAP router or all 6 to 4 router used to interconnect this=
 site with internet and to
> prohibit automatic tunnelling between 2 ISATAP routers inside the "Site" =
or between an ISATAP router
> and 6 to 4 router inside the "Site".

In some sites, configuring ISATAP/6to4 routers with a list of
all other ISATAP/6to4 routers - and then using that list for
filtering purposes - might not scale well. This is definitely
true for the case of the public Internet as a "site", and
probably also true for many large enterprises.
=20
> So if these ISATAP-ISATAP or ISATAP-6_to_4 tunnels are prohibited inside =
the "Site", and if the
> automatic tunnelling process is limited to intra-site tunnels, I don't se=
e how the loop described in
> REMI DESPRES mail can be closed in the IPv4 domain.

As above, populating a list of all IPv4 addresses of
ISATAP/6to4 routers on each router might not scale well
in many environments. So, a simple solution is to use
the ISATAP router neighbor cache to avoid looping. In
particular, an ISATAP router *with a coherent neighbor
cache* should only accept/send a tunneled packet with
dst/src address other than FE80::* IFF the tunnel far
end is a known neighbor.

Within enterprise networks protected by site border
routers there are two ways to ensure a coherent neighbor
cache: 1) administrative assurance that no IPv4 spoofing
is possible within the enterprise, or 2) secure neighbor
discovery. Within the global Internet as a site, we can
rely on neither of these and have only the
'*::0200:5EFE:V4ADDR' check as protection.

You should probably also have a look at the thread titled:
"routing loop attacks using IPv6 tunnels" in the v6ops and
6man lists.

Fred
fred.l.templin@boeing.com

> 	Eric BURGEY
>=20
> -----Message d'origine-----
> De=A0: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]
> Envoy=E9=A0: jeudi 17 septembre 2009 19:26
> =C0=A0: BURGEY Eric RD-CORE-ISS; remi.despres@free.fr; xuxh@huawei.com
> Cc=A0: softwires@ietf.org; behave@ietf.org
> Objet=A0: RE: [BEHAVE] [Softwires] Some Thought about the AutomaticTunnel=
Address
>=20
> Eric,
>=20
> The point is that ISATAP can be used with public IPv4
> addresses (in which case the IPv6 address is constructed
> as: "FOO::0200:5EFE:V4ADDR") and there is no guarantee
> in that case that the ISATAP router is located behind an
> ip-proto-41 nor ingress-filtering site border router. Plus,
> I know of at least one major enterprise network that uses
> public IPv4 addresses internally, and the network is much
> too large to be covered by a single ISATAP link.
>=20
> This discussion should probably by synchronized with the
> one taking place on the v6ops, 6man and secdir lists.
>=20
> Fred
> fred.l.templin@boeing.com
>=20
> > -----Original Message-----
> > From: eric.burgey@orange-ftgroup.com [mailto:eric.burgey@orange-ftgroup=
.com]
> > Sent: Thursday, September 17, 2009 7:45 AM
> > To: remi.despres@free.fr; xuxh@huawei.com
> > Cc: softwires@ietf.org; Templin, Fred L; behave@ietf.org
> > Subject: RE: [BEHAVE] [Softwires] Some Thought about the AutomaticTunne=
lAddress
> >
> > Hello,
> > Xu Xiaohu comment is right but probably be too much restrictive.
> > Excluding all public IPv4 addresses is too strict and not enough becaus=
e it does not excludes 6 to
> 4
> > gateways between the local private network and the IPv6 network with a =
private IPv4 address.
> >
> > ISATAP use an IPv6 operator prefix instead of a well known prefix, so i=
t means that ISATAP is built
> > to ensure IPv6 connectivity of IPv4 Islands inside an IPv6 network mana=
ged by a specific operator.
> > So the encapsulation of IPv6 packet into IPv4 done by the gateway must =
be restricted to IPv4
> > destination addresses managed by this operator (the ISATAP equipment op=
erator) excluding all IPv4
> > addresses managed by this operator and allocated to ISATAP, 6 to 4 gate=
way or any other gateway
> > between the IPv4 network and the IPv6 network like for example IVI-T ga=
teways.
> >
> >
> > This limitation can be implemented through an access list in the ISATAP=
 gateway, in IVI-T gateways
> or
> > in any other gateway between the IPv4 network and the IPv6 network doin=
g encapsulation of IPv6
> > packet, with a prefix allocated to an operator, in IPv4 packet.
> >
> >
> > 	Eric BURGEY
> >
> > -----Message d'origine-----
> > De=A0: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] De la p=
art de R=E9mi Despr=E9s
> > Envoy=E9=A0: jeudi 17 septembre 2009 10:40
> > =C0=A0: Xu Xiaohu
> > Cc=A0: softwires@ietf.org; 'Templin, Fred L'; 'Behave WG'
> > Objet=A0: Re: [BEHAVE] [Softwires] Some Thought about the AutomaticTunn=
elAddress
> >
> >
> > Xu,
> >
> > Thanks for you answer.
> > Further comment below.
> >
> >
> > Le 17 sept. 09 =E0 05:17, Xu Xiaohu a =E9crit :
> >
> > > In your msg
> > > (http://www.ietf.org/mail-archive/web/behave/current/
> > > msg06816.html), you
> > > said "... Suffice it to say that a 6to4 relay router may need, to
> > > be safe,
> > > to look at IPv4 addresses that are embedded in ISATAP IPv6
> > > addresses. In the
> > > above example, if the 6to4 relay router sees that the IPv4 embedded
> > > address
> > > in the IPv6 destination is its own IPv4 address 192.88.99.1, it can
> > > discard
> > > the packet and thus prevent the loop". However, I feel this is not
> > > a good
> > > idea for a 6to4 router to check the ISATAP address. In fact, the
> > > routing-loop attack can be easily avoided by using a private IPv4
> > > address,
> > > rather that a public IPv4 address as the ISATAP tunnel endpoint
> > > address on
> > > the ISATAP router.
> >
> > If the IPv4 address of an ISATAP router is private, the attack
> > scenario  below doesn't exists, YES.
> >
> > But 5214 says in its introduction that "ISATAP enables automatic
> > tunneling whether global or private IPv4 addresses are used".
> > To prevent all routing-loop attacks, 6to4 relay routers should
> > therefore also deal with ISATAP routers that have global IPv4 addresses=
.
> >
> > As a matter of facts, ISATAP can be useful with a global IPv4 address
> > in a large private network that has enough global IPv4 addresses to
> > use them internally: this provides IPv6 connectivity to dual-stack
> > hosts that support ISATAP (e.g. with Windows or Linux AKAIK).
> >
> >
> > > Hence, I don't think the routing-loop attack prevention is a
> > > justification
> > > for the "IID-format constraint".
> >
> > I also wish it would not have been a justification, but for the
> > reason above I believe it is one we have to live with :-(.
> >
> > Did I miss anything?
> >
> > Regards,
> > RD
> >
> >
> >
> > > For a brief illustration of one instance of the the attack, here is a=
n
> > > example:
> > >
> > > +-------------------------------------------------------+
> > > | IPv6                   IPv6 packet                    |
> > > |Internet        dst6:  2002:198.16.9.9::1              |
> > > |                src6:  2001:db8:1::200:5efe:192.88.99.1|
> > > |                                           |           |
> > > |                                           V           |
> > > |          .--------------->--------------. |           |
> > > |         /                                \|           |
> > > +--------+----------------------------------+-----------+
> > >          |                                  |
> > >   2001:db8:1::/48                       2002::/16
> > >     +---------+                        +---------+
> > >     | ISATAP  |                        |  6to4   |
> > >     +---------+                        +---------+
> > >     198.16.9.9                         192.88.99.1
> > >          |                                  |
> > > +--------+---------+                        |
> > > | IPv4   ^         |                        |
> > > | site   ^         |                        |
> > > |        ^         |                        V
> > > |        ^         |                        |
> > > +--------+---------+                        |
> > >     198.16.9.0/24                           |
> > >          |                                  |
> > >          |                                  |
> > > +--------+----------------------------------+-----------+
> > > | IPv4    \                                /            |
> > > |internet  '----------------<-------------'             |
> > > |                 IPv6 in IPv4 packet                   |
> > > |                  dst4: 198.16.9.9                     |
> > > |                  src4: 192.88.99.1                    |
> > > |                                                       |
> > > +--------+----------------------------------+-----------+
> > >
> > _______________________________________________
> > Behave mailing list
> > Behave@ietf.org
> > https://www.ietf.org/mailman/listinfo/behave

From dwing@cisco.com  Fri Sep 18 11:17:14 2009
Return-Path: <dwing@cisco.com>
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 747D83A6B57 for <behave@core3.amsl.com>; Fri, 18 Sep 2009 11:17:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.513
X-Spam-Level: 
X-Spam-Status: No, score=-6.513 tagged_above=-999 required=5 tests=[AWL=0.086,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HNEMmNnrE-cc for <behave@core3.amsl.com>; Fri, 18 Sep 2009 11:17:13 -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 53FE93A6B58 for <behave@ietf.org>; Fri, 18 Sep 2009 11:17:13 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ap0EAHprs0qrR7PD/2dsb2JhbACKbat9iFABkBgFhBuBXQ
X-IronPort-AV: E=Sophos;i="4.44,410,1249257600"; d="scan'208";a="243897051"
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-1.cisco.com with ESMTP; 18 Sep 2009 18:18:07 +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 n8III7U1025845;  Fri, 18 Sep 2009 11:18:07 -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.14.3) with ESMTP id n8III6j9013225; Fri, 18 Sep 2009 18:18:06 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.3959);  Fri, 18 Sep 2009 11:18:06 -0700
Received: from dwingwxp01 ([10.32.240.198]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 18 Sep 2009 11:18:06 -0700
From: "Dan Wing" <dwing@cisco.com>
To: "'Christian Huitema'" <huitema@microsoft.com>
References: <4AA7730F.6040602@cernet.edu.cn><36ba02b00909141038i1611b5d6ide4fd96157ed2bc8@mail.gmail.com><6B55F0F93C3E9D45AF283313B8D342BA20F54E47@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com><4AAF2C06.2020107@it.uc3m.es><6B55F0F93C3E9D45AF283313B8D342BA20F557D0@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com><4AAFA425.7040706@it.uc3m.es> <4AB079D5.1010404@cernet.edu.cn><6B55F0F93C3E9D45AF283313B8D342BA20F5A151@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com><4AB191F3.9040305@cernet.edu.cn> <6B55F0F93C3E9D45AF283313B8D342BA20F5C240@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <028301ca381a$bcc47fe0$5da36b80@cisco.com> <6B55F0F93C3E9D45AF283313B8D342BA20F5E923@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
Date: Fri, 18 Sep 2009 11:18:05 -0700
Message-ID: <055d01ca388c$5e5caff0$5da36b80@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AQHKNckZMF3GDtqt2kuK6ErD8Y/t95DXsFRQgAB6jICAAP69gIAAD6twgAE+QoD//8N50IABjcVggAADXDCAAMy2gA==
In-Reply-To: <6B55F0F93C3E9D45AF283313B8D342BA20F5E923@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-OriginalArrivalTime: 18 Sep 2009 18:18:06.0421 (UTC) FILETIME=[5E6C4050:01CA388C]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3543; t=1253297887; x=1254161887; 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]=20Security=20implications=20of =20protocol=20translation |Sender:=20; bh=uFltx9do36HNY0sHp7M/pMXzY/OeWCEdKGW7KvDlFgw=; b=pBvXHRIEy+KzCl6FxF+mcGOHWXl0GfKN+zzquNFSsJY4VZhsbjhkoZ/7mk /iEeeeU9duCDsnDIJnEQmUgd/uoUJhf6qGxe9NvP4kppAWKM6PBiWfj2sOt6 ernsdDJ1mh;
Authentication-Results: sj-dkim-3; header.From=dwing@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; ); 
Cc: 'Xing Li' <xing@cernet.edu.cn>, 'Behave WG' <behave@ietf.org>
Subject: Re: [BEHAVE] Security implications of protocol translation
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/mail-archive/web/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>
X-List-Received-Date: Fri, 18 Sep 2009 18:17:14 -0000

 

> -----Original Message-----
> From: Christian Huitema [mailto:huitema@microsoft.com] 
> Sent: Thursday, September 17, 2009 10:15 PM
> To: Dan Wing
> Cc: 'Behave WG'; 'Xing Li'
> Subject: RE: [BEHAVE] Security implications of protocol translation
> 
> > > Customer B can send spoofed packets with the source address
> > > <ISP-prefix>:<SubnetB>:<MagicB>:a.a.a.a. These packets will
> > > be considered valid by egress filtering and uRPF checks,
> > > because they do indeed come from the right path for
> > > <ISP-prefix>:<SubnetB>. Will the translator forward these
> > > packets as originating from address <a.a.a.a>? If not, how
> > > does the translator decide that the packets from B are
> > > erroneous? What information does it use?
> > 
> > I understand what you're describing now.  Thanks.
> > 
> > The translator would need to validate the incoming packet
> > by examing the a.a.a.a address and deciding if the
> > <ISP-prefix>:<SubnetB> is correct.  The translator can
> > validate it by using its same algorithm for IPv4-to-
> > IPv6 packets; if the translator receives an IPv4 packet
> > with IPv4 address a.a.a.a, it will algorithmically
> > prepend <ISP-Prefix>:<SubnetA>:<MagicB> to it.  The
> > translator can notice that the arriving packet has
> > a different subnet, and drop it.  This is akin to the
> > translator doing a uRPF check on the source address
> > of the IPv6 packet:  "would I send an IPv4 packet
> > to this same IPv6 destination".
> 
> Yes, that will work. But lets now compare this stateless 
> option to the alternative, a stateful translator with some 
> configuration. Specifically, suppose a stateful translator 
> that manages a pool of IP addresses, and that is configured 
> to "reserve" some addresses in that pool to specific IPv6 
> hosts. The configuration option would be something like "map 
> a.a.a.a to <ISP-Prefix>:<SubnetA>:<HostId-A>."
> 
> Now, lets compare the amount of administrative overhead and 
> routing overhead:
> 
> 1) At the translator: In the stateless case, the NAT is 
> programmed to map "a.a.a.a" to 
> "<ISP-Prefix>:<SubnetA>:<MagicA>:a.a.a.a"; In the stateful 
> case, the NAT is programmed to map "a.a.a.a" to 
> "<ISP-Prefix>:<SubnetA>:<HostID-A>". Basically the same cost.
> 
> 2) At the host receiving the mapping: In the stateful case, 
> the host manages exactly one address, 
> "<ISP-Prefix>:<SubnetA>:<HostID-A>"; In the stateless case, 
> the host has to be configured with two addresses, 
> "<ISP-Prefix>:<SubnetA>:<HostID-A>" and 
> "<ISP-Prefix>:<SubnetA>:<MagicA>:a.a.a.a". Somewhat more complicated.
> 
> 3) At intermediate routers: no configuration.
> 
> 4) In the DNS: the host A has to be configured to publish the 
> address a.a.a.a, in both cases.
> 
> From an administrative point of view, it seems that the two 
> solutions are almost equivalent, with a slightly lesser 
> burden for the stateful scenario. The specification of the 
> stateful is simpler, because it does not require any fancy 
> addressing format, and can use whatever host ID structure is 
> used in host A's subnet. In particular, A can use SEND.

Makes sense.  Thanks.

One note:  in this email, you appear to be using the term 
'stateful' to mean 'a translator with a configured 
1:1 mapping between an IPv6 address and an IPv4 address'.  
That use of 'stateful' is different from the use of 
'stateful' in draft-ietf-behave-v6v4-xlate-stateful-01.

-d


> -- Christian Huitema
> 
> 
> 


From dwing@cisco.com  Fri Sep 18 11:20:46 2009
Return-Path: <dwing@cisco.com>
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 8462F3A682D for <behave@core3.amsl.com>; Fri, 18 Sep 2009 11:20:46 -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 IWXd7IBudszD for <behave@core3.amsl.com>; Fri, 18 Sep 2009 11:20:45 -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 6CAF33A679C for <behave@ietf.org>; Fri, 18 Sep 2009 11:20:45 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ap0EAGpss0qrR7PE/2dsb2JhbACKbat4iFABkBgFhBuBXQ
X-IronPort-AV: E=Sophos;i="4.44,410,1249257600"; d="scan'208";a="43571140"
Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-4.cisco.com with ESMTP; 18 Sep 2009 18:21:25 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id n8IILOSe016867;  Fri, 18 Sep 2009 11:21:24 -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.14.3) with ESMTP id n8IILOFs014474; Fri, 18 Sep 2009 18:21:24 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 18 Sep 2009 11:21:24 -0700
Received: from dwingwxp01 ([10.32.240.198]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 18 Sep 2009 11:21:28 -0700
From: "Dan Wing" <dwing@cisco.com>
To: "'Christian Huitema'" <huitema@microsoft.com>
References: <4AA7730F.6040602@cernet.edu.cn><36ba02b00909141038i1611b5d6ide4fd96157ed2bc8@mail.gmail.com><6B55F0F93C3E9D45AF283313B8D342BA20F54E47@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com><4AAF2C06.2020107@it.uc3m.es><6B55F0F93C3E9D45AF283313B8D342BA20F557D0@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com><4AAFA425.7040706@it.uc3m.es><4AB079D5.1010404@cernet.edu.cn><6B55F0F93C3E9D45AF283313B8D342BA20F5A151@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com><4AB191F3.9040305@cernet.edu.cn><6B55F0F93C3E9D45AF283313B8D342BA20F5C240@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com><028301ca381a$bcc47fe0$5da36b80@cisco.com> <6B55F0F93C3E9D45AF283313B8D342BA20F5E923@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <6B55F0F93C3E9D45AF283313B8D342BA20F5E95A@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
Date: Fri, 18 Sep 2009 11:21:15 -0700
Message-ID: <056401ca388c$d0c1d020$5da36b80@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AQHKNckZMF3GDtqt2kuK6ErD8Y/t95DXsFRQgAB6jICAAP69gIAAD6twgAE+QoD//8N50IABjcVggAADXDCAAAajsIAA2hog
In-Reply-To: <6B55F0F93C3E9D45AF283313B8D342BA20F5E95A@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-OriginalArrivalTime: 18 Sep 2009 18:21:28.0554 (UTC) FILETIME=[D6E74CA0:01CA388C]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3792; t=1253298084; x=1254162084; 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]=20Security=20implications=20of =20protocol=20translation |Sender:=20; bh=rQ+Dlx8P/74yWiCb+kq9YL+gcEnV4Oo7PhYg+n3u5cU=; b=fIORtjfFsNBPAOpGlP6T/HOGWcRakw31OA9SI8KDW+ptGX9wr+GTGjcHIc pawVPgr4U/p1G2WsMJLMOAh62w6zeWOOThksL/USaxIU55fB31lcp2PfRWHE jHCVPCYDqr;
Authentication-Results: sj-dkim-4; header.From=dwing@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; ); 
Cc: 'Behave WG' <behave@ietf.org>, 'Xing Li' <xing@cernet.edu.cn>
Subject: Re: [BEHAVE] Security implications of protocol translation
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/mail-archive/web/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>
X-List-Received-Date: Fri, 18 Sep 2009 18:20:46 -0000

 

> -----Original Message-----
> From: Christian Huitema [mailto:huitema@microsoft.com] 
> Sent: Thursday, September 17, 2009 10:30 PM
> To: Dan Wing
> Cc: 'Xing Li'; 'Behave WG'
> Subject: RE: [BEHAVE] Security implications of protocol translation
> 
> > Now, lets compare the amount of administrative overhead and routing
> > overhead:
> > 
> > 1) At the translator: In the stateless case, the NAT is 
> programmed to
> > map "a.a.a.a" to "<ISP-Prefix>:<SubnetA>:<MagicA>:a.a.a.a"; In the
> > stateful case, the NAT is programmed to map "a.a.a.a" to "<ISP-
> > Prefix>:<SubnetA>:<HostID-A>". Basically the same cost.
> > 
> > 
> > 2) At the host receiving the mapping: In the stateful case, the host
> > manages exactly one address, 
> "<ISP-Prefix>:<SubnetA>:<HostID-A>"; In the
> > stateless case, the host has to be configured with two 
> addresses, "<ISP-
> > Prefix>:<SubnetA>:<HostID-A>" and "<ISP-
> > Prefix>:<SubnetA>:<MagicA>:a.a.a.a". Somewhat more complicated.
> > 
> > 3) At intermediate routers: no configuration.
> > 
> > 4) In the DNS: the host A has to be configured to publish 
> the address
> > a.a.a.a, in both cases.
> > 
> > From an administrative point of view, it seems that the two 
> solutions
> > are almost equivalent, with a slightly lesser burden for 
> the stateful
> > scenario. The specification of the stateful is simpler, 
> because it does
> > not require any fancy addressing format, and can use 
> whatever host ID
> > structure is used in host A's subnet. In particular, A can use SEND.
> 
> To be fair, Xing's stateless proposal solves the security 
> burden in a different way. Instead of using 
> "<ISP-Prefix>:<SubnetA>:<MagicA>:a.a.a.a", the mapped address 
> would be <ISP-NAT-Prefix>:a.a.a.a:padding. The analysis of 
> configuration requirements would be:
> 
> 1) At the translator: The translator is configured to map all 
> addresses in the mapped range (say a.a.a.0/n) to the 
> <ISP-NAT-Prefix>:a.a.a.a:padding. The only required 
> configuration is the range of address. There is no need to 
> configure individual addresses.
> 
> 2) At the host receiving the mapping: the host has to be 
> configured with two addresses, "<ISP-
> Prefix>:<SubnetA>:<HostID-A>" and "<ISP-NAT-Prefix>:a.a.a.a:padding". 
>  
> 3) At intermediate routers: all intermediate routers between 
> host A and the NAT need to install a route pointing the 
> prefix "<ISP-NAT-Prefix>:a.a.a.a::"/n towards the host A. The 
> last hop router, serving the domain to which A is attached, 
> must be configured to relay these packets towards "<ISP-
> Prefix>:<SubnetA>:<HostID-A>".

I'm not sure what you mean by "relay these packets towards" 
in the last sentence.  There are two routes at that last-hop 
router towards the host:  one route for the host's normal 
IPv6 address, <ISP-Prefix>:<SubnetA>:<HostID-A> and another 
route for the host's translatable IPv6 address, 
<ISP-NAT-Prefix>:a.a.a.a:padding.

> All intermediate routers must 
> implement some form of egress filtering, to prevent spoofing 
> of packets by the local NAT.
> 
> 4) In the DNS: the host A has to be configured to publish the 
> address a.a.a.a, in both cases.
> 
> This particular "stateless" solution does require a lesser 
> administrative cost in the NAT. However, there is a tradeoff. 
> The administrative cost in the intermediate routers is much 
> higher. The solution trades a centralized management burden, 
> in the NAT, for a distributed management burden, in the 
> intermediate routers. I am not sure that this is the right tradeoff.

Yes, I agree in this case the NAT is reliant on properly
configured egress filtering close to the hosts.

-d


> -- Christian Huitema
> 
> 
> 


From brian.e.carpenter@gmail.com  Fri Sep 18 13:59:18 2009
Return-Path: <brian.e.carpenter@gmail.com>
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 B3A5A3A6A05; Fri, 18 Sep 2009 13:59:18 -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 OJy1PTBsMQWt; Fri, 18 Sep 2009 13:59:18 -0700 (PDT)
Received: from mail-pz0-f183.google.com (mail-pz0-f183.google.com [209.85.222.183]) by core3.amsl.com (Postfix) with ESMTP id B28093A6A0B; Fri, 18 Sep 2009 13:59:09 -0700 (PDT)
Received: by pzk13 with SMTP id 13so1032022pzk.29 for <multiple recipients>; Fri, 18 Sep 2009 14:00:02 -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=nyb8AdaXP40zFffguzqll5Htpm4S+UUn9Sif9chB7/0=; b=KGeJKu+59ywItoVwejsgON9sl8l50OIfYYYgW7smYywg7emnb1bIDVwDmF7bDnCIoI HxnXMMR1pu/7wowHqgO16385io1bcD1Vmme5pgGW8jji9UCbrCILy1Hv+FqTm5eO6xjR oP9jWrQdzgTfByBOBR+nUnHPl4Z01k0OmKY1Y=
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=WI9lOag/izsh/F5BB6JBNquTKSyCeITb7+EbqE8lkhydgJOGIqANN//jbGeREV0Ksx STU4r9r2C+XBrBhP3M4zgRpbhFUlETYB8Glc30SUwaPbhTeQeohqymq9siqW8xqjN+Ak N3H859QhwtrUxqpplVceoj0cm9WxxnToFEtao=
Received: by 10.114.162.20 with SMTP id k20mr3153832wae.135.1253307601959; Fri, 18 Sep 2009 14:00:01 -0700 (PDT)
Received: from ?10.1.1.4? (118-93-22-7.dsl.dyn.ihug.co.nz [118.93.22.7]) by mx.google.com with ESMTPS id 21sm1160423pxi.11.2009.09.18.13.59.59 (version=SSLv3 cipher=RC4-MD5); Fri, 18 Sep 2009 14:00:01 -0700 (PDT)
Message-ID: <4AB3F4C9.4070701@gmail.com>
Date: Sat, 19 Sep 2009 08:59:53 +1200
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: eric.burgey@orange-ftgroup.com
References: <002601ca3745$63c8b710$d40c6f0a@china.huawei.com>	<57F95EAE-6705-4B8E-849F-3F35D7239EDD@free.fr>	<08BA2C59E081884DB2AAE4A0BE9D6DC1629F33@ftrdmel0.rd.francetelecom.fr>	<12F4112206976147A34FEC0277597CCF27A402C663@XCH-NW-15V.nw.nos.boeing.com> <08BA2C59E081884DB2AAE4A0BE9D6DC162A3BE@ftrdmel0.rd.francetelecom.fr>
In-Reply-To: <08BA2C59E081884DB2AAE4A0BE9D6DC162A3BE@ftrdmel0.rd.francetelecom.fr>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: softwires@ietf.org, Fred.L.Templin@boeing.com, behave@ietf.org
Subject: Re: [BEHAVE] [Softwires] Some Thought about the	AutomaticTunnelAddress
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/mail-archive/web/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>
X-List-Received-Date: Fri, 18 Sep 2009 20:59:18 -0000

Hi Eric,

On 2009-09-19 02:33, eric.burgey@orange-ftgroup.com wrote:
...
> Automatic tunnelling must be limited to a "Site".

If you are referring to ISATAP, that may be a sustainable position.
However, by definition, 6to4 and Teredo involve multiple sites,
for any reasonable definition of site.

    Brian

From xing@cernet.edu.cn  Fri Sep 18 18:43:51 2009
Return-Path: <xing@cernet.edu.cn>
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 BBC643A68C9 for <behave@core3.amsl.com>; Fri, 18 Sep 2009 18:43:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.391
X-Spam-Level: 
X-Spam-Status: No, score=0.391 tagged_above=-999 required=5 tests=[AWL=0.294,  BAYES_00=-2.599, FH_HAS_XAIMC=2.696]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v6dUX2xenpgt for <behave@core3.amsl.com>; Fri, 18 Sep 2009 18:43:50 -0700 (PDT)
Received: from cernet.edu.cn (sea.net.edu.cn [202.112.3.66]) by core3.amsl.com (Postfix) with SMTP id 558643A67C1 for <behave@ietf.org>; Fri, 18 Sep 2009 18:43:43 -0700 (PDT)
Received: from [192.168.1.100]([125.34.50.200]) by cernet.edu.cn(AIMC 3.2.0.0) with SMTP id jm2e4ab45cc7; Sat, 19 Sep 2009 09:44:32 +0800
Message-ID: <4AB43782.1070007@cernet.edu.cn>
Date: Sat, 19 Sep 2009 09:44:34 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Christian Huitema <huitema@microsoft.com>
References: <4AA7730F.6040602@cernet.edu.cn>	<36ba02b00909141038i1611b5d6ide4fd96157ed2bc8@mail.gmail.com>	<6B55F0F93C3E9D45AF283313B8D342BA20F54E47@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>	<4AAF2C06.2020107@it.uc3m.es>	<6B55F0F93C3E9D45AF283313B8D342BA20F557D0@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <4AAFA425.7040706@it.uc3m.es> <4AB079D5.1010404@cernet.edu.cn> <6B55F0F93C3E9D45AF283313B8D342BA20F5A151@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <4AB191F3.9040305@cernet.edu.cn> <6B55F0F93C3E9D45AF283313B8D342BA20F5C240@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <6B55F0F93C3E9D45AF283313B8D342BA20F5C240@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-AIMC-AUTH: xing
X-AIMC-MAILFROM: xing@cernet.edu.cn
X-AIMC-Msg-ID: wUEApoWB
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Security implications of protocol translation
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/mail-archive/web/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>
X-List-Received-Date: Sat, 19 Sep 2009 01:43:51 -0000

Christian Huitema 写道:
>>> If that is the case, if translatable addresses only differ from the
>>>       
>> regular addresses by the structure of the host identifier, how does the
>> translator verify that customer A is not attempting to use an IPv4
>> address assigned to customer B?
>>     
>> how about configure uRPF in the stateless translator?  Xing
>>     
>
> uRPF is a form of ingress filtering. Of course you should enable that. But it is not sufficient. 
>
> Suppose that customer A has an IPv6 translatable address of the form: <ISP-prefix>:<SubnetA>:<MagicA>:a.a.a.a, where a.a.a.a is the IPv4 address assigned by the ISP to A and "magicA" is the special sauce that distinguishes translatable addresses and enables checksum neutrality. Customer B normally uses addresses of the form <ISP-prefix>:<SubnetB>:<host-ID>. One of the hosts at customer B's site configures a host ID of the form <MagicB>:a.a.a.a -- using the appropriate magic, e.g. to match checksums. 
>
> Customer B can send spoofed packets with the source address <ISP-prefix>:<SubnetB>:<MagicB>:a.a.a.a. These packets will be considered valid by egress filtering and uRPF checks, because they do indeed come from the right path for <ISP-prefix>:<SubnetB>. Will the translator forward these packets as originating from address <a.a.a.a>? If not, how does the translator decide that the packets from B are erroneous? What information does it use?
>   

(1) The address format of the stateless translation is 
PREFXI:IPv4:SUFFIX::/k, therefore the the issues raised in this mail do 
not exist. 
(2) Due to the features of the stateless translation, all the IPv4 and 
IPv6 security BCPs can be applied for the stateless translator on the 
IPv4 side and the IPv6 side, respectively.
(3) In addition, on the IPv6 network, there are no additional, 
translation-specific configurations required, since the translator can 
be treated as a router connecting to the IPv6 network. The same reason 
applied to the IPv4 side.

Regards,

xing and congxiao

> -- Christian Huitema
>
>
>
>   


From xing@cernet.edu.cn  Fri Sep 18 19:11:08 2009
Return-Path: <xing@cernet.edu.cn>
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 0B3263A6765 for <behave@core3.amsl.com>; Fri, 18 Sep 2009 19:11:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.361
X-Spam-Level: 
X-Spam-Status: No, score=0.361 tagged_above=-999 required=5 tests=[AWL=0.264,  BAYES_00=-2.599, FH_HAS_XAIMC=2.696]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JPpg5-8yPJYZ for <behave@core3.amsl.com>; Fri, 18 Sep 2009 19:11:07 -0700 (PDT)
Received: from cernet.edu.cn (sea.net.edu.cn [202.112.3.66]) by core3.amsl.com (Postfix) with SMTP id 529573A67B2 for <behave@ietf.org>; Fri, 18 Sep 2009 19:11:06 -0700 (PDT)
Received: from [192.168.1.100]([125.34.50.200]) by cernet.edu.cn(AIMC 3.2.0.0) with SMTP id jm104ab46337; Sat, 19 Sep 2009 10:11:59 +0800
Message-ID: <4AB43DF5.7060209@cernet.edu.cn>
Date: Sat, 19 Sep 2009 10:12:05 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Christian Huitema <huitema@microsoft.com>
References: <4AA7730F.6040602@cernet.edu.cn><36ba02b00909141038i1611b5d6ide4fd96157ed2bc8@mail.gmail.com><6B55F0F93C3E9D45AF283313B8D342BA20F54E47@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com><4AAF2C06.2020107@it.uc3m.es><6B55F0F93C3E9D45AF283313B8D342BA20F557D0@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com><4AAFA425.7040706@it.uc3m.es>	<4AB079D5.1010404@cernet.edu.cn><6B55F0F93C3E9D45AF283313B8D342BA20F5A151@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com><4AB191F3.9040305@cernet.edu.cn>	<6B55F0F93C3E9D45AF283313B8D342BA20F5C240@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>	<028301ca381a$bcc47fe0$5da36b80@cisco.com> <6B55F0F93C3E9D45AF283313B8D342BA20F5E923@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <6B55F0F93C3E9D45AF283313B8D342BA20F5E95A@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <6B55F0F93C3E9D45AF283313B8D342BA20F5E95A@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-AIMC-AUTH: xing
X-AIMC-MAILFROM: xing@cernet.edu.cn
X-AIMC-Msg-ID: wad0poWB
Cc: 'Behave WG' <behave@ietf.org>, Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] Security implications of protocol translation
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/mail-archive/web/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>
X-List-Received-Date: Sat, 19 Sep 2009 02:11:08 -0000

Christian Huitema 写道:
>> Now, lets compare the amount of administrative overhead and routing
>> overhead:
>>
>> 1) At the translator: In the stateless case, the NAT is programmed to
>> map "a.a.a.a" to "<ISP-Prefix>:<SubnetA>:<MagicA>:a.a.a.a"; In the
>> stateful case, the NAT is programmed to map "a.a.a.a" to "<ISP-
>> Prefix>:<SubnetA>:<HostID-A>". Basically the same cost.
>>
>>
>> 2) At the host receiving the mapping: In the stateful case, the host
>> manages exactly one address, "<ISP-Prefix>:<SubnetA>:<HostID-A>"; In the
>> stateless case, the host has to be configured with two addresses, "<ISP-
>> Prefix>:<SubnetA>:<HostID-A>" and "<ISP-
>> Prefix>:<SubnetA>:<MagicA>:a.a.a.a". Somewhat more complicated.
>>
>> 3) At intermediate routers: no configuration.
>>
>> 4) In the DNS: the host A has to be configured to publish the address
>> a.a.a.a, in both cases.
>>
>> From an administrative point of view, it seems that the two solutions
>> are almost equivalent, with a slightly lesser burden for the stateful
>> scenario. The specification of the stateful is simpler, because it does
>> not require any fancy addressing format, and can use whatever host ID
>> structure is used in host A's subnet. In particular, A can use SEND.
>>     
>
>   
> To be fair, Xing's stateless proposal solves the security burden in a different way. Instead of using "<ISP-Prefix>:<SubnetA>:<MagicA>:a.a.a.a", the mapped address would be <ISP-NAT-Prefix>:a.a.a.a:padding. The analysis of configuration requirements would be:
>   

Thanks. The stateless translator (IVI) requires LIR and embed&zero-pad, 
which is discussed clearly in draft-xli-behave-v4v6-prefix-00, but 
unfortunately not very clear in draft-ietf-behave-address-format-00.txt.

> 1) At the translator: The translator is configured to map all addresses in the mapped range (say a.a.a.0/n) to the <ISP-NAT-Prefix>:a.a.a.a:padding. The only required configuration is the range of address. There is no need to configure individual addresses.
>
> 2) At the host receiving the mapping: the host has to be configured with two addresses, "<ISP-
> Prefix>:<SubnetA>:<HostID-A>" and "<ISP-NAT-Prefix>:a.a.a.a:padding". 
>   

Not correct, the IPv6 host can configure ONE IPv6 address: That is 
LIR:IPv4:SUFFIX::/128. When this host communicates with IPv6 Internet, 
the IPv6 routing system will direct the packets to the right 
destination. When this host communicates with IPv4 Internet, the IPv6 
routing system will direct the packets to the stateless translator, then 
the IPv6 packets will be converted into the IPv4 packets and sent to the 
right destination via IPv4 routing system.

BTW, please also note that "<ISP-NAT-Prefix>:a.a.a.a:padding" is a 
special subnet of "<ISP-Prefix>:<SubnetA>" . Then you will see why the 
stateless translator behaves just like an ordinary router and all the 
security BCPs can be applied to it.

>  
> 3) At intermediate routers: all intermediate routers between host A and the NAT need to install a route pointing the prefix "<ISP-NAT-Prefix>:a.a.a.a::"/n towards the host A. The last hop router, serving the domain to which A is attached, must be configured to relay these packets towards "<ISP-
> Prefix>:<SubnetA>:<HostID-A>". All intermediate routers must implement some form of egress filtering, to prevent spoofing of packets by the local NAT.
>   

Not true, see above. There is no special case here for the other 
routers, since the stateless translator behaves as an ordinary router, 
all the routes in this IPv6 network are ordinary routes.

> 4) In the DNS: the host A has to be configured to publish the address a.a.a.a, in both cases.
>   

The DNS resolver needs to know the LIR. And the IPv6 host has A record 
a.a.a.a and AAAA record LIR:a.a.a.a:SUFIX:: in the Authority DNS.

> This particular "stateless" solution does require a lesser administrative cost in the NAT. However, there is a tradeoff. The administrative cost in the intermediate routers is much higher. The solution trades a centralized management burden, in the NAT, for a distributed management burden, in the intermediate routers. I am not sure that this is the right tradeoff.
>   

Not correct, see above for reasons.

Regards,

xing


> -- Christian Huitema
>
>
>
>
>   


From xing@cernet.edu.cn  Fri Sep 18 19:14:30 2009
Return-Path: <xing@cernet.edu.cn>
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 104743A67B2 for <behave@core3.amsl.com>; Fri, 18 Sep 2009 19:14:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.337
X-Spam-Level: 
X-Spam-Status: No, score=0.337 tagged_above=-999 required=5 tests=[AWL=0.240,  BAYES_00=-2.599, FH_HAS_XAIMC=2.696]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VEJepaW29iqr for <behave@core3.amsl.com>; Fri, 18 Sep 2009 19:14:29 -0700 (PDT)
Received: from cernet.edu.cn (sea.net.edu.cn [202.112.3.66]) by core3.amsl.com (Postfix) with SMTP id 79C633A6824 for <behave@ietf.org>; Fri, 18 Sep 2009 19:14:28 -0700 (PDT)
Received: from [192.168.1.100]([125.34.50.200]) by cernet.edu.cn(AIMC 3.2.0.0) with SMTP id jm74ab46401; Sat, 19 Sep 2009 10:15:22 +0800
Message-ID: <4AB43EBC.7040304@cernet.edu.cn>
Date: Sat, 19 Sep 2009 10:15:24 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: marcelo bagnulo braun <marcelo@it.uc3m.es>
References: <4AA7730F.6040602@cernet.edu.cn><36ba02b00909141038i1611b5d6ide4fd96157ed2bc8@mail.gmail.com><6B55F0F93C3E9D45AF283313B8D342BA20F54E47@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com><4AAF2C06.2020107@it.uc3m.es><6B55F0F93C3E9D45AF283313B8D342BA20F557D0@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com><4AAFA425.7040706@it.uc3m.es>	<4AB079D5.1010404@cernet.edu.cn><6B55F0F93C3E9D45AF283313B8D342BA20F5A151@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com><4AB191F3.9040305@cernet.edu.cn>	<6B55F0F93C3E9D45AF283313B8D342BA20F5C240@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <028301ca381a$bcc47fe0$5da36b80@cisco.com> <4AB31E3D.7030207@it.uc3m.es>
In-Reply-To: <4AB31E3D.7030207@it.uc3m.es>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-AIMC-AUTH: xing
X-AIMC-MAILFROM: xing@cernet.edu.cn
X-AIMC-Msg-ID: wqu3poWB
Cc: 'Behave WG' <behave@ietf.org>, Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] Security implications of protocol translation
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/mail-archive/web/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>
X-List-Received-Date: Sat, 19 Sep 2009 02:14:30 -0000

marcelo bagnulo braun 写道:
> Dan Wing escribió:
>>
>>
>>> -----Original Message-----
>>> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On 
>>> Behalf Of Christian Huitema
>>> Sent: Wednesday, September 16, 2009 10:10 PM
>>> To: Xing Li
>>> Cc: Behave WG
>>> Subject: Re: [BEHAVE] Security implications of protocol translation
>>>
>>>>> If that is the case, if translatable addresses only 
>>> differ from the
>>>> regular addresses by the structure of the host identifier, 
>>> how does the
>>>> translator verify that customer A is not attempting to use an IPv4
>>>> address assigned to customer B?
>>>> how about configure uRPF in the stateless translator? Xing
>>> uRPF is a form of ingress filtering. Of course you should enable 
>>> that. But it is not sufficient.
>>> Suppose that customer A has an IPv6 translatable address of the 
>>> form: <ISP-prefix>:<SubnetA>:<MagicA>:a.a.a.a, where a.a.a.a is the 
>>> IPv4 address assigned by the ISP to A and "magicA" is the special 
>>> sauce that distinguishes translatable addresses and enables checksum 
>>> neutrality. Customer B normally uses addresses of the form 
>>> <ISP-prefix>:<SubnetB>:<host-ID>. One of the hosts at customer B's 
>>> site configures a host ID of the form <MagicB>:a.a.a.a -- using the 
>>> appropriate magic, e.g. to match checksums.
>>> Customer B can send spoofed packets with the source address 
>>> <ISP-prefix>:<SubnetB>:<MagicB>:a.a.a.a. These packets will be 
>>> considered valid by egress filtering and uRPF checks, because they 
>>> do indeed come from the right path for <ISP-prefix>:<SubnetB>. Will 
>>> the translator forward these packets as originating from address 
>>> <a.a.a.a>? If not, how does the translator decide that the packets 
>>> from B are erroneous? What information does it use?
>>
>> I understand what you're describing now. Thanks.
>>
>> The translator would need to validate the incoming packet
>> by examing the a.a.a.a address and deciding if the
>> <ISP-prefix>:<SubnetB> is correct. The translator can
>> validate it by using its same algorithm for IPv4-to-
>> IPv6 packets; if the translator receives an IPv4 packet
>> with IPv4 address a.a.a.a, it will algorithmically
>> prepend <ISP-Prefix>:<SubnetA>:<MagicB> to it. The
>> translator can notice that the arriving packet has
>> a different subnet, and drop it. This is akin to the
>> translator doing a uRPF check on the source address
>> of the IPv6 packet: "would I send an IPv4 packet
>> to this same IPv6 destination".
>
> the translator would then be less "stateless" since it has to have a 
> binding between IPv4 address and IPv6 prefix which i understnad must 
> be manually configured

No.
(1) The uRPF can be configured.
(2) The stateless translator maps the IPv6 source address to the IPv4 
address, if it is not translatable address, the translator will drop it.

regards,

xing


>
> Regards, marcelo
>
>> -d
>>
>> _______________________________________________
>> Behave mailing list
>> Behave@ietf.org
>> https://www.ietf.org/mailman/listinfo/behave
>>
>
>


From xuxh@huawei.com  Sat Sep 19 01:32:52 2009
Return-Path: <xuxh@huawei.com>
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 609033A6A37 for <behave@core3.amsl.com>; Sat, 19 Sep 2009 01:32:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.52
X-Spam-Level: **
X-Spam-Status: No, score=2.52 tagged_above=-999 required=5 tests=[AWL=0.226, BAYES_00=-2.599, CN_BODY_35=0.339, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, MIME_CHARSET_FARAWAY=2.45, 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 pF08UITG76Ep for <behave@core3.amsl.com>; Sat, 19 Sep 2009 01:32:51 -0700 (PDT)
Received: from szxga01-in.huawei.com (unknown [119.145.14.64]) by core3.amsl.com (Postfix) with ESMTP id 5383A3A6903 for <behave@ietf.org>; Sat, 19 Sep 2009 01:32:51 -0700 (PDT)
Received: from huawei.com (szxga01-in [172.24.2.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KQ700DUNMFUCY@szxga01-in.huawei.com> for behave@ietf.org; Sat, 19 Sep 2009 16:33:30 +0800 (CST)
Received: from huawei.com ([172.24.1.33]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KQ7001BGMFUXM@szxga01-in.huawei.com> for behave@ietf.org; Sat, 19 Sep 2009 16:33:30 +0800 (CST)
Received: from HUAWEIE75F8F11 ([10.111.12.212]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KQ7004H7MFT23@szxml06-in.huawei.com> for behave@ietf.org; Sat, 19 Sep 2009 16:33:30 +0800 (CST)
Date: Sat, 19 Sep 2009 16:33:29 +0800
From: Xu Xiaohu <xuxh@huawei.com>
In-reply-to: <20090919071207.E03813A67EC@core3.amsl.com>
To: 'Behave WG' <behave@ietf.org>
Message-id: <003701ca3903$ddbd5b60$d40c6f0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=gb2312
Content-transfer-encoding: quoted-printable
Thread-index: Aco4+KOGbt/7Fq53RkOaueIrXi4pjAACbraA
Cc: Chengd@huawei.com, "'Joel M. Halpern'" <jmh@joelhalpern.com>, mohamed.boucadair@orange-ftgroup.com
Subject: [BEHAVE] fwd: New Version Notification for draft-xu-behave-nat-state-sync-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/mail-archive/web/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>
X-List-Received-Date: Sat, 19 Sep 2009 08:32:52 -0000

Hi all,

We just submitted a draft which describes a method of using the Server =
Cache
Synchronization Protocol (SCSP) for NAT state synchronization among a =
set of
NAT devices.

The abstract is as follows:

To support NAT redundancy in hot standby mode [NAT-STANDBY] among a =
group of
NAT devices, the dynamic NAT entries created at the primary NAT device
should be synchronized consistently to the backup NAT device.  This =
document
describes a method of using the Server Cache Synchronization Protocol =
(SCSP)
for NAT state synchronization and specifies the corresponding NAT =
specific
components for this method.

Any comment is welcomed.

Best wishes,
Xiaohu, Dean, Joel, and Med

> -----=D3=CA=BC=FE=D4=AD=BC=FE-----
> =B7=A2=BC=FE=C8=CB: IETF I-D Submission Tool =
[mailto:idsubmission@ietf.org]
> =B7=A2=CB=CD=CA=B1=BC=E4: 2009=C4=EA9=D4=C219=C8=D5 15:12
> =CA=D5=BC=FE=C8=CB: xuxh@huawei.com
> =B3=AD=CB=CD: Chengd@huawei.com
> =D6=F7=CC=E2: New Version Notification for =
draft-xu-behave-nat-state-sync-00
>=20
>=20
> A new version of I-D, draft-xu-behave-nat-state-sync-00.txt has been
> successfuly submitted by Xiaohu Xu and posted to the IETF repository.
>=20
> Filename:	 draft-xu-behave-nat-state-sync
> Revision:	 00
> Title:		 NAT State Synchronization Using SCSP
> Creation_date:	 2009-09-19
> WG ID:		 Independent Submission
> Number_of_pages: 12
>=20
> Abstract:
> To support NAT redundancy in hot standby mode [NAT-STANDBY] among a
> group of NAT devices, the dynamic NAT entries created at the primary
> NAT device should be synchronized consistently to the backup NAT
> device.  This document describes a method of using the Server Cache
> Synchronization Protocol (SCSP) for NAT state synchronization and
> specifies the corresponding NAT specific components for this method.
>=20
> Conventions used in this document
>=20
> The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
> "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
> document are to be interpreted as described in RFC-2119 [RFC2119].
>=20
>=20
>=20
> The IETF Secretariat.



From xuxh@huawei.com  Sat Sep 19 01:52:53 2009
Return-Path: <xuxh@huawei.com>
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 D91E43A685E for <behave@core3.amsl.com>; Sat, 19 Sep 2009 01:52:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.515
X-Spam-Level: **
X-Spam-Status: No, score=2.515 tagged_above=-999 required=5 tests=[AWL=0.221,  BAYES_00=-2.599, CN_BODY_35=0.339, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, MIME_CHARSET_FARAWAY=2.45, 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 TWgdGGNURyCG for <behave@core3.amsl.com>; Sat, 19 Sep 2009 01:52:53 -0700 (PDT)
Received: from szxga02-in.huawei.com (unknown [119.145.14.65]) by core3.amsl.com (Postfix) with ESMTP id E46D13A6926 for <behave@ietf.org>; Sat, 19 Sep 2009 01:52:52 -0700 (PDT)
Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KQ700JYZNDEOJ@szxga02-in.huawei.com> for behave@ietf.org; Sat, 19 Sep 2009 16:53:38 +0800 (CST)
Received: from huawei.com ([172.24.1.33]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KQ7000WMNDEU4@szxga02-in.huawei.com> for behave@ietf.org; Sat, 19 Sep 2009 16:53:38 +0800 (CST)
Received: from HUAWEIE75F8F11 ([10.111.12.212]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KQ700GRINDDOY@szxml06-in.huawei.com> for behave@ietf.org; Sat, 19 Sep 2009 16:53:38 +0800 (CST)
Date: Sat, 19 Sep 2009 16:53:37 +0800
From: Xu Xiaohu <xuxh@huawei.com>
In-reply-to: 
To: 'Behave WG' <behave@ietf.org>
Message-id: <003801ca3906$add3db10$d40c6f0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=gb2312
Content-transfer-encoding: quoted-printable
Thread-index: Aco4+KOGbt/7Fq53RkOaueIrXi4pjAACbraAAAEJgqA=
Cc: Chengd@huawei.com, "'Joel M. Halpern'" <jmh@joelhalpern.com>, mohamed.boucadair@orange-ftgroup.com
Subject: Re: [BEHAVE] New Version Notification for draft-xu-behave-nat-state-sync-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/mail-archive/web/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>
X-List-Received-Date: Sat, 19 Sep 2009 08:52:53 -0000

Sorry, the link is as follows,
http://tools.ietf.org/id/draft-xu-behave-nat-state-sync-00.txt

Xiaohu

> -----=D3=CA=BC=FE=D4=AD=BC=FE-----
> =B7=A2=BC=FE=C8=CB: Xu Xiaohu [mailto:xuxh@huawei.com]
> =B7=A2=CB=CD=CA=B1=BC=E4: 2009=C4=EA9=D4=C219=C8=D5 16:33
> =CA=D5=BC=FE=C8=CB: 'Behave WG'
> =B3=AD=CB=CD: 'Chengd@huawei.com'; 'Joel M. Halpern';
> 'mohamed.boucadair@orange-ftgroup.com'
> =D6=F7=CC=E2: fwd: New Version Notification for =
draft-xu-behave-nat-state-sync-00
>=20
> Hi all,
>=20
> We just submitted a draft which describes a method of using the Server
Cache
> Synchronization Protocol (SCSP) for NAT state synchronization among a =
set
of
> NAT devices.
>=20
> The abstract is as follows:
>=20
> To support NAT redundancy in hot standby mode [NAT-STANDBY] among a =
group
of
> NAT devices, the dynamic NAT entries created at the primary NAT device
should
> be synchronized consistently to the backup NAT device.  This document
> describes a method of using the Server Cache Synchronization Protocol
(SCSP)
> for NAT state synchronization and specifies the corresponding NAT =
specific
> components for this method.
>=20
> Any comment is welcomed.
>=20
> Best wishes,
> Xiaohu, Dean, Joel, and Med
>=20
> > -----=D3=CA=BC=FE=D4=AD=BC=FE-----
> > =B7=A2=BC=FE=C8=CB: IETF I-D Submission Tool =
[mailto:idsubmission@ietf.org]
> > =B7=A2=CB=CD=CA=B1=BC=E4: 2009=C4=EA9=D4=C219=C8=D5 15:12
> > =CA=D5=BC=FE=C8=CB: xuxh@huawei.com
> > =B3=AD=CB=CD: Chengd@huawei.com
> > =D6=F7=CC=E2: New Version Notification for =
draft-xu-behave-nat-state-sync-00
> >
> >
> > A new version of I-D, draft-xu-behave-nat-state-sync-00.txt has been
> > successfuly submitted by Xiaohu Xu and posted to the IETF =
repository.
> >
> > Filename:	 draft-xu-behave-nat-state-sync
> > Revision:	 00
> > Title:		 NAT State Synchronization Using SCSP
> > Creation_date:	 2009-09-19
> > WG ID:		 Independent Submission
> > Number_of_pages: 12
> >
> > Abstract:
> > To support NAT redundancy in hot standby mode [NAT-STANDBY] among a
> > group of NAT devices, the dynamic NAT entries created at the primary
> > NAT device should be synchronized consistently to the backup NAT
> > device.  This document describes a method of using the Server Cache
> > Synchronization Protocol (SCSP) for NAT state synchronization and
> > specifies the corresponding NAT specific components for this method.
> >
> > Conventions used in this document
> >
> > The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
> > "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
> > document are to be interpreted as described in RFC-2119 [RFC2119].
> >
> >
> >
> > The IETF Secretariat.



From huitema@microsoft.com  Sat Sep 19 19:12:40 2009
Return-Path: <huitema@microsoft.com>
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 A7A2B3A6837 for <behave@core3.amsl.com>; Sat, 19 Sep 2009 19:12:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.567
X-Spam-Level: 
X-Spam-Status: No, score=-10.567 tagged_above=-999 required=5 tests=[AWL=0.032, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JxANkD7QikTO for <behave@core3.amsl.com>; Sat, 19 Sep 2009 19:12:39 -0700 (PDT)
Received: from smtp.microsoft.com (mailb.microsoft.com [131.107.115.215]) by core3.amsl.com (Postfix) with ESMTP id AC6AB3A69B1 for <behave@ietf.org>; Sat, 19 Sep 2009 19:12:39 -0700 (PDT)
Received: from TK5EX14MLTC102.redmond.corp.microsoft.com (157.54.79.180) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.176.0; Sat, 19 Sep 2009 19:13:37 -0700
Received: from TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com (157.54.71.68) by TK5EX14MLTC102.redmond.corp.microsoft.com (157.54.79.180) with Microsoft SMTP Server id 14.0.639.20; Sat, 19 Sep 2009 19:13:36 -0700
Received: from TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com ([169.254.3.19]) by TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.68]) with mapi; Sat, 19 Sep 2009 19:13:37 -0700
From: Christian Huitema <huitema@microsoft.com>
To: Xing Li <xing@cernet.edu.cn>
Thread-Topic: [BEHAVE] Security implications of protocol translation
Thread-Index: AQHKNckZMF3GDtqt2kuK6ErD8Y/t95DXsFRQgAB6jICAAP69gIAAD6twgAE+QoD//8N50IABjcVggAADXDCAAAajsIAB1CmAgAESvNA=
Date: Sun, 20 Sep 2009 02:13:35 +0000
Message-ID: <6B55F0F93C3E9D45AF283313B8D342BA20F61857@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
References: <4AA7730F.6040602@cernet.edu.cn><36ba02b00909141038i1611b5d6ide4fd96157ed2bc8@mail.gmail.com><6B55F0F93C3E9D45AF283313B8D342BA20F54E47@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com><4AAF2C06.2020107@it.uc3m.es><6B55F0F93C3E9D45AF283313B8D342BA20F557D0@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com><4AAFA425.7040706@it.uc3m.es> <4AB079D5.1010404@cernet.edu.cn><6B55F0F93C3E9D45AF283313B8D342BA20F5A151@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com><4AB191F3.9040305@cernet.edu.cn> <6B55F0F93C3E9D45AF283313B8D342BA20F5C240@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <028301ca381a$bcc47fe0$5da36b80@cisco.com> <6B55F0F93C3E9D45AF283313B8D342BA20F5E923@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <6B55F0F93C3E9D45AF283313B8D342BA20F5E95A@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <4AB43DF5.7060209@cernet.edu.cn>
In-Reply-To: <4AB43DF5.7060209@cernet.edu.cn>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: 'Behave WG' <behave@ietf.org>, Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] Security implications of protocol translation
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/mail-archive/web/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>
X-List-Received-Date: Sun, 20 Sep 2009 02:12:40 -0000

PiBOb3QgY29ycmVjdCwgdGhlIElQdjYgaG9zdCBjYW4gY29uZmlndXJlIE9ORSBJUHY2IGFkZHJl
c3M6IFRoYXQgaXMNCj4gTElSOklQdjQ6U1VGRklYOjovMTI4LiBXaGVuIHRoaXMgaG9zdCBjb21t
dW5pY2F0ZXMgd2l0aCBJUHY2IEludGVybmV0LA0KPiB0aGUgSVB2NiByb3V0aW5nIHN5c3RlbSB3
aWxsIGRpcmVjdCB0aGUgcGFja2V0cyB0byB0aGUgcmlnaHQNCj4gZGVzdGluYXRpb24uIFdoZW4g
dGhpcyBob3N0IGNvbW11bmljYXRlcyB3aXRoIElQdjQgSW50ZXJuZXQsIHRoZSBJUHY2DQo+IHJv
dXRpbmcgc3lzdGVtIHdpbGwgZGlyZWN0IHRoZSBwYWNrZXRzIHRvIHRoZSBzdGF0ZWxlc3MgdHJh
bnNsYXRvciwgdGhlbg0KPiB0aGUgSVB2NiBwYWNrZXRzIHdpbGwgYmUgY29udmVydGVkIGludG8g
dGhlIElQdjQgcGFja2V0cyBhbmQgc2VudCB0byB0aGUNCj4gcmlnaHQgZGVzdGluYXRpb24gdmlh
IElQdjQgcm91dGluZyBzeXN0ZW0uDQoNCkkgdW5kZXJzdGFuZCB3aGF0IHlvdSBhcmUgcHJvcG9z
aW5nLCBidXQgSSBkbyBub3QgYmVsaWV2ZSB0aGF0IHdlIGhhdmUgV0cgY29uc2Vuc3VzIHRoZXJl
LiBXaGF0IHlvdSBhcmUgcHJvcG9zaW5nIGFtb3VudHMgdG8gZW50aXJlbHkgcmV3b3JrIHRoZSB3
YXkgSVB2NiBhZGRyZXNzZXMgYXJlIGNvbmZpZ3VyZWQsIGluIG9yZGVyIHRvIGJldHRlciBzdXBw
b3J0IHN0YXRlbGVzcyBhZGRyZXNzIGNvbmZpZ3VyYXRpb24uIFRoYXQgbWF5IGJlIGEgdHJhZGVv
ZmYgdGhhdCB0aGUgV0cgd2FudHMgdG8gc3VwcG9ydCwgYnV0IGl0IHdpbGwgcmVxdWlyZSBzb21l
IHZlcnkgZXhwbGljaXQgZGVjaXNpb24uDQoNCllvdXIgcHJvcG9zYWwgZGlmZmVycyBmcm9tIHRo
ZSBjdXJyZW50IHByYWN0aWNlIGluIG11bHRpcGxlIHdheXMuIE1vc3Qgbm90aWNlYWJseSwgeW91
IHByb3Bvc2UgdG8gcmVwbGFjZSB0aGUgY3VycmVudCBhZGRyZXNzIGZvcm1hdCAoNjQgYml0IHN1
Ym5ldCArIDY0IGJpdCBob3N0IElEKSBieSBhIG5ldyBmb3JtYXQgKElTUCBwcmVmaXggKyAzMiBi
aXQgSVB2NCBhZGRyZXNzICsgcGFkZGluZykuIFRoZXJlIGlzIGEgc3Vic3RhbnRpYWwgbGlzdCBv
ZiBzdGFuZGFyZHMgdGhhdCB3aWxsIGhhdmUgdG8gYmUgbW9kaWZpZWQgaWYgd2Ugd2FudCB0byBy
ZXBsYWNlIHRoZSBjdXJyZW50IHByYWN0aWNlIGJ5IHlvdXIgcHJvcG9zYWwuIE9mIGNvdXJzZSwg
d2Ugd2lsbCBoYXZlIHRvIHJlcGxhY2UgdGhlIGN1cnJlbnQgYWRkcmVzcyBjb25maWd1cmF0aW9u
IHByb2NlZHVyZXMuIEJ1dCB0aGF0IGlzIG5vdCBhbGwuDQoNCkZvciBleGFtcGxlLCBpbiBvcmRl
ciB0byBtYWtlIE5EIHdvcmssIHdlIHdpbGwgaGF2ZSB0byBtYXAgSVB2NiBzdWJuZXRzIHRvIElQ
djQgc3VibmV0cywgYW5kIG1ha2Ugc3VyZSB0aGF0IHRoZSBJUHY2IHN1Ym5ldCBpcyBjb21wb3Nl
ZCBvZiB0aGUgSVNQIHByZWZpeCBhbmQgdGhlICJzdWJuZXQiIHBhcnQgb2YgdGhlIElQdjQgYWRk
cmVzcywgYW5kIG1ha2Ugc3VyZSB0aGF0IHRoZSAidHJhbnNsYXRhYmxlIiBob3N0cyByZWNlaXZl
IGFkZHJlc3NlcyBpbiB0aGUgYXBwcm9wcmlhdGUgSVB2NCBzdWJuZXQuIFRoZW4sIHdlIHdpbGwg
aGF2ZSB0byBlaXRoZXIgbWFrZSBzdXJlIHRoYXQgdGhlIG5ldyBwcmVmaXggKElTUCArIElQdjQg
c3VibmV0KSBhbHdheXMgZmFsbCBvbiBhIDY0IGJpdCBib3VuZGFyeSwgb3IsIGlmIHRoYXQgY2Fu
bm90IGJlIGFjaGlldmVkLCBtb2RpZnkgZXhpc3RpbmcgaW1wbGVtZW50YXRpb25zIHRvIG1ha2Ug
c3VyZSB0aGF0IHRoZXkgd29yayB3aXRoIGFyYml0cmFyeSBzdWJuZXQgYm91bmRhcmllcy4gDQoN
CkkgZG8gbm90IGJlbGlldmUgdGhhdCB3ZSBoYXZlIFdHIGNvbnNlbnN1cyB0byBzcGVjaWZ5IHRo
YXQuIFdlIG1pZ2h0IG9idGFpbiB0aGlzIGNvbnNlbnN1cyBpZiB0aGUgYmVuZWZpdHMgb2YgZWFz
eSB0cmFuc2xhdGlvbiB3ZXJlIHN1Y2ggdGhhdCB0aGV5IG92ZXJjb21lIHRoZSBidXJkZW4gb2Yg
bW9kaWZ5aW5nIHN0YW5kYXJkcyBhbmQgaW1wbGVtZW50YXRpb25zLiBCdXQsIGZyYW5rbHksIEkg
ZG91YnQgaXQuDQoNCkJ1dCBteSBiaWdnZXN0IHByb2JsZW0gaXMgdGhhdCB0aGUgcHJvcG9zYWwg
aXMgb25seSBlY29ub21pY2FsIGlmIHdlIGNhbiBhc3NpZ24gYSB1bmlxdWUgSVB2NCBhZGRyZXNz
IHRvIGV2ZXJ5IGhvc3QuIElmIHdlIGNhbm5vdCwgdGhlbiBuZXR3b3JrIG1hbmFnZXJzIHdpbGwg
aGF2ZSB0byBydW4gdHdvIHBhcmFsbGVsIGFkZHJlc3Npbmcgc2NoZW1lcy4gTm9kZXMgb24gdGhl
IHNhbWUgbGlua3Mgd2lsbCBlbmQgdXAgd2l0aCBkaWZmZXJlbnQgYWRkcmVzcyBwcmVmaXhlcyBk
ZXBlbmRpbmcgd2hldGhlciB0aGV5IGhhdmUgYSAidHJhbnNsYXRhYmxlIiBhZGRyZXNzIG9yIG5v
dC4gUm91dGVycyB3aWxsIGhhdmUgdG8gbWFuYWdlIHR3byBwYXJhbGxlbCBzZXQgb2YgdGFibGVz
LiANCg0KQXQgdGhlIHNhbWUgdGltZSwgSSBiZWxpZXZlIHdlIGNhbiBvYnRhaW4gdGhlIGJlbmVm
aXQgb2Ygc3RhdGVsZXNzIG1hcHBpbmcgd2l0aG91dCBoYXZpbmcgdG8gY2hhbmdlIGV4aXN0aW5n
IGFkZHJlc3MgbWFuYWdlbWVudCBwcmFjdGljZXMuIFRoZSBtYWluIGJlbmVmaXQgb2YgeW91ciBw
cm9wb3NhbCBpcyB0byBzaW1wbGlmeSB0aGUgbWFuYWdlbWVudCBvZiBzdGF0ZWxlc3MgdHJhbnNs
YXRvcnMsIHdobyBjYW4gYWxnb3JpdGhtaWNhbGx5IGV4dHJhY3QgdGhlIElQdjQgc291cmNlIGFk
ZHJlc3MgZnJvbSB0aGUgaW5jb21pbmcgSVB2NiBzb3VyY2UgYWRkcmVzcy4gQnV0IHRoZSB0cmFu
c2xhdG9ycyBjb3VsZCBqdXN0IGFzIHdlbGwgb2J0YWluIHRoZSBJUHY0IHNvdXJjZSBhZGRyZXNz
IGJ5IGEgbG9vayB1cCBpbiBhIHRhYmxlIG9mICJ0cmFuc2xhdGFibGUiIGFkZHJlc3Nlcy4gR3Jh
bnRlZCwgd2Ugd2lsbCBuZWVkIHRvIHBhc3MgdGhhdCB0YWJsZSB0byBhbGwgc3RhdGVsZXNzIHRy
YW5zbGF0b3JzLiBCdXQgSSBiZWxpZXZlIHRoYXQgb3JnYW5pemluZyB0aGUgZGlzdHJpYnV0aW9u
IG9mIHRoaXMgdGFibGUgaXMgbXVjaCBzaW1wbGVyIHRoYW4gbW9kaWZ5aW5nIHRoZSBleGlzdGlu
ZyBzdGFuZGFyZHMgYW5kIHByYWN0aWNlcyBmb3IgYWRkcmVzcyBjb25maWd1cmF0aW9uLCBuZWln
aGJvciBkaXNjb3ZlcnksIG9yIHN1Ym5ldCBtYW5hZ2VtZW50Lg0KDQotLSBDaHJpc3RpYW4gSHVp
dGVtYQ0KDQoNCg0KIA0K

From ericlklein.ipv6@gmail.com  Sun Sep 20 03:44:39 2009
Return-Path: <ericlklein.ipv6@gmail.com>
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 36CE33A67A2 for <behave@core3.amsl.com>; Sun, 20 Sep 2009 03:44:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.698
X-Spam-Level: 
X-Spam-Status: No, score=-1.698 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_62=0.6, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UZb+ZZ9P9MMP for <behave@core3.amsl.com>; Sun, 20 Sep 2009 03:44:38 -0700 (PDT)
Received: from mail-bw0-f210.google.com (mail-bw0-f210.google.com [209.85.218.210]) by core3.amsl.com (Postfix) with ESMTP id CAF8E3A696D for <behave@ietf.org>; Sun, 20 Sep 2009 03:44:37 -0700 (PDT)
Received: by bwz6 with SMTP id 6so1442229bwz.37 for <behave@ietf.org>; Sun, 20 Sep 2009 03:45:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=cGPSoL5Xxxa7WEzRA0w+u+zcuFTbOZmuKiLhBboJFwA=; b=uaFVvr1ZfhklGzVWCCq3of6Q2o/3tubqZ/Z32HmbBViLMHLYIQOkTp/ylTFH6MpZKU 7qpqfe+uofhAn+HLS5OBo2kLI9+/EHmxaFFTkJfZWyvp60Aiz7xda26FRTTmSRUWLKE5 bZbkmQapWNPncfv+4/25z1o8oCn8jW1tFCG4s=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=hx8uEOW6QcJAut1IL5OzwH/0nAOFI7cLmS7X4Jsyh+OMQ/27CT9nlzC09ZbhJ8EVpF 55B1VR+5psc/Oc5qNr5gLmXtpQF7nxCKY8fwC9aG+Qyy+DElsOXKMaFF84qH4owattNa AvYGaJEEmDbgjJcbM/f5xRRKevlJP4f8EHplQ=
MIME-Version: 1.0
Received: by 10.239.170.38 with SMTP id q38mr270198hbe.151.1253443532413; Sun,  20 Sep 2009 03:45:32 -0700 (PDT)
In-Reply-To: <095E4E4E-F4F5-4FFD-95D5-4D6C05608124@free.fr>
References: <095E4E4E-F4F5-4FFD-95D5-4D6C05608124@free.fr>
Date: Sun, 20 Sep 2009 13:45:32 +0300
Message-ID: <18d24aa20909200345o57af09baw63d7cdd0ded58dab@mail.gmail.com>
From: Eric Klein <ericlklein.ipv6@gmail.com>
To: =?ISO-8859-1?B?UultaSBEZXNwculz?= <remi.despres@free.fr>
Content-Type: multipart/alternative; boundary=001485f78c527edc01047400109b
Cc: Xing Li <xing@cernet.edu.cn>, Behave WG <behave@ietf.org>, Fred Baker <fred@cisco.com>, Dave Thaler <dthaler@windows.microsoft.com>
Subject: Re: [BEHAVE] IPv4-only and IPv6-only definitions
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/mail-archive/web/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>
X-List-Received-Date: Sun, 20 Sep 2009 10:44:39 -0000

--001485f78c527edc01047400109b
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I am not sure about such a discussion here, but last year I was part of
several versions of this as part of WiMAX Forum Service Providers and
Network Engineering teams.

For the Operator the combination of what and how IPv4 only, IPv6 only, and
mixed end devices / backbone / core devices etc. worked out to a 20 example
document that needed policies and concepts on how to handle - especially in
a mobile environment let alone in a roaming one.

Eric

On Tue, Sep 1, 2009 at 13:40, R=E9mi Despr=E9s <remi.despres@free.fr> wrote=
:

> Dave,
>
> I also also think that the current definition of IPv6-only needs more wor=
k.
>
> Here is an approach which, in my understanding, would improve the
> situation.
> (Whereas you introduced "connected", as an adjective for applications, it
> introduces "connections", and more precisely connection "endpoints" as
> objects that can be IPv6-only at one end and IPv4-only at the other end.)
>
>
> 1. The definition would become(in substance):
> "IPvX-only endpoint: In a connection that traverses an IPv6/IPv4
> translator, the endpoint that works in IPvX. Reasons for this may be that=
:
> (1) its application is IPvX-only (not IPvY capable); (2) its node is
> IPvX-only (not IPvY-enabled); (3) if the endpoint is connection initiator=
,
> all known addresses of the other endpoint are IPvX (and translatable to
> IPvY); if the endpoint is connection acceptor, all of its addresses known=
 by
> other endpoint are IPvY (translatable to IPvX)."
>
> 2. In the text, IPv6-only entities that contain connection endpoints
> ("systems", "devices", "equipment", "nodes") would be renamed "IPv6-only
> endpoints".
>
> Regards,
> RD
>
>
> Le 1 sept. 09 =E0 00:54, Dave Thaler a =E9crit :
>
>  "IPv6-only" is an adjective and can be used to describe a network,
>> a host, or an application.
>>
>> The text in the framework doc says:
>>   IPv6-only:  An IPv6-only implementation, in this context, comprises
>>      an IPv6 enabled end system stack plus routing in the network.  It
>>      implies that two application instances are capable of
>>      communicating using IPv6, but not IPv4 - they have an IPv6 stack,
>>      addresses, and network support including routing in IPv6, but some
>>      element is missing that prevents communication with IPv4 hosts.
>>
>> One problem with the above is that it confuses whether it's an adjective=
,
>> or a term "IPv6-only implementation" or an "IPv6-only end system" or
>> an "IPv6-only application"
>> ...
>> I think people would expect that an IP-version agnostic application woul=
d
>> be "IPv4-capable" but not necessarily "IPv4-connected".
>>
>
>
>
>
>
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>

--001485f78c527edc01047400109b
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I am not sure about such a discussion here, but last year =
I was part of
several versions of this as part of WiMAX Forum Service Providers and
Network Engineering teams.<br><br>For the Operator the combination of
what and how IPv4 only, IPv6 only, and mixed end devices / backbone /
core devices etc. worked out to a 20 example document that needed
policies and concepts on how to handle - especially in a mobile
environment let alone in a roaming one.<br><br>Eric<br><br><div class=3D"gm=
ail_quote">On Tue, Sep 1, 2009 at 13:40, R=E9mi Despr=E9s <span dir=3D"ltr"=
>&lt;<a href=3D"mailto:remi.despres@free.fr">remi.despres@free.fr</a>&gt;</=
span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Dave,<br>
<br>
I also also think that the current definition of IPv6-only needs more work.=
<br>
<br>
Here is an approach which, in my understanding, would improve the situation=
.<br>
(Whereas you introduced &quot;connected&quot;, as an adjective for applicat=
ions, it introduces &quot;connections&quot;, and more precisely connection =
&quot;endpoints&quot; as objects that can be IPv6-only at one end and IPv4-=
only at the other end.)<br>

<br>
<br>
1. The definition would become(in substance):<br>
&quot;IPvX-only endpoint: In a connection that traverses an IPv6/IPv4 trans=
lator, the endpoint that works in IPvX. Reasons for this may be that: (1) i=
ts application is IPvX-only (not IPvY capable); (2) its node is IPvX-only (=
not IPvY-enabled); (3) if the endpoint is connection initiator, all known a=
ddresses of the other endpoint are IPvX (and translatable to IPvY); if the =
endpoint is connection acceptor, all of its addresses known by other endpoi=
nt are IPvY (translatable to IPvX).&quot;<br>

<br>
2. In the text, IPv6-only entities that contain connection endpoints (&quot=
;systems&quot;, &quot;devices&quot;, &quot;equipment&quot;, &quot;nodes&quo=
t;) would be renamed &quot;IPv6-only endpoints&quot;.<br>
<br>
Regards,<br>
RD<br>
<br>
<br>
Le 1 sept. 09 =E0 00:54, Dave Thaler a =E9crit :<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
&quot;IPv6-only&quot; is an adjective and can be used to describe a network=
,<br>
a host, or an application.<br>
<br>
The text in the framework doc says:<br>
 =A0 IPv6-only: =A0An IPv6-only implementation, in this context, comprises<=
br>
 =A0 =A0 =A0an IPv6 enabled end system stack plus routing in the network. =
=A0It<br>
 =A0 =A0 =A0implies that two application instances are capable of<br>
 =A0 =A0 =A0communicating using IPv6, but not IPv4 - they have an IPv6 stac=
k,<br>
 =A0 =A0 =A0addresses, and network support including routing in IPv6, but s=
ome<br>
 =A0 =A0 =A0element is missing that prevents communication with IPv4 hosts.=
<br>
<br>
One problem with the above is that it confuses whether it&#39;s an adjectiv=
e,<br>
or a term &quot;IPv6-only implementation&quot; or an &quot;IPv6-only end sy=
stem&quot; or<br>
an &quot;IPv6-only application&quot;<br>
...<br>
I think people would expect that an IP-version agnostic application would b=
e &quot;IPv4-capable&quot; but not necessarily &quot;IPv4-connected&quot;.<=
br>
</blockquote>
<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
Behave mailing list<br>
<a href=3D"mailto:Behave@ietf.org" target=3D"_blank">Behave@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/behave" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/behave</a><br>
</blockquote></div><br></div>

--001485f78c527edc01047400109b--

From Michael.Tuexen@lurchi.franken.de  Mon Sep 21 02:47:46 2009
Return-Path: <Michael.Tuexen@lurchi.franken.de>
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 989B13A67E3 for <behave@core3.amsl.com>; Mon, 21 Sep 2009 02:47:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.136
X-Spam-Level: 
X-Spam-Status: No, score=-1.136 tagged_above=-999 required=5 tests=[AWL=-0.388, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, MIME_8BIT_HEADER=0.3, 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 DBRBy7Bl7BSJ for <behave@core3.amsl.com>; Mon, 21 Sep 2009 02:47:45 -0700 (PDT)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by core3.amsl.com (Postfix) with ESMTP id E55513A6A4D for <behave@ietf.org>; Mon, 21 Sep 2009 02:47:44 -0700 (PDT)
Received: from [10.0.1.107] (unknown [194.95.73.153]) by mail-n.franken.de (Postfix) with ESMTP id 5D5A61C0C0BC5; Mon, 21 Sep 2009 11:48:43 +0200 (CEST)
Message-Id: <EE45169F-85B3-4756-B5A2-99022AD1E651@lurchi.franken.de>
From: =?ISO-8859-1?Q?Michael_T=FCxen?= <Michael.Tuexen@lurchi.franken.de>
To: <Karen.Nielsen@tieto.com>
In-Reply-To: <CF340E42AED0874C81947E18863DE77B15D16590@EXMB03.eu.tieto.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v936)
Date: Mon, 21 Sep 2009 10:48:42 +0100
References: <bc023dcd0907270038k2b89e078u174850b66a865e96@mail.gmail.com> <E4561B14EE2A3E4E9D478EBFB5416E1B19A84F@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <4755150A-18EE-4B45-AA80-60CF82C4B9CF@lurchi.franken.de> <CF340E42AED0874C81947E18863DE77B15D16590@EXMB03.eu.tieto.com>
X-Mailer: Apple Mail (2.936)
Cc: draft-ietf-behave-sctpnat@tools.ietf.org, behave@ietf.org
Subject: Re: [BEHAVE] Comments on draft-ietf-behave-sctpnat-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/mail-archive/web/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>
X-List-Received-Date: Mon, 21 Sep 2009 09:47:46 -0000

On Sep 21, 2009, at 10:43 AM, <Karen.Nielsen@tieto.com> wrote:

> Hi,
>
> For someone who hasn't followed this deeply for a while..
>
> "The splitting of the document" mentioned is that a splitting into =20
> two draft - one describing
> the NAT behavior and another extensions for 4960 to support NAT - or =20=

> something else ?
That is correct.

Best regards
Michael

>
> Sorry, proceedings from Stockholm not available yet.
> Thanks!
>
> BR, Karen
>
>> -----Original Message-----
>> From: behave-bounces@ietf.org
>> [mailto:behave-bounces@ietf.org] On Behalf Of Michael T=FCxen
>> Sent: Tuesday, August 11, 2009 9:44 AM
>> To: Dave Thaler
>> Cc: behave@ietf.org; draft-ietf-behave-sctpnat@tools.ietf.org
>> Subject: Re: [BEHAVE] Comments on draft-ietf-behave-sctpnat-01
>>
>> Hi Dave,
>>
>> thank you very much for the comments. We'll incorporate them during
>> the splitting of the document.
>>
>> Best regards
>> Michael
>>
>> On Aug 11, 2009, at 3:27 AM, Dave Thaler wrote:
>>
>>> I just read this document for the first time, and there are still
>>> significant issues that need to be addressed.  My comments, both
>>> technical and editorial, are at
>>>
>> http://research.microsoft.com/en-us/um/people/dthaler/draft-ie
>> tf-behave-sctpnat-01.pdf
>>>
>>> A few of my comments duplicate things already discussed like the
>>> fact that
>>> it contains normative changes to 4690.  I agree with the proposal to
>>> remove them from this draft.
>>>
>>> I won't detail here the other technical issues I found (you
>> can find
>>> them
>>> in the PDF) but a high level summary is that there is still
>> a bunch of
>>> logic missing, since the examples don't match the prescriptive
>>> behavior
>>> that currently exists in section 5 (the behavior there
>> mostly matches,
>>> but the examples show a lot more things that aren't
>> specified anywhere
>>> in the doc).
>>>
>>> -Dave
>>>
>>>> -----Original Message-----
>>>> From: Bruce Lowekamp [mailto:bbl@lowekamp.net]
>>>> Sent: Monday, July 27, 2009 12:38 AM
>>>> To: behave@ietf.org; Behave Chairs; draft-ietf-behave-
>>>> sctpnat@tools.ietf.org
>>>> Subject: open issues in draft-ietf-behave-sctpnat-01
>>>>
>>>> There was a thread on the behave mailing list with the
>> subject "SCTP
>>>> NAT questions and concerns" that started on 11/20/08 and
>> ran through
>>>> 11/22/08 with a few additional comments from Dan on 12/17.
>> My belief
>>>> is that there were a number of issues identified in that
>> thread that
>>>> were not addressed by the -01 revision.  It's been awhile, but I'm
>>>> going to try to summarize some of the open issues:
>>>>
>>>> - the draft does not use the same terminology as 4787 to
>> describe NAT
>>>> behavior.  (Magnus also started a thread on 11/20 that discussed
>>>> terminology here in more detail.)  It also does not use the same
>>>> format to define a list of requirements, which may be desirable for
>>>> uniformity.
>>>>
>>>> - the draft is BCP, but specifies normative changes to SCTP
>>>>
>>>> - the specified changes to SCTP (NAT_SUPPORTED) essentially only
>>>> interoperate with other similarly enhanced SCTP implementations, so
>>>> non-NAT-aware implementations don't benefit from the SCTP NAT
>>>>
>>>> -  In the world we are quickly hurtling toward,
>>>> there will be no way to tell if you are going through a
>> NAT.  Between
>>>> NAT444, NAT46, and NAT64, you can have a public IP address
>>>> communicating with another public IP address that goes
>> through a NAT.
>>>> If you want that to work with SCTP, I think the implication is that
>>>> this flag needs to always be set, which eliminates restart from the
>>>> SCTP feature set.
>>>>
>>>> - the draft needs to clearly state that a rendezvous service is
>>>> necessary to exchange vtags to make a connection
>>>>
>>>> - overloading the vtag to provide multiplexing support may
>> reduce its
>>>> usefulness for security and freshness.  (I think this comment was
>>>> more
>>>> that this should be explicitly acknowledged rather than it being a
>>>> problem to do so.)
>>>>
>>>> - if a NAT needs to send an ABORT to force an SCTP app to pick a
>>>> different port, this has significant implications for application
>>>> design, since they may have already published their chosen port via
>>>> another mechanism
>>>>
>>>> I think there were a few other issues raised in the
>> thread, as well.
>>>
>>> _______________________________________________
>>> 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 Remi.Denis-Courmont@nokia.com  Mon Sep 21 04:21:57 2009
Return-Path: <Remi.Denis-Courmont@nokia.com>
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 2D8F428C0E4 for <behave@core3.amsl.com>; Mon, 21 Sep 2009 04:21:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.188
X-Spam-Level: 
X-Spam-Status: No, score=-6.188 tagged_above=-999 required=5 tests=[AWL=0.111,  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 EFljsPMD6t8a for <behave@core3.amsl.com>; Mon, 21 Sep 2009 04:21:56 -0700 (PDT)
Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134]) by core3.amsl.com (Postfix) with ESMTP id 1E4DB3A6A7A for <behave@ietf.org>; Mon, 21 Sep 2009 04:21:55 -0700 (PDT)
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211]) by mgw-mx09.nokia.com (Switch-3.3.3/Switch-3.3.3) with ESMTP id n8LBLHF2011082; Mon, 21 Sep 2009 06:22:09 -0500
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 21 Sep 2009 14:22:37 +0300
Received: from mgw-sa01.ext.nokia.com ([147.243.1.47]) by esebh102.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Mon, 21 Sep 2009 14:22:36 +0300
Received: from leon.remlab.net (esdhcp03667.research.nokia.com [172.21.36.67]) by mgw-sa01.ext.nokia.com (Switch-3.3.3/Switch-3.3.3) with ESMTP id n8LBMVDi002265; Mon, 21 Sep 2009 14:22:31 +0300
From: "=?iso-8859-1?q?R=E9mi?= Denis-Courmont" <remi.denis-courmont@nokia.com>
Organization: Maemo Devices - Nokia
To: behave@ietf.org
Date: Mon, 21 Sep 2009 14:23:11 +0300
User-Agent: KMail/1.11.2 (Linux/2.6.29.6; KDE/4.2.2; i686; ; )
References: <E4561B14EE2A3E4E9D478EBFB5416E1B1CC7A902@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com> <E4561B14EE2A3E4E9D478EBFB5416E1B1CC7AE58@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com> <21052BD84AD96A4E8749DAA4766A4747096FBED1@TK5EX14MBXC122.redmond.corp.microsoft.com>
In-Reply-To: <21052BD84AD96A4E8749DAA4766A4747096FBED1@TK5EX14MBXC122.redmond.corp.microsoft.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200909211423.12092.remi.denis-courmont@nokia.com>
Content-Type: Text/Plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-OriginalArrivalTime: 21 Sep 2009 11:22:36.0293 (UTC) FILETIME=[D225DB50:01CA3AAD]
X-Nokia-AV: Clean
Cc: Ali Turkoglu <alitu@microsoft.com>, ext Gurpreet Virdi <Gurpreet.Virdi@microsoft.com>, Dave Thaler <dthaler@microsoft.com>
Subject: Re: [BEHAVE] Comments on draft-denis-icmpv6-generation-for-teredo-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/mail-archive/web/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>
X-List-Received-Date: Mon, 21 Sep 2009 11:21:57 -0000

On Thursday 17 September 2009 23:25:06 ext Gurpreet Virdi wrote:
> Hi Teemu,
>
> I am part of the Teredo team at Microsoft and I had some comments about #=
1,
> #2, #3 and #4 points you mention below. Here are my comments:
>
> #1: The draft now says "Furthermore, the IPv6 firewall might not be on the
> return data path in which case generated ICMPv6 Echo Replies might break
> Teredo host-based relay feature.". This might seem a little confusing. See
> in both the host-based relay features and non-host-based relay
> feature....the firewall might be on the return data path. The difference =
is
> that in the host-based relay feature, the ICMPV6 Echo Reply packet hits t=
he
> relay *before* hitting the IPV6 firewall (the host itself is the relay!!!=
).
> And in the non host-based relay feature, the ICMPV6 Echo Reply packet will
> hit the relay after hitting this IPV6 firewall. Hence, the host-based rel=
ay
> feature will not work with this draft.

It does not *break* the host-based relay feature. A host-based relay behind=
 an=20
ICMPv6-filtering network infrastructure is broken to start with. Or then I=
=20
missed something...

Adding ICMPv6 generation into the picture does not fix the problem, but it=
=20
does not make it much worse either. On top of that, running a host-based=20
relays would most probably break the firewall policy (as tunneled would not=
 be=20
"seen" by the firewalls).

> #2: Currently Teredo relay discovery only succeeds when the following
> conditions are met A) if the firewall on the peer machine exempts ICMPV6
> Echo Request and B) if the IPV6 address is a valid IPV6 address belonging
> to a peer machine that is up & running.
>
> Now A is not common by default. In windows teredo clients, the time this =
is
> most common is when the peer is a host-based relay and I will not talk
> about it in detail, because you have already mentioned it in the draft as
> being one of the cases where the IPV6 firewall will not reply to pings.
>
> Now B, requires that the attacker to guess your 128 bit IPV6 address
> correctly.
>
> But with this draft, Teredo relay discovery will now succeed even if the
> above 2 conditions i.e. A & B are not met. So potentially an attacker cou=
ld
> go around sending pings to all sorts of address ranges and ping replies
> from the IPV6 firewall in front of these machines will help in discovering
> Teredo relays around the world.

Yes, this is a security consideration. But is it a problem? if you don't wa=
nt=20
your relay to be discovered, you should simply *not* filter inbound ICMPv6.=
 If=20
you do inbound ICMPv6, then your Teredo relay is totally useless anyway.

This is just the same issue as #1 really: why would one run a Teredo relay =
if=20
one implements a firewall filtering policy that is fundamentally incompatib=
le=20
with Teredo?

> This can certainly be mitigated by taking measures like: the firewall
> should only respond to ping requests that are destined to actual *active*
> IPV6 addresses behind the firewall.

Exactly, but this is hardly realistic implementation-wise.

=2D-=20
R=E9mi Denis-Courmont
Nokia Devices R&D, Maemo Software, Helsinki



From teemu.savolainen@nokia.com  Mon Sep 21 06:26:49 2009
Return-Path: <teemu.savolainen@nokia.com>
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 CDAF228C166 for <behave@core3.amsl.com>; Mon, 21 Sep 2009 06:26:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.118
X-Spam-Level: 
X-Spam-Status: No, score=-6.118 tagged_above=-999 required=5 tests=[AWL=0.481,  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 u6h17SCL8Hs9 for <behave@core3.amsl.com>; Mon, 21 Sep 2009 06:26:49 -0700 (PDT)
Received: from mgw-mx06.nokia.com (smtp.nokia.com [192.100.122.233]) by core3.amsl.com (Postfix) with ESMTP id 95F6028C130 for <behave@ietf.org>; Mon, 21 Sep 2009 06:26:48 -0700 (PDT)
Received: from vaebh106.NOE.Nokia.com (vaebh106.europe.nokia.com [10.160.244.32]) by mgw-mx06.nokia.com (Switch-3.3.3/Switch-3.3.3) with ESMTP id n8LDR4eE029655; Mon, 21 Sep 2009 16:27:32 +0300
Received: from vaebh102.NOE.Nokia.com ([10.160.244.23]) by vaebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 21 Sep 2009 16:27:33 +0300
Received: from vaebh101.NOE.Nokia.com ([10.160.244.22]) by vaebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 21 Sep 2009 16:27:11 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.5]) by vaebh101.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 21 Sep 2009 16:27:07 +0300
Received: from NOK-EUMSG-01.mgdnok.nokia.com ([65.54.30.86]) by nok-am1mhub-01.mgdnok.nokia.com ([65.54.30.5]) with mapi; Mon, 21 Sep 2009 15:26:59 +0200
From: <teemu.savolainen@nokia.com>
To: <Gurpreet.Virdi@microsoft.com>
Date: Mon, 21 Sep 2009 15:25:38 +0200
Thread-Topic: Comments on draft-denis-icmpv6-generation-for-teredo-00
Thread-Index: AcoKOIZyuTOrxeI5S+iI1NyOBmBztwAoFXsAABTsSWAK67NXAAAJaP4QAAKnxIAAATwMwAALPMhgAN+Z2lA=
Message-ID: <18034D4D7FE9AE48BF19AB1B0EF2729F3EF0923E1A@NOK-EUMSG-01.mgdnok.nokia.com>
References: <E4561B14EE2A3E4E9D478EBFB5416E1B1CC7A902@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com> <21052BD84AD96A4E8749DAA4766A4747096F99DF@TK5EX14MBXC122.redmond.corp.microsoft.com> <E4561B14EE2A3E4E9D478EBFB5416E1B1CC7AE58@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com> <21052BD84AD96A4E8749DAA4766A4747096FBED1@TK5EX14MBXC122.redmond.corp.microsoft.com>
In-Reply-To: <21052BD84AD96A4E8749DAA4766A4747096FBED1@TK5EX14MBXC122.redmond.corp.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 21 Sep 2009 13:27:07.0757 (UTC) FILETIME=[377CC9D0:01CA3ABF]
X-Nokia-AV: Clean
Cc: alitu@microsoft.com, behave@ietf.org, dthaler@microsoft.com
Subject: Re: [BEHAVE] Comments on draft-denis-icmpv6-generation-for-teredo-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/mail-archive/web/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>
X-List-Received-Date: Mon, 21 Sep 2009 13:26:49 -0000

Hi,

Thank you for your replies.

R=E9mi responded to 1 and 2, so here's for 3 and 4:=20

>#3: A windows teredo client will today re-do teredo relay=20
>discovery every 15 seconds (3 retransmissions) for a non-TCP=20
>connection and for a TCP connection it will redo relay=20
>discovery (upto 3 retransmissions) when TCP fails to confirms=20
>path reach-ability. If all 3 retransmissions don't end up=20
>getting a ping reply, the connection could potentially break.=20
>Hence, we have to be very careful when rate limiting. A way to=20
>approach this problem could be that instead of rate limiting,=20
>if the traffic increases too much, packets should be forwarded=20
>to the end host and let the end host take care of it.

Well, I'm not sure forwarding is solution (esp. in protocol translator scen=
ario), but smart rate limiting would be. I.e. allow certain number of repli=
es for unique destination (say few every 15 secs matching "legal" Teredo be=
haviour), but not humongous volumes (that resemble unreasonably strange beh=
aviour for Teredo). We can improve text on this issue.

>#4: Perhaps we need to collect data on key applications that=20
>rely on ping replies while choosing a destination address. The=20
>false positive can absolutely have an adverse effect for=20
>example: take a TCP connection which will start on the Teredo=20
>address and then fail after x seconds only after which the=20
>next address in the list *might* be tried. X seconds might be=20
>too long in terms of latency.

Isn't it somewhat dangerous to trust on ping on address selection (due reli=
ability and possible filtering issues)? Doesn't address selection usually w=
ork based on algorithms/preferences and on parallel transport layer connect=
ivity tests? And doesn't all(?) address selection solutions leave Teredo pr=
etty much as last resort connectivity approach "after all other things have=
 failed", and thus there are not many places where to fallback if also Tere=
do connectivity fails (save IP over HTTP)? I.e. the false positive could pr=
olong ultimate connection setup failure a bit, but false negative would mak=
e connection setup fail unnecessarily?

Furthermore, if an application has strict latency requirements, isn't it wa=
ste of time to first spend one RTT on ping test, the time app could've used=
 for app/transport layer signaling?=20

Best regards,

	Teemu=

From cb.list6@gmail.com  Mon Sep 21 10:55:31 2009
Return-Path: <cb.list6@gmail.com>
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 7EF5328C1FC for <behave@core3.amsl.com>; Mon, 21 Sep 2009 10:55:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.574
X-Spam-Level: 
X-Spam-Status: No, score=-2.574 tagged_above=-999 required=5 tests=[AWL=0.025,  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 K6jyf2E81tph for <behave@core3.amsl.com>; Mon, 21 Sep 2009 10:55:30 -0700 (PDT)
Received: from mail-pz0-f180.google.com (mail-pz0-f180.google.com [209.85.222.180]) by core3.amsl.com (Postfix) with ESMTP id 7297D3A6AC8 for <behave@ietf.org>; Mon, 21 Sep 2009 10:55:30 -0700 (PDT)
Received: by pzk10 with SMTP id 10so2378452pzk.19 for <behave@ietf.org>; Mon, 21 Sep 2009 10:56:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=bWdIyLOWLXpqIgR+GkIBVCWlrADIovKL4aHXseT2XMU=; b=cZYFFklJElQuC2MjXiXZaULxBKcdDqKGqwpopGp/w/HXYxstujzZfjmZuIX0PAG0f0 8Y4uzM6I9SbylIp9ximyU9/iAovlXZJ4cpJBQDwypchvprbFJKJBncJ5NMua2bKvWDD6 IPHBS8JmQ2ErFslISacPQNKqn+5EvrUiosgVw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=MrpRqmhEigw15MJz6tq363kzHVQKA8QBgvhMG3SXTzp49vDqNJmQwztBChPh0eReq+ DsSyqjwJtELmyD8+/eejIe4oXerVlGrD0Mji1+sZon2wdPspAIAX27O8YFu4kcH+vtUh H1iALfEwceoYgH9CbvHksRN73+XVTZQAEhqc8=
MIME-Version: 1.0
Received: by 10.142.152.33 with SMTP id z33mr338973wfd.26.1253555788699; Mon,  21 Sep 2009 10:56:28 -0700 (PDT)
In-Reply-To: <6B55F0F93C3E9D45AF283313B8D342BA20F61857@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
References: <4AA7730F.6040602@cernet.edu.cn> <4AB079D5.1010404@cernet.edu.cn> <6B55F0F93C3E9D45AF283313B8D342BA20F5A151@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <4AB191F3.9040305@cernet.edu.cn> <6B55F0F93C3E9D45AF283313B8D342BA20F5C240@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <028301ca381a$bcc47fe0$5da36b80@cisco.com> <6B55F0F93C3E9D45AF283313B8D342BA20F5E923@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <6B55F0F93C3E9D45AF283313B8D342BA20F5E95A@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <4AB43DF5.7060209@cernet.edu.cn> <6B55F0F93C3E9D45AF283313B8D342BA20F61857@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
Date: Mon, 21 Sep 2009 10:56:28 -0700
Message-ID: <bcff0fba0909211056u2b9d5ea1o785e76ad5e701a72@mail.gmail.com>
From: Cameron Byrne <cb.list6@gmail.com>
To: Christian Huitema <huitema@microsoft.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Behave WG <behave@ietf.org>, Xing Li <xing@cernet.edu.cn>, Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] Security implications of protocol translation
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/mail-archive/web/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>
X-List-Received-Date: Mon, 21 Sep 2009 17:55:31 -0000

On Sat, Sep 19, 2009 at 7:13 PM, Christian Huitema
<huitema@microsoft.com> wrote:
>> Not correct, the IPv6 host can configure ONE IPv6 address: That is
>> LIR:IPv4:SUFFIX::/128. When this host communicates with IPv6 Internet,
>> the IPv6 routing system will direct the packets to the right
>> destination. When this host communicates with IPv4 Internet, the IPv6
>> routing system will direct the packets to the stateless translator, then
>> the IPv6 packets will be converted into the IPv4 packets and sent to the
>> right destination via IPv4 routing system.
>
> I understand what you are proposing, but I do not believe that we have WG=
 consensus there. What you are proposing amounts to entirely rework the way=
 IPv6 addresses are configured, in order to better support stateless addres=
s configuration. That may be a tradeoff that the WG wants to support, but i=
t will require some very explicit decision.
>
> Your proposal differs from the current practice in multiple ways. Most no=
ticeably, you propose to replace the current address format (64 bit subnet =
+ 64 bit host ID) by a new format (ISP prefix + 32 bit IPv4 address + paddi=
ng). There is a substantial list of standards that will have to be modified=
 if we want to replace the current practice by your proposal. Of course, we=
 will have to replace the current address configuration procedures. But tha=
t is not all.
>
> For example, in order to make ND work, we will have to map IPv6 subnets t=
o IPv4 subnets, and make sure that the IPv6 subnet is composed of the ISP p=
refix and the "subnet" part of the IPv4 address, and make sure that the "tr=
anslatable" hosts receive addresses in the appropriate IPv4 subnet. Then, w=
e will have to either make sure that the new prefix (ISP + IPv4 subnet) alw=
ays fall on a 64 bit boundary, or, if that cannot be achieved, modify exist=
ing implementations to make sure that they work with arbitrary subnet bound=
aries.
>
> I do not believe that we have WG consensus to specify that. We might obta=
in this consensus if the benefits of easy translation were such that they o=
vercome the burden of modifying standards and implementations. But, frankly=
, I doubt it.
>
> But my biggest problem is that the proposal is only economical if we can =
assign a unique IPv4 address to every host. If we cannot, then network mana=
gers will have to run two parallel addressing schemes. Nodes on the same li=
nks will end up with different address prefixes depending whether they have=
 a "translatable" address or not. Routers will have to manage two parallel =
set of tables.
>
> At the same time, I believe we can obtain the benefit of stateless mappin=
g without having to change existing address management practices. The main =
benefit of your proposal is to simplify the management of stateless transla=
tors, who can algorithmically extract the IPv4 source address from the inco=
ming IPv6 source address. But the translators could just as well obtain the=
 IPv4 source address by a look up in a table of "translatable" addresses. G=
ranted, we will need to pass that table to all stateless translators. But I=
 believe that organizing the distribution of this table is much simpler tha=
n modifying the existing standards and practices for address configuration,=
 neighbor discovery, or subnet management.
>
> -- Christian Huitema

I agree with Christian. The complications with basic functions like ND
is at risk in this stateless model and the requirement for unique IPv4
addresses will not be easy to meet.

-- Cameron Byrne

From xing@cernet.edu.cn  Mon Sep 21 20:00:38 2009
Return-Path: <xing@cernet.edu.cn>
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 E2A1F3A6970 for <behave@core3.amsl.com>; Mon, 21 Sep 2009 20:00:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.638
X-Spam-Level: 
X-Spam-Status: No, score=0.638 tagged_above=-999 required=5 tests=[AWL=0.541,  BAYES_00=-2.599, FH_HAS_XAIMC=2.696]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5B5IH2FVxZKj for <behave@core3.amsl.com>; Mon, 21 Sep 2009 20:00:37 -0700 (PDT)
Received: from cernet.edu.cn (sea.net.edu.cn [202.112.3.66]) by core3.amsl.com (Postfix) with SMTP id 850493A6946 for <behave@ietf.org>; Mon, 21 Sep 2009 20:00:35 -0700 (PDT)
Received: from [59.66.24.75]([59.66.24.75]) by cernet.edu.cn(AIMC 3.2.0.0) with SMTP id jm264ab87b9d; Tue, 22 Sep 2009 11:01:32 +0800
Message-ID: <4AB83E0C.8010104@cernet.edu.cn>
Date: Tue, 22 Sep 2009 11:01:32 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Cameron Byrne <cb.list6@gmail.com>
References: <4AA7730F.6040602@cernet.edu.cn> <4AB079D5.1010404@cernet.edu.cn>	<6B55F0F93C3E9D45AF283313B8D342BA20F5A151@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>	<4AB191F3.9040305@cernet.edu.cn>	<6B55F0F93C3E9D45AF283313B8D342BA20F5C240@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>	<028301ca381a$bcc47fe0$5da36b80@cisco.com>	<6B55F0F93C3E9D45AF283313B8D342BA20F5E923@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>	<6B55F0F93C3E9D45AF283313B8D342BA20F5E95A@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>	<4AB43DF5.7060209@cernet.edu.cn>	<6B55F0F93C3E9D45AF283313B8D342BA20F61857@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <bcff0fba0909211056u2b9d5ea1o785e76ad5e701a72@mail.gmail.com>
In-Reply-To: <bcff0fba0909211056u2b9d5ea1o785e76ad5e701a72@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-AIMC-AUTH: xing
X-AIMC-MAILFROM: xing@cernet.edu.cn
X-AIMC-Msg-ID: NbOdvpWB
Cc: Behave WG <behave@ietf.org>, Dave Thaler <dthaler@microsoft.com>, Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] Security implications of protocol translation
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/mail-archive/web/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>
X-List-Received-Date: Tue, 22 Sep 2009 03:00:39 -0000

Cameron Byrne 写道:
> On Sat, Sep 19, 2009 at 7:13 PM, Christian Huitema
> <huitema@microsoft.com> wrote:
>   
>>> Not correct, the IPv6 host can configure ONE IPv6 address: That is
>>> LIR:IPv4:SUFFIX::/128. When this host communicates with IPv6 Internet,
>>> the IPv6 routing system will direct the packets to the right
>>> destination. When this host communicates with IPv4 Internet, the IPv6
>>> routing system will direct the packets to the stateless translator, then
>>> the IPv6 packets will be converted into the IPv4 packets and sent to the
>>> right destination via IPv4 routing system.
>>>       
>> I understand what you are proposing, but I do not believe that we have WG consensus there. What you are proposing amounts to entirely rework the way IPv6 addresses are configured, in order to better support stateless address configuration. That may be a tradeoff that the WG wants to support, but it will require some very explicit decision.
>>     

No, actually we are doing DHCPv6 configuration or manual configuration 
for the IPv4-translatable addresses. Please note that people usually 
configure the server address manually. Examples are

% host ipv6.google.com
ipv6.google.com is an alias for ipv6.l.google.com.
ipv6.l.google.com has IPv6 address 2001:4860:c004::68

% host ipv6.apnic.net
ipv6.apnic.net has address 202.12.29.122
ipv6.apnic.net has IPv6 address 2001:dc0:2001:b:4608::115

The IPv4-translatable address configuration for the IPv6 host is just 
like this, via DHCPv6 or manual configurations.
>> Your proposal differs from the current practice in multiple ways. Most noticeably, you propose to replace the current address format (64 bit subnet + 64 bit host ID) by a new format (ISP prefix + 32 bit IPv4 address + padding). There is a substantial list of standards that will have to be modified if we want to replace the current practice by your proposal. Of course, we will have to replace the current address configuration procedures. But that is not all.
>>     

We don't think so, it is just manual configuration or DHCPv6 for the 
host address configuration.

>> For example, in order to make ND work, we will have to map IPv6 subnets to IPv4 subnets, and make sure that the IPv6 subnet is composed of the ISP prefix and the "subnet" part of the IPv4 address, and make sure that the "translatable" hosts receive addresses in the appropriate IPv4 subnet. Then, we will have to either make sure that the new prefix (ISP + IPv4 subnet) always fall on a 64 bit boundary, or, if that cannot be achieved, modify existing implementations to make sure that they work with arbitrary subnet boundaries.
>>     

See above. In addition,

(1) Since the IPv6 addresses assigned to the IPv6 hosts are a subset of 
the IPv6 addresses and explicitly define by the NSP prefix and the IPv4 
addresses, the stateless auto-configuration cannot be used and the 
DHCPv6 or manual configuration should be used. We have been using 
dibbler to assign IVI addresses (IPv4-translatable) to the Windows XP 
and Linux hosts without problem.

(2) We have defined a new address format for IVI. In the new format, the 
meaning of u-bit (bit 71) can be kept.

>> I do not believe that we have WG consensus to specify that. We might obtain this consensus if the benefits of easy translation were such that they overcome the burden of modifying standards and implementations. But, frankly, I doubt it.
>>
>> But my biggest problem is that the proposal is only economical if we can assign a unique IPv4 address to every host. If we cannot, then network managers will have to run two parallel addressing schemes. Nodes on the same links will end up with different address prefixes depending whether they have a "translatable" address or not. Routers will have to manage two parallel set of tables.
>>     

We have been working on a new draft, which we call "IPv4 address sharing 
stateless translation", in this scheme, a single IPv4 address can be 
shared by a number of IPv6 hosts.

>> At the same time, I believe we can obtain the benefit of stateless mapping without having to change existing address management practices. The main benefit of your proposal is to simplify the management of stateless translators, who can algorithmically extract the IPv4 source address from the incoming IPv6 source address. But the translators could just as well obtain the IPv4 source address by a look up in a table of "translatable" addresses. Granted, we will need to pass that table to all stateless translators. But I believe that organizing the distribution of this table is much simpler than modifying the existing standards and practices for address configuration, neighbor discovery, or subnet management.
>>     

Yes, this is another alternative. But it also introduces some kind of 
states.
>> -- Christian Huitema
>>     
>
> I agree with Christian. The complications with basic functions like ND
> is at risk in this stateless model and the requirement for unique IPv4
> addresses will not be easy to meet.
>   
We need to handle ND carefully, same as DHCPv6.

regards,

xing

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


From brian.e.carpenter@gmail.com  Mon Sep 21 21:04:01 2009
Return-Path: <brian.e.carpenter@gmail.com>
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 744393A68FC for <behave@core3.amsl.com>; Mon, 21 Sep 2009 21:04:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.437
X-Spam-Level: 
X-Spam-Status: No, score=-2.437 tagged_above=-999 required=5 tests=[AWL=0.162,  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 cUIAbknKjACF for <behave@core3.amsl.com>; Mon, 21 Sep 2009 21:04:00 -0700 (PDT)
Received: from mail-px0-f177.google.com (mail-px0-f177.google.com [209.85.216.177]) by core3.amsl.com (Postfix) with ESMTP id 96D063A68F9 for <behave@ietf.org>; Mon, 21 Sep 2009 21:04:00 -0700 (PDT)
Received: by pxi7 with SMTP id 7so485538pxi.17 for <behave@ietf.org>; Mon, 21 Sep 2009 21:05:00 -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=y714wG9uZ2XW7XHvaMF6LZVv2BSrhb6LMeqQRo747jI=; b=T1AkNVeAcvZ/qZUisNPlONsAzPoCfTiPQ6g5iiXcW8ddNCXCA1P0d00dytKLVu9Y1w vb0mgSwhhEagWeYDwVh3bj+q9U4KDVF0ezxlyEOp2QAwT0T3n4ALjZz7E5dgOEMD0oX8 QDvwqSEMnPMIWREDQ8SeNczpupJGzIUi31//M=
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=ab0VTKJNUnxHzXWUwzobJmzgnwkn4+IdDavSQnHnwo8w54xJXbUfEa/J4/MAO1xosb qXbvdIP5/wUxbH+yWtwDuf3Dth6+b2OyVnMa6RU4gKq9WDG7w0shpsexHw2m74Td0j8y 9Wi5sgz80/CK2TfHkjGrPKpINfP5SUZbq7T0M=
Received: by 10.115.114.7 with SMTP id r7mr820440wam.72.1253592300790; Mon, 21 Sep 2009 21:05:00 -0700 (PDT)
Received: from ?130.216.38.124? (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id 23sm470856pxi.1.2009.09.21.21.04.58 (version=SSLv3 cipher=RC4-MD5); Mon, 21 Sep 2009 21:04:59 -0700 (PDT)
Message-ID: <4AB84CDD.3030600@gmail.com>
Date: Tue, 22 Sep 2009 16:04:45 +1200
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: Zhen Cao <caozhenpku@gmail.com>
References: <a7c8d0a30909150630i29d535bbhf3089fdfecffa328@mail.gmail.com>	 <7CB993A6-829C-46CC-A74C-7DBF7CFE88C6@muada.com>	 <a7c8d0a30909150838s230397d9r3cbffb5df6097b76@mail.gmail.com>	 <273D4852-D26C-497E-A034-2C3EE4908660@muada.com>	 <a7c8d0a30909151846w6f85cc67je3774c93e298f2e1@mail.gmail.com>	 <C37FF658-CF1A-4106-ABD9-2DB18B97B2CF@muada.com>	 <a7c8d0a30909160607l1209993ajae733d2dc116532b@mail.gmail.com>	 <519DB330-54FD-4163-91A8-DF81290A10B5@muada.com>	 <bcff0fba0909160653s59990a8al3cd29d12dab14095@mail.gmail.com>	 <4AB1B88A.6080109@gmail.com> <a7c8d0a30909171829l673de518t228defb0248bd1e9@mail.gmail.com>
In-Reply-To: <a7c8d0a30909171829l673de518t228defb0248bd1e9@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Cameron Byrne <cb.list6@gmail.com>, Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Comments on NAT64 draft
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/mail-archive/web/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>
X-List-Received-Date: Tue, 22 Sep 2009 04:04:01 -0000

On 2009-09-18 13:29, Zhen Cao wrote:
>>>> Any ideas from implementers? Is it problematic to have to buffer and
>>>> reassemble UDP fragments that don't match any state in the v6->v4 direction?
>>> According to RFC 4787 Requirement 14, a NAT MUST accommodate this out
>>> of order fragment situation.
>> This seems extreme; I wonder why it wasn't a SHOULD. However,
>> that's a BCP for IPv4-IPv4 NATs "as described in [RFC2663]."
>> We can decide independently for NAT64, but Iljitsch has asked the
>> right question: how big a deal is this for implementors?
> 
> It might not be a big problem for implementor, considering it only
> hurts the first out-of-order fragmented packet of the flow. Also from
> the statistics you provided several days before, fragmented UDP
> packets counts to a very small percentage.

Correct. But if such packets consume 100 times more resource in the
NAT, they could still be a problem. That's an engineering question,
and I am still not sure of the answer.

> 
> But changing the text in NAT64 is also not a big deal. We can analyze
> this in the document a bit for the consideration of implementors. This
> will do no harm and make the document as solid as possible.

Yes. But I think there is quite a big difference in this case between
a SHOULD and a MUST.

    Brian

From zhouboyj@gmail.com  Tue Sep 22 01:25:15 2009
Return-Path: <zhouboyj@gmail.com>
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 11BD73A68B3 for <behave@core3.amsl.com>; Tue, 22 Sep 2009 01:25:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.003
X-Spam-Level: 
X-Spam-Status: No, score=-0.003 tagged_above=-999 required=5 tests=[AWL=-1.245, BAYES_50=0.001, HTML_MESSAGE=0.001, SARE_LWSHORTT=1.24]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MGuPsqXnw7rf for <behave@core3.amsl.com>; Tue, 22 Sep 2009 01:25:13 -0700 (PDT)
Received: from mail-iw0-f200.google.com (mail-iw0-f200.google.com [209.85.223.200]) by core3.amsl.com (Postfix) with ESMTP id 9A1E53A67A5 for <behave@ietf.org>; Tue, 22 Sep 2009 01:25:13 -0700 (PDT)
Received: by iwn38 with SMTP id 38so1373497iwn.31 for <behave@ietf.org>; Tue, 22 Sep 2009 01:26:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=kjR71ikTipbgcV5kkjQMTFap0vOyXBDafTRLtdoijKg=; b=QfLq1mfaIV3qdnf9jimwKXN89dtHWBmkfm9VYqJjO2QFUIoYMl5gpxbFY/Q4zCQKbU guChyGqupjrK0RwyFyVIcamxdP/jPjUqIxVNKkLBV+uH7dL3UK4xJhWzu9Gu8qFrpy/+ l1CzaFygQth2QvLG4/X7Bkppv1RBPJbWpvg8s=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=x5yh3LoWKDgBL+tMyw91AXfULYTlxTiVpi5zh5cT+9sYcDlaTQLsr/jx12BJn4HZ6+ 8nuOqXvdjQelSMDeMf90qjWDOcgQzArjoK7cHZSezyfcRc/XP2+ZAAZ705oMCARLUIdl vAMzP/KJeh2H/BOZtucecCHtAgkW1ztENH0aE=
MIME-Version: 1.0
Received: by 10.231.125.13 with SMTP id w13mr1416778ibr.32.1253607973154; Tue,  22 Sep 2009 01:26:13 -0700 (PDT)
Date: Tue, 22 Sep 2009 16:26:13 +0800
Message-ID: <36a593230909220126r76aaa704lb4206e82cdb967aa@mail.gmail.com>
From: bo zhou <zhouboyj@gmail.com>
To: Dan Wing <dwing@cisco.com>, Dave Thaler <dthaler@microsoft.com>, Behave WG <behave@ietf.org>
Content-Type: multipart/alternative; boundary=0016e64ea928ed73ef0474265972
Subject: [BEHAVE] [behave] Call for presentations and participation: CHINA MOBILE WORKSHOP ON IPV6 DEPLOYMENT IN CELLULAR 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/mail-archive/web/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>
X-List-Received-Date: Tue, 22 Sep 2009 08:25:15 -0000

--0016e64ea928ed73ef0474265972
Content-Type: text/plain; charset=ISO-8859-1

Call for presentations and participation



CHINA MOBILE WORKSHOP ON IPV6 DEPLOYMENT IN CELLULAR NETWORKS



Location: Shanghai, China

Date: November November 5-6th, 2009

Official website: http://www.global-fair.cn/ipv6/index.asp



Internet growth faces a significant challenge in the coming years, as the
pool of remaining unallocated IPv4 address space is expected to be depleted.
At the same time new applications and connectivity options are multiplying
the number of Internet users. For instance, billions of mobile phone users
are expected to require IP connectivity in the coming years, either for
traditional Internet services or the eventual move of circuit switched voice
to IP.



The lack of addresses will have many impacts in the short term. But the
networking community has also come to the realization that long term, the
only viable model is to move to IPv6, as IPv6 allows a significantly larger
number of devices to be addressed. Network operators, equipment vendors, and
various organizations have been readying their systems to prepare for this.
The pace of these preparations has picked up in recent year as the final end
of IPv4 resources has become clearer. However, while IPv6 traffic is growing
and there is widespread product support for IPv6, on a global scale IPv6
connectivity is still available only in a fraction of networks. Improving
the situation requires time, effort, commercial incentives, and technology.
The commercial incentives exist often initially only for specific problem
domains. Once a tipping point is reached a more general demand drives the
remainder of the deployment.



The goal of this workshop is to look at IPv6 deployment in the context of
GPRS, UMTS, and LTE cellular networks. Technology to provide IPv6
connectivity has existed in these networks since 2003, after 3GPP Release 5
provided the necessary standards to support standard dual stack operation,
enabling both IPv4 and IPv6 connectivity. Most of the network components
that you can buy today support this, and countless trials have been run.
However, no commercial deployments have turned IPv6 on to date. Part of the
reason for this is that only a subset of terminals support IPv6, and that so
far, it has been possible to run cellular networks on IPv4 addresses.
However, the increase in the number of users and the desire to run always-on
and address & port hungry applications may make this harder in the future.



This workshop focuses on the operational, business, and technical enablers
that would allow us to move faster to an IPv6 enabled commercial deployment.
The topics suitable for the meeting include:



- implementation and test reports

- operational experiences

- business requirements for specific scenarios

- reports of ongoing IETF activities

- IPv6 functionality in 3GPP networks



The main focus of the workshop is discussion of the requirements, sharing of
experiences, and gaining an understanding of what further actions might help
IPv6 deployment. Note that the workshop is not a forum to create new IPv6
transition tools or the further development of existing ones. Working groups
in the IETF are the right place for that.



This workshop is also not the place to agree on specific changes to cellular
network standards. Such changes are a topic for the 3GPP.

However, by bringing this workshop together, China Mobile hopes to promote a
better understanding of this problem space and requirements, and provide
input to the standardization efforts in the IETF and 3GPP.



If you have any questions related to this workshop, please feel free to
contact with local committees:

Workshop co-chair: Hui Deng, denghui@chinamobile.com, Tel: +86 13910750201

Assistant: Bo Zhou, zhouboyj@chinamobile.com , Tel: +86 13811948723

-- 
Regards,

Bo Zhou
China Mobile

--0016e64ea928ed73ef0474265972
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br clear=3D"all">
<div></div>
<p class=3D"MsoNormal" style=3D"MARGIN: 0cm 0cm 0pt; LAYOUT-GRID-MODE: char=
; mso-pagination: widow-orphan"><span lang=3D"EN-US" style=3D"mso-bidi-font=
-size: 10.5pt; mso-font-kerning: 0pt"><font size=3D"3"><font face=3D"Times =
New Roman">Call for presentations and participation</font></font></span></p=
>

<p class=3D"MsoNormal" style=3D"MARGIN: 0cm 0cm 0pt; LAYOUT-GRID-MODE: char=
; mso-pagination: widow-orphan"><span lang=3D"EN-US" style=3D"mso-bidi-font=
-size: 10.5pt; mso-font-kerning: 0pt"><font face=3D"Times New Roman" size=
=3D"3">=A0</font></span></p>

<p class=3D"MsoNormal" style=3D"MARGIN: 0cm 0cm 0pt; LAYOUT-GRID-MODE: char=
; mso-pagination: widow-orphan"><font size=3D"3"><font face=3D"Times New Ro=
man"><span lang=3D"EN-US" style=3D"mso-bidi-font-size: 10.5pt; mso-font-ker=
ning: 0pt">CHINA</span><span lang=3D"EN-US" style=3D"mso-bidi-font-size: 10=
.5pt; mso-font-kerning: 0pt"> MOBILE WORKSHOP ON IPV6 DEPLOYMENT IN CELLULA=
R NETWORKS</span></font></font></p>

<p class=3D"MsoNormal" style=3D"MARGIN: 0cm 0cm 0pt; LAYOUT-GRID-MODE: char=
; mso-pagination: widow-orphan"><span lang=3D"EN-US" style=3D"mso-bidi-font=
-size: 10.5pt; mso-font-kerning: 0pt"><font face=3D"Times New Roman" size=
=3D"3">=A0</font></span></p>

<p class=3D"MsoNormal" style=3D"MARGIN: 0cm 0cm 0pt; LAYOUT-GRID-MODE: char=
; mso-pagination: widow-orphan"><span lang=3D"EN-US" style=3D"mso-bidi-font=
-size: 10.5pt; mso-font-kerning: 0pt"><font size=3D"3"><font face=3D"Times =
New Roman">Location: Shanghai, China</font></font></span></p>

<p class=3D"MsoNormal" style=3D"MARGIN: 0cm 0cm 0pt; LAYOUT-GRID-MODE: char=
; mso-pagination: widow-orphan"><span lang=3D"EN-US" style=3D"mso-bidi-font=
-size: 10.5pt; mso-font-kerning: 0pt"><font size=3D"3"><font face=3D"Times =
New Roman">Date: November November 5-6th, 2009</font></font></span></p>

<p class=3D"MsoNormal" style=3D"MARGIN: 0cm 0cm 0pt; LAYOUT-GRID-MODE: char=
; mso-pagination: widow-orphan"><span lang=3D"EN-US" style=3D"mso-bidi-font=
-size: 10.5pt; mso-font-kerning: 0pt"><font face=3D"Times New Roman" size=
=3D"3">Official website: </font><a href=3D"http://www.global-fair.cn/ipv6/i=
ndex.asp"><font face=3D"Times New Roman" color=3D"#800080" size=3D"3">http:=
//www.global-fair.cn/ipv6/index.asp</font></a></span></p>

<p class=3D"MsoNormal" style=3D"MARGIN: 0cm 0cm 0pt; LAYOUT-GRID-MODE: char=
; mso-pagination: widow-orphan"><span lang=3D"EN-US" style=3D"mso-bidi-font=
-size: 10.5pt; mso-font-kerning: 0pt"><font face=3D"Times New Roman" size=
=3D"3">=A0</font></span></p>

<p class=3D"MsoNormal" style=3D"MARGIN: 0cm 0cm 0pt; LAYOUT-GRID-MODE: char=
; mso-pagination: widow-orphan"><span lang=3D"EN-US" style=3D"mso-bidi-font=
-size: 10.5pt; mso-font-kerning: 0pt"><font size=3D"3"><font face=3D"Times =
New Roman">Internet growth faces a significant challenge in the coming year=
s, as the pool of remaining unallocated IPv4 address space is expected to b=
e depleted. At the same time new applications and connectivity options are =
multiplying the number of Internet users. For instance, billions of mobile =
phone users are expected to require IP connectivity in the coming years, ei=
ther for traditional Internet services or the eventual move of circuit swit=
ched voice to IP.</font></font></span></p>

<p class=3D"MsoNormal" style=3D"MARGIN: 0cm 0cm 0pt; LAYOUT-GRID-MODE: char=
; mso-pagination: widow-orphan"><span lang=3D"EN-US" style=3D"mso-bidi-font=
-size: 10.5pt; mso-font-kerning: 0pt"><font face=3D"Times New Roman" size=
=3D"3">=A0</font></span></p>

<p class=3D"MsoNormal" style=3D"MARGIN: 0cm 0cm 0pt; LAYOUT-GRID-MODE: char=
; mso-pagination: widow-orphan"><span lang=3D"EN-US" style=3D"mso-bidi-font=
-size: 10.5pt; mso-font-kerning: 0pt"><font size=3D"3"><font face=3D"Times =
New Roman">The lack of addresses will have many impacts in the short term. =
But the networking community has also come to the realization that long ter=
m, the only viable model is to move to IPv6, as IPv6 allows a significantly=
 larger number of devices to be addressed. Network operators, equipment ven=
dors, and various organizations have been readying their systems to prepare=
 for this. The pace of these preparations has picked up in recent year as t=
he final end of IPv4 resources has become clearer. However, while IPv6 traf=
fic is growing and there is widespread product support for IPv6, on a globa=
l scale IPv6 connectivity is still available only in a fraction of networks=
. Improving the situation requires time, effort, commercial incentives, and=
 technology. The commercial incentives exist often initially only for speci=
fic problem domains. Once a tipping point is reached a more general demand =
drives the remainder of the deployment.</font></font></span></p>

<p class=3D"MsoNormal" style=3D"MARGIN: 0cm 0cm 0pt; LAYOUT-GRID-MODE: char=
; mso-pagination: widow-orphan"><span lang=3D"EN-US" style=3D"mso-bidi-font=
-size: 10.5pt; mso-font-kerning: 0pt"><font face=3D"Times New Roman" size=
=3D"3">=A0</font></span></p>

<p class=3D"MsoNormal" style=3D"MARGIN: 0cm 0cm 0pt; LAYOUT-GRID-MODE: char=
; mso-pagination: widow-orphan"><span lang=3D"EN-US" style=3D"mso-bidi-font=
-size: 10.5pt; mso-font-kerning: 0pt"><font size=3D"3"><font face=3D"Times =
New Roman">The goal of this workshop is to look at IPv6 deployment in the c=
ontext of GPRS, UMTS, and LTE cellular networks. Technology to provide IPv6=
 connectivity has existed in these networks since 2003, after 3GPP Release =
5 provided the necessary standards to support standard dual stack operation=
, enabling both IPv4 and IPv6 connectivity. Most of the network components =
that you can buy today support this, and countless trials have been run. Ho=
wever, no commercial deployments have turned IPv6 on to date. Part of the r=
eason for this is that only a subset of terminals support IPv6, and that so=
 far, it has been possible to run cellular networks on IPv4 addresses. Howe=
ver, the increase in the number of users and the desire to run always-on an=
d address &amp; port hungry applications may make this harder in the future=
.</font></font></span></p>

<p class=3D"MsoNormal" style=3D"MARGIN: 0cm 0cm 0pt; LAYOUT-GRID-MODE: char=
; mso-pagination: widow-orphan"><span lang=3D"EN-US" style=3D"mso-bidi-font=
-size: 10.5pt; mso-font-kerning: 0pt"><font face=3D"Times New Roman" size=
=3D"3">=A0</font></span></p>

<p class=3D"MsoNormal" style=3D"MARGIN: 0cm 0cm 0pt; LAYOUT-GRID-MODE: char=
; mso-pagination: widow-orphan"><span lang=3D"EN-US" style=3D"mso-bidi-font=
-size: 10.5pt; mso-font-kerning: 0pt"><font size=3D"3"><font face=3D"Times =
New Roman">This workshop focuses on the operational, business, and technica=
l enablers that would allow us to move faster to an IPv6 enabled commercial=
 deployment. The topics suitable for the meeting include:</font></font></sp=
an></p>

<p class=3D"MsoNormal" style=3D"MARGIN: 0cm 0cm 0pt; LAYOUT-GRID-MODE: char=
; mso-pagination: widow-orphan"><span lang=3D"EN-US" style=3D"mso-bidi-font=
-size: 10.5pt; mso-font-kerning: 0pt"><font face=3D"Times New Roman" size=
=3D"3">=A0</font></span></p>

<p class=3D"MsoNormal" style=3D"MARGIN: 0cm 0cm 0pt; LAYOUT-GRID-MODE: char=
; mso-pagination: widow-orphan"><span lang=3D"EN-US" style=3D"mso-bidi-font=
-size: 10.5pt; mso-font-kerning: 0pt"><font size=3D"3"><font face=3D"Times =
New Roman">- implementation and test reports</font></font></span></p>

<p class=3D"MsoNormal" style=3D"MARGIN: 0cm 0cm 0pt; LAYOUT-GRID-MODE: char=
; mso-pagination: widow-orphan"><span lang=3D"EN-US" style=3D"mso-bidi-font=
-size: 10.5pt; mso-font-kerning: 0pt"><font size=3D"3"><font face=3D"Times =
New Roman">- operational experiences</font></font></span></p>

<p class=3D"MsoNormal" style=3D"MARGIN: 0cm 0cm 0pt; LAYOUT-GRID-MODE: char=
; mso-pagination: widow-orphan"><span lang=3D"EN-US" style=3D"mso-bidi-font=
-size: 10.5pt; mso-font-kerning: 0pt"><font size=3D"3"><font face=3D"Times =
New Roman">- business requirements for specific scenarios</font></font></sp=
an></p>

<p class=3D"MsoNormal" style=3D"MARGIN: 0cm 0cm 0pt; LAYOUT-GRID-MODE: char=
; mso-pagination: widow-orphan"><span lang=3D"EN-US" style=3D"mso-bidi-font=
-size: 10.5pt; mso-font-kerning: 0pt"><font size=3D"3"><font face=3D"Times =
New Roman">- reports of ongoing IETF activities</font></font></span></p>

<p class=3D"MsoNormal" style=3D"MARGIN: 0cm 0cm 0pt; LAYOUT-GRID-MODE: char=
; mso-pagination: widow-orphan"><span lang=3D"EN-US" style=3D"mso-bidi-font=
-size: 10.5pt; mso-font-kerning: 0pt"><font size=3D"3"><font face=3D"Times =
New Roman">- IPv6 functionality in 3GPP networks</font></font></span></p>

<p class=3D"MsoNormal" style=3D"MARGIN: 0cm 0cm 0pt; LAYOUT-GRID-MODE: char=
; mso-pagination: widow-orphan"><span lang=3D"EN-US" style=3D"mso-bidi-font=
-size: 10.5pt; mso-font-kerning: 0pt"><font face=3D"Times New Roman" size=
=3D"3">=A0</font></span></p>

<p class=3D"MsoNormal" style=3D"MARGIN: 0cm 0cm 0pt; LAYOUT-GRID-MODE: char=
; mso-pagination: widow-orphan"><span lang=3D"EN-US" style=3D"mso-bidi-font=
-size: 10.5pt; mso-font-kerning: 0pt"><font size=3D"3"><font face=3D"Times =
New Roman">The main focus of the workshop is discussion of the requirements=
, sharing of experiences, and gaining an understanding of what further acti=
ons might help IPv6 deployment. Note that the workshop is not a forum to cr=
eate new IPv6 transition tools or the further development of existing ones.=
 Working groups in the IETF are the right place for that. </font></font></s=
pan></p>

<p class=3D"MsoNormal" style=3D"MARGIN: 0cm 0cm 0pt; LAYOUT-GRID-MODE: char=
; mso-pagination: widow-orphan"><span lang=3D"EN-US" style=3D"mso-bidi-font=
-size: 10.5pt; mso-font-kerning: 0pt"><font face=3D"Times New Roman" size=
=3D"3">=A0</font></span></p>

<p class=3D"MsoNormal" style=3D"MARGIN: 0cm 0cm 0pt; LAYOUT-GRID-MODE: char=
; mso-pagination: widow-orphan"><span lang=3D"EN-US" style=3D"mso-bidi-font=
-size: 10.5pt; mso-font-kerning: 0pt"><font size=3D"3"><font face=3D"Times =
New Roman">This workshop is also not the place to agree on specific changes=
 to cellular network standards. Such changes are a topic for the 3GPP. </fo=
nt></font></span></p>

<p class=3D"MsoNormal" style=3D"MARGIN: 0cm 0cm 0pt; LAYOUT-GRID-MODE: char=
; mso-pagination: widow-orphan"><span lang=3D"EN-US" style=3D"mso-bidi-font=
-size: 10.5pt; mso-font-kerning: 0pt"><font size=3D"3"><font face=3D"Times =
New Roman">However, by bringing this workshop together, China Mobile hopes =
to promote a better understanding of this problem space and requirements, a=
nd provide input to the standardization efforts in the IETF and 3GPP.</font=
></font></span></p>

<p class=3D"MsoNormal" style=3D"MARGIN: 0cm 0cm 0pt"><span lang=3D"EN-US" s=
tyle=3D"mso-bidi-font-size: 10.5pt"><font face=3D"Times New Roman" size=3D"=
3">=A0</font></span></p>
<p class=3D"MsoNormal" style=3D"MARGIN: 0cm 0cm 0pt"><span lang=3D"EN-US" s=
tyle=3D"mso-bidi-font-size: 10.5pt"><font size=3D"3"><font face=3D"Times Ne=
w Roman">If you have any questions related to this workshop, please feel fr=
ee to contact with local committees:</font></font></span></p>

<p class=3D"MsoNormal" style=3D"MARGIN: 0cm 0cm 0pt"><span lang=3D"EN-US" s=
tyle=3D"mso-bidi-font-size: 10.5pt"><font face=3D"Times New Roman" size=3D"=
3">Workshop co-chair: Hui Deng, </font><a href=3D"mailto:denghui@chinamobil=
e.com"><font face=3D"Times New Roman" size=3D"3">denghui@chinamobile.com</f=
ont></a><font size=3D"3"><font face=3D"Times New Roman">, Tel: +86 13910750=
201</font></font></span></p>

<p class=3D"MsoNormal" style=3D"MARGIN: 0cm 0cm 0pt"><span lang=3D"EN-US" s=
tyle=3D"mso-bidi-font-size: 10.5pt"><font face=3D"Times New Roman" size=3D"=
3">Assistant: Bo Zhou, </font><a href=3D"mailto:zhouboyj@chinamobile.com"><=
font face=3D"Times New Roman" size=3D"3">zhouboyj@chinamobile.com</font></a=
><font size=3D"3"><font face=3D"Times New Roman"> , Tel: +86 13811948723</f=
ont></font></span></p>
<br>-- <br>Regards,<br><br>Bo Zhou<br>China Mobile<br>

--0016e64ea928ed73ef0474265972--

From Gurpreet.Virdi@microsoft.com  Mon Sep 21 10:01:07 2009
Return-Path: <Gurpreet.Virdi@microsoft.com>
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 0FD793A6980 for <behave@core3.amsl.com>; Mon, 21 Sep 2009 10:01:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.449
X-Spam-Level: 
X-Spam-Status: No, score=-10.449 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1zuUKQHHCjKM for <behave@core3.amsl.com>; Mon, 21 Sep 2009 10:01:06 -0700 (PDT)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.212]) by core3.amsl.com (Postfix) with ESMTP id D178C28C1C0 for <behave@ietf.org>; Mon, 21 Sep 2009 10:01:05 -0700 (PDT)
Received: from TK5EX14MLTC102.redmond.corp.microsoft.com (157.54.79.180) by TK5-EXGWY-E801.partners.extranet.microsoft.com (10.251.56.50) with Microsoft SMTP Server (TLS) id 8.2.176.0; Mon, 21 Sep 2009 10:02:07 -0700
Received: from TK5EX14MBXC124.redmond.corp.microsoft.com ([169.254.4.223]) by TK5EX14MLTC102.redmond.corp.microsoft.com ([157.54.79.180]) with mapi; Mon, 21 Sep 2009 10:01:43 -0700
From: Gurpreet Virdi <Gurpreet.Virdi@microsoft.com>
To: =?iso-8859-1?Q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>, "behave@ietf.org" <behave@ietf.org>
Thread-Topic: [BEHAVE] Comments on draft-denis-icmpv6-generation-for-teredo-00
Thread-Index: AQHKOq36y8hTENFj+UGlIIwGZarYS5DhQfDe
Date: Mon, 21 Sep 2009 17:01:42 +0000
Message-ID: <21052BD84AD96A4E8749DAA4766A47470DAEF606@TK5EX14MBXC124.redmond.corp.microsoft.com>
References: <E4561B14EE2A3E4E9D478EBFB5416E1B1CC7A902@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com> <E4561B14EE2A3E4E9D478EBFB5416E1B1CC7AE58@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com> <21052BD84AD96A4E8749DAA4766A4747096FBED1@TK5EX14MBXC122.redmond.corp.microsoft.com>, <200909211423.12092.remi.denis-courmont@nokia.com>
In-Reply-To: <200909211423.12092.remi.denis-courmont@nokia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Tue, 22 Sep 2009 09:41:29 -0700
Cc: Ali Turkoglu <alitu@microsoft.com>, Dave Thaler <dthaler@microsoft.com>
Subject: Re: [BEHAVE] Comments on draft-denis-icmpv6-generation-for-teredo-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/mail-archive/web/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>
X-List-Received-Date: Mon, 21 Sep 2009 17:01:07 -0000

#1: If we are guranteed that the network infrastructure is dropping ICMPV6 =
Echo Requests, then I agree to you. But if we are not, I would rather argue=
 that the proposal in this draft could end up breaking teredo relay functio=
naility. Here is why. With the proposal in the draft, teredo relay function=
aility ends up depending on relays hosted out in the wild instead of host-b=
ased relay (windows clients by default are host-based relays). Is it gurant=
eed that there will be a teredo relay hosted in the wild that will end up g=
etting hit for this host machine? If yes, then once again i think that this=
 draft is good to go. But if not, we could end up breaking a connection tha=
t could have potentially succeeded with host specific relay (rather than re=
lying on a relay hosted in the wild which doesn't quite exist).

#2: I agree to you in that indeed a teredo relay should take care of this. =
All I was pointing out was that in terms of talking about backward *compati=
bility* or rather supporting backward behaviour..this draft might have made=
 it worse for existing Teredo relays deployed in the world.=20

Thanks
Gurpreet

 ________________________________________
From: R=E9mi Denis-Courmont [remi.denis-courmont@nokia.com]
Sent: Monday, September 21, 2009 4:23 AM
To: behave@ietf.org
Cc: Gurpreet Virdi; Savolainen Teemu (Nokia-D-MSW/Tampere); Ali Turkoglu; D=
ave Thaler
Subject: Re: [BEHAVE] Comments on draft-denis-icmpv6-generation-for-teredo-=
00

On Thursday 17 September 2009 23:25:06 ext Gurpreet Virdi wrote:
> Hi Teemu,
>
> I am part of the Teredo team at Microsoft and I had some comments about #=
1,
> #2, #3 and #4 points you mention below. Here are my comments:
>
> #1: The draft now says "Furthermore, the IPv6 firewall might not be on th=
e
> return data path in which case generated ICMPv6 Echo Replies might break
> Teredo host-based relay feature.". This might seem a little confusing. Se=
e
> in both the host-based relay features and non-host-based relay
> feature....the firewall might be on the return data path. The difference =
is
> that in the host-based relay feature, the ICMPV6 Echo Reply packet hits t=
he
> relay *before* hitting the IPV6 firewall (the host itself is the relay!!!=
).
> And in the non host-based relay feature, the ICMPV6 Echo Reply packet wil=
l
> hit the relay after hitting this IPV6 firewall. Hence, the host-based rel=
ay
> feature will not work with this draft.

It does not *break* the host-based relay feature. A host-based relay behind=
 an
ICMPv6-filtering network infrastructure is broken to start with. Or then I
missed something...

Adding ICMPv6 generation into the picture does not fix the problem, but it
does not make it much worse either. On top of that, running a host-based
relays would most probably break the firewall policy (as tunneled would not=
 be
"seen" by the firewalls).

> #2: Currently Teredo relay discovery only succeeds when the following
> conditions are met A) if the firewall on the peer machine exempts ICMPV6
> Echo Request and B) if the IPV6 address is a valid IPV6 address belonging
> to a peer machine that is up & running.
>
> Now A is not common by default. In windows teredo clients, the time this =
is
> most common is when the peer is a host-based relay and I will not talk
> about it in detail, because you have already mentioned it in the draft as
> being one of the cases where the IPV6 firewall will not reply to pings.
>
> Now B, requires that the attacker to guess your 128 bit IPV6 address
> correctly.
>
> But with this draft, Teredo relay discovery will now succeed even if the
> above 2 conditions i.e. A & B are not met. So potentially an attacker cou=
ld
> go around sending pings to all sorts of address ranges and ping replies
> from the IPV6 firewall in front of these machines will help in discoverin=
g
> Teredo relays around the world.

Yes, this is a security consideration. But is it a problem? if you don't wa=
nt
your relay to be discovered, you should simply *not* filter inbound ICMPv6.=
 If
you do inbound ICMPv6, then your Teredo relay is totally useless anyway.

This is just the same issue as #1 really: why would one run a Teredo relay =
if
one implements a firewall filtering policy that is fundamentally incompatib=
le
with Teredo?

> This can certainly be mitigated by taking measures like: the firewall
> should only respond to ping requests that are destined to actual *active*
> IPV6 addresses behind the firewall.

Exactly, but this is hardly realistic implementation-wise.

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

From Gurpreet.Virdi@microsoft.com  Mon Sep 21 10:03:04 2009
Return-Path: <Gurpreet.Virdi@microsoft.com>
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 C9B4C28C19E for <behave@core3.amsl.com>; Mon, 21 Sep 2009 10:03:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.549
X-Spam-Level: 
X-Spam-Status: No, score=-10.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nNWWXj5+-Qou for <behave@core3.amsl.com>; Mon, 21 Sep 2009 10:03:04 -0700 (PDT)
Received: from smtp.microsoft.com (mailb.microsoft.com [131.107.115.215]) by core3.amsl.com (Postfix) with ESMTP id ED63028C1C7 for <behave@ietf.org>; Mon, 21 Sep 2009 10:03:03 -0700 (PDT)
Received: from TK5EX14MLTC103.redmond.corp.microsoft.com (157.54.79.174) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.176.0; Mon, 21 Sep 2009 10:04:05 -0700
Received: from TK5EX14MBXC124.redmond.corp.microsoft.com ([169.254.4.223]) by TK5EX14MLTC103.redmond.corp.microsoft.com ([157.54.79.174]) with mapi; Mon, 21 Sep 2009 10:04:05 -0700
From: Gurpreet Virdi <Gurpreet.Virdi@microsoft.com>
To: "teemu.savolainen@nokia.com" <teemu.savolainen@nokia.com>
Thread-Topic: Comments on draft-denis-icmpv6-generation-for-teredo-00
Thread-Index: AcoKOIZyuTOrxeI5S+iI1NyOBmBztwAoFXsAABTsSWAK67NXAAAJaP4QAAKnxIAAATwMwAALPMhgAN+Z2lAACFVyjg==
Date: Mon, 21 Sep 2009 17:02:04 +0000
Message-ID: <21052BD84AD96A4E8749DAA4766A47470DAF1DD1@TK5EX14MBXC124.redmond.corp.microsoft.com>
References: <E4561B14EE2A3E4E9D478EBFB5416E1B1CC7A902@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com> <21052BD84AD96A4E8749DAA4766A4747096F99DF@TK5EX14MBXC122.redmond.corp.microsoft.com> <E4561B14EE2A3E4E9D478EBFB5416E1B1CC7AE58@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com> <21052BD84AD96A4E8749DAA4766A4747096FBED1@TK5EX14MBXC122.redmond.corp.microsoft.com>, <18034D4D7FE9AE48BF19AB1B0EF2729F3EF0923E1A@NOK-EUMSG-01.mgdnok.nokia.com>
In-Reply-To: <18034D4D7FE9AE48BF19AB1B0EF2729F3EF0923E1A@NOK-EUMSG-01.mgdnok.nokia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Tue, 22 Sep 2009 09:41:30 -0700
Cc: Ali Turkoglu <alitu@microsoft.com>, "behave@ietf.org" <behave@ietf.org>, Dave Thaler <dthaler@microsoft.com>
Subject: Re: [BEHAVE] Comments on draft-denis-icmpv6-generation-for-teredo-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/mail-archive/web/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>
X-List-Received-Date: Mon, 21 Sep 2009 17:03:04 -0000

#3: Ok. Sounds good. I will look forward to the modified draft.

#4: Correct in the sense that apps should not use ping to detect reachabili=
ty etc.. But the reality is that some apps do that and it wouldn't be good =
to break them. So my suggestion would be to do a survey on applications tha=
t use this kind of a ping model.

Thanks
Gurpreet
________________________________________
From: teemu.savolainen@nokia.com [teemu.savolainen@nokia.com]
Sent: Monday, September 21, 2009 6:25 AM
To: Gurpreet Virdi
Cc: Dave Thaler; Ali Turkoglu; behave@ietf.org
Subject: RE: Comments on draft-denis-icmpv6-generation-for-teredo-00

Hi,

Thank you for your replies.

R=E9mi responded to 1 and 2, so here's for 3 and 4:

>#3: A windows teredo client will today re-do teredo relay
>discovery every 15 seconds (3 retransmissions) for a non-TCP
>connection and for a TCP connection it will redo relay
>discovery (upto 3 retransmissions) when TCP fails to confirms
>path reach-ability. If all 3 retransmissions don't end up
>getting a ping reply, the connection could potentially break.
>Hence, we have to be very careful when rate limiting. A way to
>approach this problem could be that instead of rate limiting,
>if the traffic increases too much, packets should be forwarded
>to the end host and let the end host take care of it.

Well, I'm not sure forwarding is solution (esp. in protocol translator scen=
ario), but smart rate limiting would be. I.e. allow certain number of repli=
es for unique destination (say few every 15 secs matching "legal" Teredo be=
haviour), but not humongous volumes (that resemble unreasonably strange beh=
aviour for Teredo). We can improve text on this issue.

>#4: Perhaps we need to collect data on key applications that
>rely on ping replies while choosing a destination address. The
>false positive can absolutely have an adverse effect for
>example: take a TCP connection which will start on the Teredo
>address and then fail after x seconds only after which the
>next address in the list *might* be tried. X seconds might be
>too long in terms of latency.

Isn't it somewhat dangerous to trust on ping on address selection (due reli=
ability and possible filtering issues)? Doesn't address selection usually w=
ork based on algorithms/preferences and on parallel transport layer connect=
ivity tests? And doesn't all(?) address selection solutions leave Teredo pr=
etty much as last resort connectivity approach "after all other things have=
 failed", and thus there are not many places where to fallback if also Tere=
do connectivity fails (save IP over HTTP)? I.e. the false positive could pr=
olong ultimate connection setup failure a bit, but false negative would mak=
e connection setup fail unnecessarily?

Furthermore, if an application has strict latency requirements, isn't it wa=
ste of time to first spend one RTT on ping test, the time app could've used=
 for app/transport layer signaling?

Best regards,

        Teemu=

From dthaler@microsoft.com  Tue Sep 22 17:17:24 2009
Return-Path: <dthaler@microsoft.com>
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 B59DA3A68F8 for <behave@core3.amsl.com>; Tue, 22 Sep 2009 17:17:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.484
X-Spam-Level: 
X-Spam-Status: No, score=-10.484 tagged_above=-999 required=5 tests=[AWL=0.115, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 57uuGXWBqFJI for <behave@core3.amsl.com>; Tue, 22 Sep 2009 17:17:22 -0700 (PDT)
Received: from smtp.microsoft.com (mailc.microsoft.com [131.107.115.214]) by core3.amsl.com (Postfix) with ESMTP id 8A7323A67B0 for <behave@ietf.org>; Tue, 22 Sep 2009 17:17:22 -0700 (PDT)
Received: from TK5EX14HUBC102.redmond.corp.microsoft.com (157.54.7.154) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.2.176.0; Tue, 22 Sep 2009 17:18:14 -0700
Received: from TK5EX14MLTW651.wingroup.windeploy.ntdev.microsoft.com (157.54.71.39) by TK5EX14HUBC102.redmond.corp.microsoft.com (157.54.7.154) with Microsoft SMTP Server id 14.0.639.20; Tue, 22 Sep 2009 17:18:14 -0700
Received: from TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com ([169.254.3.19]) by TK5EX14MLTW651.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.39]) with mapi; Tue, 22 Sep 2009 17:18:14 -0700
From: Dave Thaler <dthaler@microsoft.com>
To: Behave WG <behave@ietf.org>
Thread-Topic: Minutes from Sept. interim teleconference
Thread-Index: Aco741bpkvzgZxSVQ46J0IG19KIv3Q==
Date: Wed, 23 Sep 2009 00:18:13 +0000
Message-ID: <E4561B14EE2A3E4E9D478EBFB5416E1B21EE11C9@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [BEHAVE] Minutes from Sept. interim teleconference
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/mail-archive/web/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>
X-List-Received-Date: Wed, 23 Sep 2009 00:17:25 -0000

Below are the proposed minutes from last week's interim
conf call.  Please send any additions/corrections.
As a reminder, it is also IETF policy to confirm consensus on=20
the list, so the WG is invited to review the items listed as=20
consensus-among-those-present.

-Dave


BEHAVE Interim meeting minutes, Sept. 17, 2009, 7am-9:10am PDT
Attendance was via WebEx screen sharing and PSTN voice
Chairs: Dan Wing, dwing@cisco.com, Dave Thaler, dthaler@microsoft.com
WebEx recording: https://cisco.webex.com/ciscosales/lsr.php?AT=3Dpb&SP=3DMC=
&rID=3D40376397&rKey=3D4126d72ee3b4a9cc


Attendees
-----------------
Dan Wing (chair)
Dave Thaler (chair)
Agnes Tow
Bo Zhou
Cameron Byrne
Dan Romascanu
Dean Chung
Fred Baker
Heinrich Haager
Hui Deng
Iljitsch van Beijnum
Jacni Qin
Lin Xiao
Liu Dapeng
Magnus Westerlund
Marcelo Bagnulo
Philip Matthews
Simon Perreault
Teemu Savolainen
Zhen Cao

Notes taken by Dave Thaler

draft-ietf-behave-v6v4-xlate-01: Xing Li
----------------------------------------
Multicast packets reference address format docs
Marcelo - we should do it in a different document, maybe Stig's
Xing - no preference
Magnus - reasonable to push out to a separate doc
Dan - let's talk about this during the DNS64 update on the agenda

Terminology: use of "network-specific prefix (NSP)" vs "LIR prefix"
    The consensus among those present was to use NSP since it applies=20
    better to other cases such as home gateways.  The NSP definition=20
    still needs some work though.

Terminology: use of "mapped" and "translatable" etc
    The consensus among those present was to not define a new term for=20
    normal IPv6 addresses used with stateful translators.
    The term "IPv4-mapped" conflicts with address range, e.g. in sockets AP=
I,
    and so another term is needed.


Comments on draft-ietf-behave-v6v4-framework-01: Gang Chen
----------------------------------------------------------
Today there is no generic term for the concept of translation-in-host.
The term "IPv4-adapted-IPv6 implementation" was proposed and discussed.
Fred Baker - not sure why it's useful
Dave - how about changing "implementation" to "host".  Update definition=20
    to make it clear it's a term for the host stack, similar to=20
    "dual stack host"
Fred/Dan - where would this term be used?
    BIS/BIA update, PNAT
There was no consensus reached about whether adding a term to the
    framework was needed.


Christian Huitema was not able to make it to the interim meeting,
and enough time was requested for discussion of other documents to
fill up the interim meeting, so the discussion on the address-format=20
document was deferred to the next interim meeting.


Comments on draft-ietf-behave-v6v4-framework-01: Bo Zhou
--------------------------------------------------------
After some discussion, there was consensus among those present that one=20
    can't use "translator" in a definition to distinguish between=20
    "Internet" and "a network".
The motivation for wanting to more precisely define the difference seems
    to be something about implementation, although others didn't=20
    necessarily agree with this motivation.
Dave - distinction is far more applicable to a deployer than an implementer
Dan - what about just capitalizing "A Network"

Discussion of sentence about "stateful doesn't support IPv4-initiation":
    The concern is this statement doesn't apply to all stateful proposals,=
=20
    e.g. the deprecated NAT-PT.
Dan - change to "<NAT64doc> doesn't support IPv4-initiation"
The consensus among those present was to do that.

Discussion of ALG in framework section 3.1.5:
    Some expressed reservations about not wanting to recommend ALGs.
Dave - add reference that Dan posted to the list - RFC 4924 section 2.3
The consensus among those present was to do that.

draft-ietf-behave-v6v4-xlate-stateful-01: Marcelo Bagnulo
---------------------------------------------------------
Some pending updates still need to be added, specifically around
fragment & MTU handling.
Using the #'s of alternatives from the minutes of the August interim
    meeting, Iljitsch wants 2 but allow people to do 4, but wants more=20
    people to speak up.
Dan - chairs can step in and call for consensus. =20
ACTION ITEM: Iljitsch to send summary of question to Dan by next week.

Xing - some text should move over to the xlate doc?
Marcelo - anything in common should move, anything specific to stateful=20
    should stay
There was agreement among those present on this.  Xing and Marcelo
    will agree over email on which text needs to move.

FTP64 issues: Liu Dapeng
------------------------
The context of the proposal is to introduce FTP client changes that avoid=20
    the need for FTP64 in cases where you can change the FTP clients,
    leaving an FTP64 ALG only when you cnanot.  =20
    There were three sub-topics...

1) How client uses PASV's response messages IPv4 address
The proposal is to just use control channel's IPv4 address.
After some discussion this seemed ok, and Iljitsch agreed to make this chan=
ge.

2) Which try first: EPSV or PASV?
Proposal is PASV first then fallback to EPSV
This is better if know you're talking to an IPv4 server.
The opposite is better if talking to an IPv6 server.
Dan - if host/app can learn prefixes, it can tell which case and modify=20
      behavior=20
Dave - don't overconstrain, allow both and leave it up to config or=20
       heurtistic like dan said=20

3) ALG considerations
Recommend against unless have no choice such as ISP doing translation
And perhaps reference RFC 4924 section 2.3 here too?


draft-ietf-behave-dns64-00: Iljitsch van Beijnum
---------------------------------------------
The only thing needed in DNS64 to make multicast work is a longest prefix=20
    match for translation prefixes.
Iljitsch will work with Stig and get text to Andrew by next week or so.


At the conclusion of the meeting, Dan summarized the list of open issues
the chairs need to discuss:
1) IPv4-adapted-ipv6 host terminology
2) IPv4-mapped terminology




From eric.burgey@orange-ftgroup.com  Wed Sep 23 04:51:02 2009
Return-Path: <eric.burgey@orange-ftgroup.com>
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 2CFB03A6905; Wed, 23 Sep 2009 04:51:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.415
X-Spam-Level: 
X-Spam-Status: No, score=-1.415 tagged_above=-999 required=5 tests=[AWL=0.234,  BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 EzyHeMSUbyyy; Wed, 23 Sep 2009 04:51:00 -0700 (PDT)
Received: from R-MAIL1.rd.francetelecom.com (r-mail1.rd.francetelecom.com [217.108.152.41]) by core3.amsl.com (Postfix) with ESMTP id 16A403A682E; Wed, 23 Sep 2009 04:50:59 -0700 (PDT)
Received: from ftrdmel0.rd.francetelecom.fr ([10.192.128.56]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 23 Sep 2009 13:52:02 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 23 Sep 2009 13:52:01 +0200
Message-ID: <08BA2C59E081884DB2AAE4A0BE9D6DC1663123@ftrdmel0.rd.francetelecom.fr>
In-Reply-To: <12F4112206976147A34FEC0277597CCF27A4062166@XCH-NW-15V.nw.nos.boeing.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BEHAVE] [Softwires] Some Thought about the AutomaticTunnelAddress
Thread-Index: Aco3coauTE1fkrVPRrG72UVQD5MnuAAMFF4wAAYPB4AAKyOw0AAF4qVQAPEZVEA=
References: <002601ca3745$63c8b710$d40c6f0a@china.huawei.com><57F95EAE-6705-4B8E-849F-3F35D7239EDD@free.fr><08BA2C59E081884DB2AAE4A0BE9D6DC1629F33@ftrdmel0.rd.francetelecom.fr><12F4112206976147A34FEC0277597CCF27A402C663@XCH-NW-15V.nw.nos.boeing.com><08BA2C59E081884DB2AAE4A0BE9D6DC162A3BE@ftrdmel0.rd.francetelecom.fr> <12F4112206976147A34FEC0277597CCF27A4062166@XCH-NW-15V.nw.nos.boeing.com>
From: <eric.burgey@orange-ftgroup.com>
To: <Fred.L.Templin@boeing.com>
X-OriginalArrivalTime: 23 Sep 2009 11:52:02.0647 (UTC) FILETIME=[43CD9670:01CA3C44]
Cc: softwires@ietf.org, behave@ietf.org, xuxh@huawei.com
Subject: Re: [BEHAVE] [Softwires] Some Thought about the AutomaticTunnelAddress
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/mail-archive/web/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>
X-List-Received-Date: Wed, 23 Sep 2009 11:51:02 -0000

Hi Fred
I fully agree with you.=20
If the Site is the internet we clearly need a mechanism known by all =
manager of ISATAP equipment connected to internet and the ISATAP =
interface prefix is the best solution.=20

	Eric BURGEY



-----Message d'origine-----
De=A0: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] De la =
part de Templin, Fred L
Envoy=E9=A0: vendredi 18 septembre 2009 19:23
=C0=A0: BURGEY Eric RD-CORE-ISS
Cc=A0: softwires@ietf.org; behave@ietf.org; xuxh@huawei.com
Objet=A0: Re: [BEHAVE] [Softwires] Some Thought about the =
AutomaticTunnelAddress

Hi Eric,

> -----Original Message-----
> From: eric.burgey@orange-ftgroup.com =
[mailto:eric.burgey@orange-ftgroup.com]
> Sent: Friday, September 18, 2009 7:34 AM
> To: Templin, Fred L
> Cc: softwires@ietf.org; behave@ietf.org; remi.despres@free.fr; =
xuxh@huawei.com
> Subject: RE: [BEHAVE] [Softwires] Some Thought about the =
AutomaticTunnelAddress
>=20
> Thanks Fred,
>=20
> Thanks Fred,
> You are right it is difficult to protect tunnelling mechanism against =
spoofing attacks without ip-
> proto-41 and ingress filtering in site border router.
> A major enterprise or an ISP may use more than one single ISATAP link.

OK.

> But the point is, as you have written in chapter 4 of RFC 5214 ,
> >"The domain of applicability for this technical specification is =
automatic >tunneling of IPv6
> packets in IPv4 for ISATAP nodes within sites that >observe the =
security considerations found in this
> document, including host->to-router, router-to-host, and host-to-host =
automatic tunneling in certain
> >enterprise networks and 3GPP/3GPP2 wireless operator networks.  =
(Other >scenarios with a sufficient
> trust basis ensured by the mechanisms specified >in this document also =
fall   within this domain of
> applicability.)",
> Automatic tunnelling must be limited to a "Site".

The statement beginning: "Other scenarios with a sufficient
trust basis..." is the one to consider when the "site" we
are considering is the public Internet itself. The check
for '*::0200:5EFE:V4ADDR' updates this statement.

> Even if I have not found a precise definition of a "Site" IMHO it =
means that there is an organisation
> able to create the trust inside the "Site".

The "organization" in this case is the IANA that delegated
the public IPv4 addresses, along with the collective
administrative authorities of all BGP routers in the DFZ.
=20
> Such organisation is able to know all IPv4 addresses
> allocated to ISATAP router or all 6 to 4 router used to interconnect =
this site with internet and to
> prohibit automatic tunnelling between 2 ISATAP routers inside the =
"Site" or between an ISATAP router
> and 6 to 4 router inside the "Site".

In some sites, configuring ISATAP/6to4 routers with a list of
all other ISATAP/6to4 routers - and then using that list for
filtering purposes - might not scale well. This is definitely
true for the case of the public Internet as a "site", and
probably also true for many large enterprises.
=20
> So if these ISATAP-ISATAP or ISATAP-6_to_4 tunnels are prohibited =
inside the "Site", and if the
> automatic tunnelling process is limited to intra-site tunnels, I don't =
see how the loop described in
> REMI DESPRES mail can be closed in the IPv4 domain.

As above, populating a list of all IPv4 addresses of
ISATAP/6to4 routers on each router might not scale well
in many environments. So, a simple solution is to use
the ISATAP router neighbor cache to avoid looping. In
particular, an ISATAP router *with a coherent neighbor
cache* should only accept/send a tunneled packet with
dst/src address other than FE80::* IFF the tunnel far
end is a known neighbor.

Within enterprise networks protected by site border
routers there are two ways to ensure a coherent neighbor
cache: 1) administrative assurance that no IPv4 spoofing
is possible within the enterprise, or 2) secure neighbor
discovery. Within the global Internet as a site, we can
rely on neither of these and have only the
'*::0200:5EFE:V4ADDR' check as protection.

You should probably also have a look at the thread titled:
"routing loop attacks using IPv6 tunnels" in the v6ops and
6man lists.

Fred
fred.l.templin@boeing.com

> 	Eric BURGEY
>=20
> -----Message d'origine-----
> De=A0: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]
> Envoy=E9=A0: jeudi 17 septembre 2009 19:26
> =C0=A0: BURGEY Eric RD-CORE-ISS; remi.despres@free.fr; xuxh@huawei.com
> Cc=A0: softwires@ietf.org; behave@ietf.org
> Objet=A0: RE: [BEHAVE] [Softwires] Some Thought about the =
AutomaticTunnelAddress
>=20
> Eric,
>=20
> The point is that ISATAP can be used with public IPv4
> addresses (in which case the IPv6 address is constructed
> as: "FOO::0200:5EFE:V4ADDR") and there is no guarantee
> in that case that the ISATAP router is located behind an
> ip-proto-41 nor ingress-filtering site border router. Plus,
> I know of at least one major enterprise network that uses
> public IPv4 addresses internally, and the network is much
> too large to be covered by a single ISATAP link.
>=20
> This discussion should probably by synchronized with the
> one taking place on the v6ops, 6man and secdir lists.
>=20
> Fred
> fred.l.templin@boeing.com
>=20
> > -----Original Message-----
> > From: eric.burgey@orange-ftgroup.com =
[mailto:eric.burgey@orange-ftgroup.com]
> > Sent: Thursday, September 17, 2009 7:45 AM
> > To: remi.despres@free.fr; xuxh@huawei.com
> > Cc: softwires@ietf.org; Templin, Fred L; behave@ietf.org
> > Subject: RE: [BEHAVE] [Softwires] Some Thought about the =
AutomaticTunnelAddress
> >
> > Hello,
> > Xu Xiaohu comment is right but probably be too much restrictive.
> > Excluding all public IPv4 addresses is too strict and not enough =
because it does not excludes 6 to
> 4
> > gateways between the local private network and the IPv6 network with =
a private IPv4 address.
> >
> > ISATAP use an IPv6 operator prefix instead of a well known prefix, =
so it means that ISATAP is built
> > to ensure IPv6 connectivity of IPv4 Islands inside an IPv6 network =
managed by a specific operator.
> > So the encapsulation of IPv6 packet into IPv4 done by the gateway =
must be restricted to IPv4
> > destination addresses managed by this operator (the ISATAP equipment =
operator) excluding all IPv4
> > addresses managed by this operator and allocated to ISATAP, 6 to 4 =
gateway or any other gateway
> > between the IPv4 network and the IPv6 network like for example IVI-T =
gateways.
> >
> >
> > This limitation can be implemented through an access list in the =
ISATAP gateway, in IVI-T gateways
> or
> > in any other gateway between the IPv4 network and the IPv6 network =
doing encapsulation of IPv6
> > packet, with a prefix allocated to an operator, in IPv4 packet.
> >
> >
> > 	Eric BURGEY
> >
> > -----Message d'origine-----
> > De=A0: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] De =
la part de R=E9mi Despr=E9s
> > Envoy=E9=A0: jeudi 17 septembre 2009 10:40
> > =C0=A0: Xu Xiaohu
> > Cc=A0: softwires@ietf.org; 'Templin, Fred L'; 'Behave WG'
> > Objet=A0: Re: [BEHAVE] [Softwires] Some Thought about the =
AutomaticTunnelAddress
> >
> >
> > Xu,
> >
> > Thanks for you answer.
> > Further comment below.
> >
> >
> > Le 17 sept. 09 =E0 05:17, Xu Xiaohu a =E9crit :
> >
> > > In your msg
> > > (http://www.ietf.org/mail-archive/web/behave/current/
> > > msg06816.html), you
> > > said "... Suffice it to say that a 6to4 relay router may need, to
> > > be safe,
> > > to look at IPv4 addresses that are embedded in ISATAP IPv6
> > > addresses. In the
> > > above example, if the 6to4 relay router sees that the IPv4 =
embedded
> > > address
> > > in the IPv6 destination is its own IPv4 address 192.88.99.1, it =
can
> > > discard
> > > the packet and thus prevent the loop". However, I feel this is not
> > > a good
> > > idea for a 6to4 router to check the ISATAP address. In fact, the
> > > routing-loop attack can be easily avoided by using a private IPv4
> > > address,
> > > rather that a public IPv4 address as the ISATAP tunnel endpoint
> > > address on
> > > the ISATAP router.
> >
> > If the IPv4 address of an ISATAP router is private, the attack
> > scenario  below doesn't exists, YES.
> >
> > But 5214 says in its introduction that "ISATAP enables automatic
> > tunneling whether global or private IPv4 addresses are used".
> > To prevent all routing-loop attacks, 6to4 relay routers should
> > therefore also deal with ISATAP routers that have global IPv4 =
addresses.
> >
> > As a matter of facts, ISATAP can be useful with a global IPv4 =
address
> > in a large private network that has enough global IPv4 addresses to
> > use them internally: this provides IPv6 connectivity to dual-stack
> > hosts that support ISATAP (e.g. with Windows or Linux AKAIK).
> >
> >
> > > Hence, I don't think the routing-loop attack prevention is a
> > > justification
> > > for the "IID-format constraint".
> >
> > I also wish it would not have been a justification, but for the
> > reason above I believe it is one we have to live with :-(.
> >
> > Did I miss anything?
> >
> > Regards,
> > RD
> >
> >
> >
> > > For a brief illustration of one instance of the the attack, here =
is an
> > > example:
> > >
> > > +-------------------------------------------------------+
> > > | IPv6                   IPv6 packet                    |
> > > |Internet        dst6:  2002:198.16.9.9::1              |
> > > |                src6:  2001:db8:1::200:5efe:192.88.99.1|
> > > |                                           |           |
> > > |                                           V           |
> > > |          .--------------->--------------. |           |
> > > |         /                                \|           |
> > > +--------+----------------------------------+-----------+
> > >          |                                  |
> > >   2001:db8:1::/48                       2002::/16
> > >     +---------+                        +---------+
> > >     | ISATAP  |                        |  6to4   |
> > >     +---------+                        +---------+
> > >     198.16.9.9                         192.88.99.1
> > >          |                                  |
> > > +--------+---------+                        |
> > > | IPv4   ^         |                        |
> > > | site   ^         |                        |
> > > |        ^         |                        V
> > > |        ^         |                        |
> > > +--------+---------+                        |
> > >     198.16.9.0/24                           |
> > >          |                                  |
> > >          |                                  |
> > > +--------+----------------------------------+-----------+
> > > | IPv4    \                                /            |
> > > |internet  '----------------<-------------'             |
> > > |                 IPv6 in IPv4 packet                   |
> > > |                  dst4: 198.16.9.9                     |
> > > |                  src4: 192.88.99.1                    |
> > > |                                                       |
> > > +--------+----------------------------------+-----------+
> > >
> > _______________________________________________
> > 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 remi.despres@free.fr  Thu Sep 24 06:44:08 2009
Return-Path: <remi.despres@free.fr>
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 E7DD83A687E for <behave@core3.amsl.com>; Thu, 24 Sep 2009 06:44:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.769
X-Spam-Level: 
X-Spam-Status: No, score=-1.769 tagged_above=-999 required=5 tests=[AWL=0.180,  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 CD+amgZed0jl for <behave@core3.amsl.com>; Thu, 24 Sep 2009 06:44:08 -0700 (PDT)
Received: from smtp6-g21.free.fr (smtp6-g21.free.fr [212.27.42.6]) by core3.amsl.com (Postfix) with ESMTP id 02BF33A69B9 for <behave@ietf.org>; Thu, 24 Sep 2009 06:44:06 -0700 (PDT)
Received: from smtp6-g21.free.fr (localhost [127.0.0.1]) by smtp6-g21.free.fr (Postfix) with ESMTP id F0BC9E08128; Thu, 24 Sep 2009 15:45:10 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by smtp6-g21.free.fr (Postfix) with ESMTP id D3A06E08162; Thu, 24 Sep 2009 15:45:07 +0200 (CEST)
In-Reply-To: <a7c8d0a30909080645t342f7bd7udfc553c0303f25ff@mail.gmail.com>
References: <a7c8d0a30909080645t342f7bd7udfc553c0303f25ff@mail.gmail.com>
Mime-Version: 1.0 (Apple Message framework v753.1)
Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed
Message-Id: <9F696598-6783-4E56-AFB5-2702BA089314@free.fr>
Content-Transfer-Encoding: quoted-printable
From: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
Date: Thu, 24 Sep 2009 15:45:04 +0200
To: Zhen Cao <caozhenpku@gmail.com>
X-Mailer: Apple Mail (2.753.1)
Cc: Behave WG <behave@ietf.org>, Dave Thaler <dthaler@microsoft.com>
Subject: Re: [BEHAVE] Stateless translation definition
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/mail-archive/web/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>
X-List-Received-Date: Thu, 24 Sep 2009 13:44:09 -0000

Zhen,

It may be late to offer one more view on the subject, but I hope it =20
clarifies it.

In the context of address translations, my understanding of stateless =20=

vs stateful is:
- Address Translation is STATELESS if it is 1 to 1.
- Address Translation is STATEFUL if it is NOT 1 to 1:
   . It may differ from one transport connection to another.
   . Port states have to be maintained in addition to address states =20
(and in combinations with them).

Whether translation is in a router or in a host doesn't influence =20
this definition.

Regards,
RD







Le 8 sept. 09 =E0 15:45, Zhen Cao a =E9crit :

> I have a concern with respect to the definition of stateful/=20
> stateless translation. Could you help me? Thanks in advance.
>
> The framework draft defines stateful translation as:
> A translation algorithm may be said to
> "require state in a network element" or be "stateful" if the
> transmission or reception of a packet creates or modifies a data
> structure in the relevant network element.
> According to this definition, say, if hosts are configured with a =20
> public IPv4 address in the host-based translation (draft-huang-pnat-=20=

> host-ipv6-02), and the used local prefix is unique, then the =20
> translation on prefix-nat will NOT create or modify any data =20
> structure. Can we call it stateless translation?
>
> Thanks for your help.
>
> Best regards,
> Zhen
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave


From remi.despres@free.fr  Thu Sep 24 06:53:45 2009
Return-Path: <remi.despres@free.fr>
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 92EE53A69E2; Thu, 24 Sep 2009 06:53:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.776
X-Spam-Level: 
X-Spam-Status: No, score=-1.776 tagged_above=-999 required=5 tests=[AWL=0.173,  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 0KCZ3RghOSQA; Thu, 24 Sep 2009 06:53:45 -0700 (PDT)
Received: from smtp6-g21.free.fr (smtp6-g21.free.fr [212.27.42.6]) by core3.amsl.com (Postfix) with ESMTP id 249DE3A6A0D; Thu, 24 Sep 2009 06:53:42 -0700 (PDT)
Received: from smtp6-g21.free.fr (localhost [127.0.0.1]) by smtp6-g21.free.fr (Postfix) with ESMTP id 5C66AE080D7; Thu, 24 Sep 2009 15:54:45 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by smtp6-g21.free.fr (Postfix) with ESMTP id EE981E08144; Thu, 24 Sep 2009 15:54:42 +0200 (CEST)
In-Reply-To: <4AB3F4C9.4070701@gmail.com>
References: <002601ca3745$63c8b710$d40c6f0a@china.huawei.com>	<57F95EAE-6705-4B8E-849F-3F35D7239EDD@free.fr>	<08BA2C59E081884DB2AAE4A0BE9D6DC1629F33@ftrdmel0.rd.francetelecom.fr>	<12F4112206976147A34FEC0277597CCF27A402C663@XCH-NW-15V.nw.nos.boeing.com> <08BA2C59E081884DB2AAE4A0BE9D6DC162A3BE@ftrdmel0.rd.francetelecom.fr> <4AB3F4C9.4070701@gmail.com>
Mime-Version: 1.0 (Apple Message framework v753.1)
Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed
Message-Id: <182A3219-DCEE-4FAC-9676-5718CA3AEEA1@free.fr>
Content-Transfer-Encoding: quoted-printable
From: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
Date: Thu, 24 Sep 2009 15:54:39 +0200
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.753.1)
Cc: softwires@ietf.org, eric.burgey@orange-ftgroup.com, behave@ietf.org, Fred.L.Templin@boeing.com
Subject: Re: [BEHAVE] [Softwires] Some Thought about the	AutomaticTunnelAddress
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/mail-archive/web/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>
X-List-Received-Date: Thu, 24 Sep 2009 13:53:45 -0000

Le 18 sept. 09 =E0 22:59, Brian E Carpenter a =E9crit :

> Hi Eric,
>
> On 2009-09-19 02:33, eric.burgey@orange-ftgroup.com wrote:
> ...
>> Automatic tunnelling must be limited to a "Site".
>
> If you are referring to ISATAP, that may be a sustainable position.
> However, by definition, 6to4 and Teredo involve multiple sites,
> for any reasonable definition of site.

... and we can add 6rd (an ISP IP4 network across which IPv6 is =20
tunneled in 6rd isn't in general considered a "site").

Regards,

RD


From Fred.L.Templin@boeing.com  Thu Sep 24 09:22:30 2009
Return-Path: <Fred.L.Templin@boeing.com>
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 4C22C3A695C; Thu, 24 Sep 2009 09:22:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.9
X-Spam-Level: 
X-Spam-Status: No, score=-5.9 tagged_above=-999 required=5 tests=[AWL=0.399, 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 oul46nhrmh1k; Thu, 24 Sep 2009 09:22:29 -0700 (PDT)
Received: from stl-smtpout-01.boeing.com (stl-smtpout-01.boeing.com [130.76.96.56]) by core3.amsl.com (Postfix) with ESMTP id 350D83A690C; Thu, 24 Sep 2009 09:22:29 -0700 (PDT)
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [130.247.48.231]) by stl-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id n8OGNN3F005787 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 24 Sep 2009 11:23:28 -0500 (CDT)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1]) by blv-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id n8OGNNNu020490; Thu, 24 Sep 2009 09:23:23 -0700 (PDT)
Received: from XCH-NWHT-02.nw.nos.boeing.com (xch-nwht-02.nw.nos.boeing.com [130.247.70.248]) by blv-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id n8OGNNIm020484 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Thu, 24 Sep 2009 09:23:23 -0700 (PDT)
Received: from XCH-NW-15V.nw.nos.boeing.com ([130.247.25.104]) by XCH-NWHT-02.nw.nos.boeing.com ([130.247.70.248]) with mapi; Thu, 24 Sep 2009 09:23:23 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Date: Thu, 24 Sep 2009 09:23:22 -0700
Thread-Topic: [BEHAVE] [Softwires] Some Thought 	aboutthe AutomaticTunnelAddress
Thread-Index: Aco9HptLoVsOZy5JRxSf+XH8Mj+DEgAFIdHA
Message-ID: <12F4112206976147A34FEC0277597CCF27A40BAA9C@XCH-NW-15V.nw.nos.boeing.com>
References: <002601ca3745$63c8b710$d40c6f0a@china.huawei.com>	<57F95EAE-6705 -4B8E-849F-3F35D7239EDD@free.fr>	<08BA2C59E081884DB2AAE4A0BE9D6DC1629F33@ft rdmel0.rd.francetelecom.fr>	<12F4112206976147A34FEC0277597CCF27A402C663@XCH -NW-15V.nw.nos.boeing.com><08BA2C59E081884DB2AAE4A0BE9D6DC162A3BE@ftrdmel0.rd.francetelecom.fr><4AB3F4C9.4070701@gmail.com> <182A3219-DCEE-4FAC-9676-5718CA3AEEA1@free.fr>
In-Reply-To: <182A3219-DCEE-4FAC-9676-5718CA3AEEA1@free.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "softwires@ietf.org" <softwires@ietf.org>, "eric.burgey@orange-ftgroup.com" <eric.burgey@orange-ftgroup.com>, "behave@ietf.org" <behave@ietf.org>
Subject: Re: [BEHAVE] [Softwires] Some Thought aboutthe	AutomaticTunnelAddress
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/mail-archive/web/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>
X-List-Received-Date: Thu, 24 Sep 2009 16:22:30 -0000

> -----Original Message-----
> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On Behalf =
Of R=E9mi Despr=E9s
> Sent: Thursday, September 24, 2009 6:55 AM
> To: Brian E Carpenter
> Cc: softwires@ietf.org; eric.burgey@orange-ftgroup.com; behave@ietf.org; =
Templin, Fred L
> Subject: Re: [BEHAVE] [Softwires] Some Thought aboutthe AutomaticTunnelAd=
dress
>=20
>=20
> Le 18 sept. 09 =E0 22:59, Brian E Carpenter a =E9crit :
>=20
> > Hi Eric,
> >
> > On 2009-09-19 02:33, eric.burgey@orange-ftgroup.com wrote:
> > ...
> >> Automatic tunnelling must be limited to a "Site".
> >
> > If you are referring to ISATAP, that may be a sustainable position.
> > However, by definition, 6to4 and Teredo involve multiple sites,
> > for any reasonable definition of site.
>=20
> ... and we can add 6rd (an ISP IP4 network across which IPv6 is
> tunneled in 6rd isn't in general considered a "site").

That depends on one's definition of "site". I would consider
the ISP network as a site that contains other sites (i.e.,
recursively-nested sites-within-sites).

Fred
fred.l.templin@boeing.com

>=20
> Regards,
>=20
> RD
>=20
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave

From remi.despres@free.fr  Thu Sep 24 10:01:57 2009
Return-Path: <remi.despres@free.fr>
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 A7DB828C13A; Thu, 24 Sep 2009 10:01:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.781
X-Spam-Level: 
X-Spam-Status: No, score=-1.781 tagged_above=-999 required=5 tests=[AWL=0.168,  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 NK13NSvjd2Yb; Thu, 24 Sep 2009 10:01:56 -0700 (PDT)
Received: from smtp6-g21.free.fr (smtp6-g21.free.fr [212.27.42.6]) by core3.amsl.com (Postfix) with ESMTP id 1D6B53A6A8C; Thu, 24 Sep 2009 10:01:54 -0700 (PDT)
Received: from smtp6-g21.free.fr (localhost [127.0.0.1]) by smtp6-g21.free.fr (Postfix) with ESMTP id 095F9E08089; Thu, 24 Sep 2009 19:02:57 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by smtp6-g21.free.fr (Postfix) with ESMTP id 4E3E7E0806F; Thu, 24 Sep 2009 19:02:54 +0200 (CEST)
In-Reply-To: <12F4112206976147A34FEC0277597CCF27A40BAA9C@XCH-NW-15V.nw.nos.boeing.com>
References: <002601ca3745$63c8b710$d40c6f0a@china.huawei.com>	<57F95EAE-6705 -4B8E-849F-3F35D7239EDD@free.fr>	<08BA2C59E081884DB2AAE4A0BE9D6DC1629F33@ft rdmel0.rd.francetelecom.fr>	<12F4112206976147A34FEC0277597CCF27A402C663@XCH -NW-15V.nw.nos.boeing.com><08BA2C59E081884DB2AAE4A0BE9D6DC162A3BE@ftrdmel0.rd.francetelecom.fr><4AB3F4C9.4070701@gmail.com> <182A3219-DCEE-4FAC-9676-5718CA3AEEA1@free.fr> <12F4112206976147A34FEC0277597CCF27A40BAA9C@XCH-NW-15V.nw.nos.boeing.com>
Mime-Version: 1.0 (Apple Message framework v753.1)
Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed
Message-Id: <DADBE159-368F-40F8-8EA1-3E4A34A68898@free.fr>
Content-Transfer-Encoding: quoted-printable
From: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
Date: Thu, 24 Sep 2009 19:02:50 +0200
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
X-Mailer: Apple Mail (2.753.1)
Cc: "softwires@ietf.org" <softwires@ietf.org>, "eric.burgey@orange-ftgroup.com" <eric.burgey@orange-ftgroup.com>, "behave@ietf.org" <behave@ietf.org>
Subject: Re: [BEHAVE] [Softwires] Some Thought aboutthe AutomaticTunnelAddress
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/mail-archive/web/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>
X-List-Received-Date: Thu, 24 Sep 2009 17:01:57 -0000

Le 24 sept. 09 =E0 18:23, Templin, Fred L a =E9crit :

>
>
>> -----Original Message-----
>> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On =20
>> Behalf Of R=E9mi Despr=E9s
>> Sent: Thursday, September 24, 2009 6:55 AM
>> To: Brian E Carpenter
>> Cc: softwires@ietf.org; eric.burgey@orange-ftgroup.com; =20
>> behave@ietf.org; Templin, Fred L
>> Subject: Re: [BEHAVE] [Softwires] Some Thought aboutthe =20
>> AutomaticTunnelAddress
>>
>>
>> Le 18 sept. 09 =E0 22:59, Brian E Carpenter a =E9crit :
>>
>>> Hi Eric,
>>>
>>> On 2009-09-19 02:33, eric.burgey@orange-ftgroup.com wrote:
>>> ...
>>>> Automatic tunnelling must be limited to a "Site".
>>>
>>> If you are referring to ISATAP, that may be a sustainable position.
>>> However, by definition, 6to4 and Teredo involve multiple sites,
>>> for any reasonable definition of site.
>>
>> ... and we can add 6rd (an ISP IP4 network across which IPv6 is
>> tunneled in 6rd isn't in general considered a "site").
>
> That depends on one's definition of "site".

Agreed.
Only if there would be an agreed definition of site would it be =20
possible to be sure what Eric's sentence means, and to then formally =20
agree or disagree with it.

> I would consider
> the ISP network as a site that contains other sites (i.e.,
> recursively-nested sites-within-sites).

In my understanding, the original meaning of site (now deprecated but =20=

still present in many minds) was close to "customer site", and in any =20=

case not recursive.

"Domain" seems to me more intuitive than "site" for recursive or =20
hierarchical entities (routing domains, administrative domains etc.)

Regards,
RD

>

> In

> Fred
> fred.l.templin@boeing.com
>
>>
>> Regards,
>>
>> RD
>>
>> _______________________________________________
>> Behave mailing list
>> Behave@ietf.org
>> https://www.ietf.org/mailman/listinfo/behave


From Fred.L.Templin@boeing.com  Thu Sep 24 10:11:47 2009
Return-Path: <Fred.L.Templin@boeing.com>
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 E8F9A3A68A7; Thu, 24 Sep 2009 10:11:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.906
X-Spam-Level: 
X-Spam-Status: No, score=-5.906 tagged_above=-999 required=5 tests=[AWL=0.393,  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 qCG+xlyT0RHJ; Thu, 24 Sep 2009 10:11:47 -0700 (PDT)
Received: from slb-smtpout-01.boeing.com (slb-smtpout-01.boeing.com [130.76.64.48]) by core3.amsl.com (Postfix) with ESMTP id 0BC423A6901; Thu, 24 Sep 2009 10:11:47 -0700 (PDT)
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [130.247.48.231]) by slb-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id n8OHClq4003236 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 24 Sep 2009 10:12:48 -0700 (PDT)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1]) by blv-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id n8OHClAI000822; Thu, 24 Sep 2009 10:12:47 -0700 (PDT)
Received: from XCH-NWHT-11.nw.nos.boeing.com (xch-nwht-11.nw.nos.boeing.com [130.247.25.114]) by blv-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id n8OHClm9000814 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Thu, 24 Sep 2009 10:12:47 -0700 (PDT)
Received: from XCH-NW-15V.nw.nos.boeing.com ([130.247.25.104]) by XCH-NWHT-11.nw.nos.boeing.com ([130.247.25.114]) with mapi; Thu, 24 Sep 2009 10:12:47 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
Date: Thu, 24 Sep 2009 10:12:45 -0700
Thread-Topic: [BEHAVE] [Softwires] Some Thought abouttheAutomaticTunnelAddress
Thread-Index: Aco9OOWwHjAXJIpPQc2AdEAr87l+KgAAN/4g
Message-ID: <12F4112206976147A34FEC0277597CCF27A40BAAD4@XCH-NW-15V.nw.nos.boeing.com>
References: <002601ca3745$63c8b710$d40c6f0a@china.huawei.com>	<57F95EAE-6705 -4B8E-849F-3F35D7239EDD@free.fr>	<08BA2C59E081884DB2AAE4A0BE9D6DC1629F33@ft rdmel0.rd.francetelecom.fr>	<12F4112206976147A34FEC0277597CCF27A402C663@XCH -NW-15V.nw.nos.boeing.com><08BA2C59E081884DB2AAE4A0BE9D6DC162A3BE@ftrdmel0. rd.francetelecom.fr><4AB3F4C9.4070701@gmail.com><182A3219-DCEE-4FAC-9676-57 18CA3AEEA1@free.fr><12F4112206976147A34FEC0277597CCF27A40BAA9C@XCH-NW-15V.nw.nos.boeing.com> <DADBE159-368F-40F8-8EA1-3E4A34A68898@free.fr>
In-Reply-To: <DADBE159-368F-40F8-8EA1-3E4A34A68898@free.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-tm-as-product-ver: SMEX-8.0.0.1181-5.600.1016-16888.004
x-tm-as-result: No--70.938700-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "softwires@ietf.org" <softwires@ietf.org>, "eric.burgey@orange-ftgroup.com" <eric.burgey@orange-ftgroup.com>, "behave@ietf.org" <behave@ietf.org>
Subject: Re: [BEHAVE] [Softwires] Some Thought abouttheAutomaticTunnelAddress
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/mail-archive/web/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>
X-List-Received-Date: Thu, 24 Sep 2009 17:11:48 -0000

Hi Remi,

> -----Original Message-----
> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On Behalf =
Of R=E9mi Despr=E9s
> Sent: Thursday, September 24, 2009 10:03 AM
> To: Templin, Fred L
> Cc: softwires@ietf.org; eric.burgey@orange-ftgroup.com; behave@ietf.org
> Subject: Re: [BEHAVE] [Softwires] Some Thought abouttheAutomaticTunnelAdd=
ress
>=20
>=20
> Le 24 sept. 09 =E0 18:23, Templin, Fred L a =E9crit :
>=20
> >
> >
> >> -----Original Message-----
> >> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On
> >> Behalf Of R=E9mi Despr=E9s
> >> Sent: Thursday, September 24, 2009 6:55 AM
> >> To: Brian E Carpenter
> >> Cc: softwires@ietf.org; eric.burgey@orange-ftgroup.com;
> >> behave@ietf.org; Templin, Fred L
> >> Subject: Re: [BEHAVE] [Softwires] Some Thought aboutthe
> >> AutomaticTunnelAddress
> >>
> >>
> >> Le 18 sept. 09 =E0 22:59, Brian E Carpenter a =E9crit :
> >>
> >>> Hi Eric,
> >>>
> >>> On 2009-09-19 02:33, eric.burgey@orange-ftgroup.com wrote:
> >>> ...
> >>>> Automatic tunnelling must be limited to a "Site".
> >>>
> >>> If you are referring to ISATAP, that may be a sustainable position.
> >>> However, by definition, 6to4 and Teredo involve multiple sites,
> >>> for any reasonable definition of site.
> >>
> >> ... and we can add 6rd (an ISP IP4 network across which IPv6 is
> >> tunneled in 6rd isn't in general considered a "site").
> >
> > That depends on one's definition of "site".
>=20
> Agreed.
> Only if there would be an agreed definition of site would it be
> possible to be sure what Eric's sentence means, and to then formally
> agree or disagree with it.
>=20
> > I would consider
> > the ISP network as a site that contains other sites (i.e.,
> > recursively-nested sites-within-sites).
>=20
> In my understanding, the original meaning of site (now deprecated but
> still present in many minds) was close to "customer site", and in any
> case not recursive.
>=20
> "Domain" seems to me more intuitive than "site" for recursive or
> hierarchical entities (routing domains, administrative domains etc.)

Actually, in my opinion better than either "domain" or
"site" is "enterprise", which RANGER and VET talk about.
This is also almost the same as what the original CATENET
work called "Packet Switching Network (PSN)".

Fred
fred.l.templin@boeing.com
 =20
>=20
> Regards,
> RD
>=20
> >
>=20
> > In
>=20
> > Fred
> > fred.l.templin@boeing.com
> >
> >>
> >> Regards,
> >>
> >> RD
> >>
> >> _______________________________________________
> >> Behave mailing list
> >> Behave@ietf.org
> >> https://www.ietf.org/mailman/listinfo/behave
>=20
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave

From zhangdong_rh@huaweisymantec.com  Fri Sep 25 00:53:22 2009
Return-Path: <zhangdong_rh@huaweisymantec.com>
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 E108028C122; Fri, 25 Sep 2009 00:53:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.071
X-Spam-Level: 
X-Spam-Status: No, score=-1.071 tagged_above=-999 required=5 tests=[AWL=1.228,  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 Mk6repY9JDh1; Fri, 25 Sep 2009 00:53:22 -0700 (PDT)
Received: from mta2.huaweisymantec.com (mta2.huaweisymantec.com [218.17.155.15]) by core3.amsl.com (Postfix) with ESMTP id 258AF28C0F7; Fri, 25 Sep 2009 00:53:22 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; charset=gb2312
Received: from hstml01-in.huaweisymantec.com ([172.26.3.42]) by hstga02-in.huaweisymantec.com (Sun Java(tm) System Messaging Server 6.3-8.03 (built Apr 24 2009; 32bit)) with ESMTP id <0KQI005HTOM5LD50@hstga02-in.huaweisymantec.com>; Fri, 25 Sep 2009 15:54:06 +0800 (CST)
Received: from z90001956 ([10.27.154.76]) by hstml01-in.huaweisymantec.com (Sun Java(tm) System Messaging Server 6.3-8.03 (built Apr 24 2009; 32bit)) with ESMTPA id <0KQI00MZ1OM4FU10@hstml01-in.huaweisymantec.com>; Fri, 25 Sep 2009 15:54:05 +0800 (CST)
Date: Fri, 25 Sep 2009 15:54:05 +0800
From: Dong Zhang <zhangdong_rh@huaweisymantec.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, =?gb2312?B?UultaV9EZXNwculz?= <remi.despres@free.fr>, Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <002601ca3745$63c8b710$d40c6f0a@china.huawei.com> <"57F95EAE-6705, -4B8E-849F-3F35D7239EDD"@free.fr> <08BA2C59E081884DB2AAE4A0BE9D6DC162A3BE@ftrdmel0.rd.francetelecom.fr> <4AB3F4C9.4070701@gmail.com> <182A3219-DCEE-4FAC-9676-5718CA3AEEA1@free.fr> <12F4112206976147A34FEC0277597CCF27A40BAA9C@XCH-NW-15V.nw.nos.boeing.com>
Message-id: <200909251554046771722@huaweisymantec.com>
X-Mailer: Foxmail 6, 10, 201, 20 [cn]
Cc: "softwires@ietf.org" <softwires@ietf.org>, "eric.burgey@orange-ftgroup.com" <eric.burgey@orange-ftgroup.com>, "behave@ietf.org" <behave@ietf.org>
Subject: Re: [BEHAVE] [Softwires] Some Thought	aboutthe	AutomaticTunnelAddress
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/mail-archive/web/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>
X-List-Received-Date: Fri, 25 Sep 2009 07:53:23 -0000

>That depends on one's definition of "site". I would consider
>the ISP network as a site that contains other sites (i.e.,
>recursively-nested sites-within-sites).

Imho, the word of "site" means a network. However, the size 
of the network is not fixed. It seems that "site" is not a 
clear concept. This leads to some misunderstanding.
If there is a specific definition for "site",
it could be easier to understand when using this word.

Thank you.
------------------				 
Dong Zhang
2009-09-25


From joelja@bogus.com  Fri Sep 25 08:10:08 2009
Return-Path: <joelja@bogus.com>
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 9C2363A69A4; Fri, 25 Sep 2009 08:10:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.549
X-Spam-Level: 
X-Spam-Status: No, score=-2.549 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j-TcxgskdvNN; Fri, 25 Sep 2009 08:10:07 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by core3.amsl.com (Postfix) with ESMTP id 3F6BE28C146; Fri, 25 Sep 2009 08:10:03 -0700 (PDT)
Received: from [192.168.1.151] (c-98-234-104-156.hsd1.ca.comcast.net [98.234.104.156]) (authenticated bits=0) by nagasaki.bogus.com (8.14.3/8.14.3) with ESMTP id n8PF8fqP073055 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 25 Sep 2009 15:08:55 GMT (envelope-from joelja@bogus.com)
Message-ID: <4ABCDCF5.3080907@bogus.com>
Date: Fri, 25 Sep 2009 08:08:37 -0700
From: Joel Jaeggli <joelja@bogus.com>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: Dong Zhang <zhangdong_rh@huaweisymantec.com>
References: <002601ca3745$63c8b710$d40c6f0a@china.huawei.com>	<"57F95EAE-6705, -4B8E-849F-3F35D7239EDD"@free.fr>	<08BA2C59E081884DB2AAE4A0BE9D6DC162A3BE@ftrdmel0.rd.francetelecom.fr>	<4AB3F4C9.4070701@gmail.com>	<182A3219-DCEE-4FAC-9676-5718CA3AEEA1@free.fr>	<12F4112206976147A34FEC0277597CCF27A40BAA9C@XCH-NW-15V.nw.nos.boeing.com> <200909251554046771722@huaweisymantec.com>
In-Reply-To: <200909251554046771722@huaweisymantec.com>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.2 (nagasaki.bogus.com [147.28.0.81]); Fri, 25 Sep 2009 15:08:58 +0000 (UTC)
Cc: "behave@ietf.org" <behave@ietf.org>, "Templin, Fred L" <Fred.L.Templin@boeing.com>, =?UTF-8?B?UumWmWlfRGVz?=, "softwires@ietf.org" <softwires@ietf.org>, "eric.burgey@orange-ftgroup.com" <eric.burgey@orange-ftgroup.com>
Subject: Re: [BEHAVE] [Softwires] Some	Thought	aboutthe	AutomaticTunnelAddress
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/mail-archive/web/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>
X-List-Received-Date: Fri, 25 Sep 2009 15:10:08 -0000

Dong Zhang wrote:
>> That depends on one's definition of "site". I would consider
>> the ISP network as a site that contains other sites (i.e.,
>> recursively-nested sites-within-sites).
> 
> Imho, the word of "site" means a network. However, the size 
> of the network is not fixed. It seems that "site" is not a 
> clear concept. This leads to some misunderstanding.
> If there is a specific definition for "site",
> it could be easier to understand when using this word.

Part of the problem with site-local was that the scope was ambiguous.
the term is not rooted in a discrete object with a position in the
topology, contrast with autonomous system or prefix.

> Thank you.
> ------------------				 
> Dong Zhang
> 2009-09-25
> 
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
> 

From rpenno@juniper.net  Fri Sep 25 13:58:10 2009
Return-Path: <rpenno@juniper.net>
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 41D2D3A68C8 for <behave@core3.amsl.com>; Fri, 25 Sep 2009 13:58:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.441
X-Spam-Level: 
X-Spam-Status: No, score=-6.441 tagged_above=-999 required=5 tests=[AWL=0.159,  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 bq+ieymUCgsP for <behave@core3.amsl.com>; Fri, 25 Sep 2009 13:58:09 -0700 (PDT)
Received: from exprod7og125.obsmtp.com (exprod7og125.obsmtp.com [64.18.2.28]) by core3.amsl.com (Postfix) with ESMTP id C57A83A681E for <behave@ietf.org>; Fri, 25 Sep 2009 13:58:08 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob125.postini.com ([64.18.6.12]) with SMTP ID DSNKSr0vJepizGYxfx4ZgXPT2mEN5UU+tGd+@postini.com; Fri, 25 Sep 2009 13:59:21 PDT
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.1.375.2; Fri, 25 Sep 2009 13:57:38 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Fri, 25 Sep 2009 16:57:37 -0400
From: Reinaldo Penno <rpenno@juniper.net>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Zhen Cao <caozhenpku@gmail.com>
Date: Fri, 25 Sep 2009 16:57:35 -0400
Thread-Topic: [BEHAVE] Comments on NAT64 draft
Thread-Index: Aco7OeVMg2Im0IzkTH+JIaDOhSWsuAC6OlWQ
Message-ID: <C6E27CCF.38FE8%rpenno@juniper.net>
In-Reply-To: <4AB84CDD.3030600@gmail.com>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Cameron Byrne <cb.list6@gmail.com>, Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Comments on NAT64 draft
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/mail-archive/web/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>
X-List-Received-Date: Fri, 25 Sep 2009 20:58:10 -0000

There is certainly the engineering issue which we could debate but it would
be good to hear service provider requirements in relation to this aspect in
the context of NAT64. In the case of NAT44 dropping fragments is not okay
(at least this is what I hear).

Thanks,

Reinaldo

=20

On 9/21/09 9:04 PM, "Brian E Carpenter" <brian.e.carpenter@gmail.com> wrote=
:

> On 2009-09-18 13:29, Zhen Cao wrote:
>>>>> Any ideas from implementers? Is it problematic to have to buffer and
>>>>> reassemble UDP fragments that don't match any state in the v6->v4
>>>>> direction?
>>>> According to RFC 4787 Requirement 14, a NAT MUST accommodate this out
>>>> of order fragment situation.
>>> This seems extreme; I wonder why it wasn't a SHOULD. However,
>>> that's a BCP for IPv4-IPv4 NATs "as described in [RFC2663]."
>>> We can decide independently for NAT64, but Iljitsch has asked the
>>> right question: how big a deal is this for implementors?
>>=20
>> It might not be a big problem for implementor, considering it only
>> hurts the first out-of-order fragmented packet of the flow. Also from
>> the statistics you provided several days before, fragmented UDP
>> packets counts to a very small percentage.
>=20
> Correct. But if such packets consume 100 times more resource in the
> NAT, they could still be a problem. That's an engineering question,
> and I am still not sure of the answer.
>=20
>>=20
>> But changing the text in NAT64 is also not a big deal. We can analyze
>> this in the document a bit for the consideration of implementors. This
>> will do no harm and make the document as solid as possible.
>=20
> Yes. But I think there is quite a big difference in this case between
> a SHOULD and a MUST.
>=20
>     Brian
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave


From cb.list6@gmail.com  Fri Sep 25 15:11:25 2009
Return-Path: <cb.list6@gmail.com>
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 AFB293A698F for <behave@core3.amsl.com>; Fri, 25 Sep 2009 15:11:25 -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 X6N9djY8203P for <behave@core3.amsl.com>; Fri, 25 Sep 2009 15:11:24 -0700 (PDT)
Received: from mail-px0-f173.google.com (mail-px0-f173.google.com [209.85.216.173]) by core3.amsl.com (Postfix) with ESMTP id DB2243A6883 for <behave@ietf.org>; Fri, 25 Sep 2009 15:11:24 -0700 (PDT)
Received: by pxi3 with SMTP id 3so4308662pxi.31 for <behave@ietf.org>; Fri, 25 Sep 2009 15:12:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=shJBPJbqD0ClH+CTSyos7hUyIZXsTgMlw/STCyUoB2Y=; b=orMTcKBSs9EVB49U4ajyJpWwC846eiGhJMuBKhwM866+Kw5my2wZsagOv724avUSE4 43iBs14wwSA3LKMgnaJ/Md26msVgjLeBlMuGKeZIc/+BHN4dILoedeg9mL1PZJ7bi3iK dl6HGo4t/bl49EfMTsi9NzMhPkfv0iBAtiDB8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=fxvEhFGPi/DaNBOiY713TQqOdZP+MbL1qB/fFelqt2At4i7h9qsGQHnb7u0ldu6Fb9 bplBDf4QH3719Cl4dQrGkXZLy1NNMuPhN4Kfd5T9lzJvmvEBWpq+JA6xxwqOV7O3kRBF TllPpcpG0Cum0r6aTl8xhRqqLzFzZBft/lx98=
MIME-Version: 1.0
Received: by 10.143.138.7 with SMTP id q7mr50067wfn.188.1253916754354; Fri, 25  Sep 2009 15:12:34 -0700 (PDT)
In-Reply-To: <C6E27CCF.38FE8%rpenno@juniper.net>
References: <4AB84CDD.3030600@gmail.com> <C6E27CCF.38FE8%rpenno@juniper.net>
Date: Fri, 25 Sep 2009 15:12:34 -0700
Message-ID: <bcff0fba0909251512xcc08a90s328fb91d3dfb0ff4@mail.gmail.com>
From: Cameron Byrne <cb.list6@gmail.com>
To: Reinaldo Penno <rpenno@juniper.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Behave WG <behave@ietf.org>, Zhen Cao <caozhenpku@gmail.com>
Subject: Re: [BEHAVE] Comments on NAT64 draft
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/mail-archive/web/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>
X-List-Received-Date: Fri, 25 Sep 2009 22:11:25 -0000

On Fri, Sep 25, 2009 at 1:57 PM, Reinaldo Penno <rpenno@juniper.net> wrote:
> There is certainly the engineering issue which we could debate but it wou=
ld
> be good to hear service provider requirements in relation to this aspect =
in
> the context of NAT64. In the case of NAT44 dropping fragments is not okay
> (at least this is what I hear).

As stated before, as much as i dislike making NAT64 any more
complicated than it absolutely must be, I believe it is best to have
parity with NAT44, and RFC 4787 / BCP 127 states we must support the
out of order fragments while at the same time mitigating against any
DOS attacks that may come from holding state for out-of-order
fragments.  My goal is that i can offer IPv6 only service to customers
and they cannot tell the difference from IPv4 service.   If for some
reason they send out-of-order fragments today with my current NAT44
and I support it in IPv4, i must support it in IPv6 as with NAT64 as
well.

Cameron Byrne
Principal Engineer
T-Mobile USA

>
> Thanks,
>
> Reinaldo
>
>
>
> On 9/21/09 9:04 PM, "Brian E Carpenter" <brian.e.carpenter@gmail.com> wro=
te:
>
>> On 2009-09-18 13:29, Zhen Cao wrote:
>>>>>> Any ideas from implementers? Is it problematic to have to buffer and
>>>>>> reassemble UDP fragments that don't match any state in the v6->v4
>>>>>> direction?
>>>>> According to RFC 4787 Requirement 14, a NAT MUST accommodate this out
>>>>> of order fragment situation.
>>>> This seems extreme; I wonder why it wasn't a SHOULD. However,
>>>> that's a BCP for IPv4-IPv4 NATs "as described in [RFC2663]."
>>>> We can decide independently for NAT64, but Iljitsch has asked the
>>>> right question: how big a deal is this for implementors?
>>>
>>> It might not be a big problem for implementor, considering it only
>>> hurts the first out-of-order fragmented packet of the flow. Also from
>>> the statistics you provided several days before, fragmented UDP
>>> packets counts to a very small percentage.
>>
>> Correct. But if such packets consume 100 times more resource in the
>> NAT, they could still be a problem. That's an engineering question,
>> and I am still not sure of the answer.
>>
>>>
>>> But changing the text in NAT64 is also not a big deal. We can analyze
>>> this in the document a bit for the consideration of implementors. This
>>> will do no harm and make the document as solid as possible.
>>
>> Yes. But I think there is quite a big difference in this case between
>> a SHOULD and a MUST.
>>
>> =A0 =A0 Brian
>> _______________________________________________
>> Behave mailing list
>> Behave@ietf.org
>> https://www.ietf.org/mailman/listinfo/behave
>
>

From caozhenpku@gmail.com  Fri Sep 25 22:04:09 2009
Return-Path: <caozhenpku@gmail.com>
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 AD1D73A680C for <behave@core3.amsl.com>; Fri, 25 Sep 2009 22:04:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.495
X-Spam-Level: 
X-Spam-Status: No, score=-2.495 tagged_above=-999 required=5 tests=[AWL=0.104,  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 JGFediXk5yGj for <behave@core3.amsl.com>; Fri, 25 Sep 2009 22:04:08 -0700 (PDT)
Received: from mail-vw0-f196.google.com (mail-vw0-f196.google.com [209.85.212.196]) by core3.amsl.com (Postfix) with ESMTP id 9245A3A68AB for <behave@ietf.org>; Fri, 25 Sep 2009 22:04:08 -0700 (PDT)
Received: by vws34 with SMTP id 34so2241351vws.32 for <behave@ietf.org>; Fri, 25 Sep 2009 22:05:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=FOQ4T0KaFSX+1SF92Y47+FJwWcjKO+/vtBfIi9WrY9Q=; b=rf8ripYrEClzAad7tCVQF44d9AhS+AfMUzzP5kFvdjp+VQgzvxekBIn63mB/KTLdPP RUVkIj4AIsVHJVu10W86vSwcdmogCi7CD3oISvLjLQuJoKg2PpxviVdujeF0WMosr1PN bLT0S7CnoXjfAhulgwxUlRVFNbyeeRPVwhqWo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=V9L0OCPf2km3gks4McH4xMp/dFNsoqfEVHyMGEcB3zS+PmTCoSblYbFQfN0b/0lGvV 4JrZAvx8yPYtXjh97hEgmALlSU+hPh0QTBGux7ZGjkXt4thbGtDBxN04b0h/HvF8Iez4 wE+0mWs9EYF91jBsVqyIotjRJQgK2HREmQyus=
MIME-Version: 1.0
Received: by 10.220.89.93 with SMTP id d29mr1808482vcm.26.1253941514699; Fri,  25 Sep 2009 22:05:14 -0700 (PDT)
In-Reply-To: <C6E27CCF.38FE8%rpenno@juniper.net>
References: <4AB84CDD.3030600@gmail.com> <C6E27CCF.38FE8%rpenno@juniper.net>
Date: Sat, 26 Sep 2009 13:05:14 +0800
Message-ID: <a7c8d0a30909252205t29eee6e8sea896b94169aab02@mail.gmail.com>
From: Zhen Cao <caozhenpku@gmail.com>
To: Reinaldo Penno <rpenno@juniper.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Cameron Byrne <cb.list6@gmail.com>, Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Comments on NAT64 draft
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/mail-archive/web/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>
X-List-Received-Date: Sat, 26 Sep 2009 05:04:09 -0000

I thinks we should keep the NAT64 compatible with NAT44 in dealing
with out of order fragments.

Also in this case, what the implementor should do is dealing with the
first arriving out-of-order fragment. Buffering the fragment is
troublesome but it is easy to couple with some timeout scheme to avoid
consuming too much resource. So from implementation point, this does
not count much.

Thanks,
Zhen

On Sat, Sep 26, 2009 at 4:57 AM, Reinaldo Penno <rpenno@juniper.net> wrote:
> There is certainly the engineering issue which we could debate but it wou=
ld
> be good to hear service provider requirements in relation to this aspect =
in
> the context of NAT64. In the case of NAT44 dropping fragments is not okay
> (at least this is what I hear).
>
> Thanks,
>
> Reinaldo
>
>
>
> On 9/21/09 9:04 PM, "Brian E Carpenter" <brian.e.carpenter@gmail.com> wro=
te:
>
>> On 2009-09-18 13:29, Zhen Cao wrote:
>>>>>> Any ideas from implementers? Is it problematic to have to buffer and
>>>>>> reassemble UDP fragments that don't match any state in the v6->v4
>>>>>> direction?
>>>>> According to RFC 4787 Requirement 14, a NAT MUST accommodate this out
>>>>> of order fragment situation.
>>>> This seems extreme; I wonder why it wasn't a SHOULD. However,
>>>> that's a BCP for IPv4-IPv4 NATs "as described in [RFC2663]."
>>>> We can decide independently for NAT64, but Iljitsch has asked the
>>>> right question: how big a deal is this for implementors?
>>>
>>> It might not be a big problem for implementor, considering it only
>>> hurts the first out-of-order fragmented packet of the flow. Also from
>>> the statistics you provided several days before, fragmented UDP
>>> packets counts to a very small percentage.
>>
>> Correct. But if such packets consume 100 times more resource in the
>> NAT, they could still be a problem. That's an engineering question,
>> and I am still not sure of the answer.
>>
>>>
>>> But changing the text in NAT64 is also not a big deal. We can analyze
>>> this in the document a bit for the consideration of implementors. This
>>> will do no harm and make the document as solid as possible.
>>
>> Yes. But I think there is quite a big difference in this case between
>> a SHOULD and a MUST.
>>
>> =A0 =A0 Brian
>> _______________________________________________
>> Behave mailing list
>> Behave@ietf.org
>> https://www.ietf.org/mailman/listinfo/behave
>
>

From caozhenpku@gmail.com  Fri Sep 25 22:52:35 2009
Return-Path: <caozhenpku@gmail.com>
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 B077828C0E3 for <behave@core3.amsl.com>; Fri, 25 Sep 2009 22:52:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.349
X-Spam-Level: 
X-Spam-Status: No, score=-2.349 tagged_above=-999 required=5 tests=[AWL=-0.050, 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 tY55iHerV9X4 for <behave@core3.amsl.com>; Fri, 25 Sep 2009 22:52:35 -0700 (PDT)
Received: from mail-vw0-f196.google.com (mail-vw0-f196.google.com [209.85.212.196]) by core3.amsl.com (Postfix) with ESMTP id D24ED28C0ED for <behave@ietf.org>; Fri, 25 Sep 2009 22:52:34 -0700 (PDT)
Received: by vws34 with SMTP id 34so2253519vws.32 for <behave@ietf.org>; Fri, 25 Sep 2009 22:53:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=Jk6lQQlJrCk+SRZx07PkDBIXfNNtd4WgjKzOnGIsYCc=; b=I1PqYuOLzCIF6A7ON6/LujA1AIXEwhVYbPPwnSwYmE1x7DBCDgTuFx/Tb3Y54apOB5 OKVNlV88aNerBE3uwOeUvdbWoI1JXabFnK+0dvXzstojzEFBMxxE7Qb8U68ltCjdrrxW Oiat9tLNPDadAw+n3ignofZ6oszWiOT4Txve0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=RX5dqi2JvlpW/n8O95XVe+oOIII8HcasOq1HS0sfpLpuZBNM/jlp/WE2FTLVToUpYL kMX65fwJq/QUeZUAH7BjoSXPPUe5AhOA8PgVMZcbivn7ksBsAKu4fqTg0QfvzW719gMi KbMw+KP9ZJollw6fspCzoexdkcVPK4TTz03Rs=
MIME-Version: 1.0
Received: by 10.220.103.15 with SMTP id i15mr1909688vco.15.1253944421232; Fri,  25 Sep 2009 22:53:41 -0700 (PDT)
In-Reply-To: <9F696598-6783-4E56-AFB5-2702BA089314@free.fr>
References: <a7c8d0a30909080645t342f7bd7udfc553c0303f25ff@mail.gmail.com> <9F696598-6783-4E56-AFB5-2702BA089314@free.fr>
Date: Sat, 26 Sep 2009 13:53:41 +0800
Message-ID: <a7c8d0a30909252253i583edfdq9b141e1005fa1869@mail.gmail.com>
From: Zhen Cao <caozhenpku@gmail.com>
To: =?ISO-8859-1?B?UultaSBEZXNwculz?= <remi.despres@free.fr>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Behave WG <behave@ietf.org>, Dave Thaler <dthaler@microsoft.com>
Subject: Re: [BEHAVE] Stateless translation definition
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/mail-archive/web/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>
X-List-Received-Date: Sat, 26 Sep 2009 05:52:35 -0000

On Thu, Sep 24, 2009 at 9:45 PM, R=E9mi Despr=E9s <remi.despres@free.fr> wr=
ote:
> Zhen,
>
> It may be late to offer one more view on the subject, but I hope it
> clarifies it.

Thanks for sharing your opinion.
>
> In the context of address translations, my understanding of stateless vs
> stateful is:
> - Address Translation is STATELESS if it is 1 to 1.
> - Address Translation is STATEFUL if it is NOT 1 to 1:
> =A0. It may differ from one transport connection to another.
> =A0. Port states have to be maintained in addition to address states (and=
 in
> combinations with them).

It seems a straightforward understanding. I am afraid of some stateful
translation also has an 1:1 mapping table. From example, each
LIR:PrivateV4Addr maps to a different public IPv6 address.

>
> Whether translation is in a router or in a host doesn't influence this
> definition.
>
> Regards,
> RD
>
>
>
>
>
>
>
> Le 8 sept. 09 =E0 15:45, Zhen Cao a =E9crit :
>
>> I have a concern with respect to the definition of stateful/stateless
>> translation. Could you help me? Thanks in advance.
>>
>> The framework draft defines stateful translation as:
>> A translation algorithm may be said to
>> "require state in a network element" or be "stateful" if the
>> transmission or reception of a packet creates or modifies a data
>> structure in the relevant network element.
>> According to this definition, say, if hosts are configured with a public
>> IPv4 address in the host-based translation (draft-huang-pnat-host-ipv6-0=
2),
>> and the used local prefix is unique, then the translation on prefix-nat =
will
>> NOT create or modify any data structure. Can we call it stateless
>> translation?
>>
>> Thanks for your help.
>>
>> Best regards,
>> Zhen
>> _______________________________________________
>> Behave mailing list
>> Behave@ietf.org
>> https://www.ietf.org/mailman/listinfo/behave
>
>

From caozhenpku@gmail.com  Fri Sep 25 22:54:25 2009
Return-Path: <caozhenpku@gmail.com>
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 2A22728C0F0 for <behave@core3.amsl.com>; Fri, 25 Sep 2009 22:54:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.347
X-Spam-Level: 
X-Spam-Status: No, score=-2.347 tagged_above=-999 required=5 tests=[AWL=-0.048, 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 xmVatv0Ar+bv for <behave@core3.amsl.com>; Fri, 25 Sep 2009 22:54:24 -0700 (PDT)
Received: from mail-vw0-f196.google.com (mail-vw0-f196.google.com [209.85.212.196]) by core3.amsl.com (Postfix) with ESMTP id 49F3A28C0EE for <behave@ietf.org>; Fri, 25 Sep 2009 22:54:24 -0700 (PDT)
Received: by vws34 with SMTP id 34so2253997vws.32 for <behave@ietf.org>; Fri, 25 Sep 2009 22:55:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=pd78gJsL50xsFFbVg1C7KOcF0gQEC1YQTx/2kilkPuU=; b=UIPTmn2dutXrCFBDVycnuvI99CZgz1xZPUJ2aumDdHX62E/BwsoN4woZS8jJDAmkdZ zUX2c3DEX/wr3k9uJDdt0mHwkPNtE3DwHOHit2oBobjyi7ZSPaYp3GkdZQ7J2PGB/+4J 340RhZ08SMD0JSubnjoj5UsdNXO9+VvMBBX8U=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=LyxbIyljQDpBE48L2qxivaX/N0T8uL+OlWcd2VS5OP5mMMFKHIwg4H1y51uTDVjOLc gKb1jru353ZvR/RwalPUAinNdMb7ldLigAsv0zIwIswQPmJJFZuufWYfKDdtAZ4LsGJf F5Wg7hpNGLPR8apKJ9J9oGUeSZdJ2dUfLxgYs=
MIME-Version: 1.0
Received: by 10.220.102.2 with SMTP id e2mr1889167vco.41.1253944533866; Fri,  25 Sep 2009 22:55:33 -0700 (PDT)
In-Reply-To: <a7c8d0a30909252253i583edfdq9b141e1005fa1869@mail.gmail.com>
References: <a7c8d0a30909080645t342f7bd7udfc553c0303f25ff@mail.gmail.com> <9F696598-6783-4E56-AFB5-2702BA089314@free.fr> <a7c8d0a30909252253i583edfdq9b141e1005fa1869@mail.gmail.com>
Date: Sat, 26 Sep 2009 13:55:33 +0800
Message-ID: <a7c8d0a30909252255x2e1a9938jeca667ff79f08ab3@mail.gmail.com>
From: Zhen Cao <caozhenpku@gmail.com>
To: =?ISO-8859-1?B?UultaSBEZXNwculz?= <remi.despres@free.fr>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Behave WG <behave@ietf.org>, Dave Thaler <dthaler@microsoft.com>
Subject: Re: [BEHAVE] Stateless translation definition
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/mail-archive/web/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>
X-List-Received-Date: Sat, 26 Sep 2009 05:54:25 -0000

On Sat, Sep 26, 2009 at 1:53 PM, Zhen Cao <caozhenpku@gmail.com> wrote:
> On Thu, Sep 24, 2009 at 9:45 PM, R=E9mi Despr=E9s <remi.despres@free.fr> =
wrote:
>> Zhen,
>>
>> It may be late to offer one more view on the subject, but I hope it
>> clarifies it.
>
> Thanks for sharing your opinion.
>>
>> In the context of address translations, my understanding of stateless vs
>> stateful is:
>> - Address Translation is STATELESS if it is 1 to 1.
>> - Address Translation is STATEFUL if it is NOT 1 to 1:
>> =A0. It may differ from one transport connection to another.
>> =A0. Port states have to be maintained in addition to address states (an=
d in
>> combinations with them).
>
> It seems a straightforward understanding. I am afraid of some stateful
> translation also has an 1:1 mapping table. From example, each
> LIR:PrivateV4Addr maps to a different public IPv4 address.

sorry for the typo above, i meant "each LIR:PrivateV4Addr maps to a
different public IPv4 address"
>
>>
>> Whether translation is in a router or in a host doesn't influence this
>> definition.
>>
>> Regards,
>> RD
>>
>>
>>
>>
>>
>>
>>
>> Le 8 sept. 09 =E0 15:45, Zhen Cao a =E9crit :
>>
>>> I have a concern with respect to the definition of stateful/stateless
>>> translation. Could you help me? Thanks in advance.
>>>
>>> The framework draft defines stateful translation as:
>>> A translation algorithm may be said to
>>> "require state in a network element" or be "stateful" if the
>>> transmission or reception of a packet creates or modifies a data
>>> structure in the relevant network element.
>>> According to this definition, say, if hosts are configured with a publi=
c
>>> IPv4 address in the host-based translation (draft-huang-pnat-host-ipv6-=
02),
>>> and the used local prefix is unique, then the translation on prefix-nat=
 will
>>> NOT create or modify any data structure. Can we call it stateless
>>> translation?
>>>
>>> Thanks for your help.
>>>
>>> Best regards,
>>> Zhen
>>> _______________________________________________
>>> Behave mailing list
>>> Behave@ietf.org
>>> https://www.ietf.org/mailman/listinfo/behave
>>
>>
>

From caozhenpku@gmail.com  Fri Sep 25 22:59:35 2009
Return-Path: <caozhenpku@gmail.com>
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 C4B3728C0EE for <behave@core3.amsl.com>; Fri, 25 Sep 2009 22:59:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.495
X-Spam-Level: 
X-Spam-Status: No, score=-2.495 tagged_above=-999 required=5 tests=[AWL=0.104,  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 7qOlkczi9UQn for <behave@core3.amsl.com>; Fri, 25 Sep 2009 22:59:35 -0700 (PDT)
Received: from mail-vw0-f196.google.com (mail-vw0-f196.google.com [209.85.212.196]) by core3.amsl.com (Postfix) with ESMTP id D8F9428C0F0 for <behave@ietf.org>; Fri, 25 Sep 2009 22:59:34 -0700 (PDT)
Received: by vws34 with SMTP id 34so2255238vws.32 for <behave@ietf.org>; Fri, 25 Sep 2009 23:00:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=UcuqxNyKVernDHC8Hwc842zTDxtJAAzLHA2a9U7NUe4=; b=odXdozOfPfyAKDTMbEHp9D/6tF9N3LeNOXGc6N7zS0H0+E4sW068a5W4zTRmXsE4U4 KqN65hgAucfELFLoM0i1gi6gkpDmSHjwOrVKA9lwo1YJIOT637crxK3CI7zM4J9xyD4o rM5oxYGd7bS/OhgYIlsGDNpvfwvXQedjI/p3U=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=rJ9yWZx8VAF8QNpiD00DP8wEdJLDrD64R2yHK4Uc0iZv4tWbx3X6KKykSIJ1ivTlLh EV2KlBc8WvPEJOuIGgOB9wfCIJLneSrdK3roZ7OLceeJ18MNqdVu7vluLGRKjIHKnSNV w2JzTkZDpuZQvZv58fJdnU4jnpFi75ejbF32w=
MIME-Version: 1.0
Received: by 10.220.88.15 with SMTP id y15mr1848099vcl.62.1253944847330; Fri,  25 Sep 2009 23:00:47 -0700 (PDT)
In-Reply-To: <6B55F0F93C3E9D45AF283313B8D342BA20F59D61@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
References: <a7c8d0a30909080645t342f7bd7udfc553c0303f25ff@mail.gmail.com> <09f701ca30a0$01e90730$c5f0200a@cisco.com> <a7c8d0a30909091804j368a8a6fr4ee1b75eb7081559@mail.gmail.com> <073801ca31b6$60299ff0$c6f0200a@cisco.com> <a7c8d0a30909100304w69593812o29778ad80f28451c@mail.gmail.com> <004701ca3246$015ea5c0$c6f0200a@cisco.com> <6B55F0F93C3E9D45AF283313B8D342BA20F59D61@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
Date: Sat, 26 Sep 2009 14:00:47 +0800
Message-ID: <a7c8d0a30909252300n6e5d18d6s97093eb724956398@mail.gmail.com>
From: Zhen Cao <caozhenpku@gmail.com>
To: Christian Huitema <huitema@microsoft.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Behave WG <behave@ietf.org>, Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] Stateless translation definition
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/mail-archive/web/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>
X-List-Received-Date: Sat, 26 Sep 2009 05:59:35 -0000

On Wed, Sep 16, 2009 at 1:08 PM, Christian Huitema
<huitema@microsoft.com> wrote:
>> Looking at the diagram in
>> http://tools.ietf.org/html/draft-huang-pnat-host-ipv6-01#section-2 and
>> reading
>> the PNAT44COM definition in that section, the conclusion I reach is that
>> it
>> can be done statelessly if both of these are true:
>>
>> =A01. each IPv6 host consumes one IPv4 address in the PNAT64 device;
>> =A0 =A0 this allows a stateless, algorithmic mapping on the PNAT64 devic=
e
>> =A0 =A0 similar to what is described in the IVI drafts and in
>> =A0 =A0 http://tools.ietf.org/html/draft-ietf-behave-address-format-
>> 00#section-2.3
>>
>> and
>> =A02. there are only routable, non-overlapping IPv4 addresses on
>> =A0 =A0 the IPv4 site.
>>
>> But if either of those are false, there needs to be per-flow state
>> somewhere.
>
> I think the "stateless translation" can have two definitions. The least r=
estrictive one is what Dan just described: when it is possible to allocate =
an IPv4 address to the IPv6 host. The domain of application is very limited=
, because there are not enough 32 bits IPv4 addresses to map every 128 bit =
IPv6 address. I can see one application: when we want an IPv6 host to be vi=
sible, for example as a web server, by IPv4 hosts.
>
> The more restrictive is an operational definition. A translation is state=
less if two different translators, presented with the same packets, would p=
erform exactly the same translation. This is even more restrictive, because=
 it requires that every NAT can interpret the IPv6 source and destination a=
ddress and translate them to the same pair of IPv4 addresses.

Sounds interesting. Do you see any solution achieving this kind of
stateless translation?

>
> By the way, even the least restrictive definition implies that stateless =
translation is very much a specialty product, and cannot be used as a gener=
al solution for providing IPv6 networks with connectivity to the IPv4 Inter=
net.

I agree.
>
> -- Christian Huitema
>
>
>
>
>

From brian.e.carpenter@gmail.com  Sat Sep 26 13:27:06 2009
Return-Path: <brian.e.carpenter@gmail.com>
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 A5D293A6998 for <behave@core3.amsl.com>; Sat, 26 Sep 2009 13:27:06 -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 p2OZ8JE8OHWF for <behave@core3.amsl.com>; Sat, 26 Sep 2009 13:27:05 -0700 (PDT)
Received: from mail-pz0-f174.google.com (mail-pz0-f174.google.com [209.85.222.174]) by core3.amsl.com (Postfix) with ESMTP id C63C03A6816 for <behave@ietf.org>; Sat, 26 Sep 2009 13:27:05 -0700 (PDT)
Received: by pzk4 with SMTP id 4so1549513pzk.32 for <behave@ietf.org>; Sat, 26 Sep 2009 13:27:51 -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=OaeqqjY5lDDzk4FQn+jxlwuTdtVZ2G0MZEAtvG5wfos=; b=mqjsHvDIbOfLb+nhOXizUtN0QMqW+qmgOt/fecVt2/XkC+DAqQIw9niM+QddFdG/6j yKnSsHDu/kfFHFfpu9yUBQprclPlc+YF8X4YDLyt3cPB7UTxILsopCIcdAHx+2aPXoX3 BFN/VmdIhMEPL/NW/yXRYFWrkGI3Wk79aajwU=
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=uhY7EW3lm8rrBzTSb6QbJfTRotz/SIFJN4q8I4I8RpU2rZ1SFqjG1FQ7+NtoAFrxPQ EdZnGiKyF+zboZzHihnR/PNg5Js9UXUJCziOU8+7JTCvb4YtoRLF/D/Hi1GqhwKX8Rbu 3RasQp8XzG6o/bDxblT1gQOmkN9DKgxyPlRsw=
Received: by 10.114.214.24 with SMTP id m24mr2336155wag.93.1253996871095; Sat, 26 Sep 2009 13:27:51 -0700 (PDT)
Received: from ?10.1.1.4? (118-93-6-221.dsl.dyn.ihug.co.nz [118.93.6.221]) by mx.google.com with ESMTPS id 21sm1290948pzk.11.2009.09.26.13.27.46 (version=SSLv3 cipher=RC4-MD5); Sat, 26 Sep 2009 13:27:49 -0700 (PDT)
Message-ID: <4ABE7938.1010106@gmail.com>
Date: Sun, 27 Sep 2009 09:27:36 +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: Zhen Cao <caozhenpku@gmail.com>
References: <4AB84CDD.3030600@gmail.com> <C6E27CCF.38FE8%rpenno@juniper.net> <a7c8d0a30909252205t29eee6e8sea896b94169aab02@mail.gmail.com>
In-Reply-To: <a7c8d0a30909252205t29eee6e8sea896b94169aab02@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Cameron Byrne <cb.list6@gmail.com>, Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Comments on NAT64 draft
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/mail-archive/web/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>
X-List-Received-Date: Sat, 26 Sep 2009 20:27:06 -0000

On 2009-09-26 17:05, Zhen Cao wrote:
> I thinks we should keep the NAT64 compatible with NAT44 in dealing
> with out of order fragments.
> 
> Also in this case, what the implementor should do is dealing with the
> first arriving out-of-order fragment. Buffering the fragment is
> troublesome but it is easy to couple with some timeout scheme to avoid
> consuming too much resource. So from implementation point, this does
> not count much.

In the 4 to 6 direction, if you have to calculate the UDP checksum, you
have to buffer all the fragments. And if the first fragment happens to arrive
last, you don't know until then whether you have to calculate the checksum.
So it seems to me that it is significantly worse than NAT44, because you
always have to buffer all UDP fragments in that case. I don't mean to say
it's impossible, but we should be very clear what we are requiring.

   Brian

> 
> Thanks,
> Zhen
> 
> On Sat, Sep 26, 2009 at 4:57 AM, Reinaldo Penno <rpenno@juniper.net> wrote:
>> There is certainly the engineering issue which we could debate but it would
>> be good to hear service provider requirements in relation to this aspect in
>> the context of NAT64. In the case of NAT44 dropping fragments is not okay
>> (at least this is what I hear).
>>
>> Thanks,
>>
>> Reinaldo
>>
>>
>>
>> On 9/21/09 9:04 PM, "Brian E Carpenter" <brian.e.carpenter@gmail.com> wrote:
>>
>>> On 2009-09-18 13:29, Zhen Cao wrote:
>>>>>>> Any ideas from implementers? Is it problematic to have to buffer and
>>>>>>> reassemble UDP fragments that don't match any state in the v6->v4
>>>>>>> direction?
>>>>>> According to RFC 4787 Requirement 14, a NAT MUST accommodate this out
>>>>>> of order fragment situation.
>>>>> This seems extreme; I wonder why it wasn't a SHOULD. However,
>>>>> that's a BCP for IPv4-IPv4 NATs "as described in [RFC2663]."
>>>>> We can decide independently for NAT64, but Iljitsch has asked the
>>>>> right question: how big a deal is this for implementors?
>>>> It might not be a big problem for implementor, considering it only
>>>> hurts the first out-of-order fragmented packet of the flow. Also from
>>>> the statistics you provided several days before, fragmented UDP
>>>> packets counts to a very small percentage.
>>> Correct. But if such packets consume 100 times more resource in the
>>> NAT, they could still be a problem. That's an engineering question,
>>> and I am still not sure of the answer.
>>>
>>>> But changing the text in NAT64 is also not a big deal. We can analyze
>>>> this in the document a bit for the consideration of implementors. This
>>>> will do no harm and make the document as solid as possible.
>>> Yes. But I think there is quite a big difference in this case between
>>> a SHOULD and a MUST.
>>>
>>>     Brian
>>> _______________________________________________
>>> Behave mailing list
>>> Behave@ietf.org
>>> https://www.ietf.org/mailman/listinfo/behave
>>
> 

From xuxh@huawei.com  Sat Sep 26 18:18:23 2009
Return-Path: <xuxh@huawei.com>
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 CA4EF3A6808 for <behave@core3.amsl.com>; Sat, 26 Sep 2009 18:18:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.255
X-Spam-Level: ***
X-Spam-Status: No, score=3.255 tagged_above=-999 required=5 tests=[AWL=-0.528,  BAYES_05=-1.11, CN_BODY_35=0.339, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, MIME_CHARSET_FARAWAY=2.45, 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 cJ0ldgQXwOZB for <behave@core3.amsl.com>; Sat, 26 Sep 2009 18:18:22 -0700 (PDT)
Received: from szxga02-in.huawei.com (unknown [119.145.14.65]) by core3.amsl.com (Postfix) with ESMTP id C04FF3A67D7 for <behave@ietf.org>; Sat, 26 Sep 2009 18:18:22 -0700 (PDT)
Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KQL00EV9VO24X@szxga02-in.huawei.com> for behave@ietf.org; Sun, 27 Sep 2009 09:19:14 +0800 (CST)
Received: from huawei.com ([172.24.1.33]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KQL00KSIVO2N1@szxga02-in.huawei.com> for behave@ietf.org; Sun, 27 Sep 2009 09:19:14 +0800 (CST)
Received: from HUAWEIE75F8F11 ([10.111.12.212]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KQL00MS1VO2KJ@szxml06-in.huawei.com> for behave@ietf.org; Sun, 27 Sep 2009 09:19:14 +0800 (CST)
Date: Sun, 27 Sep 2009 09:19:14 +0800
From: Xu Xiaohu <xuxh@huawei.com>
In-reply-to: <20090925073422.4B31A3A683F@core3.amsl.com>
To: 'Behave WG' <behave@ietf.org>
Message-id: <002301ca3f10$872adbc0$d40c6f0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=gb2312
Content-transfer-encoding: quoted-printable
Thread-index: Aco9ssmlDpiZ2QUiT0ixtvFF5brqTgBW3+pg
Cc: mohamed.boucadair@orange-ftgroup.com
Subject: [BEHAVE] fwd: New Version Notification for draft-xu-behave-stateful-nat-standby-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/mail-archive/web/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>
X-List-Received-Date: Sun, 27 Sep 2009 01:18:23 -0000

Hi all,

I just submitted an updated version of =
draft-xu-behave-stateful-nat-standby.
The link is
http://tools.ietf.org/id/draft-xu-behave-stateful-nat-standby-01.txt.

The major changes from the 00 version are:
1) Mohamed Boucadair is added as co-author.
2) Editorial Changes which make the draft more readable.

The detailed difference is shown in
http://tools.ietf.org/rfcdiff?difftype=3D--hwdiff&url2=3Ddraft-xu-behave-=
statefu
l-nat-standby-01.txt.

Any comment is welcomed!

Xiaohu

> -----=D3=CA=BC=FE=D4=AD=BC=FE-----
> =B7=A2=BC=FE=C8=CB: IETF I-D Submission Tool =
[mailto:idsubmission@ietf.org]
> =B7=A2=CB=CD=CA=B1=BC=E4: 2009=C4=EA9=D4=C225=C8=D5 15:34
> =CA=D5=BC=FE=C8=CB: xuxh@huawei.com
> =D6=F7=CC=E2: New Version Notification for =
draft-xu-behave-stateful-nat-standby-01
>=20
>=20
> A new version of I-D, draft-xu-behave-stateful-nat-standby-01.txt has =
been
> successfuly submitted by Xiaohu Xu and posted to the IETF repository.
>=20
> Filename:	 draft-xu-behave-stateful-nat-standby
> Revision:	 01
> Title:		 Redundancy and Load Balancing Framework for
Stateful Network
> Address Translators (NAT)
> Creation_date:	 2009-09-25
> WG ID:		 Independent Submission
> Number_of_pages: 13
>=20
> Abstract:
> This document defines a framework for ensuring redundancy and/or
> load balancing for stateful Network Address Translators (NAT),
> including NAT44, NAT46 and NAT64.
>=20
> Conventions used in this document
>=20
> The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
> "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
> document are to be interpreted as described in RFC-2119 [RFC2119].
>=20
>=20
>=20
> The IETF Secretariat.



From root@core3.amsl.com  Sun Sep 27 23:30:01 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: behave@ietf.org
Delivered-To: behave@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 845C63A6869; Sun, 27 Sep 2009 23:30: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: <20090928063001.845C63A6869@core3.amsl.com>
Date: Sun, 27 Sep 2009 23:30:01 -0700 (PDT)
Cc: behave@ietf.org
Subject: [BEHAVE] I-D Action:draft-ietf-behave-nat-behavior-discovery-08.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/mail-archive/web/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>
X-List-Received-Date: Mon, 28 Sep 2009 06:30:01 -0000

--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 Behavior Discovery Using STUN
	Author(s)       : D. MacDonald, B. Lowekamp
	Filename        : draft-ietf-behave-nat-behavior-discovery-08.txt
	Pages           : 31
	Date            : 2009-09-27

This specification defines an experimental usage of the Session
Traversal Utilities for NAT (STUN) Protocol that discovers the
presence and current behaviour of NATs and firewalls between the STUN
client and the STUN server.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-behave-nat-behavior-discovery-08.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-behavior-discovery-08.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From derek.macdonald@gmail.com  Sun Sep 27 23:35:10 2009
Return-Path: <derek.macdonald@gmail.com>
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 E103D3A67ED for <behave@core3.amsl.com>; Sun, 27 Sep 2009 23:35:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.184
X-Spam-Level: 
X-Spam-Status: No, score=-0.184 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, HTML_MESSAGE=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 opqwcEB9cX5S for <behave@core3.amsl.com>; Sun, 27 Sep 2009 23:35:09 -0700 (PDT)
Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.24]) by core3.amsl.com (Postfix) with ESMTP id 828E93A67CF for <behave@ietf.org>; Sun, 27 Sep 2009 23:35:09 -0700 (PDT)
Received: by qw-out-2122.google.com with SMTP id 5so669034qwi.31 for <behave@ietf.org>; Sun, 27 Sep 2009 23:36:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=Fo3Xc+cxUKiAozOd79/jG5Q2szKcHuLbePa1Sl7R5T8=; b=OEj8Q3xagCEjfYYwN7aOzjl2JxRY/H+/kk1hS6YvmGnfGUHn6DNz/DvC6L7OKkdchs gvYM34ZpT8xtDfTAHGlXyDrCnT8YPNi43tkUItBTp1OWoODd6Hs7v1tsTgEJIHe3edSd AGAQC/Y8wmIIS+tCorOU/j0vXc7SejDTNDsxs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=tiaeVCpLeQ3gjePk2GzSvb8Eo9OXP6ko0AwMMoNlDVIvLhppQuuOS38XVyEfyQjMmU A7a1XT12taXU4izOi7T2Fz8KsnqT1sK72fXFvRWPnICA8KJksM5Hrm54uNJUS9hd0Awu JPOXEJ7eQtrAESlIY1icibk8wck1ImE2aFQ5A=
MIME-Version: 1.0
Received: by 10.229.59.215 with SMTP id m23mr1013480qch.4.1254119784456; Sun,  27 Sep 2009 23:36:24 -0700 (PDT)
Date: Sun, 27 Sep 2009 23:36:24 -0700
Message-ID: <ef68b73f0909272336h91cebe1tc065104f42a3011b@mail.gmail.com>
From: Derek MacDonald <derek.macdonald@gmail.com>
To: Behave WG <behave@ietf.org>
Content-Type: multipart/alternative; boundary=002354790ac04222e304749d8480
Subject: [BEHAVE] New revision of behavior-discovery 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/mail-archive/web/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>
X-List-Received-Date: Mon, 28 Sep 2009 06:35:11 -0000

--002354790ac04222e304749d8480
Content-Type: text/plain; charset=ISO-8859-1

Hi all,

I've just submitted a version of behavior-discovery:
draft-ietf-behave-nat-behavior-discovery-08.txt. I don't see the new rev in
the tracker yet.

 Important changes to the document as described below; inline with text from
original comments which led to the changes.

Cullen Jenning:
>
> Discuss:
>
> The usage of RESPONSE-TARGET seems like it would only need to allow
> the response port, not IP address to be changed. This would improve
> the security situation. Why is the IP address allowed to change?
>

XOR-RESPONSE-TARGET is now RESPONSE-PORT. This also greatly simplified the
security considerations. CACHE-TIMEOUT and XOR-REFLECTED have been removed.

Dan Romascanu
>
Discuss:
> 1. The document presents as principal usage of NAT behavior discovery
> network diagonstics for 'network administrator or system programmer
> trying to determine the causes of network failure; particularly when
> behavior varies by load, destination, or other factors that may be
> related to NAT behavior'. This almost sounds like another OAM layer,
> or duplicating the OAM layer functionality. It is not clear however
> how this is going to be activated, will this run permanently or on
> demand, how are results being collected by an operator using discovery
> as a diagnostics tool
>
Behaviour-discovery is meant to be an applictation level mechanism. It will
be up to applications using this mechanism to determine how aggresively it
will be used, and if diagnostics will be recorded or if it will just be used
to adjust application behaviour.

>
> 2. I do not understand well what 'experimental success' section 2.3
> refers to. This is not about the success of the experiment of the
> discovery method, but rather about whether an application can improve
> its behavior. Using the 'Experimental Success' title for this section
> is confusing.
>
Success is defined as an improvement over existing behvaiour; there could be
varying levels of success. I couldn't think of a better phrase or any
percentage based metrics that have good provenance.

>
> Comment:
> At the end of Section 1:
>
>   If a draft specifies the use of any portion of this STUN usage, that
>   draft MUST document
>
Changed to "standards document"

Tim Polk
>
> It seems clear that two of the conditions for NAT behavior discovery
> to be generally
> useful are
> (1) detecting the "correct" information a reasonably high percentage
> of the time; and
>
The percentage of time that "correct" information is required will vary
greatly from application to aplication, so no one value could be selected.


> (2) unambiguous determination that the fallback mechanism should be
> invoked.
>
This is cleared up the the section describing referencing standards.

Lisa Dusseault
> Comment: [IESG Evaluation DISCUSS]
>
> This is a good document & I have a few comments. Most of the comments are
> minor; the question about discovering a STUN server with this new usage
> supported is probably the biggest issue. But it's probably not a blocking
> issue, so I plan to clear this DISCUSS and let the authors handle this
> input as
> they will, after getting a chance to discuss on the telechat.
>
> There is an unambiguous mechanism when SRV is used; when it isn't used, it
would seem that we might need to add an attribute to a Binding Response to
solve this problem. However, 5389 support can be determined, as can support
for PADDING and RESPONSE-PORT, so it might not be necessary. Personally, I
don't have a strong opinion on this either way.

I also incorporate a fair bit of the suggested text for Section 1 and the
other changes for 2, 3.6 and 7.3 from
https://datatracker.ietf.org/idtracker/draft-ietf-behave-nat-behavior-discovery/comment/99576/
.

-Derek

--002354790ac04222e304749d8480
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi all,<br><br>I&#39;ve just submitted a version of behavior-discovery: dra=
ft-ietf-behave-nat-behavior-discovery-08.txt. I don&#39;t see the new rev i=
n the tracker yet.<br><div id=3D":8b" class=3D"ii gt"><br> </div>=A0Importa=
nt changes to the document as described below; inline with text from origin=
al comments which led to the changes.<br>
<br><blockquote style=3D"border-left: 1px solid rgb(204, 204, 204); margin:=
 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class=3D"gmail_quote">
Cullen Jenning:<br><br>Discuss:<br><br>
The usage of RESPONSE-TARGET seems like it would only need to allow<br>
the response port, not IP address to be changed. This would improve<br>
the security situation. Why is the IP address allowed to change?<br></block=
quote><br>XOR-RESPONSE-TARGET is now RESPONSE-PORT. This also greatly simpl=
ified the security considerations. CACHE-TIMEOUT and XOR-REFLECTED have bee=
n removed.<br>
<br><blockquote style=3D"border-left: 1px solid rgb(204, 204, 204); margin:=
 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class=3D"gmail_quote">
<div>Dan Romascanu <br></div></blockquote><blockquote style=3D"border-left:=
 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex=
;" class=3D"gmail_quote">Discuss:<br>
1. The document presents as principal usage of NAT behavior discovery<br>
network diagonstics for &#39;network administrator or system programmer<br>
trying to determine the causes of network failure; particularly when<br>
behavior varies by load, destination, or other factors that may be<br>
related to NAT behavior&#39;. This almost sounds like another OAM layer,<br=
>
or duplicating the OAM layer functionality. It is not clear however<br>
how this is going to be activated, will this run permanently or on<br>
demand, how are results being collected by an operator using discovery<br>
as a diagnostics tool<br></blockquote><div>Behaviour-discovery is meant to =
be an applictation level mechanism. It will be up to applications using thi=
s mechanism to determine how aggresively it will be used, and if diagnostic=
s will be recorded or if it will just be used to adjust application behavio=
ur. <br>

</div><blockquote style=3D"border-left: 1px solid rgb(204, 204, 204); margi=
n: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class=3D"gmail_quote"><br>
2. I do not understand well what &#39;experimental success&#39; section 2.3=
<br>
refers to. This is not about the success of the experiment of the<br>
discovery method, but rather about whether an application can improve<br>
its behavior. Using the &#39;Experimental Success&#39; title for this secti=
on<br>
is confusing.<br></blockquote><div>Success is defined as an improvement ove=
r existing behvaiour; there could be varying levels of success. I couldn&#3=
9;t think of a better phrase or any percentage based metrics that have good=
 provenance.<br>

</div><blockquote style=3D"border-left: 1px solid rgb(204, 204, 204); margi=
n: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class=3D"gmail_quote"><br>
Comment:<br>
At the end of Section 1:<br><br>
=A0 If a draft specifies the use of any portion of this STUN usage, that<br=
>
=A0 draft MUST document<br></blockquote>



Changed to &quot;standards document&quot;<br><br><blockquote style=3D"borde=
r-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-le=
ft: 1ex;" class=3D"gmail_quote">Tim Polk<br><br>It seems clear that two of =
the conditions for NAT behavior discovery<br>


to be generally<br>
useful are<br>
(1) detecting the &quot;correct&quot; information a reasonably high percent=
age<br>
of the time; and<br></blockquote><div>The percentage of time that &quot;cor=
rect&quot; information is required will vary greatly from application to ap=
lication, so no one value could be selected.<br>=A0</div><blockquote style=
=3D"border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; p=
adding-left: 1ex;" class=3D"gmail_quote">


(2) unambiguous determination that the fallback mechanism should be invoked=
.<br></blockquote><div>This is cleared up the the section describing refere=
ncing standards.<br><br><blockquote style=3D"border-left: 1px solid rgb(204=
, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class=3D"gmail_=
quote">

Lisa Dusseault<br>Comment: [IESG Evaluation DISCUSS]<br><br>This is a good =
document &amp; I have a few comments.  Most of the comments are<br>minor; t=
he question about discovering a STUN server with this new usage<br>supporte=
d is probably the biggest issue.  But it&#39;s probably not a blocking<br>

issue, so I plan to clear this DISCUSS and let the authors handle this inpu=
t as<br>they will, after getting a chance to discuss on the telechat.<br><b=
r></blockquote><div>There is an unambiguous mechanism when SRV is used; whe=
n it isn&#39;t used, it would seem that we might need to add an attribute t=
o a Binding Response to solve this problem. However, 5389 support can be de=
termined, as can support for PADDING and RESPONSE-PORT, so it might not be =
necessary. Personally, I don&#39;t have a strong opinion on this either way=
.<br>

<br>I also incorporate a fair bit of the suggested text for Section 1 and t=
he other changes for 2, 3.6 and 7.3 from <a href=3D"https://datatracker.iet=
f.org/idtracker/draft-ietf-behave-nat-behavior-discovery/comment/99576/" ta=
rget=3D"_blank">https://datatracker.ietf.org/idtracker/draft-ietf-behave-na=
t-behavior-discovery/comment/99576/</a>.<br>

<br>-Derek<br><br></div></div><br>

--002354790ac04222e304749d8480--

From zhangdong_rh@huaweisymantec.com  Mon Sep 28 23:27:41 2009
Return-Path: <zhangdong_rh@huaweisymantec.com>
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 D5C873A6A60; Mon, 28 Sep 2009 23:27:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.52
X-Spam-Level: 
X-Spam-Status: No, score=0.52 tagged_above=-999 required=5 tests=[AWL=-0.474,  BAYES_05=-1.11, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  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 zqYA4t4hDYFi; Mon, 28 Sep 2009 23:27:41 -0700 (PDT)
Received: from mta2.huaweisymantec.com (unknown [218.17.155.15]) by core3.amsl.com (Postfix) with ESMTP id 1106E3A6A5F; Mon, 28 Sep 2009 23:27:41 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; charset=gb2312
Received: from hstml01-in.huaweisymantec.com ([172.26.3.42]) by hstga02-in.huaweisymantec.com (Sun Java(tm) System Messaging Server 6.3-8.03 (built Apr 24 2009; 32bit)) with ESMTP id <0KQP0022PZBIUI10@hstga02-in.huaweisymantec.com>; Tue, 29 Sep 2009 14:28:30 +0800 (CST)
Received: from z90001956 ([10.27.154.76]) by hstml01-in.huaweisymantec.com (Sun Java(tm) System Messaging Server 6.3-8.03 (built Apr 24 2009; 32bit)) with ESMTPA id <0KQP003Q7ZBHQR10@hstml01-in.huaweisymantec.com>; Tue, 29 Sep 2009 14:28:30 +0800 (CST)
Date: Tue, 29 Sep 2009 14:28:29 +0800
From: Dong Zhang <zhangdong_rh@huaweisymantec.com>
To: Joel Jaeggli <joelja@bogus.com>
References: <002601ca3745$63c8b710$d40c6f0a@china.huawei.com> <"57F95EAE-6705, -4B8E-849F-3F35D7239EDD"@free.fr> <08BA2C59E081884DB2AAE4A0BE9D6DC162A3BE@ftrdmel0.rd.francetelecom.fr> <4AB3F4C9.4070701@gmail.com> <182A3219-DCEE-4FAC-9676-5718CA3AEEA1@free.fr> <12F4112206976147A34FEC0277597CCF27A40BAA9C@XCH-NW-15V.nw.nos.boeing.com> <200909251554046771722@huaweisymantec.com> <4ABCDCF5.3080907@bogus.com>
Message-id: <200909291428289139664@huaweisymantec.com>
X-Mailer: Foxmail 6, 10, 201, 20 [cn]
Cc: "softwires@ietf.org" <softwires@ietf.org>, =?gb2312?B?UultaV9EZXNAY29yZTMuYW1zbC5jb20=?= <R***i_Des@core3.amsl.com>, "Templin, Fred L" <Fred.L.Templin@boeing.com>, "behave@ietf.org" <behave@ietf.org>, "eric.burgey@orange-ftgroup.com" <eric.burgey@orange-ftgroup.com>
Subject: Re: [BEHAVE] [Softwires]	Some	Thought	aboutthe	AutomaticTunnelAddress
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/mail-archive/web/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>
X-List-Received-Date: Tue, 29 Sep 2009 06:27:41 -0000

Hi Joel,

Joel Jaeggli 2009-09-25 Wrote:
>
>
>Dong Zhang wrote:
>>> That depends on one's definition of "site". I would consider
>>> the ISP network as a site that contains other sites (i.e.,
>>> recursively-nested sites-within-sites).
>> 
>> Imho, the word of "site" means a network. However, the size 
>> of the network is not fixed. It seems that "site" is not a 
>> clear concept. This leads to some misunderstanding.
>> If there is a specific definition for "site",
>> it could be easier to understand when using this word.
>
>Part of the problem with site-local was that the scope was ambiguous.
Agree.
>the term is not rooted in a discrete object with a position in the
>topology, contrast with autonomous system or prefix.
Just because of this point, it would better confirm the scope of
"site" when talking about it in case misunderstanding and confusion.

Thank you.

------------------				 
Dong Zhang
2009-09-29


From root@core3.amsl.com  Tue Sep 29 09:30:01 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: behave@ietf.org
Delivered-To: behave@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id CBD933A6942; Tue, 29 Sep 2009 09:30:01 -0700 (PDT)
From: IESG Secretary <iesg-secretary@ietf.org>
To: ietf-announce@ietf.org
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20090929163001.CBD933A6942@core3.amsl.com>
Date: Tue, 29 Sep 2009 09:30:01 -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/mail-archive/web/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>
X-List-Received-Date: Tue, 29 Sep 2009 16:30:02 -0000

A modified charter has been submitted for the Behavior Engineering for
Hindrance Avoidance (behave) 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 Tuesday, October
6, 2009.

Behavior Engineering for Hindrance Avoidance (behave)
-----------------------------------------------------
Current Status: Active Working Group
Last Modified: 2009-09-09

Current Status: Active Working Group

Additional information is available at tools.ietf.org/wg/behave
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://www.ietf.org/mail-archive/web/behave

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 and is usable with both IPv4 and 
IPv6, and capable of relaying between the two IP versions.

Due to the WG's experience with translators and their behavior it has 
been given the following tasks to help 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 six 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 is intended to service a specific IPv4 network using either 
private or public IPv4 addresses. This scenario has different 
constraints compared to (1), e.g. the IPv4 hosts that are to be 
reachable over IPv6 can be enumerated. Therefore, 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.

5. An IPv6 network to an IPv4 network, i.e., perform translation between
IPv6 and IPv4 for packets in uni- or bi-directional flows that are 
initiated from an IPv6 host towards an IPv4 host.  The translation 
function is intended to service a specific IPv6 network of arbitrary 
size and a specific IPv4 network of arbitrary size (neither of which are 
the Internet).

6. An IPv4 network 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 translation 
function is intended to service a specific IPv6 network of arbitrary 
size and a specific IPv4 network of arbitrary size (neither of which are 
the Internet).

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 parts of ICMP that can be translated are also required 
to work across a translation solution.  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.

Goals and Milestones:

Done	  Submit BCP that defines unicast UDP behavioral requirements 
for NATs to IESG
Done	  Submit a BCP that defines TCP behavioral requireents 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 2009  Submit to IESG: SCTP NAT behavior (BCP)
Done      Submit to IESG: relay protocol (std)
Done      Determine relative prioritization of the four translation 
cases. Documented in IETF74 minutes.
Sep 2009  Submit to IESG: relaying of a TCP bytestream (std)
Dec 2009  Submit to IESG: IPv6 relay protocol (std)
Done      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. Documented in IETF74 minutes.
Done      Submit to IESG:  TURN-URI document (std)
Dec 2009  Submit to IESG:  framework for IPv6/IPv4 translation (info)
Dec 2009  Submit to IESG:  stateless IPv6/IPv4 translation (std)
Dec 2009  Submit to IESG:  stateful IPv6/IPv4 translation (std)
Dec 2009  Submit to IESG:  DNS rewriting for IPv6/IPv4 translation (std)
Jan 2010  Submit to IESG:  FTP ALG for IPv6/IPv4 translation (std)
Jan 2010  Submit to IESG:  IPv6 prefix for IPv6/IPv4 translator (std)
Mar 2010  Submit to IESG:  large scale NAT requirements (BCP)

From brian.e.carpenter@gmail.com  Tue Sep 29 13:06:32 2009
Return-Path: <brian.e.carpenter@gmail.com>
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 282143A688D; Tue, 29 Sep 2009 13:06:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[AWL=0.164,  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 1P7myt78acOF; Tue, 29 Sep 2009 13:06:31 -0700 (PDT)
Received: from mail-pz0-f197.google.com (mail-pz0-f197.google.com [209.85.222.197]) by core3.amsl.com (Postfix) with ESMTP id 687B93A63EB; Tue, 29 Sep 2009 13:06:31 -0700 (PDT)
Received: by pzk35 with SMTP id 35so5563595pzk.29 for <multiple recipients>; Tue, 29 Sep 2009 13:07:49 -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=1OwWKNDLtEuvSxF13u8a+QXRxLUX8oVMN1x5UoO3Sho=; b=jgjDZ3iMCek3Z+avj7NuQ5K12TE6gN8f2rnlx/JOmBa8U/LnroNwS1pj8lxVeOYQ7V wfQ6O3hu2cKXAJcgWP2zFULbWUfLBcNBbGJtUGeV2kqjdBRNepgCkrjwa9oQ2bFgjTRI KEMX8rnpAwfDHD7547hHyY8Ne8yRpSL6Nkbdo=
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=g319yi4okvj/sP9HM9xaX5BSjKSe7LM+hYuQNZ9eZx9JQDV50Ca9qFFKu+DPQmWczr DPL/WDuIOsiqBk0g+Ahh2jovMFnuhwW6MZU3F5ifnPCH6nJX1q5KkiA6SXLug8naomq8 VHbfQPcLeCt5Q1rRYHl2MmJMvTjHZ3viFn25c=
Received: by 10.115.132.6 with SMTP id j6mr8808106wan.4.1254254869031; Tue, 29 Sep 2009 13:07:49 -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 20sm2989861pzk.1.2009.09.29.13.07.47 (version=SSLv3 cipher=RC4-MD5); Tue, 29 Sep 2009 13:07:48 -0700 (PDT)
Message-ID: <4AC2685E.9010203@gmail.com>
Date: Wed, 30 Sep 2009 09:04:46 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Dong Zhang <zhangdong_rh@huaweisymantec.com>
References: <002601ca3745$63c8b710$d40c6f0a@china.huawei.com>	<"57F95EAE-6705, -4B8E-849F-3F35D7239EDD"@free.fr>	<08BA2C59E081884DB2AAE4A0BE9D6DC162A3BE@ftrdmel0.rd.francetelecom.fr>	<4AB3F4C9.4070701@gmail.com>	<182A3219-DCEE-4FAC-9676-5718CA3AEEA1@free.fr>	<12F4112206976147A34FEC0277597CCF27A40BAA9C@XCH-NW-15V.nw.nos.boeing.com>	<200909251554046771722@huaweisymantec.com> <4ABCDCF5.3080907@bogus.com> <200909291428289139664@huaweisymantec.com>
In-Reply-To: <200909291428289139664@huaweisymantec.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "softwires@ietf.org" <softwires@ietf.org>, "Templin, Fred L" <Fred.L.Templin@boeing.com>, "behave@ietf.org" <behave@ietf.org>, "eric.burgey@orange-ftgroup.com" <eric.burgey@orange-ftgroup.com>
Subject: [BEHAVE] What is a site? [Re: [Softwires]Some Thought about the Automatic Tunnel Address
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/mail-archive/web/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>
X-List-Received-Date: Tue, 29 Sep 2009 20:06:32 -0000

On 2009-09-29 19:28, Dong Zhang wrote:
...
>> Part of the problem with site-local was that the scope was ambiguous.
> Agree.
>> the term is not rooted in a discrete object with a position in the
>> topology, contrast with autonomous system or prefix.
> Just because of this point, it would better confirm the scope of
> "site" when talking about it in case misunderstanding and confusion.

It may be impossible. Actually I'd be very interested to hear any comments
about the approach to defining address scope that we have taken in
draft-carpenter-behave-referral-object. Maybe what we call a "limited scope"
is a site? This should be discussed at a BOF in Hiroshima. Comments on the
grobj mailing list please:
 grobj@ietf.org
 https://www.ietf.org/mailman/listinfo/grobj .

    Brian


From Fred.L.Templin@boeing.com  Tue Sep 29 14:10:41 2009
Return-Path: <Fred.L.Templin@boeing.com>
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 2F45E3A680A; Tue, 29 Sep 2009 14:10:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.067
X-Spam-Level: 
X-Spam-Status: No, score=-6.067 tagged_above=-999 required=5 tests=[AWL=0.532,  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 ZGrMvajoVQo7; Tue, 29 Sep 2009 14:10:40 -0700 (PDT)
Received: from stl-smtpout-01.boeing.com (stl-smtpout-01.boeing.com [130.76.96.56]) by core3.amsl.com (Postfix) with ESMTP id 4A7043A6358; Tue, 29 Sep 2009 14:10:40 -0700 (PDT)
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6]) by stl-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id n8TLAo6g018208 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 29 Sep 2009 16:10:50 -0500 (CDT)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id n8TLAoTH016177; Tue, 29 Sep 2009 16:10:50 -0500 (CDT)
Received: from XCH-NWHT-11.nw.nos.boeing.com (xch-nwht-11.nw.nos.boeing.com [130.247.25.114]) by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id n8TLAnXR016166 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Tue, 29 Sep 2009 16:10:50 -0500 (CDT)
Received: from XCH-NW-15V.nw.nos.boeing.com ([130.247.25.104]) by XCH-NWHT-11.nw.nos.boeing.com ([130.247.25.114]) with mapi; Tue, 29 Sep 2009 14:10:49 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Dong Zhang <zhangdong_rh@huaweisymantec.com>
Date: Tue, 29 Sep 2009 14:10:48 -0700
Thread-Topic: [BEHAVE] What is a site? [Re: [Softwires]Some Thought about theAutomatic Tunnel Address
Thread-Index: AcpBQIm09KAiHGSNQBm620Vz+9RVwgABee9w
Message-ID: <12F4112206976147A34FEC0277597CCF27A40BB48F@XCH-NW-15V.nw.nos.boeing.com>
References: <002601ca3745$63c8b710$d40c6f0a@china.huawei.com>	<"57F95EAE-670 5, -4B8E-849F-3F35D7239EDD"@free.fr>	<08BA2C59E081884DB2AAE4A0BE9D6DC162A3BE @ftrdmel0.rd.francetelecom.fr>	<4AB3F4C9.4070701@gmail.com>	<182A3219-DCEE- 4FAC-9676-5718CA3AEEA1@free.fr>	<12F4112206976147A34FEC0277597CCF27A40BAA9C @XCH-NW-15V.nw.nos.boeing.com>	<200909251554046771722@huaweisymantec.com><4 ABCDCF5.3080907@bogus.com><200909291428289139664@huaweisymantec.com> <4AC2685E.9010203@gmail.com>
In-Reply-To: <4AC2685E.9010203@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-tm-as-product-ver: SMEX-8.0.0.1181-5.600.1016-16888.004
x-tm-as-result: No--71.283000-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "softwires@ietf.org" <softwires@ietf.org>, "grobj@ietf.org" <grobj@ietf.org>, "eric.burgey@orange-ftgroup.com" <eric.burgey@orange-ftgroup.com>, "behave@ietf.org" <behave@ietf.org>
Subject: Re: [BEHAVE] What is a site? [Re: [Softwires]Some Thought about theAutomatic Tunnel Address
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/mail-archive/web/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>
X-List-Received-Date: Tue, 29 Sep 2009 21:10:41 -0000

Brian,

> -----Original Message-----
> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On Behalf =
Of Brian E Carpenter
> Sent: Tuesday, September 29, 2009 1:05 PM
> To: Dong Zhang
> Cc: softwires@ietf.org; Templin, Fred L; behave@ietf.org; eric.burgey@ora=
nge-ftgroup.com
> Subject: [BEHAVE] What is a site? [Re: [Softwires]Some Thought about theA=
utomatic Tunnel Address
>=20
> On 2009-09-29 19:28, Dong Zhang wrote:
> ...
> >> Part of the problem with site-local was that the scope was ambiguous.
> > Agree.
> >> the term is not rooted in a discrete object with a position in the
> >> topology, contrast with autonomous system or prefix.
> > Just because of this point, it would better confirm the scope of
> > "site" when talking about it in case misunderstanding and confusion.
>=20
> It may be impossible. Actually I'd be very interested to hear any comment=
s
> about the approach to defining address scope that we have taken in
> draft-carpenter-behave-referral-object. Maybe what we call a "limited sco=
pe"
> is a site? This should be discussed at a BOF in Hiroshima. Comments on th=
e
> grobj mailing list please:
>  grobj@ietf.org
>  https://www.ietf.org/mailman/listinfo/grobj .

I'm not sure it is impossible to define "site"; a site is
just a logical or physical partition (bounded by site border
routers) within a connected routing region. As long as the
nodes within the site remain associated with their site
border routers, they are still within the same site.

Back to site-locals, my understanding was that RFC4193
ULAs were introduced in part to accommodate sites that
partition or merge. As long as each site border router
configures and advertises a its own ULA prefix, there
would be no ambiguity regarding the scope over which
the ULA applies.

Fred
fred.l.templin@boeing.com=20
=20
>     Brian
>=20
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave

From brian.e.carpenter@gmail.com  Tue Sep 29 15:00:13 2009
Return-Path: <brian.e.carpenter@gmail.com>
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 17BF33A683B; Tue, 29 Sep 2009 15:00:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.437
X-Spam-Level: 
X-Spam-Status: No, score=-2.437 tagged_above=-999 required=5 tests=[AWL=0.162,  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 O0bBmfYUqaSx; Tue, 29 Sep 2009 15:00:12 -0700 (PDT)
Received: from mail-px0-f173.google.com (mail-px0-f173.google.com [209.85.216.173]) by core3.amsl.com (Postfix) with ESMTP id 3368B3A6837; Tue, 29 Sep 2009 15:00:12 -0700 (PDT)
Received: by pxi3 with SMTP id 3so7527137pxi.31 for <multiple recipients>; Tue, 29 Sep 2009 15:01: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=k8PLw6ULAZokx6ANi81WGT/9HXgV3drm7e2eFXjUT98=; b=fWr3BsWkvUagalWV2XW9zy7J92BER3ARQQ9C2GEeU00l3dsDBA/cIRFElPVyGFOwYB 6RIyR6ksVOwTEbO67+m9/t7sHdvBKRWhg/f0/LmvWQUPF28T80ENuNLNneDI3M5K8OnA O2RvNFaXsMcdeEp92bdZz+3btOTjlY3dJyfIo=
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=OQ1IH5pCHbWhSHk9QAcHwe8kaoO9fVeRvXLqYMNTnzzefoDMCvgPxpKKDWRCjdr3Dc /VRYEQHTQDv1LBlkrdXN/hLRS7/m/F3yyhT8vvwIqC4RfyYvJV/BpIecuByE/QULeSCa MDkO+UtskKIzbykcYX7b73ftMCr7x/ySz8+pg=
Received: by 10.114.33.30 with SMTP id g30mr9030733wag.214.1254261690104; Tue, 29 Sep 2009 15:01: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 23sm1259728pxi.1.2009.09.29.15.01.28 (version=SSLv3 cipher=RC4-MD5); Tue, 29 Sep 2009 15:01:29 -0700 (PDT)
Message-ID: <4AC283B6.6000001@gmail.com>
Date: Wed, 30 Sep 2009 11:01: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: "Templin, Fred L" <Fred.L.Templin@boeing.com>
References: <002601ca3745$63c8b710$d40c6f0a@china.huawei.com>	<"57F95EAE-670	5, -4B8E-849F-3F35D7239EDD"@free.fr>	<08BA2C59E081884DB2AAE4A0BE9D6DC162A3BE	@ftrdmel0.rd.francetelecom.fr>	<4AB3F4C9.4070701@gmail.com>	<182A3219-DCEE-	4FAC-9676-5718CA3AEEA1@free.fr>	<12F4112206976147A34FEC0277597CCF27A40BAA9C	@XCH-NW-15V.nw.nos.boeing.com>	<200909251554046771722@huaweisymantec.com><4	ABCDCF5.3080907@bogus.com><200909291428289139664@huaweisymantec.com> <4AC2685E.9010203@gmail.com> <12F4112206976147A34FEC0277597CCF27A40BB48F@XCH-NW-15V.nw.nos.boeing.com>
In-Reply-To: <12F4112206976147A34FEC0277597CCF27A40BB48F@XCH-NW-15V.nw.nos.boeing.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "softwires@ietf.org" <softwires@ietf.org>, "grobj@ietf.org" <grobj@ietf.org>, Dong Zhang <zhangdong_rh@huaweisymantec.com>, "behave@ietf.org" <behave@ietf.org>, "eric.burgey@orange-ftgroup.com" <eric.burgey@orange-ftgroup.com>
Subject: Re: [BEHAVE] What is a site? [Re: [Softwires]Some Thought about the Automatic Tunnel Address
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/mail-archive/web/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>
X-List-Received-Date: Tue, 29 Sep 2009 22:00:13 -0000

On 2009-09-30 10:10, Templin, Fred L wrote:
> Brian,
> 
>> -----Original Message-----
>> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On Behalf Of Brian E Carpenter
>> Sent: Tuesday, September 29, 2009 1:05 PM
>> To: Dong Zhang
>> Cc: softwires@ietf.org; Templin, Fred L; behave@ietf.org; eric.burgey@orange-ftgroup.com
>> Subject: [BEHAVE] What is a site? [Re: [Softwires]Some Thought about theAutomatic Tunnel Address
>>
>> On 2009-09-29 19:28, Dong Zhang wrote:
>> ...
>>>> Part of the problem with site-local was that the scope was ambiguous.
>>> Agree.
>>>> the term is not rooted in a discrete object with a position in the
>>>> topology, contrast with autonomous system or prefix.
>>> Just because of this point, it would better confirm the scope of
>>> "site" when talking about it in case misunderstanding and confusion.
>> It may be impossible. Actually I'd be very interested to hear any comments
>> about the approach to defining address scope that we have taken in
>> draft-carpenter-behave-referral-object. Maybe what we call a "limited scope"
>> is a site? This should be discussed at a BOF in Hiroshima. Comments on the
>> grobj mailing list please:
>>  grobj@ietf.org
>>  https://www.ietf.org/mailman/listinfo/grobj .
> 
> I'm not sure it is impossible to define "site"; a site is
> just a logical or physical partition (bounded by site border
> routers) within a connected routing region. As long as the
> nodes within the site remain associated with their site
> border routers, they are still within the same site.
> 
> Back to site-locals, my understanding was that RFC4193
> ULAs were introduced in part to accommodate sites that
> partition or merge. As long as each site border router
> configures and advertises a its own ULA prefix, there
> would be no ambiguity regarding the scope over which
> the ULA applies.

That can change if you use the ULA over a VPN to another "site",
or if the scope is chopped up with a NAT. I think it's rather
a different thing for a human to understand what the effective
scope is, compared with all hosts knowing algorithmically the
scope of an arbitrary address. I think Dong Zhang is asking for
an algorithmic definition.

    Brian

From swb@employees.org  Tue Sep 29 15:52:42 2009
Return-Path: <swb@employees.org>
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 0A8753A68F3; Tue, 29 Sep 2009 15:52:42 -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 vUKZleCGtweE; Tue, 29 Sep 2009 15:52:41 -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 D9A8E3A67AA; Tue, 29 Sep 2009 15:52:40 -0700 (PDT)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEAOcswkpAZnme/2dsb2JhbAC+N5h+hB4F
X-IronPort-AV: E=Sophos;i="4.44,475,1249257600"; d="scan'208";a="60618003"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-2.cisco.com with ESMTP; 29 Sep 2009 22:54:01 +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 n8TMs1rV023469;  Tue, 29 Sep 2009 18:54:01 -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.14.3) with ESMTP id n8TMs16R025737; Tue, 29 Sep 2009 22:54:01 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 29 Sep 2009 18:54:01 -0400
Received: from sbrim-mbp.local ([10.86.243.253]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 29 Sep 2009 18:54:00 -0400
Message-ID: <4AC29008.9080104@employees.org>
Date: Tue, 29 Sep 2009 18:54:00 -0400
From: Scott Brim <swb@employees.org>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <002601ca3745$63c8b710$d40c6f0a@china.huawei.com>	<"57F95EAE-670	5, -4B8E-849F-3F35D7239EDD"@free.fr>	<08BA2C59E081884DB2AAE4A0BE9D6DC162A3BE	@ftrdmel0.rd.francetelecom.fr>	<4AB3F4C9.4070701@gmail.com>	<182A3219-DCEE-	4FAC-9676-5718CA3AEEA1@free.fr>	<12F4112206976147A34FEC0277597CCF27A40BAA9C	@XCH-NW-15V.nw.nos.boeing.com>	<200909251554046771722@huaweisymantec.com><4	ABCDCF5.3080907@bogus.com><200909291428289139664@huaweisymantec.com>	<4AC2685E.9010203@gmail.com>	<12F4112206976147A34FEC0277597CCF27A40BB48F@XCH-NW-15V.nw.nos.boeing.com> <4AC283B6.6000001@gmail.com>
In-Reply-To: <4AC283B6.6000001@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 29 Sep 2009 22:54:01.0125 (UTC) FILETIME=[BC56DD50:01CA4157]
Cc: "behave@ietf.org" <behave@ietf.org>, "Templin, Fred L" <Fred.L.Templin@boeing.com>, "grobj@ietf.org" <grobj@ietf.org>, "softwires@ietf.org" <softwires@ietf.org>, "eric.burgey@orange-ftgroup.com" <eric.burgey@orange-ftgroup.com>, Dong Zhang <zhangdong_rh@huaweisymantec.com>
Subject: Re: [BEHAVE] [grobj] What is a site? [Re: [Softwires]Some Thought about the Automatic Tunnel Address
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/mail-archive/web/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>
X-List-Received-Date: Tue, 29 Sep 2009 22:52:42 -0000

Brian E Carpenter allegedly wrote on 09/29/2009 6:01 PM:
>> I'm not sure it is impossible to define "site"; a site is
>> just a logical or physical partition (bounded by site border
>> routers) within a connected routing region. As long as the
>> nodes within the site remain associated with their site
>> border routers, they are still within the same site.
>>
>> Back to site-locals, my understanding was that RFC4193
>> ULAs were introduced in part to accommodate sites that
>> partition or merge. As long as each site border router
>> configures and advertises a its own ULA prefix, there
>> would be no ambiguity regarding the scope over which
>> the ULA applies.
> 
> That can change if you use the ULA over a VPN to another "site",
> or if the scope is chopped up with a NAT. I think it's rather
> a different thing for a human to understand what the effective
> scope is, compared with all hosts knowing algorithmically the
> scope of an arbitrary address. I think Dong Zhang is asking for
> an algorithmic definition.

That gives you two different viewpoints: that of the tunnel client (of
whatever size) and that of the network transporting the tunnel.  From
the point of view of the client it is in the same "site" as the other
client.  Outside the tunnel IP forwarders see the outer header, and
carry it across a "site" boundary.

The scope is not physical.  A site is defined by shared state and
behaviors that cannot be done outside of a "site" scope.

imho fwiw, ymmv ... swb

From zhangdong_rh@huaweisymantec.com  Tue Sep 29 19:28:59 2009
Return-Path: <zhangdong_rh@huaweisymantec.com>
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 6BB8C3A6887; Tue, 29 Sep 2009 19:28:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.256
X-Spam-Level: 
X-Spam-Status: No, score=-1.256 tagged_above=-999 required=5 tests=[AWL=1.343,  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 9pC9LtUed-Uw; Tue, 29 Sep 2009 19:28:58 -0700 (PDT)
Received: from mta1.huaweisymantec.com (mta1.huaweisymantec.com [218.17.155.14]) by core3.amsl.com (Postfix) with ESMTP id 91D5D3A68FE; Tue, 29 Sep 2009 19:28:58 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; charset=gb2312
Received: from hstml01-in.huaweisymantec.com ([172.26.3.41]) by hstga01-in.huaweisymantec.com (Sun Java(tm) System Messaging Server 6.3-8.03 (built Apr 24 2009; 32bit)) with ESMTP id <0KQR00M7RIXYH7B0@hstga01-in.huaweisymantec.com>; Wed, 30 Sep 2009 10:29:59 +0800 (CST)
Received: from z90001956 ([10.27.154.76]) by hstml01-in.huaweisymantec.com (Sun Java(tm) System Messaging Server 6.3-8.03 (built Apr 24 2009; 32bit)) with ESMTPA id <0KQR00GZGIXXN100@hstml01-in.huaweisymantec.com>; Wed, 30 Sep 2009 10:29:58 +0800 (CST)
Date: Wed, 30 Sep 2009 10:29:57 +0800
From: Dong Zhang <zhangdong_rh@huaweisymantec.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "Templin, Fred L" <Fred.L.Templin@boeing.com>
References: <002601ca3745$63c8b710$d40c6f0a@china.huawei.com> <"57F95EAE-670, 5, -4B8E-849F-3F35D7239EDD"@free.fr> <08BA2C59E081884DB2AAE4A0BE9D6DC162A3BE@ftrdmel0.rd.francetelecom.fr> <4AB3F4C9.4070701@gmail.com> <"182A3219-DCEE-, 4FAC-9676-5718CA3AEEA1"@free.fr> <12F4112206976147A34FEC0277597CCF27A40BAA9C@XCH-NW-15V.nw.nos.boeing.com> <200909251554046771722@huaweisymantec.com> <"4, ABCDCF5.3080907"@bogus.com> <200909291428289139664@huaweisymantec.com> <4AC2685E.9010203@gmail.com> <12F4112206976147A34FEC0277597CCF27A40BB48F@XCH-NW-15V.nw.nos.boeing.com> <4AC283B6.6000001@gmail.com>
Message-id: <200909301029575879351@huaweisymantec.com>
X-Mailer: Foxmail 6, 10, 201, 20 [cn]
Cc: "softwires@ietf.org" <softwires@ietf.org>, "behave@ietf.org" <behave@ietf.org>, "eric.burgey@orange-ftgroup.com" <eric.burgey@orange-ftgroup.com>, "grobj@ietf.org" <grobj@ietf.org>
Subject: Re: [BEHAVE] What is a site? [Re: [Softwires]Some Thought about theAutomatic Tunnel Address
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/mail-archive/web/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>
X-List-Received-Date: Wed, 30 Sep 2009 02:28:59 -0000

Brian E Carpenter 2009-09-30 Wrote:
>> I'm not sure it is impossible to define "site"; a site is
>> just a logical or physical partition (bounded by site border
>> routers) within a connected routing region. As long as the
>> nodes within the site remain associated with their site
>> border routers, they are still within the same site.
>> 
>> Back to site-locals, my understanding was that RFC4193
>> ULAs were introduced in part to accommodate sites that
>> partition or merge. As long as each site border router
>> configures and advertises a its own ULA prefix, there
>> would be no ambiguity regarding the scope over which
>> the ULA applies.
>
>That can change if you use the ULA over a VPN to another "site",
>or if the scope is chopped up with a NAT. I think it's rather
>a different thing for a human to understand what the effective
>scope is, compared with all hosts knowing algorithmically the
>scope of an arbitrary address. I think Dong Zhang is asking for
>an algorithmic definition.
Hmm... Yes.


------------------				 
Dong Zhang
2009-09-30


From zhangdong_rh@huaweisymantec.com  Tue Sep 29 19:45:11 2009
Return-Path: <zhangdong_rh@huaweisymantec.com>
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 1ACD63A6892; Tue, 29 Sep 2009 19:45:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.26
X-Spam-Level: 
X-Spam-Status: No, score=-0.26 tagged_above=-999 required=5 tests=[AWL=0.235,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  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 A6EW5RObFyxY; Tue, 29 Sep 2009 19:45:10 -0700 (PDT)
Received: from mta2.huaweisymantec.com (unknown [218.17.155.15]) by core3.amsl.com (Postfix) with ESMTP id 584923A6875; Tue, 29 Sep 2009 19:45:10 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; charset=gb2312
Received: from hstml02-in.huaweisymantec.com ([172.26.3.42]) by hstga02-in.huaweisymantec.com (Sun Java(tm) System Messaging Server 6.3-8.03 (built Apr 24 2009; 32bit)) with ESMTP id <0KQR00DI5JP9G490@hstga02-in.huaweisymantec.com>; Wed, 30 Sep 2009 10:46:21 +0800 (CST)
Received: from z90001956 ([10.27.154.76]) by hstml02-in.huaweisymantec.com (Sun Java(tm) System Messaging Server 6.3-8.03 (built Apr 24 2009; 32bit)) with ESMTPA id <0KQR00JVEJP8LL00@hstml02-in.huaweisymantec.com>; Wed, 30 Sep 2009 10:46:21 +0800 (CST)
Date: Wed, 30 Sep 2009 10:46:20 +0800
From: Dong Zhang <zhangdong_rh@huaweisymantec.com>
To: Scott Brim <swb@employees.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <002601ca3745$63c8b710$d40c6f0a@china.huawei.com> <"57F95EAE-670, 5, -4B8E-849F-3F35D7239EDD"@free.fr> <08BA2C59E081884DB2AAE4A0BE9D6DC162A3BE@ftrdmel0.rd.francetelecom.fr> <4AB3F4C9.4070701@gmail.com> <"182A3219-DCEE-, 4FAC-9676-5718CA3AEEA1"@free.fr> <12F4112206976147A34FEC0277597CCF27A40BAA9C@XCH-NW-15V.nw.nos.boeing.com> <200909251554046771722@huaweisymantec.com> <"4, ABCDCF5.3080907"@bogus.com> <200909291428289139664@huaweisymantec.com> <4AC2685E.9010203@gmail.com> <12F4112206976147A34FEC0277597CCF27A40BB48F@XCH-NW-15V.nw.nos.boeing.com> <4AC283B6.6000001@gmail.com> <4AC29008.9080104@employees.org>
Message-id: <200909301046205407238@huaweisymantec.com>
X-Mailer: Foxmail 6, 10, 201, 20 [cn]
Cc: "softwires@ietf.org" <softwires@ietf.org>, "grobj@ietf.org" <grobj@ietf.org>, "Templin, Fred L" <Fred.L.Templin@boeing.com>, "behave@ietf.org" <behave@ietf.org>, "eric.burgey@orange-ftgroup.com" <eric.burgey@orange-ftgroup.com>
Subject: Re: [BEHAVE] [grobj] What is a site? [Re: [Softwires]Some Thoughtabout the Automatic Tunnel Address
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/mail-archive/web/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>
X-List-Received-Date: Wed, 30 Sep 2009 02:45:11 -0000

Hi Scott,
Scott Brim 2009-09-30 Wrote:
>That gives you two different viewpoints: that of the tunnel client (of
>whatever size) and that of the network transporting the tunnel.  From
>the point of view of the client it is in the same "site" as the other
>client.  Outside the tunnel IP forwarders see the outer header, and
>carry it across a "site" boundary.
>
>The scope is not physical.  A site is defined by shared state and
>behaviors that cannot be done outside of a "site" scope.
Agree, imho, the nodes who have the same behaviors, policy rules and so on 
compose a "site". It is a logical scope. If so, the unambiguous definition 
of logical partition rule should be unified.

Thanks.
------------------				 
Dong Zhang
2009-09-30


From Xiangsong.Cui@huawei.com  Tue Sep 29 19:48:56 2009
Return-Path: <Xiangsong.Cui@huawei.com>
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 664523A67AD for <behave@core3.amsl.com>; Tue, 29 Sep 2009 19:48:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.535
X-Spam-Level: 
X-Spam-Status: No, score=-0.535 tagged_above=-999 required=5 tests=[AWL=-0.041, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1, STOX_REPLY_TYPE=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 87zl9vXl0DR1 for <behave@core3.amsl.com>; Tue, 29 Sep 2009 19:48:55 -0700 (PDT)
Received: from szxga02-in.huawei.com (unknown [119.145.14.65]) by core3.amsl.com (Postfix) with ESMTP id 61A1E3A672E for <behave@ietf.org>; Tue, 29 Sep 2009 19:48:55 -0700 (PDT)
Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KQR000G9JVIB0@szxga02-in.huawei.com> for behave@ietf.org; Wed, 30 Sep 2009 10:50:07 +0800 (CST)
Received: from c00111037 ([10.111.16.64]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KQR00DGFJVIRN@szxga02-in.huawei.com> for behave@ietf.org; Wed, 30 Sep 2009 10:50:06 +0800 (CST)
Date: Wed, 30 Sep 2009 10:50:06 +0800
From: Xiangsong Cui <Xiangsong.Cui@huawei.com>
To: behave@ietf.org
Message-id: <007601ca4178$b791ff40$40106f0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Outlook Express 6.00.2900.3598
Content-type: text/plain; format=flowed; charset=ISO-8859-1; reply-type=original
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <20090909091501.EFF623A68BC@core3.amsl.com>
Subject: Re: [BEHAVE] I-D Action:draft-ietf-behave-v6v4-xlate-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/mail-archive/web/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>
X-List-Received-Date: Wed, 30 Sep 2009 02:48:56 -0000

Hello all,

I'm reading this draft and I have a comment.

In section 3.1 Translating IPv6 Headers into IPv4 Headers,
for the protocol translation, it says
"Protocol:  Next Header field copied from IPv6 header."

It seems that in the translation procedure, the protocol type
copying is before the IPv6 extension headers' being ignored.

For the example mentioned in section 4 of [RFC2460],

   +---------------+----------------+------------------------
   |   IPv6 header   | Routing header  | TCP header + data
   |                         |                          |
   | Next Header = |  Next Header = |
   |    Routing         |         TCP          |
   +---------------+----------------+------------------------
The value of Next Header field in IPv6 header is for Routing header.

So, how about changing this sentence to a clearer statement?
such as "Next Header field copied from IPv6 header if there is no
IPv6 extension header, or copied from the last IPv6 extension header"...

Regards
Xiangsong


----- Original Message ----- 
From: <Internet-Drafts@ietf.org>
To: <i-d-announce@ietf.org>
Cc: <behave@ietf.org>
Sent: Wednesday, September 09, 2009 5:15 PM
Subject: [BEHAVE] I-D Action:draft-ietf-behave-v6v4-xlate-01.txt


>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           : IP/ICMP Translation Algorithm
> Author(s)       : X. Li, et al.
> Filename        : draft-ietf-behave-v6v4-xlate-01.txt
> Pages           : 24
> Date            : 2009-09-09
>
> 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 stateless and a stateful mode.
> In the stateless mode, translation information is carried in the
> address itself, permitting both IPv4->IPv6 and IPv6->IPv4 session
> establishment without maintaining state in the IP/ICMP translator.
> 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.  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 stateless and stateful modes that are
> not addressed in this document, related to the address assignment and
> the maintenance of the translation tables, respectively.  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.
>
> The changes in this document reflect five components:
>
> 1.  Redescribing the network model to map to present and projected
>
> usage [I-D.ietf-behave-v6v4-framework].
>
> 2.  Moving the address format to the address format document
>
> [I-D.ietf-behave-address-format], to coordinate with other drafts
>
> on the topic.
>
> 3.  Describing both stateful and stateless operation.
> 4.  Some changes in ICMP.
>
> 5.  Updating references.
>
> Requirements
>
> The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
> "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
> document are to be interpreted as described in RFC 2119.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-behave-v6v4-xlate-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.
>


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


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


From william.polk@nist.gov  Wed Sep 30 06:06:16 2009
Return-Path: <william.polk@nist.gov>
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 D64C93A6941 for <behave@core3.amsl.com>; Wed, 30 Sep 2009 06:06:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.523
X-Spam-Level: 
X-Spam-Status: No, score=-6.523 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FO81MMkLh5UA for <behave@core3.amsl.com>; Wed, 30 Sep 2009 06:06:16 -0700 (PDT)
Received: from smtp.nist.gov (rimp1.nist.gov [129.6.16.226]) by core3.amsl.com (Postfix) with ESMTP id F21403A693B for <behave@ietf.org>; Wed, 30 Sep 2009 06:06:15 -0700 (PDT)
Received: from WSXGHUB1.xchange.nist.gov (wsxghub1.nist.gov [129.6.18.96]) by smtp.nist.gov (8.13.1/8.13.1) with ESMTP id n8UD78hq010385; Wed, 30 Sep 2009 09:07:08 -0400
Received: from MBCLUSTER.xchange.nist.gov ([fe80::d479:3188:aec0:cb66]) by WSXGHUB1.xchange.nist.gov ([2002:8106:1260::8106:1260]) with mapi; Wed, 30 Sep 2009 09:06:54 -0400
From: "Polk, William T." <william.polk@nist.gov>
To: Cullen Jennings <fluffy@cisco.com>, Magnus Westerlund <magnus.westerlund@ericsson.com>
Date: Wed, 30 Sep 2009 09:06:53 -0400
Thread-Topic: [BEHAVE] Discusses regarding security mechanism usage for TURN
Thread-Index: Aco28sP7p4vDTBIdQfaaBGhXofJVewK3B0v4
Message-ID: <C6E8D02D.15B22%tim.polk@nist.gov>
In-Reply-To: <DEC650B6-6380-41CD-9049-DE87D3D3CD55@cisco.com>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_C6E8D02D15B22timpolknistgov_"
MIME-Version: 1.0
X-NIST-MailScanner: Found to be clean
X-NIST-MailScanner-From: william.polk@nist.gov
X-Mailman-Approved-At: Wed, 30 Sep 2009 08:16:28 -0700
Cc: "Polk, William T." <william.polk@nist.gov>, Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] Discusses regarding security mechanism usage for TURN
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/mail-archive/web/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>
X-List-Received-Date: Wed, 30 Sep 2009 13:06:16 -0000

--_000_C6E8D02D15B22timpolknistgov_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

This would work for me too.


On 9/16/09 12:51 PM, "Cullen Jennings" <fluffy@cisco.com> wrote:



On Sep 14, 2009, at 1:15 , Magnus Westerlund wrote:

> NEW:
>    [RFC5389] specifies a Long-Term Credential mechanism for STUN.
> TURN
>    servers and clients MUST implement this mechanism.  The server MUST
>    demand that all requests from the client be authenticated using
> this
>    mechanism, or that a equally strong or stronger mechanism for
> client
>    authentication is used. One such mechanism is TLS, if using client
>    and server certificates that actually identify the parties, i.e. no
>    self-signed certificates.  The client MUST always be prepared to
>    authenticate requests use the Long-Term Credential mechanism if
>    required.
>
> Cullen and Tim, does this text satisfies your discusses?

That would solve my concern.

Cullen <in my AD role>




--_000_C6E8D02D15B22timpolknistgov_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Re: [BEHAVE] Discusses regarding security mechanism usage for TURN</=
TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:=
11pt'>This would work for me too.<BR>
<BR>
<BR>
On 9/16/09 12:51 PM, &quot;Cullen Jennings&quot; &lt;<a href=3D"fluffy@cisc=
o.com">fluffy@cisco.com</a>&gt; wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"=
><SPAN STYLE=3D'font-size:11pt'><BR>
<BR>
On Sep 14, 2009, at 1:15 , Magnus Westerlund wrote:<BR>
<BR>
&gt; NEW:<BR>
&gt; &nbsp;&nbsp;&nbsp;[RFC5389] specifies a Long-Term Credential mechanism=
 for STUN. &nbsp;<BR>
&gt; TURN<BR>
&gt; &nbsp;&nbsp;&nbsp;servers and clients MUST implement this mechanism. &=
nbsp;The server MUST<BR>
&gt; &nbsp;&nbsp;&nbsp;demand that all requests from the client be authenti=
cated using <BR>
&gt; this<BR>
&gt; &nbsp;&nbsp;&nbsp;mechanism, or that a equally strong or stronger mech=
anism for <BR>
&gt; client<BR>
&gt; &nbsp;&nbsp;&nbsp;authentication is used. One such mechanism is TLS, i=
f using client<BR>
&gt; &nbsp;&nbsp;&nbsp;and server certificates that actually identify the p=
arties, i.e. no<BR>
&gt; &nbsp;&nbsp;&nbsp;self-signed certificates. &nbsp;The client MUST alwa=
ys be prepared to<BR>
&gt; &nbsp;&nbsp;&nbsp;authenticate requests use the Long-Term Credential m=
echanism if<BR>
&gt; &nbsp;&nbsp;&nbsp;required.<BR>
&gt;<BR>
&gt; Cullen and Tim, does this text satisfies your discusses?<BR>
<BR>
That would solve my concern.<BR>
<BR>
Cullen &lt;in my AD role&gt;<BR>
<BR>
<BR>
<BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>


--_000_C6E8D02D15B22timpolknistgov_--

From Fred.L.Templin@boeing.com  Wed Sep 30 08:22:03 2009
Return-Path: <Fred.L.Templin@boeing.com>
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 986A23A67B4; Wed, 30 Sep 2009 08:22:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.073
X-Spam-Level: 
X-Spam-Status: No, score=-6.073 tagged_above=-999 required=5 tests=[AWL=0.526,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b+NExYJWUELI; Wed, 30 Sep 2009 08:22:02 -0700 (PDT)
Received: from slb-smtpout-01.boeing.com (slb-smtpout-01.boeing.com [130.76.64.48]) by core3.amsl.com (Postfix) with ESMTP id 937F93A659B; Wed, 30 Sep 2009 08:22:02 -0700 (PDT)
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4]) by slb-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id n8UFMPPF011361 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 30 Sep 2009 08:22:25 -0700 (PDT)
Received: from slb-av-01.boeing.com (localhost [127.0.0.1]) by slb-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id n8UFMPft008651; Wed, 30 Sep 2009 08:22:25 -0700 (PDT)
Received: from XCH-NWHT-07.nw.nos.boeing.com (xch-nwht-07.nw.nos.boeing.com [130.247.25.111]) by slb-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id n8UFMOLL008606 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Wed, 30 Sep 2009 08:22:25 -0700 (PDT)
Received: from XCH-NW-15V.nw.nos.boeing.com ([130.247.25.104]) by XCH-NWHT-07.nw.nos.boeing.com ([130.247.25.111]) with mapi; Wed, 30 Sep 2009 08:22:24 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Date: Wed, 30 Sep 2009 08:22:24 -0700
Thread-Topic: [BEHAVE] What is a site? [Re: [Softwires]Some Thought about theAutomatic Tunnel Address
Thread-Index: AcpBUGcCSOf/Qx53QCGjn58nwgRMmQAkE9Bg
Message-ID: <12F4112206976147A34FEC0277597CCF27A40BB5F8@XCH-NW-15V.nw.nos.boeing.com>
References: <002601ca3745$63c8b710$d40c6f0a@china.huawei.com>	<"57F95EAE-670 5, -4B8E-849F-3F35D7239EDD"@free.fr>	<08BA2C59E081884DB2AAE4A0BE9D6DC162A3B E	@ftrdmel0.rd.francetelecom.fr>	<4AB3F4C9.4070701@gmail.com>	<182A3219-DCE E-	4FAC-9676-5718CA3AEEA1@free.fr>	<12F4112206976147A34FEC0277597CCF27A40BA A9C	@XCH-NW-15V.nw.nos.boeing.com>	<200909251554046771722@huaweisymantec.co m><4	ABCDCF5.3080907@bogus.com><200909291428289139664@huaweisymantec.com> <4AC2685E.9010203@gmail.com> <12F4112206976147A34FEC0277597CCF27A40BB48F@XCH-NW-15V.nw.nos.boeing.com> <4AC283B6.6000001@gmail.com>
In-Reply-To: <4AC283B6.6000001@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-tm-as-product-ver: SMEX-8.0.0.1181-3.800.1026-15056.000
x-tm-as-result: No--62.927900-8.000000-2
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "softwires@ietf.org" <softwires@ietf.org>, "grobj@ietf.org" <grobj@ietf.org>, Dong Zhang <zhangdong_rh@huaweisymantec.com>, "behave@ietf.org" <behave@ietf.org>, "eric.burgey@orange-ftgroup.com" <eric.burgey@orange-ftgroup.com>
Subject: Re: [BEHAVE] What is a site? [Re: [Softwires]Some Thought about theAutomatic Tunnel Address
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/mail-archive/web/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>
X-List-Received-Date: Wed, 30 Sep 2009 15:22:03 -0000

Hi Brian,

> -----Original Message-----
> From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com]
> Sent: Tuesday, September 29, 2009 3:01 PM
> To: Templin, Fred L
> Cc: Dong Zhang; softwires@ietf.org; behave@ietf.org; eric.burgey@orange-f=
tgroup.com; grobj@ietf.org
> Subject: Re: [BEHAVE] What is a site? [Re: [Softwires]Some Thought about =
theAutomatic Tunnel Address
>=20
> On 2009-09-30 10:10, Templin, Fred L wrote:
> > Brian,
> >
> >> -----Original Message-----
> >> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On Beha=
lf Of Brian E Carpenter
> >> Sent: Tuesday, September 29, 2009 1:05 PM
> >> To: Dong Zhang
> >> Cc: softwires@ietf.org; Templin, Fred L; behave@ietf.org; eric.burgey@=
orange-ftgroup.com
> >> Subject: [BEHAVE] What is a site? [Re: [Softwires]Some Thought about t=
heAutomatic Tunnel Address
> >>
> >> On 2009-09-29 19:28, Dong Zhang wrote:
> >> ...
> >>>> Part of the problem with site-local was that the scope was ambiguous=
.
> >>> Agree.
> >>>> the term is not rooted in a discrete object with a position in the
> >>>> topology, contrast with autonomous system or prefix.
> >>> Just because of this point, it would better confirm the scope of
> >>> "site" when talking about it in case misunderstanding and confusion.
> >> It may be impossible. Actually I'd be very interested to hear any comm=
ents
> >> about the approach to defining address scope that we have taken in
> >> draft-carpenter-behave-referral-object. Maybe what we call a "limited =
scope"
> >> is a site? This should be discussed at a BOF in Hiroshima. Comments on=
 the
> >> grobj mailing list please:
> >>  grobj@ietf.org
> >>  https://www.ietf.org/mailman/listinfo/grobj .
> >
> > I'm not sure it is impossible to define "site"; a site is
> > just a logical or physical partition (bounded by site border
> > routers) within a connected routing region. As long as the
> > nodes within the site remain associated with their site
> > border routers, they are still within the same site.
> >
> > Back to site-locals, my understanding was that RFC4193
> > ULAs were introduced in part to accommodate sites that
> > partition or merge. As long as each site border router
> > configures and advertises a its own ULA prefix, there
> > would be no ambiguity regarding the scope over which
> > the ULA applies.
>=20
> That can change if you use the ULA over a VPN to another "site",
> or if the scope is chopped up with a NAT. I think it's rather
> a different thing for a human to understand what the effective
> scope is, compared with all hosts knowing algorithmically the
> scope of an arbitrary address. I think Dong Zhang is asking for
> an algorithmic definition.

I think what I was suggesting can be expressed algorithmically.
For a node within a site, as long as its site border routers
are still reachable and as long as its on-link or delegated
prefixes are still valid, then the node is still in the same
site. So, the site simply comprises the set of all nodes which
affiliate with the same set of site border routers in this way.

Additionally, the site is known by a name, e.g., "example.com".
Nodes within the site can resolve this name to determine the
list of site border routers.

Fred
fred.l.templin@boeing.com

>     Brian

From dwing@cisco.com  Wed Sep 30 09:31:38 2009
Return-Path: <dwing@cisco.com>
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 F030E3A677D; Wed, 30 Sep 2009 09:31:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.377
X-Spam-Level: 
X-Spam-Status: No, score=-6.377 tagged_above=-999 required=5 tests=[AWL=0.222,  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 qfdpDBg5wTAb; Wed, 30 Sep 2009 09:31:37 -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 C8C433A659B; Wed, 30 Sep 2009 09:31:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=1221; q=dns/txt; s=sjiport03001; t=1254328381; x=1255537981; h=from:sender:reply-to:subject:date:message-id:to:cc: mime-version:content-transfer-encoding:content-id: content-description:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-message-id:in-reply-to: references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; z=From:=20"Dan=20Wing"=20<dwing@cisco.com>|Reply-To:=20<gr obj@ietf.org>|Subject:=20Application=20referrals=20-=20GR OBJ|Date:=20Wed,=2030=20Sep=202009=2009:32:49=20-0700 |Message-ID:=20<07ab01ca41eb$a65db700$c2f0200a@cisco.com> |To:=20<apps-discuss@ietf.org>,=20<grobj@ietf.org>,=20<be have@ietf.org>,=0D=0A=20=20=20=20=20=20=20=20<int-area@ie tf.org>,=20"'IETF=20Discussion=20Mailing=20List'"=20<ietf @ietf.org>,=0D=0A=20=20=20=20=20=20=20=20<tae@ietf.org> |Cc:=20"'Sheng=20Jiang'"=20<shengjiang@huawei.com> |MIME-Version:=201.0|Content-Transfer-Encoding:=207bit; bh=krMTXUiqIu4kT3phUnETqZrYpuXSOlFV2BcFdqSXaqI=; b=PcIuFQHlHUA1LxD0VrqKWFQ4nG0rXjaBpRjSnBCYTjjTsBZ+OnqEVUcc zTTvbcYokMvaN2TKUuTXkNXm+xjSsvaIM/A8Ye4owRannDb6MIIdSfphL daZcB+Sv9gnwEinBGFYO7z4CR+QA1oSd91VbSFAvi7UakmJ3Qi0wl+2yQ Q=;
Authentication-Results: sj-iport-3.cisco.com; dkim=pass (signature verified [TEST]) header.i=dwing@cisco.com
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ap4EAN4kw0qrR7MV/2dsb2JhbACKcbYgiFsBkAgGhCeBUQ
X-IronPort-AV: E=Sophos;i="4.44,481,1249257600"; d="scan'208";a="193379031"
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-3.cisco.com with ESMTP; 30 Sep 2009 16:32:53 +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 n8UGWooY021145;  Wed, 30 Sep 2009 09:32:50 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id n8UGWojD000355; Wed, 30 Sep 2009 16:32:50 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.3959);  Wed, 30 Sep 2009 09:32:50 -0700
Received: from dwingwxp01 ([10.32.240.194]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 30 Sep 2009 09:32:49 -0700
From: "Dan Wing" <dwing@cisco.com>
To: <apps-discuss@ietf.org>, <grobj@ietf.org>, <behave@ietf.org>, <int-area@ietf.org>, "'IETF Discussion Mailing List'" <ietf@ietf.org>,  <tae@ietf.org>
Date: Wed, 30 Sep 2009 09:32:49 -0700
Message-ID: <07ab01ca41eb$a65db700$c2f0200a@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcpB66XyIThkGbtVQJiZNN/LMtPkEQ==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-OriginalArrivalTime: 30 Sep 2009 16:32:49.0916 (UTC) FILETIME=[A67313C0:01CA41EB]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1221; t=1254328370; x=1255192370; 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=20referrals=20-=20GROBJ |Sender:=20; bh=krMTXUiqIu4kT3phUnETqZrYpuXSOlFV2BcFdqSXaqI=; b=M9zn8IEelPCptMasbWN5a6LS0CnuWnG9lx3yN9v1JD3iN9r8xDauoL/AZk FNqkP3TLG9mLJp0RI/EYz51gm/K/NgnaJDk9vpChCV44tFR3edvVoPIjejIf ysGbeFeCPNrmMfq7Sa415FdfgmHCpjrS1An1f993Jnnv0NjFzJ8UM=;
Cc: 'Sheng Jiang' <shengjiang@huawei.com>
Subject: [BEHAVE] Application referrals - GROBJ
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: grobj@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/mail-archive/web/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>
X-List-Received-Date: Wed, 30 Sep 2009 16:31:39 -0000

(Please send replies to grobj@ietf.org)

Today's applications usually exchange an IP address and a TCP (or UDP)
port for referrals.  While this works in a wide variety of situations,
it has been shown insufficient with more complex networks that consist
of different address realms (due to IPv4 NATs and IPv6 ULAs),
different address families (IPv4 and IPv6) and new transport protocols
(such as SCTP).  Some applications have pursued their own mechanisms
to extend their referral mechanism (e.g., draft-ietf-mmusic-ice).

It is important to provide guidance to applications and network
devices so that referrals can work between two applications.  Such
guidance is important today, and will be more important as networks
become more complex with common deployments of host and network
multi-homing, tunnels, VPNs, and address family translators.

The mailing list GROBJ has been created to discuss Generic Referral 
Objects (GRO) for application referrals.  Interested parties can 
join the mailing list at https://www.ietf.org/mailman/listinfo/grobj

Draft:
http://tools.ietf.org/html/draft-carpenter-behave-referral-object

BoF proposal: http://www.cs.auckland.ac.nz/~brian/GROBJ-BOF.txt

-d

