Re: [Hipsec] Teredo compatibility

Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com> Mon, 21 December 2009 09:48 UTC

Return-Path: <gonzalo.camarillo@ericsson.com>
X-Original-To: hipsec@core3.amsl.com
Delivered-To: hipsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2FBA63A6949 for <hipsec@core3.amsl.com>; Mon, 21 Dec 2009 01:48:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.24
X-Spam-Level:
X-Spam-Status: No, score=-6.24 tagged_above=-999 required=5 tests=[AWL=0.009, 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 8JGCyDr-Ot24 for <hipsec@core3.amsl.com>; Mon, 21 Dec 2009 01:48:03 -0800 (PST)
Received: from mailgw5.ericsson.se (mailgw5.ericsson.se [193.180.251.36]) by core3.amsl.com (Postfix) with ESMTP id D5FC23A685A for <hipsec@ietf.org>; Mon, 21 Dec 2009 01:48:02 -0800 (PST)
X-AuditID: c1b4fb24-b7beeae000003a71-16-4b2f4441aaea
Received: from esealmw127.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw5.ericsson.se (Symantec Mail Security) with SMTP id E1.C0.14961.1444F2B4; Mon, 21 Dec 2009 10:47:45 +0100 (CET)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.175]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959); Mon, 21 Dec 2009 10:47:45 +0100
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959); Mon, 21 Dec 2009 10:47:44 +0100
Received: from [131.160.126.149] (rvi2-126-149.lmf.ericsson.se [131.160.126.149]) by mail.lmf.ericsson.se (Postfix) with ESMTP id F089324F1; Mon, 21 Dec 2009 11:47:43 +0200 (EET)
Message-ID: <4B2F443F.8070900@ericsson.com>
Date: Mon, 21 Dec 2009 11:47:43 +0200
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: "miika.komu@hiit.fi" <miika.komu@hiit.fi>
References: <4B2231E6.4020706@hiit.fi> <42A3E98A-50DE-448C-9C71-C6BA6752ED74@indranet.co.nz> <4B2234EC.3070102@hiit.fi> <A14CB7E0-56F2-4CA0-AE64-B3EA9511B3C1@indranet.co.nz> <4B2B3EB9.3090601@ericsson.com> <4B2E3757.3080408@hiit.fi>
In-Reply-To: <4B2E3757.3080408@hiit.fi>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 Dec 2009 09:47:44.0879 (UTC) FILETIME=[A5643FF0:01CA8222]
X-Brightmail-Tracker: AAAAAA==
Cc: HIP <hipsec@ietf.org>
Subject: Re: [Hipsec] Teredo compatibility
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hipsec>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Dec 2009 09:48:04 -0000

Hi,

trying to predict the outcome of the probes was mainstream thinking a 
few years ago. ICE was developed when it was pretty clear that 
prediction just did not work...

In any case, the idea in the HIP WG is to specify how to use NAT 
traversal mechanisms in HIP. If somebody wants to optimize ICE, MMUSIC 
(or maybe BEHAVE) would probably be the place to do it.

Cheers,

Gonzalo

Miika Komu wrote:
> Gonzalo Camarillo wrote:
> 
> Hi,
> 
> running ICE over Teredo works but is potentially a big overkill due to 
> redundant functionality. Some of the results can be predicted as 
> depicted below (and even incorporated in the ICE module if needed).
> 
>> Hi,
>>
>> as Andrew indicates, the whole point of ICE is that it sends probes to 
>> see what works and what does not. We should not go off and specify stuff 
>> that will be discovered anyway at run time.
>>
>> Cheers,
>>
>> Gonzalo
>>
>> Andrew McGregor wrote:
>>> Ok, but in any case, candidate address probing deals with those issues.
>>>
>>> Andrew
>>>
>>> On 12/12/2009, at 1:02 AM, Miika Komu wrote:
>>>
>>>> Andrew McGregor wrote:
>>>>
>>>> Hi,
>>>>
>>>> it should be short section then, right?)
>>>>
>>>> I basically agree with you. Based on our experimentation, it works 
>>>> but there are some caveats regarding to pairing of addressing. So, 
>>>> sending of packets from src->dst:
>>>>
>>>> Teredo->Teredo: works
>>>> Teredo->IPv6: does not work without a (commercial) relay service
>>>> IPv6->Teredo: works
>>>> IPv6->IPv6: (works :)
>>>>
>>>> Samu, please comment if I got the two middle ones in wrong order.
>>>>
>>>> Also, at least the miredo implementation on linux is good, but not 
>>>> perfect. Some performance-related issues and sometimes HIP packets 
>>>> just don't go through (usually restarting of miredo works).
>>>>
>>>>> Why?  It just works, if Teredo is available it's just another IPv6 
>>>>> address.
>>>>> Andrew
>>>>> On 12/12/2009, at 12:49 AM, Miika Komu wrote:
>>>>>> Hi,
>>>>>>
>>>>>> we've done some concrete work on NAT traversal with ICE, but what 
>>>>>> about Teredo? I think RFC5201 and RFC5206 should have some 
>>>>>> statements about Teredo-based addresses?
>>>>>> _______________________________________________
>>>>>> Hipsec mailing list
>>>>>> Hipsec@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/hipsec
>>>>>>
>>> _______________________________________________
>>> Hipsec mailing list
>>> Hipsec@ietf.org
>>> https://www.ietf.org/mailman/listinfo/hipsec
>>>
>