Re: [nemo] a special discussion session for threat analysis and security requirements

Alexandru Petrescu <Alexandru.Petrescu@motorola.com> Mon, 01 March 2004 09:54 UTC

Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA05979 for <nemo-archive@lists.ietf.org>; Mon, 1 Mar 2004 04:54:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Axk7d-0007c0-8r; Mon, 01 Mar 2004 04:54:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Axk7K-0007bH-Ag for nemo@optimus.ietf.org; Mon, 01 Mar 2004 04:53:42 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA05969 for <nemo@ietf.org>; Mon, 1 Mar 2004 04:53:40 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Axk7H-0006LG-00 for nemo@ietf.org; Mon, 01 Mar 2004 04:53:39 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Axk6Q-0006GE-00 for nemo@ietf.org; Mon, 01 Mar 2004 04:52:46 -0500
Received: from motgate8.mot.com ([129.188.136.8]) by ietf-mx with esmtp (Exim 4.12) id 1Axk5s-0006A8-00 for nemo@ietf.org; Mon, 01 Mar 2004 04:52:12 -0500
Received: from il06exr04.mot.com (il06exr04.mot.com [129.188.137.134]) by motgate8.mot.com (Motorola/Motgate3) with ESMTP id i219po5h007059; Mon, 1 Mar 2004 02:52:00 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8]) by il06exr04.mot.com (Motorola/il06exr04) with ESMTP id i219phjT027990; Mon, 1 Mar 2004 03:51:44 -0600
Received: from motorola.com (zfr01-2117.crm.mot.com [10.161.201.117]) by zfr01srv02.crm.mot.com (Postfix) with ESMTP id 6A6A685272E; Mon, 1 Mar 2004 10:51:43 +0100 (CET)
Message-ID: <404307AE.60701@motorola.com>
Date: Mon, 01 Mar 2004 10:51:42 +0100
From: Alexandru Petrescu <Alexandru.Petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "S. Felix Wu" <wu@cs.ucdavis.edu>
Cc: IETF NEMO WG <nemo@ietf.org>, Hong-Yon Lach <hong-yon.lach@motorola.com>
Subject: Re: [nemo] a special discussion session for threat analysis and security requirements
References: <4042B535.5010003@cs.ucdavis.edu> <4042C703.5090901@cs.ucdavis.edu>
In-Reply-To: <4042C703.5090901@cs.ucdavis.edu>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: nemo-admin@ietf.org
Errors-To: nemo-admin@ietf.org
X-BeenThere: nemo@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nemo>, <mailto:nemo-request@ietf.org?subject=unsubscribe>
List-Id: NEMO Working Group <nemo.ietf.org>
List-Post: <mailto:nemo@ietf.org>
List-Help: <mailto:nemo-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nemo>, <mailto:nemo-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

S. Felix Wu wrote:
> 
> I forgot to mention in my earlier message -- if you can not attend 
> the meeting or the discussion meeting, you are very welcome to submit
>  your opinions and comments regarding the security issue in NEMO.
> 
>> In order for us to work together more effectively as a team and to 
>> consolidate different efforts, I proposed to TJ that maybe we 
>> should have a special meeting this week in Seoul to discuss about 
>> security issue. This special discussion will be open to any one who
>>  is interested in the security issue under NEMO.

Hello Felix,

I'm interested in the security discussion of the NEMO base protocol
now, and maybe later in other security aspects related to NEMO.

I've tried to summarize most important aspects of the security threats
for NEMO base protocol, as we understand them, in
draft-petrescu-nemo-threats-01.txt.  The document benefitted from one
NEMO WG member review.

While we're not sure at this time whether we can attend the meeting
you're proposing (I personally can not) I'm interested in participating
in the eventual online discussion.  If the meeting produces some
informal minutes, I'm interested to see them, thank you.

> you are very welcome to submit your opinions and comments regarding 
> the security issue in NEMO.

Where would one start?  I think the only two issues are: (1) location
privacy and (2) threats induced by the insecure NEMO dynamic HA discovery.

Alex