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

Colin Perkins <csp@csperkins.org> Mon, 01 December 2008 12:28 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 301B728C166; Mon, 1 Dec 2008 04:28:20 -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 6048F3A6A73; Mon, 1 Dec 2008 03:12:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.165
X-Spam-Level:
X-Spam-Status: No, score=-6.165 tagged_above=-999 required=5 tests=[AWL=0.434, 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 U9V8YdafapMM; Mon, 1 Dec 2008 03:12:18 -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 5FFA63A6A4C; Mon, 1 Dec 2008 03:12:18 -0800 (PST)
Received: from starkperkins.demon.co.uk ([80.176.158.71]:60740 helo=[192.168.0.4]) by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42) id 1L76hJ-00069O-H6; Mon, 01 Dec 2008 11:12:13 +0000
In-Reply-To: <4933C53B.5000303@ericsson.com>
References: <C55A089B.A7D6%hesham@elevatemobile.com> <4933C53B.5000303@ericsson.com>
Mime-Version: 1.0 (Apple Message framework v753.1)
Message-Id: <0B298FEA-6D38-4FE5-8210-A382E1E7DFA3@csperkins.org>
From: Colin Perkins <csp@csperkins.org>
Date: Mon, 1 Dec 2008 11:12:11 +0000
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
X-Mailer: Apple Mail (2.753.1)
X-Mailman-Approved-At: Mon, 01 Dec 2008 04:28:17 -0800
Cc: "mext@ietf.org" <mext@ietf.org>, TSV Dir <tsv-dir@ietf.org>, ietf@ietf.org
Subject: Re: [MEXT] [tsv-dir] 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 1 Dec 2008, at 11:06, Magnus Westerlund wrote:
> Hesham Soliman skrev:
>> Thanks Colin,
>>
>> I agree with your rationale but I wonder if we need to support  
>> every broken device out there. In any case, if we have to, I  
>> prefer to require encryption than to add the XORED address option.  
>> I'd like to hear what people in MEXT think about this, comments  
>> from MEXT?
>
> I don't think we should go to far to correct this bug in
> implementations. My understanding is that this have been observed  
> but is
> not a common behavior as these generic ALGs do break things  
> randomly and
> horribly. I would only do something about if it has no minimal  
> impact on
> the specification and any deployed implementations. Otherwise the  
> fix is
> likely to cause more grief than the few devices that are broken.


Right - the issue should be documented, and if there is a trivial fix  
it should be recommended, but this isn't a big issue.

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



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