Re: [MEXT] tsv-dir review of draft-ietf-mext-nemo-v4traversal-06.txt

Colin Perkins <csp@csperkins.org> Wed, 03 December 2008 09:50 UTC

Return-Path: <mext-bounces@ietf.org>
X-Original-To: monami6-archive@megatron.ietf.org
Delivered-To: ietfarch-monami6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 588D53A6870; Wed, 3 Dec 2008 01:50:51 -0800 (PST)
X-Original-To: mext@core3.amsl.com
Delivered-To: mext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 86B7D3A6870; Wed, 3 Dec 2008 01:42:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.227
X-Spam-Level:
X-Spam-Status: No, score=-6.227 tagged_above=-999 required=5 tests=[AWL=0.372, 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 T0Ko-idLVGaE; Wed, 3 Dec 2008 01:42:54 -0800 (PST)
Received: from mr1.dcs.gla.ac.uk (mr1.dcs.gla.ac.uk [130.209.249.184]) by core3.amsl.com (Postfix) with ESMTP id 7AE7C3A6B42; Wed, 3 Dec 2008 01:42:54 -0800 (PST)
Received: from starkperkins.demon.co.uk ([80.176.158.71]:63160 helo=[192.168.0.4]) by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42) id 1L7oFs-0000zM-4V; Wed, 03 Dec 2008 09:42:48 +0000
In-Reply-To: <493591AC.2030303@piuha.net>
References: <FB1A81A1-8ADB-43DC-A820-9BDE8EE75919@csperkins.org> <493591AC.2030303@piuha.net>
Mime-Version: 1.0 (Apple Message framework v753.1)
Message-Id: <066113AC-B0BC-4817-9FE3-1F953FC7D770@csperkins.org>
From: Colin Perkins <csp@csperkins.org>
Date: Wed, 3 Dec 2008 09:42:44 +0000
To: Jari Arkko <jari.arkko@piuha.net>
X-Mailer: Apple Mail (2.753.1)
X-Mailman-Approved-At: Wed, 03 Dec 2008 01:50:50 -0800
Cc: "mext@ietf.org" <mext@ietf.org>, TSV Dir <tsv-dir@ietf.org>, ietf@ietf.org
Subject: Re: [MEXT] tsv-dir review of draft-ietf-mext-nemo-v4traversal-06.txt
X-BeenThere: mext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobile IPv6 EXTensions WG <mext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mext>, <mailto:mext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/mext>
List-Post: <mailto:mext@ietf.org>
List-Help: <mailto:mext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mext>, <mailto:mext-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: mext-bounces@ietf.org
Errors-To: mext-bounces@ietf.org

On 2 Dec 2008, at 19:51, Jari Arkko wrote:
> Thanks for your review, Colin.
>
> I agree that fixes or better explanations of the background should  
> be given for the points that you raised. It seems that you and  
> Hesham are making progress on what needs to be added to the  
> document, great!
>
> The only item that I too am somewhat worried about in your list is  
> the address replacement by broken NATs and the tricks used to  
> prevent that. I feel that the best way to deal with that is to  
> document this as a potential problem -- the protocol already has  
> tools to provide a far better obfuscation technique than XOR --  
> just turn on encryption if this turns out to be a problem and the  
> device in question cannot be ripped out of the network.

Agreed.

> Do we have any information about how widespread such NATs might be?  
> RFC 5389 just says "some NATs".


Not really, but something that broken can't be common: it'd cause too  
many obvious problems.

-- 
Colin Perkins
http://csperkins.org/



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