From mip6-bounces@ietf.org  Tue Sep 21 18:19:15 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07708
	for <mip6-web-archive@ietf.org>; Tue, 21 Sep 2004 18:19:15 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C9t5B-0008Qa-Un
	for mip6-web-archive@ietf.org; Tue, 21 Sep 2004 18:25:58 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C9srQ-00017O-JN; Tue, 21 Sep 2004 18:11:44 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C9sdA-00009c-4B
	for mip6@megatron.ietf.org; Tue, 21 Sep 2004 17:57:00 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03919
	for <mip6@ietf.org>; Tue, 21 Sep 2004 17:56:57 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C9sjb-0007YQ-R5
	for mip6@ietf.org; Tue, 21 Sep 2004 18:03:40 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id i8LLuKG07088; Tue, 21 Sep 2004 23:56:20 +0200
Received: from givry.rennes.enst-bretagne.fr
	(localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.12.3/8.12.3) with ESMTP id
	i8LLuLSj054150; Tue, 21 Sep 2004 23:56:21 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200409212156.i8LLuLSj054150@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Pekka Savola <pekkas@netcore.fi>
Subject: Re: [Mip6] Justifications for standardizing
	draft-ietf-mip6-auth-protocol-00.txt 
In-reply-to: Your message of Tue, 21 Sep 2004 17:46:55 +0300.
	<Pine.LNX.4.44.0409211743200.7869-100000@netcore.fi> 
Date: Tue, 21 Sep 2004 23:56:21 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: mip6@ietf.org, Pete McCann <mccap@lucent.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a

 In your previous mail you wrote:

   I don't quite understand this.  IKEv2 is basically done.  It's past a
   couple of IESG evaluations and revisions.  Currently, the I-D tracker
   says it's in "Approved-announcement to be sent :: Point Raised -
   writeup needed" -state, meaning that there is a minor or two issues
   which need to be written out before sending it for publication as an
   RFC.  The IESG has already basically approved it.
   
=> I can't forget it took a lot of months for RFC 3775 and 3776 from
drafts to RFCs.

   So, AFAICS, the standardization status of IKEv2 should not be an
   issue.  There may be other issues with IKEv2 (such as implementation,
   number of messages, integration with AAA systems, etc.) but those are 
   the issues which can be discussed.
   
=> IMHO the main issue is the lack of implementations, in particular
open source implementations (for IKEv1 we have at least 3 well known
implementations: racoon, isakmpd and pluto). And the RFC 2401bis is
not trivial at all... Of course, I'd like to be wrong.

Thanks

Francis.Dupont@enst-bretagne.fr

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6


From mip6-bounces@ietf.org  Tue Sep 21 18:44:51 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09902
	for <mip6-web-archive@ietf.org>; Tue, 21 Sep 2004 18:44:50 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C9tTy-0000SC-4C
	for mip6-web-archive@ietf.org; Tue, 21 Sep 2004 18:51:34 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C9tIX-0006ZE-GE; Tue, 21 Sep 2004 18:39:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C9tBV-0004xB-OB
	for mip6@megatron.ietf.org; Tue, 21 Sep 2004 18:32:29 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09202
	for <mip6@ietf.org>; Tue, 21 Sep 2004 18:32:27 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C9tHw-0000En-QV
	for mip6@ietf.org; Tue, 21 Sep 2004 18:39:10 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id i8LMVVG10058; Wed, 22 Sep 2004 00:31:31 +0200
Received: from givry.rennes.enst-bretagne.fr
	(localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.12.3/8.12.3) with ESMTP id
	i8LMVWSj054621; Wed, 22 Sep 2004 00:31:32 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200409212231.i8LMVWSj054621@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "Charles E.Perkins" <charliep@iprg.nokia.com>
Subject: Re: [Mip6] Justifications
	forstandardizingdraft-ietf-mip6-auth-protocol-00.txt 
In-reply-to: Your message of Tue, 21 Sep 2004 12:00:06 PDT.
	<41507A36.CC766C0A@iprg.nokia.com> 
Date: Wed, 22 Sep 2004 00:31:32 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe

 In your previous mail you wrote:

   Francis Dupont wrote:
   
   > => I agree, manual keying is not really usable.
   
=> by "really" I meaned "in the real world for general deployment".

   This is way over the top.
   
   Manual keying is obviously usable.  People
   use it today.  It's easy.
   
=> I disagree: it is not easy and it is even difficult between
different implementations. Even pre-shared secret can be hairy!

   There is a lot of understanding about its
   limitations.  I could understand it if you
   would say,
   
   "Manual keying doesn't work when ..."
   
   or,
   
   "Manual keyong only works when ..."
   
=> it works but it is not easy to setup in the real world and
it is essentially insecure (exactly for the same reason it doesn't
provide anti-replay protection).

   or any one of a large number of reasonable
   statements.  But to say it is not really
   usable is just plain wrong.
   
=> I believe you don't understand what I've meant.

   And, I would like to also mention, it is
   pretty simple and appropriate for the scenarios
   where it does work.

=> IMHO the only scenario is in the labs...

   Sometimes it seems to me
   that such value does not receive due respect
   in security arguments.  Just because a solution
   doesn't cover all of the cases doesn't mean it
   is a kludge or is unusable.
   
=> I can't believe you suggest to use manual keying in a commercial
service... Obviously I don't understand what you mean.

Thanks

Francis.Dupont@enst-bretagne.fr

PS: I don't joke about pre-shared keys: I had the bad idea to use quotes
in a config file. And this kind of things is really (argh, I use again
this word :-) hard to debug!

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6


From mip6-bounces@ietf.org  Tue Sep 21 18:54:36 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10377
	for <mip6-web-archive@ietf.org>; Tue, 21 Sep 2004 18:54:36 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C9tdP-0000av-ES
	for mip6-web-archive@ietf.org; Tue, 21 Sep 2004 19:01:19 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C9tS9-0000Sr-W6; Tue, 21 Sep 2004 18:49:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C9tKd-0006r6-66
	for mip6@megatron.ietf.org; Tue, 21 Sep 2004 18:41:56 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09642
	for <mip6@ietf.org>; Tue, 21 Sep 2004 18:41:52 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C9tR4-0000Me-6g
	for mip6@ietf.org; Tue, 21 Sep 2004 18:48:35 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id i8LMetG10895; Wed, 22 Sep 2004 00:40:56 +0200
Received: from givry.rennes.enst-bretagne.fr
	(localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.12.3/8.12.3) with ESMTP id
	i8LMetSj054839; Wed, 22 Sep 2004 00:40:55 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200409212240.i8LMetSj054839@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
Subject: Re: [Mip6] Justifications for standardizing
	draft-ietf-mip6-auth-protocol-00.txt 
In-reply-to: Your message of Tue, 21 Sep 2004 23:56:21 +0200.
	<200409212156.i8LLuLSj054150@givry.rennes.enst-bretagne.fr> 
Date: Wed, 22 Sep 2004 00:40:55 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2870a44b67ee17965ce5ad0177e150f4
Cc: mip6@ietf.org, Pete McCann <mccap@lucent.com>,
        Pekka Savola <pekkas@netcore.fi>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014

I answer to my own message because IKEv2 draft is in last call (cf
a very recent announce from the IESG)!

Francis.Dupont@enst-bretagne.fr

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6


From mip6-bounces@ietf.org  Tue Sep 21 18:56:39 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10540
	for <mip6-web-archive@ietf.org>; Tue, 21 Sep 2004 18:56:39 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C9tfO-0000dA-5C
	for mip6-web-archive@ietf.org; Tue, 21 Sep 2004 19:03:23 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C9tSC-0000TM-FY; Tue, 21 Sep 2004 18:49:44 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C9tMh-0007Kn-Ay
	for mip6@megatron.ietf.org; Tue, 21 Sep 2004 18:44:04 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09853
	for <mip6@ietf.org>; Tue, 21 Sep 2004 18:44:00 -0400 (EDT)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C9tT8-0000QX-UI
	for mip6@ietf.org; Tue, 21 Sep 2004 18:50:43 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id i8LMFOu18752;
	Tue, 21 Sep 2004 15:15:24 -0700
X-mProtect: <200409212215> Nokia Silicon Valley Messaging Protection
Received: from manisht.iprg.nokia.com (205.226.2.40,
	claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpdS5oUUf; Tue, 21 Sep 2004 15:15:22 PDT
Message-ID: <4150B0F3.1050905@iprg.nokia.com>
Date: Tue, 21 Sep 2004 15:53:39 -0700
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040430
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Sri Gundavelli <sgundave@cisco.com>
Subject: Re: [Mip6] Re: MR for MIP6-MIB
References: <200409161939.PAA09291@ietf.org>
	<414CBEAC.1070004@cysols.com>	<414FFC4B.6000205@motorola.com>	<20040921193112.01c1453c.ernst@sfc.wide.ad.jp>	<41500398.7030609@motorola.com>	<Pine.GSO.4.58.0409210809450.1818@irp-view7.cisco.com>	<41505D4F.9020
In-Reply-To: <Pine.GSO.4.58.0409211006270.1818@irp-view7.cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org, Thierry Ernst <ernst@sfc.wide.ad.jp>, glenn@cysols.com,
        Alexandru Petrescu <Alexandru.Petrescu@motorola.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Content-Transfer-Encoding: 7bit

Sri Gundavelli wrote:
> Sure. That may be a good idea. Probably marking the binding and
> also adding an object for Home Agents that support the Mobile
> Router ("R" bit). But, the NEMO Base Protocol has to be finalized
> before we add this to the MIPv6 MIB. May be this is a good time
> as the draft is in final stages.

it has been finalized. it is in the RFC Editor queue and I dont
expect any major changes before being published as an RFC.

Vijay

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6


From mip6-bounces@ietf.org  Tue Sep 21 19:27:29 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA12324
	for <mip6-web-archive@ietf.org>; Tue, 21 Sep 2004 19:27:28 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C9u9E-00015U-Oc
	for mip6-web-archive@ietf.org; Tue, 21 Sep 2004 19:34:12 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C9tzx-0007kf-Cp; Tue, 21 Sep 2004 19:24:37 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C9twK-0006nR-OF
	for mip6@megatron.ietf.org; Tue, 21 Sep 2004 19:20:52 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA12018
	for <mip6@ietf.org>; Tue, 21 Sep 2004 19:20:49 -0400 (EDT)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C9u2m-00010R-92
	for mip6@ietf.org; Tue, 21 Sep 2004 19:27:33 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id i8LMrLW07948;
	Tue, 21 Sep 2004 15:53:21 -0700
X-mProtect: <200409212253> Nokia Silicon Valley Messaging Protection
Received: from charliep.iprg.nokia.com (205.226.2.89,
	claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpd6MGPoB; Tue, 21 Sep 2004 15:53:19 PDT
Message-ID: <4150B761.72C83A64@iprg.nokia.com>
Date: Tue, 21 Sep 2004 16:21:05 -0700
From: "Charles E.Perkins" <charliep@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
Subject: Re: [Mip6] 
	Justificationsforstandardizingdraft-ietf-mip6-auth-protocol-00.txt
References: <200409212231.i8LMVWSj054621@givry.rennes.enst-bretagne.fr>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b
Content-Transfer-Encoding: 7bit


Hello Francis,

Francis Dupont wrote:

>    Manual keying is obviously usable.  People
>    use it today.  It's easy.
> 
> => I disagree: it is not easy and it is even difficult between
> different implementations. Even pre-shared secret can be hairy!

Do you mean manual keying for ...?IPsec?...
...Mobile IPv6?...   or what?

> => it works but it is not easy to setup in the real world and
> it is essentially insecure (exactly for the same reason it doesn't
> provide anti-replay protection).

Your statement was _VERY_ general.  So, for instance,
in systems where replay protection is already provided
by some other means, this isn't a problem.  Say, for
instance, Mobile IPv6 in many scenarios.

Plus, ease of setup is largely a function of
the user interface, so I claim it's not at all
relevant to the validity of your original
too-broad statement.

>    or any one of a large number of reasonable
>    statements.  But to say it is not really
>    usable is just plain wrong.
> 
> => I believe you don't understand what I've meant.

That's always a possibility, but up until now I
thought I did -- except that you didn't state
the restrictions which eventually would cause
your statement to become true.

>    And, I would like to also mention, it is
>    pretty simple and appropriate for the scenarios
>    where it does work.
> 
> => IMHO the only scenario is in the labs...

Are we talking in general, or about Mobile IPv6
products...?

If in general, then I suggest that most password
based systems are "manual keyed" systems.  In fact,
they often have manual key refresh, which of course
nobody loves.

If only about Mobile IPv6 products, then I cannot
show you the commercial product that uses manual
keying so I have to yield the discussion.


>    Sometimes it seems to me
>    that such value does not receive due respect
>    in security arguments.  Just because a solution
>    doesn't cover all of the cases doesn't mean it
>    is a kludge or is unusable.
> 
> => I can't believe you suggest to use manual keying in a commercial
> service... Obviously I don't understand what you mean.

I think one could make a lot of money in a
commercial service by selling such systems,
and that they could be targeted towards uses
in which they would be plenty secure enough,
and the customers would be delighted.  If you
include password-based systems that are not
necessarily meant to be used with Mobile IPv6,
then naturally people already make a lot of
money on those.  I am pretty sure I could
desgn a manual-keyed system even for Mobile IPv6
that would solve the user-interface problems.

It depends on how _broadly applicable_ the
solution has to be.


> PS: I don't joke about pre-shared keys: I had the bad idea to use quotes
> in a config file. And this kind of things is really (argh, I use again
> this word :-) hard to debug!

First, your example shows the fallibility of poor
user interfaces.  Second, I never claimed that
manual keying is universally simplest.  Third,
your example again doesn't show the downside of
manual keying, it shows that it's nice to be able
to debug what the key is if it's done manually.


Cordialement,
Charlie P.

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6


From mip6-bounces@ietf.org  Wed Sep 22 01:05:09 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA01266
	for <mip6-web-archive@ietf.org>; Wed, 22 Sep 2004 01:05:09 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C9zQ1-0006Gk-Eg
	for mip6-web-archive@ietf.org; Wed, 22 Sep 2004 01:11:54 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C9z9j-00085z-It; Wed, 22 Sep 2004 00:55:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C9z25-0006UN-J9
	for mip6@megatron.ietf.org; Wed, 22 Sep 2004 00:47:10 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA29962
	for <mip6@ietf.org>; Wed, 22 Sep 2004 00:47:06 -0400 (EDT)
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C9z8a-0005rL-Kv
	for mip6@ietf.org; Wed, 22 Sep 2004 00:53:53 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i8M4kSR27504;
	Wed, 22 Sep 2004 07:46:28 +0300
Date: Wed, 22 Sep 2004 07:46:28 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
Subject: Re: [Mip6] Justifications for standardizing
	draft-ietf-mip6-auth-protocol-00.txt
In-Reply-To: <200409212240.i8LMetSj054839@givry.rennes.enst-bretagne.fr>
Message-ID: <Pine.LNX.4.44.0409220745390.26949-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370

On Wed, 22 Sep 2004, Francis Dupont wrote:
> I answer to my own message because IKEv2 draft is in last call (cf
> a very recent announce from the IESG)!

s/in last call/was just approved for publication as RFC/ :)

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings



_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6


From mip6-bounces@ietf.org  Wed Sep 22 01:06:47 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA01435
	for <mip6-web-archive@ietf.org>; Wed, 22 Sep 2004 01:06:47 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C9zRc-0006Jb-Kn
	for mip6-web-archive@ietf.org; Wed, 22 Sep 2004 01:13:32 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C9z9m-00086O-7T; Wed, 22 Sep 2004 00:55:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C9z3w-0006to-Eg
	for mip6@megatron.ietf.org; Wed, 22 Sep 2004 00:49:04 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA00119
	for <mip6@ietf.org>; Wed, 22 Sep 2004 00:49:01 -0400 (EDT)
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C9zAR-0005tT-KV
	for mip6@ietf.org; Wed, 22 Sep 2004 00:55:48 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i8M4mMh27541;
	Wed, 22 Sep 2004 07:48:22 +0300
Date: Wed, 22 Sep 2004 07:48:22 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
Subject: Re: [Mip6] Justifications for standardizing
	draft-ietf-mip6-auth-protocol-00.txt
In-Reply-To: <200409212156.i8LLuLSj054150@givry.rennes.enst-bretagne.fr>
Message-ID: <Pine.LNX.4.44.0409220746330.26949-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: mip6@ietf.org, Pete McCann <mccap@lucent.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464

On Tue, 21 Sep 2004, Francis Dupont wrote:
>  In your previous mail you wrote:
> 
>    I don't quite understand this.  IKEv2 is basically done.  It's past a
>    couple of IESG evaluations and revisions.  Currently, the I-D tracker
>    says it's in "Approved-announcement to be sent :: Point Raised -
>    writeup needed" -state, meaning that there is a minor or two issues
>    which need to be written out before sending it for publication as an
>    RFC.  The IESG has already basically approved it.
>    
> => I can't forget it took a lot of months for RFC 3775 and 3776 from
> drafts to RFCs.

True, though the critical part was the IANA assignments -- which was, 
I believe, an IANA organizational problem which is now fixed.

Further, if there are particular reasons why the publication needs to
be fast-tracked (e.g., 3GPP2 deadlines or whatever, I don't know), I'm
sure the IESG can listen to reason if needed, and send a note to the
RFC-editor/IANA to put certain documents "in front of the queue".  
This has happened before, I think.

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6


From mip6-bounces@ietf.org  Wed Sep 22 01:37:32 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA03247
	for <mip6-web-archive@ietf.org>; Wed, 22 Sep 2004 01:37:32 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C9zvO-0006qg-7h
	for mip6-web-archive@ietf.org; Wed, 22 Sep 2004 01:44:18 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C9zk1-00083U-SA; Wed, 22 Sep 2004 01:32:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C9zih-0007he-4D
	for mip6@megatron.ietf.org; Wed, 22 Sep 2004 01:31:11 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA02929
	for <mip6@ietf.org>; Wed, 22 Sep 2004 01:31:09 -0400 (EDT)
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C9zp2-0006kn-M0
	for mip6@ietf.org; Wed, 22 Sep 2004 01:37:55 -0400
Message-ID: <046901c4a065$746d07a0$5f6015ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Pekka Savola" <pekkas@netcore.fi>,
        "Francis Dupont" <Francis.Dupont@enst-bretagne.fr>
References: <Pine.LNX.4.44.0409220746330.26949-100000@netcore.fi>
Subject: Re: [Mip6] Justifications for
	standardizingdraft-ietf-mip6-auth-protocol-00.txt
Date: Tue, 21 Sep 2004 22:31:39 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org, Pete McCann <mccap@lucent.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Content-Transfer-Encoding: 7bit

> True, though the critical part was the IANA assignments -- which was,
> I believe, an IANA organizational problem which is now fixed.
>
> Further, if there are particular reasons why the publication needs to
> be fast-tracked (e.g., 3GPP2 deadlines or whatever, I don't know), I'm
> sure the IESG can listen to reason if needed, and send a note to the
> RFC-editor/IANA to put certain documents "in front of the queue".
> This has happened before, I think.


Yes, the IESG and RFC Editor have a system for fast-tracking documents. It
was used for some 3GPP documents. However, it does require that the other
SDO make a specific request for the documents to be accelerated.

            jak



_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6


From mip6-bounces@ietf.org  Wed Sep 22 03:48:56 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA10397
	for <mip6-web-archive@ietf.org>; Wed, 22 Sep 2004 03:48:56 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CA1yY-0000RB-If
	for mip6-web-archive@ietf.org; Wed, 22 Sep 2004 03:55:43 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CA1qb-0001PI-2B; Wed, 22 Sep 2004 03:47:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CA1ml-0000aZ-Gg
	for mip6@megatron.ietf.org; Wed, 22 Sep 2004 03:43:31 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA10176
	for <mip6@ietf.org>; Wed, 22 Sep 2004 03:43:29 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CA1tI-0000MB-DU
	for mip6@ietf.org; Wed, 22 Sep 2004 03:50:16 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id i8M7gWV31212; Wed, 22 Sep 2004 09:42:32 +0200
Received: from givry.rennes.enst-bretagne.fr
	(localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.12.3/8.12.3) with ESMTP id
	i8M7gWSj056276; Wed, 22 Sep 2004 09:42:32 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200409220742.i8M7gWSj056276@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "Charles E.Perkins" <charliep@iprg.nokia.com>
Subject: Re: [Mip6]
	Justificationsforstandardizingdraft-ietf-mip6-auth-protocol-00.txt
In-reply-to: Your message of Tue, 21 Sep 2004 16:21:05 PDT.
	<4150B761.72C83A64@iprg.nokia.com> 
Date: Wed, 22 Sep 2004 09:42:32 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87

 In your previous mail you wrote:

   >    Manual keying is obviously usable.  People
   >    use it today.  It's easy.
   > 
   > => I disagree: it is not easy and it is even difficult between
   > different implementations. Even pre-shared secret can be hairy!
   
   Do you mean manual keying for ...?IPsec?...
   ...Mobile IPv6?...   or what?
   
=> manual keying for IPsec, in any context including the Mobile IPv6 one.
The pre-shared secret allusion is about IKE.

   > => it works but it is not easy to setup in the real world and
   > it is essentially insecure (exactly for the same reason it doesn't
   > provide anti-replay protection).
   
   Your statement was _VERY_ general.

=> yes, the reason is intrinsic so the consequence is general.

   So, for instance,
   in systems where replay protection is already provided
   by some other means, this isn't a problem.

=> the replay protection issue is a consequence. My argument is the long
term use of a shared secret is essentially not a good thing, specially
with mechanisms which are not designed for it.

   Say, for instance, Mobile IPv6 in many scenarios.

=> IPsec (AH or ESP) is a good example of a mechanism not designed for
a long term shared secret. Counter mode is an extreme example.
   
   Plus, ease of setup is largely a function of
   the user interface,

=> I agree and I've never found a manual keying user interface that
one can say it is user friendly...

   so I claim it's not at all
   relevant to the validity of your original
   too-broad statement.
   
=> I don't understand why you insist.

   > => IMHO the only scenario is in the labs...
   
   Are we talking in general, or about Mobile IPv6
   products...?
   
=> in general

   If in general, then I suggest that most password
   based systems are "manual keyed" systems.  In fact,
   they often have manual key refresh, which of course
   nobody loves.
   
=> yes but password systems have more issue, specially
about the real secret length. On the other hand they are designed
for long term shared secret, for instance they don't use
the password directly as a key, they derive session keys
with it using mechanisms where the shared secret is protected
(unfortunately here I describe more an ideal system than
a real world one :-).

   > => I can't believe you suggest to use manual keying in a commercial
   > service... Obviously I don't understand what you mean.
   
   I think one could make a lot of money in a
   commercial service by selling such systems,
   and that they could be targeted towards uses
   in which they would be plenty secure enough,

=> the last point (be plenty secure enough) is where our opinions
diverge, specially about what means "enough".

   and the customers would be delighted.  If you
   include password-based systems that are not
   necessarily meant to be used with Mobile IPv6,
   then naturally people already make a lot of
   money on those.  I am pretty sure I could
   design a manual-keyed system even for Mobile IPv6
   that would solve the user-interface problems.
   
   It depends on how _broadly applicable_ the
   solution has to be.
   
=> by "really" I meant anywhere on the Internet.
   
Thanks

Francis.Dupont@enst-bretagne.fr

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6


From mip6-bounces@ietf.org  Wed Sep 22 03:56:52 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA11240
	for <mip6-web-archive@ietf.org>; Wed, 22 Sep 2004 03:56:52 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CA26G-0000yr-0I
	for mip6-web-archive@ietf.org; Wed, 22 Sep 2004 04:03:40 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CA1yL-00031A-0H; Wed, 22 Sep 2004 03:55:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CA1uz-0002CT-MF
	for mip6@megatron.ietf.org; Wed, 22 Sep 2004 03:52:01 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA10656
	for <mip6@ietf.org>; Wed, 22 Sep 2004 03:51:59 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CA21W-0000TP-RZ
	for mip6@ietf.org; Wed, 22 Sep 2004 03:58:47 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id i8M7pCV00550; Wed, 22 Sep 2004 09:51:12 +0200
Received: from givry.rennes.enst-bretagne.fr
	(localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.12.3/8.12.3) with ESMTP id
	i8M7pBSj056538; Wed, 22 Sep 2004 09:51:11 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200409220751.i8M7pBSj056538@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Pekka Savola <pekkas@netcore.fi>
Subject: Re: [Mip6] Justifications for standardizing
	draft-ietf-mip6-auth-protocol-00.txt 
In-reply-to: Your message of Wed, 22 Sep 2004 07:46:28 +0300.
	<Pine.LNX.4.44.0409220745390.26949-100000@netcore.fi> 
Date: Wed, 22 Sep 2004 09:51:11 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126

 In your previous mail you wrote:

   On Wed, 22 Sep 2004, Francis Dupont wrote:
   > I answer to my own message because IKEv2 draft is in last call (cf
   > a very recent announce from the IESG)!
   
   s/in last call/was just approved for publication as RFC/ :)
   
=> oops, it was too late in the night. I apologize...
BTW is there an open source implementation in an advanced state?

Thanks

Francis.Dupont@enst-bretagne.fr

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6


From mip6-bounces@ietf.org  Thu Sep 23 07:56:32 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA04184
	for <mip6-web-archive@ietf.org>; Thu, 23 Sep 2004 07:56:32 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CASJy-0006DB-2e
	for mip6-web-archive@ietf.org; Thu, 23 Sep 2004 08:03:34 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CAS8V-00061Q-82; Thu, 23 Sep 2004 07:51:43 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CAS71-0005hg-V4
	for mip6@megatron.ietf.org; Thu, 23 Sep 2004 07:50:16 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA03627
	for <mip6@ietf.org>; Thu, 23 Sep 2004 07:50:10 -0400 (EDT)
Received: from dns1.tilab.com ([163.162.42.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CASDd-0005wG-Mb
	for mip6@ietf.org; Thu, 23 Sep 2004 07:57:12 -0400
Received: from iowa2k01a.cselt.it ([163.162.242.201])
	by dns1.cselt.it (PMDF V6.0-025 #38895)
	with ESMTP id <0I4H00M7GSRGFI@dns1.cselt.it> for mip6@ietf.org; Thu,
	23 Sep 2004 13:47:40 +0200 (MEST)
Received: from EXC01B.cselt.it ([163.162.4.199]) by iowa2k01a.cselt.it with
	Microsoft SMTPSVC(6.0.3790.0); Thu, 23 Sep 2004 13:51:14 +0200
Date: Thu, 23 Sep 2004 13:49:27 +0200
From: Giaretta Gerardo <Gerardo.Giaretta@TILAB.COM>
To: mip6@ietf.org
Message-id: <DA62A6E0CDD1B34A84557FF1AC850C57228A87@EXC01B.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: quoted-printable
Importance: normal
Priority: normal
Thread-Topic: New I-D: Goals for AAA-HA interface
Thread-Index: AcShY2FgsNBLhs1iTHuknthN4YBscw==
content-class: urn:content-classes:message
X-OriginalArrivalTime: 23 Sep 2004 11:51:14.0781 (UTC)
	FILETIME=[A0FA50D0:01C4A163]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Content-Transfer-Encoding: quoted-printable
Cc: Julien Bournelle <Julien.Bournelle@int-evry.fr>,
        Demaria Elena <Elena.Demaria@TILAB.COM>, rafa@dif.um.es,
        Guardini Ivano <Ivano.Guardini@TILAB.COM>
Subject: [Mip6] New I-D: Goals for AAA-HA interface
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Content-Transfer-Encoding: quoted-printable

Hi all,

we have submitted a new I-D regarding the interaction between MIPv6 and
the AAA infrastructure.=20
The I-D can be found at:
http://www.ietf.org/internet-drafts/draft-giaretta-mip6-aaa-ha-goals-00.
txt.=20
The document describes various scenarios where an interface between the
Home Agent and the AAA infrastructure of the Mobility Service Provider
(MSP) is required. Furthermore, a list of design goals for this
interface is provided.

Comments are welcome.

--Gerardo


Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia =
S.p.A.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please send an e_mail to=20
MailAdmin@tilab.com. Thank you
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6


From mip6-bounces@ietf.org  Thu Sep 23 11:24:41 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22678
	for <mip6-web-archive@ietf.org>; Thu, 23 Sep 2004 11:24:41 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CAVZR-0001z0-AO
	for mip6-web-archive@ietf.org; Thu, 23 Sep 2004 11:31:46 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CAVPx-0007DV-KL; Thu, 23 Sep 2004 11:21:57 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CAVCG-0004lN-Eu
	for mip6@megatron.ietf.org; Thu, 23 Sep 2004 11:07:49 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21052
	for <mip6@ietf.org>; Thu, 23 Sep 2004 11:07:45 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CAVJ4-0001YI-Ai
	for mip6@ietf.org; Thu, 23 Sep 2004 11:14:50 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id i8NF72J15470; Thu, 23 Sep 2004 17:07:02 +0200
Received: from givry.rennes.enst-bretagne.fr
	(localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.12.3/8.12.3) with ESMTP id
	i8NF71Sj062970; Thu, 23 Sep 2004 17:07:02 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200409231507.i8NF71Sj062970@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "Charles E.Perkins" <charliep@iprg.nokia.com>
Subject: Re: [Mip6]
	Justificationsforstandardizingdraft-ietf-mip6-auth-protocol-00.txt
In-reply-to: Your message of Tue, 21 Sep 2004 16:21:05 PDT.
	<4150B761.72C83A64@iprg.nokia.com> 
Date: Thu, 23 Sep 2004 17:07:01 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370

I've heard that my comments about IPsec manual keying were interpreted
as against pre-shared secret for routing optimization. This mechanism
was carefully designed to avoid the usual weaknesses of long term shared
secret, in fact, IMHO it is very clear that it is far better than a
manual keyed IPsec security association pair for the same use (protection
of MIPv6 signaling in the routing optimization case, i.e., between the
mobile node and a correspondent node).

Francis.Dupont@enst-bretagne.fr

Ref: draft-ietf-mip6-precfgKbm-00.txt
PS: and of course it is far better than the return routability procedure!

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6


From mip6-bounces@ietf.org  Thu Sep 23 13:08:48 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01783
	for <mip6-web-archive@ietf.org>; Thu, 23 Sep 2004 13:08:48 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CAXCE-0004jn-RI
	for mip6-web-archive@ietf.org; Thu, 23 Sep 2004 13:15:55 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CAWuE-0003Ml-NY; Thu, 23 Sep 2004 12:57:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CAWfb-0000Rr-3p
	for mip6@megatron.ietf.org; Thu, 23 Sep 2004 12:42:11 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29794
	for <mip6@ietf.org>; Thu, 23 Sep 2004 12:42:07 -0400 (EDT)
Received: from auds951.usa.alcatel.com ([143.209.238.80])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CAWmP-00045J-TS
	for mip6@ietf.org; Thu, 23 Sep 2004 12:49:14 -0400
Received: from alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.10/8.12.10) with ESMTP id
	i8NGfc2Q004068
	for <mip6@ietf.org>; Thu, 23 Sep 2004 11:41:38 -0500 (CDT)
Message-ID: <4152FCC2.7C821ECF@alcatel.com>
Date: Thu, 23 Sep 2004 11:41:38 -0500
From: Tim Ozugur <tim.ozugur@alcatel.com>
X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: mip6@ietf.org
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 20f22c03b5c66958bff5ef54fcda6e48
Content-Transfer-Encoding: 7bit
Subject: [Mip6] Keynote speakers at BroadNets 2004: Vinton Cerf and Dr.
 Lawrence G. Roberts
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 156eddb66af16eef49a76ae923b15b92
Content-Transfer-Encoding: 7bit


(Apologies if you are receiving this message more than once)

-----------------------------------------------------------------------
                     CALL FOR PARTICIPATION

                          BroadNets 2004
        First International Conference on Broadband Networking

       Technically Co-Sponsored by IEEE Communications Society
                 In-Cooperation with ACM SIGMOBILE

                           Co-sponsored by:

                           CreateNet, Inc.
                                 ICST

         National Science Foundation (Student Travel Awards)
      Philips, Inc. (Bronze Level Sponsor; Student Best Paper Awards)

                     Hilton San Jose and Towers
                     San Jose, California, USA
                       October 25 - 29, 2004
                   
                      http://www.broadnets.org

            Early Registration Deadline: Sept. 30, 2004
         Discounted Hotel Reservation Deadline: Oct. 4, 2004
-----------------------------------------------------------------------

BroadNets 2004 is a new conference focusing on broadband networking
and covers the entire gamut of next generation networks with 
ultra-high bandwidth available all the way from access networks 
(xDSL, Cable, EPON, Broadband Wireless, multi-Gigabit uplinks), 
to regional and metropolitan networks to wide-area core networks.

Keynote speakers include:

* Vinton Cerf, Senior Vice President of Technology Strategy for MCI

* Dr. Lawrence G. Roberts, CEO of Anagran and Founder and Vice
  Chairman of Caspian Networks

The conference will consist of two symposia, panels, six tutorials and
seven workshops:

* Broadband Optical Symposium includes 32 papers covering topics such
  as optical burst and packet switching, IP over optical networks,
  survivability, routing and wavelength assignment, traffic and
  wavelength grooming, switching and routing, and optical network
  design and resource allocation.

* Broadband Wireless Symposium includes 38 papers covering topics such
  as 802.11 networks, UWB and 802.15 based networks, performance
  analysis, wireless multimedia, resource management, multimedia
  transport, contention and media access, routing in ad hoc networks,
  and sensor networks.

* TUTORIALS (on Oct 25 and Oct 29):

  - Broadband Metro and Access Networks (Full-day), Dr. Raj Jain
  - Optical Mesh Survivability (Half-day), Dr. Suresh Subramaniam
    and Dr. Srinivasan Ramasubramanian
  - Advancements in Metro Optical Network Architecture and Technologies
    (Half-day) Dr. Loukas Paraschis
  - Wireless Broadband: Services, Networks, and Management (Full-day),
    Dr. Mani Subramanian
  - Multimedia Transmission over Spectrum Agile Radio Wireless Networks
    (Half-day) Dr. Mihaela van der Schaar
  - A Practical Perspective on the Role of Optical Layer Protection
    (Half-day) Dr. Ori Gerstel

WORKSHOPS co-located with BroadNets 2004:

  - Broadband Wireless Multimedia  (BroadWim)
  - Broadband Advanced Sensor Networks  (BaseNets)
  - Broadband Wireless Services and Applications (BroadWise)
  - Networks for Grid Applications (GridNets)
  - Optical Burst Switching  (OBS)
  - Provisioning and Transport for Hybrid Networks (PathNets)
  - Traffic Grooming 

  Workshops will be held on Monday, October 25 and Friday, October 29.

For the advance program of BroadNets 2004, as well as registration and
travel information, please visit: http://www.broadnets.org.

CONFERENCE ORGANIZING COMMITTEE
-------------------------------

BroadNets Conference General Chair: 
  
 Dr. Raj Jain, Nayna Networks/Ohio State University, raj@nayna.com

_________________________________
Broadband Optical Networking Symposium Co-Chairs:

 Dr. Ori Gerstel, Cisco Systems, ogerstel@cisco.com
 Dr. Jason Jue, University of Texas at Dallas, jjue@utdallas.edu

Technical Program Co-Chairs:

 Dr. Galen Sasaki, University of Hawaii, sasaki@spectra.eng.hawaii.edu
 Dr. Suresh Subramaniam, George Washington University, suresh@gwu.edu

__________________________________

Broadband Wireless Networking Symposium Chair: 

  Dr. Zhensheng Zhang, San Diego Research Center, zzhang@ieee.org 
   

Technical Program Co-Chairs: 

  Dr. Parameswaran Ramanathan, University of Wisconsin-Madison,
  parmesh@ece.wisc.edu 
  Dr. Thomas Hou,   Virginia Tech, thou@vt.edu 

_____________________________


Panels Co-Chairs:

 Dr. Byrav Ramamurthy, University of Nebraska - Lincoln,
byrav@cse.unl.edu
 Dr. Loukas Paraschis, Cisco Systems, loukas@cisco.com
 Dr. Mohammed Atiquzzaman, University of Oklahoma, atiq@ou.edu

Tutorials Co-Chairs:

 Dr. Hakki Candan Cankaya, Alcatel USA, hakki.cankaya@alcatel.com
 Dr. Surendar Chandra, Univ of Notre Dame, surendar@cse.nd.edu

Workshops Chair:

 Dr. Nasir Ghani, Tennessee Tech University, nghani@ieee.org
 Dr. Rajeev Shorey, National University of Singapore and IBM Research
India,
                rajeev@comp.nus.edu.sg

Exhibits and Sponsorships Chairs:

 Dr. Samrat Ganguly, NEC Labs, samrat@nec-labs.com
 Dr. Javier Aracil, Universidad Publica de Navarra, Spain, 
                javier.aracil@unavarra.es 
  
Publicity Co-Chairs: 

 Dr. Tim Ozugur, Alcatel USA,  tim.ozugur@alcatel.com
 Dr. Gaoxi Xiao, Nanyang Technological Univ. Singapore,
		egxxiao@ntu.edu.sg
 Dr. Marcos Rogerio Salvador, CPqD Telecom & IT Solutions,
		marcosrs@cpqd.com.br

Local Arrangements Chair:

 Dr. Subhankar Dhar, San Jose State University, dhar_s@cob.sjsu.edu
 Sukesh Pai, Microsoft Corp. sukeshp@microsoft.com

Steering Committee  Co-Chairs:

 Dr. Imrich Chlamtac, UT Dallas, chlamtac@utdallas.edu
 Dr. Krishna Sivalingam, University of Maryland, Baltimore County,
                krishna@umbc.edu 
--------------------------------------------------------------------------

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6


From mip6-bounces@ietf.org  Thu Sep 23 18:21:16 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29454
	for <mip6-web-archive@ietf.org>; Thu, 23 Sep 2004 18:21:16 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CAc4V-0003dd-Rd
	for mip6-web-archive@ietf.org; Thu, 23 Sep 2004 18:28:26 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CAbiQ-0008Dm-2q; Thu, 23 Sep 2004 18:05:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CAbYy-0003eu-Jh
	for mip6@megatron.ietf.org; Thu, 23 Sep 2004 17:55:40 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26923
	for <mip6@ietf.org>; Thu, 23 Sep 2004 17:55:37 -0400 (EDT)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CAbfq-0003Cb-CU
	for mip6@ietf.org; Thu, 23 Sep 2004 18:02:46 -0400
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-2.cisco.com with ESMTP; 23 Sep 2004 14:57:39 -0700
Received: from mira-sjc5-d.cisco.com (IDENT:mirapoint@mira-sjc5-d.cisco.com
	[171.71.163.28])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i8NLt3wr008737
	for <mip6@ietf.org>; Thu, 23 Sep 2004 14:55:05 -0700 (PDT)
Received: from gdommety-w2k04.cisco.com (dhcp-128-107-178-184.cisco.com
	[128.107.178.184]) by mira-sjc5-d.cisco.com (MOS 3.4.6-GR)
	with ESMTP id AEP89893; Thu, 23 Sep 2004 14:55:05 -0700 (PDT)
Message-Id: <4.3.2.7.2.20040923143829.029e1a48@mira-sjc5-d.cisco.com>
X-Sender: gdommety@mira-sjc5-d.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 23 Sep 2004 14:55:05 -0700
To: mip6@ietf.org
From: Gopal Dommety <gdommety@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Subject: [Mip6] Summary of Justification for Alternative Authentication
	Option
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793

Hello All,

             I am attaching a summary of the discussion that took place on
justification of an alternate authentication mechanism.  Please let me know if
I have left out any important issue in the summary. I could have also mis-read
people opinions, so if there is a correction please let me know. I will 
send a follow-up
  email with the next steps.


Thanks,
-Gopal


Summary
=======

The WG has been engaged in a discussion over the last week on the
topic of standardizing an authentication date suboption based
mechanism for the purpose of registering an MN with its HA via the
BU/BAck messages.
To summarize the discussion in brief:
1. The I-D draft-patil-mip6-whyauthdataoption-00.txt was used as the
    baseline for the discussion
2. Opinion was expressed that the I-D was more inclined in justifying
    why the use of  IKE was a problem for setting up the MN-HA IPsec SA
    and not really providing sufficient justifications for an
    alternative scheme to the use of IPsec for securing the signaling
    messages between the MN and HA
3. There were a few people who expressed strong views of keeping IPsec
    as the only means for MIP6 security between MN and HA (Francis and 
Hesham (?))
4. There were others who claimed the need for an alternate option to
    MIP6 including one operator who plans to deploy the protocol in
    their network (Raj, James Kempf, Alpesh, Gopal, Kuntal, Vijay, Michael Roe)
5. There was also a note from an implementers perspective on the
    challenges of integrating MIP6 with IPsec (Michael Roe)
6. There was discussion about the problem of replay attacks and the
    need for key refreshment
7. IKEv2 is expected to provide a solution to the problem of setting
    up dynamic SAs in networks that rely on AAA infrastructures. While
    IKEv2 itself has been approved, the details of how IKEv2 is used
    with MIP6 are still being worked out in an I-D that is not ready
    yet.
8. There was an opinion that the bootstrap work being done in the WG
    would address the needs of the environment claimed in I-D
    draft-patil-mip6-whyauthdataoption-00.txt


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6


From mip6-bounces@ietf.org  Thu Sep 23 19:38:56 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05391
	for <mip6-web-archive@ietf.org>; Thu, 23 Sep 2004 19:38:56 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CAdHq-0005Ay-Ps
	for mip6-web-archive@ietf.org; Thu, 23 Sep 2004 19:46:07 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CAd9D-0002fW-EB; Thu, 23 Sep 2004 19:37:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CAd5l-00028p-1i
	for mip6@megatron.ietf.org; Thu, 23 Sep 2004 19:33:38 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05073
	for <mip6@ietf.org>; Thu, 23 Sep 2004 19:33:33 -0400 (EDT)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CAdCc-00054O-BD
	for mip6@ietf.org; Thu, 23 Sep 2004 19:40:43 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id i8NN61j01628;
	Thu, 23 Sep 2004 16:06:01 -0700
X-mProtect: <200409232306> Nokia Silicon Valley Messaging Protection
Received: from manisht.iprg.nokia.com (205.226.2.40,
	claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpdT3YHCf; Thu, 23 Sep 2004 16:05:59 PDT
Message-ID: <41535FE0.8040600@iprg.nokia.com>
Date: Thu, 23 Sep 2004 16:44:32 -0700
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040430
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Gopal Dommety <gdommety@cisco.com>
Subject: Re: [Mip6] Summary of Justification for Alternative Authentication
	Option
References: <4.3.2.7.2.20040923143829.029e1a48@mira-sjc5-d.cisco.com>
In-Reply-To: <4.3.2.7.2.20040923143829.029e1a48@mira-sjc5-d.cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Content-Transfer-Encoding: 7bit

hi Gopla,

there were a few coments on just using the AAA infrastructure
for creating security associations for IPsec. no IKE.

and there were also some concerns expressed on using both
authentication mechanisms at the same time.

Vijay

Gopal Dommety wrote:
> Hello All,
> 
>             I am attaching a summary of the discussion that took place on
> justification of an alternate authentication mechanism.  Please let me 
> know if
> I have left out any important issue in the summary. I could have also 
> mis-read
> people opinions, so if there is a correction please let me know. I will 
> send a follow-up
>  email with the next steps.
> 
> 
> Thanks,
> -Gopal
> 
> 
> Summary
> =======
> 
> The WG has been engaged in a discussion over the last week on the
> topic of standardizing an authentication date suboption based
> mechanism for the purpose of registering an MN with its HA via the
> BU/BAck messages.
> To summarize the discussion in brief:
> 1. The I-D draft-patil-mip6-whyauthdataoption-00.txt was used as the
>    baseline for the discussion
> 2. Opinion was expressed that the I-D was more inclined in justifying
>    why the use of  IKE was a problem for setting up the MN-HA IPsec SA
>    and not really providing sufficient justifications for an
>    alternative scheme to the use of IPsec for securing the signaling
>    messages between the MN and HA
> 3. There were a few people who expressed strong views of keeping IPsec
>    as the only means for MIP6 security between MN and HA (Francis and 
> Hesham (?))
> 4. There were others who claimed the need for an alternate option to
>    MIP6 including one operator who plans to deploy the protocol in
>    their network (Raj, James Kempf, Alpesh, Gopal, Kuntal, Vijay, 
> Michael Roe)
> 5. There was also a note from an implementers perspective on the
>    challenges of integrating MIP6 with IPsec (Michael Roe)
> 6. There was discussion about the problem of replay attacks and the
>    need for key refreshment
> 7. IKEv2 is expected to provide a solution to the problem of setting
>    up dynamic SAs in networks that rely on AAA infrastructures. While
>    IKEv2 itself has been approved, the details of how IKEv2 is used
>    with MIP6 are still being worked out in an I-D that is not ready
>    yet.
> 8. There was an opinion that the bootstrap work being done in the WG
>    would address the needs of the environment claimed in I-D
>    draft-patil-mip6-whyauthdataoption-00.txt
> 
> 
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6


From mip6-bounces@ietf.org  Fri Sep 24 01:51:16 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA26634
	for <mip6-web-archive@ietf.org>; Fri, 24 Sep 2004 01:51:16 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CAj6A-0002RA-OD
	for mip6-web-archive@ietf.org; Fri, 24 Sep 2004 01:58:26 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CAixT-0000bO-3L; Fri, 24 Sep 2004 01:49:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CAiwz-0000UE-RG
	for mip6@megatron.ietf.org; Fri, 24 Sep 2004 01:48:57 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA26513
	for <mip6@ietf.org>; Fri, 24 Sep 2004 01:48:57 -0400 (EDT)
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CAj3l-0002OX-Eu
	for mip6@ietf.org; Fri, 24 Sep 2004 01:56:08 -0400
Message-ID: <06a601c4a1fa$45827510$5f6015ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: <mip6@ietf.org>, "Gopal Dommety" <gdommety@cisco.com>
References: <4.3.2.7.2.20040923143829.029e1a48@mira-sjc5-d.cisco.com>
Subject: Re: [Mip6] Summary of Justification for Alternative
	AuthenticationOption
Date: Thu, 23 Sep 2004 22:49:27 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Content-Transfer-Encoding: 7bit
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Content-Transfer-Encoding: 7bit

Gopal,

I believe you missed the need for some mechanism to allow an MN to determine
which authentication technique to use. Without this, there is an
interoperability problem, because the MN cannot infer simply from the
failure of the signaling that it should try the other method.

            jak

----- Original Message ----- 
From: "Gopal Dommety" <gdommety@cisco.com>
To: <mip6@ietf.org>
Sent: Thursday, September 23, 2004 2:55 PM
Subject: [Mip6] Summary of Justification for Alternative
AuthenticationOption


> Hello All,
>
>              I am attaching a summary of the discussion that took place on
> justification of an alternate authentication mechanism.  Please let me
know if
> I have left out any important issue in the summary. I could have also
mis-read
> people opinions, so if there is a correction please let me know. I will
> send a follow-up
>   email with the next steps.
>
>
> Thanks,
> -Gopal
>
>
> Summary
> =======
>
> The WG has been engaged in a discussion over the last week on the
> topic of standardizing an authentication date suboption based
> mechanism for the purpose of registering an MN with its HA via the
> BU/BAck messages.
> To summarize the discussion in brief:
> 1. The I-D draft-patil-mip6-whyauthdataoption-00.txt was used as the
>     baseline for the discussion
> 2. Opinion was expressed that the I-D was more inclined in justifying
>     why the use of  IKE was a problem for setting up the MN-HA IPsec SA
>     and not really providing sufficient justifications for an
>     alternative scheme to the use of IPsec for securing the signaling
>     messages between the MN and HA
> 3. There were a few people who expressed strong views of keeping IPsec
>     as the only means for MIP6 security between MN and HA (Francis and
> Hesham (?))
> 4. There were others who claimed the need for an alternate option to
>     MIP6 including one operator who plans to deploy the protocol in
>     their network (Raj, James Kempf, Alpesh, Gopal, Kuntal, Vijay, Michael
Roe)
> 5. There was also a note from an implementers perspective on the
>     challenges of integrating MIP6 with IPsec (Michael Roe)
> 6. There was discussion about the problem of replay attacks and the
>     need for key refreshment
> 7. IKEv2 is expected to provide a solution to the problem of setting
>     up dynamic SAs in networks that rely on AAA infrastructures. While
>     IKEv2 itself has been approved, the details of how IKEv2 is used
>     with MIP6 are still being worked out in an I-D that is not ready
>     yet.
> 8. There was an opinion that the bootstrap work being done in the WG
>     would address the needs of the environment claimed in I-D
>     draft-patil-mip6-whyauthdataoption-00.txt
>
>
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>



_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6


From mip6-bounces@ietf.org  Fri Sep 24 12:07:19 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20669
	for <mip6-web-archive@ietf.org>; Fri, 24 Sep 2004 12:07:19 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CAsiS-0004Uq-GE
	for mip6-web-archive@ietf.org; Fri, 24 Sep 2004 12:14:37 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CAsRv-0001yK-A0; Fri, 24 Sep 2004 11:57:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CAsO7-0001FI-LK
	for mip6@megatron.ietf.org; Fri, 24 Sep 2004 11:53:35 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19873
	for <mip6@ietf.org>; Fri, 24 Sep 2004 11:53:33 -0400 (EDT)
From: Basavaraj.Patil@nokia.com
Received: from mgw-x2.nokia.com ([131.228.20.22])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CAsV7-0004FB-RW
	for mip6@ietf.org; Fri, 24 Sep 2004 12:00:51 -0400
Received: from esdks003.ntc.nokia.com (esdks003.ntc.nokia.com [172.21.138.158])
	by mgw-x2.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	i8OFrRL21371; Fri, 24 Sep 2004 18:53:27 +0300 (EET DST)
X-Scanned: Fri, 24 Sep 2004 18:51:55 +0300 Nokia Message Protector V1.3.31
	2004060815 - RELEASE
Received: (from root@localhost)
	by esdks003.ntc.nokia.com (8.12.9/8.12.9) id i8OFptSL029942;
	Fri, 24 Sep 2004 18:51:55 +0300
Received: from mgw-int2.ntc.nokia.com (172.21.143.97)
	by esdks003.ntc.nokia.com 00yYanP7; Fri, 24 Sep 2004 18:51:53 EEST
Received: from daebh002.NOE.Nokia.com (daebh002.americas.nokia.com
	[10.241.35.122])
	by mgw-int2.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	i8OFplS25453; Fri, 24 Sep 2004 18:51:47 +0300 (EET DST)
Received: from daebe007.NOE.Nokia.com ([10.241.35.107]) by
	daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Fri, 24 Sep 2004 10:51:40 -0500
x-mimeole: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] Summary of Justification for
	AlternativeAuthenticationOption
Date: Fri, 24 Sep 2004 10:51:38 -0500
Message-ID: <697DAA22C5004B4596E033803A7CEF4403B1BE7C@daebe007.americas.nokia.com>
Thread-Topic: [Mip6] Summary of Justification for
	AlternativeAuthenticationOption
Thread-Index: AcSh+tHCAvrx9XBMTKCkwIH+9oKyhwAU2neQ
To: <kempf@docomolabs-usa.com>, <mip6@ietf.org>, <gdommety@cisco.com>
X-OriginalArrivalTime: 24 Sep 2004 15:51:40.0020 (UTC)
	FILETIME=[6180DB40:01C4A24E]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: a87a9cdae4ac5d3fbeee75cd0026d632
Content-Transfer-Encoding: quoted-printable
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6
Content-Transfer-Encoding: quoted-printable


James,

I disagree with the need for having such a mechanism in view of the fact
that an HA is expected to support both the authentication schemes =
mandatorily.

-BPa

>=20
> Gopal,
>=20
> I believe you missed the need for some mechanism to allow an=20
> MN to determine
> which authentication technique to use. Without this, there is an
> interoperability problem, because the MN cannot infer simply from the
> failure of the signaling that it should try the other method.
>=20
>             jak
>=20
> ----- Original Message -----=20
> From: "Gopal Dommety" <gdommety@cisco.com>
> To: <mip6@ietf.org>
> Sent: Thursday, September 23, 2004 2:55 PM
> Subject: [Mip6] Summary of Justification for Alternative
> AuthenticationOption
>=20
>=20
> > Hello All,
> >
> >              I am attaching a summary of the discussion=20
> that took place on
> > justification of an alternate authentication mechanism. =20
> Please let me
> know if
> > I have left out any important issue in the summary. I could=20
> have also
> mis-read
> > people opinions, so if there is a correction please let me=20
> know. I will
> > send a follow-up
> >   email with the next steps.
> >
> >
> > Thanks,
> > -Gopal
> >
> >
> > Summary
> > =3D=3D=3D=3D=3D=3D=3D
> >
> > The WG has been engaged in a discussion over the last week on the
> > topic of standardizing an authentication date suboption based
> > mechanism for the purpose of registering an MN with its HA via the
> > BU/BAck messages.
> > To summarize the discussion in brief:
> > 1. The I-D draft-patil-mip6-whyauthdataoption-00.txt was used as the
> >     baseline for the discussion
> > 2. Opinion was expressed that the I-D was more inclined in=20
> justifying
> >     why the use of  IKE was a problem for setting up the=20
> MN-HA IPsec SA
> >     and not really providing sufficient justifications for an
> >     alternative scheme to the use of IPsec for securing the=20
> signaling
> >     messages between the MN and HA
> > 3. There were a few people who expressed strong views of=20
> keeping IPsec
> >     as the only means for MIP6 security between MN and HA=20
> (Francis and
> > Hesham (?))
> > 4. There were others who claimed the need for an alternate option to
> >     MIP6 including one operator who plans to deploy the protocol in
> >     their network (Raj, James Kempf, Alpesh, Gopal, Kuntal,=20
> Vijay, Michael
> Roe)
> > 5. There was also a note from an implementers perspective on the
> >     challenges of integrating MIP6 with IPsec (Michael Roe)
> > 6. There was discussion about the problem of replay attacks and the
> >     need for key refreshment
> > 7. IKEv2 is expected to provide a solution to the problem of setting
> >     up dynamic SAs in networks that rely on AAA=20
> infrastructures. While
> >     IKEv2 itself has been approved, the details of how IKEv2 is used
> >     with MIP6 are still being worked out in an I-D that is not ready
> >     yet.
> > 8. There was an opinion that the bootstrap work being done in the WG
> >     would address the needs of the environment claimed in I-D
> >     draft-patil-mip6-whyauthdataoption-00.txt
> >
> >
> > _______________________________________________
> > Mip6 mailing list
> > Mip6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mip6
> >
>=20
>=20
>=20
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>=20

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6


From mip6-bounces@ietf.org  Fri Sep 24 13:52:50 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01741
	for <mip6-web-archive@ietf.org>; Fri, 24 Sep 2004 13:52:50 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CAuMZ-0007qp-3a
	for mip6-web-archive@ietf.org; Fri, 24 Sep 2004 14:00:08 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CAuAN-0004Xl-L7; Fri, 24 Sep 2004 13:47:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CAu2I-0001HR-VT
	for mip6@megatron.ietf.org; Fri, 24 Sep 2004 13:39:12 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00474
	for <mip6@ietf.org>; Fri, 24 Sep 2004 13:39:08 -0400 (EDT)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CAu9K-0007Wa-0S
	for mip6@ietf.org; Fri, 24 Sep 2004 13:46:27 -0400
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-3.cisco.com with ESMTP; 24 Sep 2004 10:51:10 +0000
X-BrightmailFiltered: true
Received: from mira-sjc5-d.cisco.com (IDENT:mirapoint@mira-sjc5-d.cisco.com
	[171.71.163.28])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i8OHcXwp003596;
	Fri, 24 Sep 2004 10:38:34 -0700 (PDT)
Received: from gdommety-w2k04.cisco.com (sjc-vpn1-30.cisco.com [10.21.96.30])
	by mira-sjc5-d.cisco.com (MOS 3.4.6-GR) with ESMTP id AEQ34041;
	Fri, 24 Sep 2004 10:38:27 -0700 (PDT)
Message-Id: <4.3.2.7.2.20040924103809.02d51c40@mira-sjc5-d.cisco.com>
X-Sender: gdommety@mira-sjc5-d.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 24 Sep 2004 10:38:24 -0700
To: "James Kempf" <kempf@docomolabs-usa.com>
From: Gopal Dommety <gdommety@cisco.com>
Subject: Re: [Mip6] Summary of Justification for Alternative
	AuthenticationOption
In-Reply-To: <06a601c4a1fa$45827510$5f6015ac@dcml.docomolabsusa.com>
References: <4.3.2.7.2.20040923143829.029e1a48@mira-sjc5-d.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8

James,


Would HA having to support both techniques be acceptable mechanism?

Thanks,
-Gopal

At 10:49 PM 9/23/2004 -0700, James Kempf wrote:
>Gopal,
>
>I believe you missed the need for some mechanism to allow an MN to determine
>which authentication technique to use. Without this, there is an
>interoperability problem, because the MN cannot infer simply from the
>failure of the signaling that it should try the other method.
>
>             jak
>
>----- Original Message -----
>From: "Gopal Dommety" <gdommety@cisco.com>
>To: <mip6@ietf.org>
>Sent: Thursday, September 23, 2004 2:55 PM
>Subject: [Mip6] Summary of Justification for Alternative
>AuthenticationOption
>
>
> > Hello All,
> >
> >              I am attaching a summary of the discussion that took place on
> > justification of an alternate authentication mechanism.  Please let me
>know if
> > I have left out any important issue in the summary. I could have also
>mis-read
> > people opinions, so if there is a correction please let me know. I will
> > send a follow-up
> >   email with the next steps.
> >
> >
> > Thanks,
> > -Gopal
> >
> >
> > Summary
> > =======
> >
> > The WG has been engaged in a discussion over the last week on the
> > topic of standardizing an authentication date suboption based
> > mechanism for the purpose of registering an MN with its HA via the
> > BU/BAck messages.
> > To summarize the discussion in brief:
> > 1. The I-D draft-patil-mip6-whyauthdataoption-00.txt was used as the
> >     baseline for the discussion
> > 2. Opinion was expressed that the I-D was more inclined in justifying
> >     why the use of  IKE was a problem for setting up the MN-HA IPsec SA
> >     and not really providing sufficient justifications for an
> >     alternative scheme to the use of IPsec for securing the signaling
> >     messages between the MN and HA
> > 3. There were a few people who expressed strong views of keeping IPsec
> >     as the only means for MIP6 security between MN and HA (Francis and
> > Hesham (?))
> > 4. There were others who claimed the need for an alternate option to
> >     MIP6 including one operator who plans to deploy the protocol in
> >     their network (Raj, James Kempf, Alpesh, Gopal, Kuntal, Vijay, Michael
>Roe)
> > 5. There was also a note from an implementers perspective on the
> >     challenges of integrating MIP6 with IPsec (Michael Roe)
> > 6. There was discussion about the problem of replay attacks and the
> >     need for key refreshment
> > 7. IKEv2 is expected to provide a solution to the problem of setting
> >     up dynamic SAs in networks that rely on AAA infrastructures. While
> >     IKEv2 itself has been approved, the details of how IKEv2 is used
> >     with MIP6 are still being worked out in an I-D that is not ready
> >     yet.
> > 8. There was an opinion that the bootstrap work being done in the WG
> >     would address the needs of the environment claimed in I-D
> >     draft-patil-mip6-whyauthdataoption-00.txt
> >
> >
> > _______________________________________________
> > Mip6 mailing list
> > Mip6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mip6
> >
>
>
>
>_______________________________________________
>Mip6 mailing list
>Mip6@ietf.org
>https://www1.ietf.org/mailman/listinfo/mip6


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6


From mip6-bounces@ietf.org  Fri Sep 24 17:34:05 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22726
	for <mip6-web-archive@ietf.org>; Fri, 24 Sep 2004 17:34:05 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CAxok-0005T1-BB
	for mip6-web-archive@ietf.org; Fri, 24 Sep 2004 17:41:26 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CAxZn-0003CQ-Dy; Fri, 24 Sep 2004 17:25:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CAxRX-0001P9-Nx; Fri, 24 Sep 2004 17:17:28 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21410;
	Fri, 24 Sep 2004 17:17:25 -0400 (EDT)
Received: from node-402449f2.sfo.onnet.us.uu.net ([64.36.73.242]
	helo=deimos.multihop.net) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CAxYZ-00057s-9n; Fri, 24 Sep 2004 17:24:45 -0400
Received: from localhost (unknown [127.0.0.1])
	by deimos.multihop.net (Postfix) with ESMTP id 7EC34621B;
	Fri, 24 Sep 2004 14:14:58 -0700 (PDT)
Received: from deimos.multihop.net ([127.0.0.1])
	by localhost (deimos.multihop.net [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 98335-10; Fri, 24 Sep 2004 14:14:57 -0700 (PDT)
Received: by deimos.multihop.net (Postfix, from userid 1013)
	id 79073621A; Fri, 24 Sep 2004 14:14:57 -0700 (PDT)
Received: from [208.54.51.97] (m613336d0.tmodns.net [208.54.51.97])
	(using TLSv1 with cipher RC4-SHA (128/128 bits))
	(No client certificate requested)
	by deimos.multihop.net (Postfix) with ESMTP id CE26D6241;
	Fri, 24 Sep 2004 14:14:44 -0700 (PDT)
In-Reply-To: <20031024.213244.38493611.keiichi@iij.ad.jp>
References: <200310201752.h9KHqRuT723936@jurassic.eng.sun.com>
	<20031024.213244.38493611.keiichi@iij.ad.jp>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=ISO-2022-JP; format=flowed
Message-Id: <2F4B009E-0E40-11D9-8867-000A95DA08F2@kniveton.com>
Content-Transfer-Encoding: 7bit
From: "T.J.Kniveton" <tj@kniveton.com>
Subject: Re: [Mipshop] Re: [Mip6] Mobile IPv6 Interop Testing Draft
Date: Fri, 24 Sep 2004 08:41:21 -0700
To: =?ISO-2022-JP?B?S2VpaWNoaSBTSElNQSAvIBskQkVnN0QwbBsoQg==?=
	<keiichi@iij.ad.jp>
X-Mailer: Apple Mail (2.619)
X-Virus-Scanned: by amavisd-new at deimos.multihop.net
X-Spam-Score: 0.7 (/)
X-Scan-Signature: 5d7a7e767f20255fce80fa0b77fb2433
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org, mipshop@ietf.org, Samita.Chakrabarti@eng.sun.com
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org
X-Spam-Score: 0.7 (/)
X-Scan-Signature: b22590c27682ace61775ee7b453b40d3
Content-Transfer-Encoding: 7bit

Hi Keiichi,

Sorry it took me 11 months to reply. But thanks for your comment. Right 
now we are revising this draft, and the virtual home link is one topic 
to revisit. Of course, there have been various discussions about 
virtual home links since then.

In terms of configuring the home agent end to allow the right prefix 
and routing info, I would imagine a few couple possibilities that might 
work which I will try to describe.

1. The first scenario you described: a physical link and then multiple 
point-to-point tunnels. The physical link owns the prefix, but the 
local and remote addresses of the tunnel also come from that prefix. If 
necessary, a host route for the MN can be added with the tunnel 
interface as outgoing interface. rtadvd would also have to be signaled 
to send advertisements on each tunnel (haven't tried that personally; 
hopefully it's possible).

2. The physical link does, or does not exist. Either way, bridging is 
enabled between all of the tunnels and either a virtual or real link, 
which owns the prefix. The tunnel has a local and remote address on a 
different prefix (or no address, depending on tunneling used), but then 
the home address is configured from RAs that are echoed to the tunnel 
by the bridge.

3. ? There are probably more ways to do this.


On Oct 24, 2003, at 5:32 AM, Keiichi SHIMA / $BEg7D0l(B wrote:

> Hello Samita and T.J.,
>
> It is very interesting and good idea to establish a remote test
> environment. (and we are interested in participating the test, of
> course :-)
>
> By the way, I have a question (or concern) about the virtual home link
> described in Section 8 in the draft.
>
> Section 8 proposes the method for mobile node implementers to test
> 'returning to home' with other home agent vendor's implementation,
> even when the mobile node cannot access the real home link of the home
> agent.
>
> My question is, how is a home agent (and a home link) configured?
>
> I imagined the following network, for example.
>
>
>       ----+----------  home link P::/64
>   	  |
>           |P::1 (home agent address)
>        IF1|200.0.0.1
>        +--+-+
>        | HA |    IF3(200.0.0.1 - 100.0.0.1)
>        +--+-+
>        IF2|
> 	  |
>      ((Internet))
> 	  |
> 	  |
>        ---+---------+------------ visited link of MN tester Q::/64
> 	      	    |
> 	      	    |Q::100 (care-of address)
> 	      	 IF1|100.0.0.1
> 	      	 +--+-+
>        	       	 | MN |   IF2(100.0.0.1-200.0.0.1)
> 		 +----+
>
> HA has physically two interfaces, IF1 and IF2.  In this case, IF2 has
> nothing to do with this scenario, I ignore it.  HA also has one tunnel
> interface IF3 between 200.0.0.1 and 100.0.0.1.
>
> MN has physically one interface IF1, and one tunnel interface IF2
> between 100.0.0.1 and 200.0.0.1.
>
> The draft says, MN receives a router advertisement for home link from
> HA via the tunnel interface IF2.  However I think it is difficult,
> since HA must have two different interfaces and those interfaces must
> be assigned the same prefix (in this case, P::/64).  This means HA is
> required to support a kind of multi-link subnet technology.  (Or did I
> misread?)
>
> If there is no physical home link, I think it is possible to configure.
> For example,
>
>        +--+-+  IF1(200.0.0.1 - 100.0.0.1)
>        | HA |       P::1/64 (home address)
>        +--+-+
>        IF2|200.0.0.1
> 	  |
>      ((Internet))
> 	  |
> 	  |
>        ---+---------+------------ visited link of MN tester Q::/64
> 	      	    |
> 	      	    |Q::100 (care-of address)
> 	      	 IF1|100.0.0.1
> 	      	 +--+-+
>        	       	 | MN |   IF2(100.0.0.1-200.0.0.1)
> 		 +----+
>
> In this case, I see no problem.  However, this scenario requires as
> many home subnets as the number of mobile nodes, since HA must arrange
> different tunnel interface and home prefix for each mobile node.
>
> I don't think the former scenario is not appropriate.  It is of course
> more efficient than the latter, if HA can do that.  But I just think
> not so many home agent can do it.  I may be wrong...
>
> Best Regards,
> ---
> Keiichi SHIMA
> IIJ Research Laboratory <keiichi@iij.ad.jp>
> KAME Project <keiichi@kame.net>
>
> _______________________________________________
> Mipshop mailing list
> Mipshop@ietf.org
> https://www1.ietf.org/mailman/listinfo/mipshop


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6


From mip6-bounces@ietf.org  Fri Sep 24 17:36:17 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22885
	for <mip6-web-archive@ietf.org>; Fri, 24 Sep 2004 17:36:17 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CAxqs-0005Vq-C9
	for mip6-web-archive@ietf.org; Fri, 24 Sep 2004 17:43:38 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CAxe5-00041i-O4; Fri, 24 Sep 2004 17:30:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CAxWJ-00028q-VR; Fri, 24 Sep 2004 17:22:24 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21727;
	Fri, 24 Sep 2004 17:22:21 -0400 (EDT)
Received: from node-402449f2.sfo.onnet.us.uu.net ([64.36.73.242]
	helo=deimos.multihop.net) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CAxdN-0005D4-VT; Fri, 24 Sep 2004 17:29:42 -0400
Received: from localhost (unknown [127.0.0.1])
	by deimos.multihop.net (Postfix) with ESMTP id 0F43A6241;
	Fri, 24 Sep 2004 14:20:03 -0700 (PDT)
Received: from deimos.multihop.net ([127.0.0.1])
	by localhost (deimos.multihop.net [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 98532-07; Fri, 24 Sep 2004 14:20:02 -0700 (PDT)
Received: by deimos.multihop.net (Postfix, from userid 1013)
	id EE0C9621B; Fri, 24 Sep 2004 14:20:01 -0700 (PDT)
Received: from [208.54.51.97] (m613336d0.tmodns.net [208.54.51.97])
	(using TLSv1 with cipher RC4-SHA (128/128 bits))
	(No client certificate requested)
	by deimos.multihop.net (Postfix) with ESMTP id CFF2A61D2;
	Fri, 24 Sep 2004 14:18:51 -0700 (PDT)
In-Reply-To: <000301c39a64$30afcaa0$0900a8c0@eremmell>
References: <000301c39a64$30afcaa0$0900a8c0@eremmell>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <A75780CA-0E40-11D9-8867-000A95DA08F2@kniveton.com>
Content-Transfer-Encoding: 7bit
From: "T.J.Kniveton" <tj@kniveton.com>
Subject: Re: [Mipshop] RE: [Mip6] Mobile IPv6 Interop Testing Draft
Date: Fri, 24 Sep 2004 08:44:43 -0700
To: "Ed Remmell" <eremmell@elmic.com>
X-Mailer: Apple Mail (2.619)
X-Virus-Scanned: by amavisd-new at deimos.multihop.net
X-Spam-Score: 0.7 (/)
X-Scan-Signature: 3971661e40967acfc35f708dd5f33760
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org, mipshop@ietf.org, keiichi@iij.ad.jp,
        "'Samita Chakrabarti'" <Samita.Chakrabarti@eng.sun.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org
X-Spam-Score: 0.7 (/)
X-Scan-Signature: 2e8fc473f5174be667965460bd5288ba
Content-Transfer-Encoding: 7bit

The idea of that setup is just to get some rudimentary testing of MN 
returning home without it physically going to the home agent. Of 
course, face to face interops are necessary to get truly good test 
coverage. And if you are in favor of deploying virtual home networks, 
well.. then you can just skip that section of the draft. :-)

On Oct 24, 2003, at 12:22 PM, Ed Remmell wrote:

> Gee, it seems like it will be difficult to test the "MN return-to-home"
> and/or "MN move-from-home" scenarios this way, but no biggie, I'd 
> prefer
> if MIPv6 was deployed using virtual home networks implemented internal
> to the HA anyways since that's a big simplification to MIPv6 protocol
> operation. So, we probably won't test MN operation on the home link via
> this remote testing, instead our MN will always be attached to a 
> foreign
> link. Still, you can get some good test coverage this way.
>
> Thanks.
> - Ed
>
>> -----Original Message-----
>> From: mip6-admin@ietf.org [mailto:mip6-admin@ietf.org] On
>> Behalf Of Samita Chakrabarti
>> Sent: Friday, October 24, 2003 12:17 PM
>> To: keiichi@iij.ad.jp
>> Cc: mip6@ietf.org; mipshop@ietf.org
>> Subject: Re: [Mip6] Mobile IPv6 Interop Testing Draft
>>
>>
>>
>>
>>> Section 8 proposes the method for mobile node implementers to test
>>> 'returning to home' with other home agent vendor's implementation,
>>> even when the mobile node cannot access the real home link
>> of the home
>>> agent.
>>>
>>> My question is, how is a home agent (and a home link) configured?
>>
>>
>> We need to discuss more and flush out the configuration of HA
>> and virtual home tunnel without changing the HA
>> implementation. Working group comments would be helpful for this.
>>
>>>
>>> I imagined the following network, for example.
>>>
>>>
>>>       ----+----------  home link P::/64
>>>   	  |
>>>           |P::1 (home agent address)
>>>        IF1|200.0.0.1
>>>        +--+-+
>>>        | HA |    IF3(200.0.0.1 - 100.0.0.1)
>>>        +--+-+
>>>        IF2|
>>> 	  |
>>>      ((Internet))
>>> 	  |
>>> 	  |
>>>        ---+---------+------------ visited link of MN tester Q::/64
>>> 	      	    |
>>> 	      	    |Q::100 (care-of address)
>>> 	      	 IF1|100.0.0.1
>>> 	      	 +--+-+
>>>        	       	 | MN |   IF2(100.0.0.1-200.0.0.1)
>>> 		 +----+
>>>
>>> HA has physically two interfaces, IF1 and IF2.  In this
>> case, IF2 has
>>> nothing to do with this scenario, I ignore it.  HA also has
>> one tunnel
>>> interface IF3 between 200.0.0.1 and 100.0.0.1.
>>>
>>> MN has physically one interface IF1, and one tunnel interface IF2
>>> between 100.0.0.1 and 200.0.0.1.
>>>
>>> The draft says, MN receives a router advertisement for home
>> link from
>>> HA via the tunnel interface IF2.  However I think it is difficult,
>>> since HA must have two different interfaces and those
>> interfaces must
>>> be assigned the same prefix (in this case, P::/64).  This
>> means HA is
>>> required to support a kind of multi-link subnet technology.
>>  (Or did I
>>> misread?)
>>>
>>
>> I think the draft meant virtual tunnel interface. The idea is
>> that the MN would setup the tunnel when it thinks it comes
>> back home and when it is away, it should disable the tunnel
>> and thus not receive any HA adv. It would require some
>> special configuration on HA side. I don't know if that is not
>> possible or complicated - TJ and others in the design team
>> may have comments on that.
>>
>>> If there is no physical home link, I think it is possible to
>>> configure. For example,
>>>
>>>        +--+-+  IF1(200.0.0.1 - 100.0.0.1)
>>>        | HA |       P::1/64 (home address)
>>>        +--+-+
>>>        IF2|200.0.0.1
>>> 	  |
>>>      ((Internet))
>>> 	  |
>>> 	  |
>>>        ---+---------+------------ visited link of MN tester Q::/64
>>> 	      	    |
>>> 	      	    |Q::100 (care-of address)
>>> 	      	 IF1|100.0.0.1
>>> 	      	 +--+-+
>>>        	       	 | MN |   IF2(100.0.0.1-200.0.0.1)
>>> 		 +----+
>>>
>>> In this case, I see no problem.  However, this scenario requires as
>>> many home subnets as the number of mobile nodes, since HA
>> must arrange
>>> different tunnel interface and home prefix for each mobile node.
>>>
>>
>> This scenario looks ok to me for adv. But not sure how HA
>> would receive packets from CN to relay to MN on a different tunnel.
>>
>> Thanks,
>> -Samita
>>
>>
>> _______________________________________________
>> Mip6 mailing list
>> Mip6@ietf.org
>> https://www.ietf.org/mailman/listinfo/mip6
>>
>> ---
>> Incoming mail is certified Virus Free.
>> Checked by AVG anti-virus system (http://www.grisoft.com).
>> Version: 6.0.522 / Virus Database: 320 - Release Date: 9/29/2003
>>
>>
>
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.522 / Virus Database: 320 - Release Date: 9/29/2003
>
>
>
> _______________________________________________
> Mipshop mailing list
> Mipshop@ietf.org
> https://www1.ietf.org/mailman/listinfo/mipshop


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6


From mip6-bounces@ietf.org  Fri Sep 24 17:54:08 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24165
	for <mip6-web-archive@ietf.org>; Fri, 24 Sep 2004 17:54:08 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CAy89-0005xx-Ix
	for mip6-web-archive@ietf.org; Fri, 24 Sep 2004 18:01:29 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CAxj7-0004yv-Ep; Fri, 24 Sep 2004 17:35:37 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CAxZy-0003Cm-2N; Fri, 24 Sep 2004 17:26:11 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22073;
	Fri, 24 Sep 2004 17:26:08 -0400 (EDT)
Received: from node-402449f2.sfo.onnet.us.uu.net ([64.36.73.242]
	helo=deimos.multihop.net) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CAxh2-0005Ic-6j; Fri, 24 Sep 2004 17:33:28 -0400
Received: from localhost (unknown [127.0.0.1])
	by deimos.multihop.net (Postfix) with ESMTP id 653FB6234;
	Fri, 24 Sep 2004 14:24:00 -0700 (PDT)
Received: from deimos.multihop.net ([127.0.0.1])
	by localhost (deimos.multihop.net [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 98532-09; Fri, 24 Sep 2004 14:23:59 -0700 (PDT)
Received: by deimos.multihop.net (Postfix, from userid 1013)
	id 5DFAA621B; Fri, 24 Sep 2004 14:23:59 -0700 (PDT)
Received: from [208.54.51.97] (m613336d0.tmodns.net [208.54.51.97])
	(using TLSv1 with cipher RC4-SHA (128/128 bits))
	(No client certificate requested)
	by deimos.multihop.net (Postfix) with ESMTP id 4D98361D2;
	Fri, 24 Sep 2004 14:23:19 -0700 (PDT)
In-Reply-To: <9C422444DE99BC46B3AD3C6EAFC9711B047CA220@tayexc13.americas.cpqcorp.net>
References: <9C422444DE99BC46B3AD3C6EAFC9711B047CA220@tayexc13.americas.cpqcorp.net>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <11374446-0E44-11D9-8867-000A95DA08F2@kniveton.com>
Content-Transfer-Encoding: 7bit
From: "T.J.Kniveton" <tj@kniveton.com>
Subject: Re: [Mipshop] RE: [Mip6] Mobile IPv6 Interop Testing Draft
Date: Fri, 24 Sep 2004 09:09:09 -0700
To: "Bound, Jim" <jim.bound@hp.com>
X-Mailer: Apple Mail (2.619)
X-Virus-Scanned: by amavisd-new at deimos.multihop.net
X-Spam-Score: 0.7 (/)
X-Scan-Signature: 9af087f15dbdd4c64ae6bbcdbc5b1d44
Content-Transfer-Encoding: 7bit
Cc: "<mip6@ietf.org>" <mip6@ietf.org>, "<mipshop@ietf.org>" <mipshop@ietf.org>,
        "<Maeva.Petitjean@etsi.org>" <Maeva.Petitjean@etsi.org>,
        Samita Chakrabarti <Samita.Chakrabarti@eng.sun.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org
X-Spam-Score: 0.7 (/)
X-Scan-Signature: e8c5db863102a3ada84e0cd52a81a79e
Content-Transfer-Encoding: 7bit

On Nov 6, 2003, at 11:41 AM, Bound, Jim wrote:

> I don't think that is required I hope.  But we have a lot of people
> banging on IPv6 issues that are good operational issues for
> configuration and use that are not relative to the standard for writing
> the code. But, is good input to implementors, and this point is very
> useful.  We will never ship standards on time if we try to solve world
> hunger and dictate to implementation (which will usually be ignored). 
> We
> have enough work to get the standards functions done correctly.  The
> other thing is in my work from now on if I put little hints in specs
> that are not really part of the standard I am going to put clear huge
> text that this is not part of the standard but information for
> implementors and operators.  Or something.
>
> thanks
> /jim
>
>> -----Original Message-----
>> From: mipshop-admin@ietf.org [mailto:mipshop-admin@ietf.org]
>> On Behalf Of Samita Chakrabarti
>> Sent: Thursday, November 06, 2003 1:19 PM
>> To: Bound, Jim
>> Cc: Maeva.Petitjean@etsi.org; mip6@ietf.org; mipshop@ietf.org
>> Subject: RE: [Mipshop] RE: [Mip6] Mobile IPv6 Interop Testing Draft
>>
>>
>>
>>
>>> This is fine optimization for lab or testing but don't expect
>>> production MN's to do this or assume it in any specs std or
>>> operational.

Jim,

Was there some sort of operation in particular that we shouldn't expect 
MNs to do? Are you talking about the dual-stack operations mentioned in 
this message? Or the virtual home tunneling we were talking about in 
the other messages? Or were you saying that this spec in general should 
be clearly stated to be for testing only?

Some people are interested in virtual home links as we know, but we can 
state more clearly that this draft is intended for testing purposes, if 
you think it needs to be emphasized.

TJ


>>>
>>
>> Agreed. The draft only talks about the testing scenario.
>> Perhaps it can be clarified further in the document to avoid
>> any confusion.
>>
>> Thanks,
>> -Samita
>>
>>
>>>> -----Original Message-----
>>>> From: mipshop-admin@ietf.org [mailto:mipshop-admin@ietf.org]
>>>> On Behalf Of Samita Chakrabarti
>>>> Sent: Monday, October 27, 2003 2:27 PM
>>>> To: Maeva.Petitjean@etsi.org
>>>> Cc: mip6@ietf.org; mipshop@ietf.org
>>>> Subject: Re: [Mipshop] RE: [Mip6] Mobile IPv6 Interop
>> Testing Draft
>>>>
>>>>
>>>>
>>>>
>>>>>
>>>>>    5.3.1. Home Agent
>>>>>
>>>>>     -  Company and contact information
>>>>>
>>>>>     -  Home agent IPv6 address and the corresponding IPv4
>>>> addresses (if
>>>>>        dual stack)
>>>>>
>>>>> --> Is there more than one corresponding IPv4 address
>> for one IPv6
>>>>> address ?
>>>>>
>>>>
>>>>
>>>> Actually listing IPv4 addresses are not necessary. But
>>>> sometimes knowing the corresponding IPv4 address helps in
>>>> finding out whether the node is dead or having trouble with
>>>> IPv6 connection. Thus one IPv4 address on the node should be
>>>> fine, I think.
>>>>
>>>>>     -  List of home-addresses it assigns.  This list must
>>>> also indicate
>>>>>        which home-addresses are presently used and which
>>>> are available.
>>>>>        Example:
>>>>>        HOA1 (used by KEIO Univ.- contact name)
>>>>>        HOA2 (available)
>>>>>        HOA3 (available)
>>>>>
>>>>> --> Is there more than one home-address for one home agent ?
>>>>>
>>>>
>>>> Yes. It depends on the administrator of the home-agent. I
>>>> assume, usually they would allow multiple mobile-nodes
>> for testing.
>>>>
>>>>
>>>> -Samita
>>>>
>>>>
>>>>>
>>>>> -----Original Message-----
>>>>> From: Samita Chakrabarti [mailto:Samita.Chakrabarti@eng.sun.com]
>>>>> Sent: 20 October 2003 19:54
>>>>> To: mip6@ietf.org; mipshop@ietf.org
>>>>> Subject: [Mip6] Mobile IPv6 Interop Testing Draft
>>>>>
>>>>>
>>>>>
>>>>> As per Basavaraj Patil's recommendation, a mip6-interop design
>>>>> team
>>>>> has been formed and the team has worked on producing the
>>>> first draft
>>>>> on the Mobile IPv6 remote interop testing requirements,
>>>> scenarios and
>>>>> procedures.
>>>>>
>>>>> The draft has been submitted as an individual draft for
>> now, but
>>>>> it is targeting to be a working group draft in the next
>> revision.
>>>>> It is available through T.J Kniveton's webpage until the draft
>>>>> becomes available at the IETF directory.
>>>>>
>>>>>
>>>> http://www.mipv6.org/specs/draft-kniveton->
>>> mipv6-remote-testing-00.txt
>>>>>
>>>>>
>>>>> Thanks.
>>>>>
>>>>> The mip6-interop design team.
>>>>> T.J Kniveton,
>>>>> Basavaraj Patil,
>>>>> Hesham Soliman,
>>>>> Henrik Petander,
>>>>> Samita Chakrabarti
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Mip6 mailing list
>>>>> Mip6@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/mip6
>>>>>
>>>>> _______________________________________________
>>>>> Mipshop mailing list
>>>>> Mipshop@ietf.org https://www1.ietf.org/mailman/listinfo/mipshop
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Mipshop mailing list
>>>> Mipshop@ietf.org https://www1.ietf.org/mailman/listinfo/mipshop
>>>>
>>>
>>
>>
>> _______________________________________________
>> Mipshop mailing list
>> Mipshop@ietf.org
>> https://www1.ietf.org/mailman/listinfo/mipshop
>>
>
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www.ietf.org/mailman/listinfo/mip6


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6


From mip6-bounces@ietf.org  Sat Sep 25 04:48:12 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA13126
	for <mip6-web-archive@ietf.org>; Sat, 25 Sep 2004 04:48:12 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CB8LD-0007eu-Cx
	for mip6-web-archive@ietf.org; Sat, 25 Sep 2004 04:55:39 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CB8AQ-00086R-Ak; Sat, 25 Sep 2004 04:44:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CB86m-0007Lv-Av
	for mip6@megatron.ietf.org; Sat, 25 Sep 2004 04:40:44 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA12902
	for <mip6@ietf.org>; Sat, 25 Sep 2004 04:40:41 -0400 (EDT)
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CB8Dl-0007Z7-RS
	for mip6@ietf.org; Sat, 25 Sep 2004 04:48:09 -0400
Message-ID: <004401c4a2db$6c3e0d40$576015ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: <Basavaraj.Patil@nokia.com>, <mip6@ietf.org>, <gdommety@cisco.com>
References: <697DAA22C5004B4596E033803A7CEF4403B1BE7C@daebe007.americas.nokia.com>
Subject: Re: [Mip6] Summary of Justification for
	AlternativeAuthenticationOption
Date: Sat, 25 Sep 2004 01:41:09 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 932cba6e0228cc603da43d861a7e09d8
Content-Transfer-Encoding: 7bit
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2ed806e2f53ff1a061ad4f97e00345ac
Content-Transfer-Encoding: 7bit

Raj,

Whether we agree is not the point, the point is that Gopal's email was
ostensibly a summary of the discussion on the list, and I believe it missed
an important point that I brought up, namely that IETF cannot mandate
whether an operator enables their HA to accept both kinds of traffic or not,
and if we standardize two ways of doing the same thing - even if we mandate
that the HA support both - an operator can decide to support only one
causing an interoperability problem.

Additonally, I believe Gopal's summary misrepresented my position. My
position is not one of unqualified support for the authentication option. It
is:

- We should select either IPsec or the authentication option (RFC 1958, if
there's two choices for the same functionality, choose one).

- Since we have already standardized IPsec and the authentication option is
only of interest to cdma2K operators, we should process the authentication
option as an informational draft and *NOT* an Internet standard.

I hope that makes my position clearer. I hope, in the future, that the WG
chairs will strive to be a little more accurate and objective when
performing concensus calls.

            jak

----- Original Message ----- 
From: <Basavaraj.Patil@nokia.com>
To: <kempf@docomolabs-usa.com>; <mip6@ietf.org>; <gdommety@cisco.com>
Sent: Friday, September 24, 2004 8:51 AM
Subject: RE: [Mip6] Summary of Justification for
AlternativeAuthenticationOption



James,

I disagree with the need for having such a mechanism in view of the fact
that an HA is expected to support both the authentication schemes
mandatorily.

-BPa

>
> Gopal,
>
> I believe you missed the need for some mechanism to allow an
> MN to determine
> which authentication technique to use. Without this, there is an
> interoperability problem, because the MN cannot infer simply from the
> failure of the signaling that it should try the other method.
>
>             jak
>
> ----- Original Message ----- 
> From: "Gopal Dommety" <gdommety@cisco.com>
> To: <mip6@ietf.org>
> Sent: Thursday, September 23, 2004 2:55 PM
> Subject: [Mip6] Summary of Justification for Alternative
> AuthenticationOption
>
>
> > Hello All,
> >
> >              I am attaching a summary of the discussion
> that took place on
> > justification of an alternate authentication mechanism.
> Please let me
> know if
> > I have left out any important issue in the summary. I could
> have also
> mis-read
> > people opinions, so if there is a correction please let me
> know. I will
> > send a follow-up
> >   email with the next steps.
> >
> >
> > Thanks,
> > -Gopal
> >
> >
> > Summary
> > =======
> >
> > The WG has been engaged in a discussion over the last week on the
> > topic of standardizing an authentication date suboption based
> > mechanism for the purpose of registering an MN with its HA via the
> > BU/BAck messages.
> > To summarize the discussion in brief:
> > 1. The I-D draft-patil-mip6-whyauthdataoption-00.txt was used as the
> >     baseline for the discussion
> > 2. Opinion was expressed that the I-D was more inclined in
> justifying
> >     why the use of  IKE was a problem for setting up the
> MN-HA IPsec SA
> >     and not really providing sufficient justifications for an
> >     alternative scheme to the use of IPsec for securing the
> signaling
> >     messages between the MN and HA
> > 3. There were a few people who expressed strong views of
> keeping IPsec
> >     as the only means for MIP6 security between MN and HA
> (Francis and
> > Hesham (?))
> > 4. There were others who claimed the need for an alternate option to
> >     MIP6 including one operator who plans to deploy the protocol in
> >     their network (Raj, James Kempf, Alpesh, Gopal, Kuntal,
> Vijay, Michael
> Roe)
> > 5. There was also a note from an implementers perspective on the
> >     challenges of integrating MIP6 with IPsec (Michael Roe)
> > 6. There was discussion about the problem of replay attacks and the
> >     need for key refreshment
> > 7. IKEv2 is expected to provide a solution to the problem of setting
> >     up dynamic SAs in networks that rely on AAA
> infrastructures. While
> >     IKEv2 itself has been approved, the details of how IKEv2 is used
> >     with MIP6 are still being worked out in an I-D that is not ready
> >     yet.
> > 8. There was an opinion that the bootstrap work being done in the WG
> >     would address the needs of the environment claimed in I-D
> >     draft-patil-mip6-whyauthdataoption-00.txt
> >
> >
> > _______________________________________________
> > Mip6 mailing list
> > Mip6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mip6
> >
>
>
>
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>



_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6


From mip6-bounces@ietf.org  Sun Sep 26 13:39:01 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20442
	for <mip6-web-archive@ietf.org>; Sun, 26 Sep 2004 13:39:01 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CBd6j-0004tV-P5
	for mip6-web-archive@ietf.org; Sun, 26 Sep 2004 13:46:46 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CBcxt-0000yb-HL; Sun, 26 Sep 2004 13:37:37 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CBcoe-0000Ti-3G
	for mip6@megatron.ietf.org; Sun, 26 Sep 2004 13:28:04 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20140
	for <mip6@ietf.org>; Sun, 26 Sep 2004 13:28:01 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CBcw6-0004lW-5R
	for mip6@ietf.org; Sun, 26 Sep 2004 13:35:46 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id i8QHR3f05843; Sun, 26 Sep 2004 19:27:03 +0200
Received: from givry.rennes.enst-bretagne.fr
	(localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.12.3/8.12.3) with ESMTP id
	i8QHR3Sj077583; Sun, 26 Sep 2004 19:27:03 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200409261727.i8QHR3Sj077583@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Gopal Dommety <gdommety@cisco.com>
Subject: Re: [Mip6] Summary of Justification for Alternative Authentication
	Option 
In-reply-to: Your message of Thu, 23 Sep 2004 14:55:05 PDT.
	<4.3.2.7.2.20040923143829.029e1a48@mira-sjc5-d.cisco.com> 
Date: Sun, 26 Sep 2004 19:27:03 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17

 In your previous mail you wrote:

   Summary
   =======
   
   The WG has been engaged in a discussion over the last week on the
   topic of standardizing an authentication date suboption based

=> I believe "standardizing" means to make it a Proposed Standard,
doesn't it?

   mechanism for the purpose of registering an MN with its HA via the
   BU/BAck messages.
   To summarize the discussion in brief:
   1. The I-D draft-patil-mip6-whyauthdataoption-00.txt was used as the
       baseline for the discussion
   2. Opinion was expressed that the I-D was more inclined in justifying
       why the use of  IKE was a problem for setting up the MN-HA IPsec SA
       and not really providing sufficient justifications for an
       alternative scheme to the use of IPsec for securing the signaling
       messages between the MN and HA
   3. There were a few people who expressed strong views of keeping IPsec
       as the only means for MIP6 security between MN and HA (Francis and 
   Hesham (?))
   4. There were others who claimed the need for an alternate option to
       MIP6 including one operator who plans to deploy the protocol in
       their network (Raj, James Kempf, Alpesh, Gopal, Kuntal, Vijay,
       Michael Roe)

=> you should be more accurate: just alternate option or standardized
alternate option?

   5. There was also a note from an implementers perspective on the
       challenges of integrating MIP6 with IPsec (Michael Roe)
   6. There was discussion about the problem of replay attacks and the
       need for key refreshment
   7. IKEv2 is expected to provide a solution to the problem of setting
       up dynamic SAs in networks that rely on AAA infrastructures. While
       IKEv2 itself has been approved, the details of how IKEv2 is used
       with MIP6 are still being worked out in an I-D that is not ready
       yet.

=> IMHO the main problem with an IKEv2 based solution is that there is
no public implementation... Another point is that IKEv2 does not support
home agent allocation.

   8. There was an opinion that the bootstrap work being done in the WG
       would address the needs of the environment claimed in I-D
       draft-patil-mip6-whyauthdataoption-00.txt
   
=> some AAA/EAP based solutions are already ready (i.e., implemented)
and of course they support home agent allocation.

There are some other points:
 - we were supposed to ask an advice from security area directors
 - the requirement level of auth data option is still not clear enough
 - if the auth data option is only for the 3GPP2 environment there is
   no reason to standardize it at the IETF: the 3GPP2 can require what
   it wants in its own environment. If it likes to get an IETF document,
   an informational RFC should be enough and even faster (less possible
   concerns from the IESG).
Some of these points were already mentioned on the list...

Regards

Francis.Dupont@enst-bretagne.fr

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6


From mip6-bounces@ietf.org  Sun Sep 26 13:47:37 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20705
	for <mip6-web-archive@ietf.org>; Sun, 26 Sep 2004 13:47:37 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CBdF2-0004zT-9n
	for mip6-web-archive@ietf.org; Sun, 26 Sep 2004 13:55:20 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CBd6r-0001t8-Pd; Sun, 26 Sep 2004 13:46:53 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CBd67-0001o6-5s
	for mip6@megatron.ietf.org; Sun, 26 Sep 2004 13:46:07 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20681
	for <mip6@ietf.org>; Sun, 26 Sep 2004 13:46:06 -0400 (EDT)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CBdDZ-0004yJ-7p
	for mip6@ietf.org; Sun, 26 Sep 2004 13:53:49 -0400
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-2.cisco.com with ESMTP; 26 Sep 2004 10:48:38 -0700
Received: from mira-sjc5-d.cisco.com (IDENT:mirapoint@mira-sjc5-d.cisco.com
	[171.71.163.28])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i8QHjXwp005588;
	Sun, 26 Sep 2004 10:45:33 -0700 (PDT)
Received: from gdommety-w2k04.cisco.com (sjc-vpn4-903.cisco.com [10.21.83.134])
	by mira-sjc5-d.cisco.com (MOS 3.4.6-GR) with ESMTP id AEQ89296;
	Sun, 26 Sep 2004 10:45:32 -0700 (PDT)
Message-Id: <4.3.2.7.2.20040926104125.02c04c10@mira-sjc5-d.cisco.com>
X-Sender: gdommety@mira-sjc5-d.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Sun, 26 Sep 2004 10:45:33 -0700
To: "James Kempf" <kempf@docomolabs-usa.com>
From: Gopal Dommety <gdommety@cisco.com>
Subject: Re: [Mip6] Summary of Justification for
	AlternativeAuthenticationOption
In-Reply-To: <004401c4a2db$6c3e0d40$576015ac@dcml.docomolabsusa.com>
References: <697DAA22C5004B4596E033803A7CEF4403B1BE7C@daebe007.americas.nokia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 03169bfe4792634a390035a01a6c6d2f
Cc: mip6@ietf.org, Basavaraj.Patil@nokia.com
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3fbd9b434023f8abfcb1532abaec7a21

James,


I don't see the issue with mandating in the RFC that both mechanisms should 
be supported on the HA.
If someone chooses to ignore the standard they will do it at their own risk.


I was simplifying the positions...apologies for the mis-representation.

thanks,
-Gopal


At 01:41 AM 9/25/2004 -0700, James Kempf wrote:
>Raj,
>
>Whether we agree is not the point, the point is that Gopal's email was
>ostensibly a summary of the discussion on the list, and I believe it missed
>an important point that I brought up, namely that IETF cannot mandate
>whether an operator enables their HA to accept both kinds of traffic or not,
>and if we standardize two ways of doing the same thing - even if we mandate
>that the HA support both - an operator can decide to support only one
>causing an interoperability problem.
>
>Additonally, I believe Gopal's summary misrepresented my position. My
>position is not one of unqualified support for the authentication option. It
>is:
>
>- We should select either IPsec or the authentication option (RFC 1958, if
>there's two choices for the same functionality, choose one).
>
>- Since we have already standardized IPsec and the authentication option is
>only of interest to cdma2K operators, we should process the authentication
>option as an informational draft and *NOT* an Internet standard.
>
>I hope that makes my position clearer. I hope, in the future, that the WG
>chairs will strive to be a little more accurate and objective when
>performing concensus calls.
>
>             jak
>
>----- Original Message -----
>From: <Basavaraj.Patil@nokia.com>
>To: <kempf@docomolabs-usa.com>; <mip6@ietf.org>; <gdommety@cisco.com>
>Sent: Friday, September 24, 2004 8:51 AM
>Subject: RE: [Mip6] Summary of Justification for
>AlternativeAuthenticationOption
>
>
>
>James,
>
>I disagree with the need for having such a mechanism in view of the fact
>that an HA is expected to support both the authentication schemes
>mandatorily.
>
>-BPa
>
> >
> > Gopal,
> >
> > I believe you missed the need for some mechanism to allow an
> > MN to determine
> > which authentication technique to use. Without this, there is an
> > interoperability problem, because the MN cannot infer simply from the
> > failure of the signaling that it should try the other method.
> >
> >             jak
> >
> > ----- Original Message -----
> > From: "Gopal Dommety" <gdommety@cisco.com>
> > To: <mip6@ietf.org>
> > Sent: Thursday, September 23, 2004 2:55 PM
> > Subject: [Mip6] Summary of Justification for Alternative
> > AuthenticationOption
> >
> >
> > > Hello All,
> > >
> > >              I am attaching a summary of the discussion
> > that took place on
> > > justification of an alternate authentication mechanism.
> > Please let me
> > know if
> > > I have left out any important issue in the summary. I could
> > have also
> > mis-read
> > > people opinions, so if there is a correction please let me
> > know. I will
> > > send a follow-up
> > >   email with the next steps.
> > >
> > >
> > > Thanks,
> > > -Gopal
> > >
> > >
> > > Summary
> > > =======
> > >
> > > The WG has been engaged in a discussion over the last week on the
> > > topic of standardizing an authentication date suboption based
> > > mechanism for the purpose of registering an MN with its HA via the
> > > BU/BAck messages.
> > > To summarize the discussion in brief:
> > > 1. The I-D draft-patil-mip6-whyauthdataoption-00.txt was used as the
> > >     baseline for the discussion
> > > 2. Opinion was expressed that the I-D was more inclined in
> > justifying
> > >     why the use of  IKE was a problem for setting up the
> > MN-HA IPsec SA
> > >     and not really providing sufficient justifications for an
> > >     alternative scheme to the use of IPsec for securing the
> > signaling
> > >     messages between the MN and HA
> > > 3. There were a few people who expressed strong views of
> > keeping IPsec
> > >     as the only means for MIP6 security between MN and HA
> > (Francis and
> > > Hesham (?))
> > > 4. There were others who claimed the need for an alternate option to
> > >     MIP6 including one operator who plans to deploy the protocol in
> > >     their network (Raj, James Kempf, Alpesh, Gopal, Kuntal,
> > Vijay, Michael
> > Roe)
> > > 5. There was also a note from an implementers perspective on the
> > >     challenges of integrating MIP6 with IPsec (Michael Roe)
> > > 6. There was discussion about the problem of replay attacks and the
> > >     need for key refreshment
> > > 7. IKEv2 is expected to provide a solution to the problem of setting
> > >     up dynamic SAs in networks that rely on AAA
> > infrastructures. While
> > >     IKEv2 itself has been approved, the details of how IKEv2 is used
> > >     with MIP6 are still being worked out in an I-D that is not ready
> > >     yet.
> > > 8. There was an opinion that the bootstrap work being done in the WG
> > >     would address the needs of the environment claimed in I-D
> > >     draft-patil-mip6-whyauthdataoption-00.txt
> > >
> > >
> > > _______________________________________________
> > > Mip6 mailing list
> > > Mip6@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/mip6
> > >
> >
> >
> >
> > _______________________________________________
> > Mip6 mailing list
> > Mip6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mip6
> >


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6


From mip6-bounces@ietf.org  Sun Sep 26 13:54:34 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20917
	for <mip6-web-archive@ietf.org>; Sun, 26 Sep 2004 13:54:34 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CBdLl-00055y-F6
	for mip6-web-archive@ietf.org; Sun, 26 Sep 2004 14:02:17 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CBdB5-0002Q9-KC; Sun, 26 Sep 2004 13:51:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CBdAB-0002I5-GF
	for mip6@megatron.ietf.org; Sun, 26 Sep 2004 13:50:19 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20796
	for <mip6@ietf.org>; Sun, 26 Sep 2004 13:50:18 -0400 (EDT)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CBdHd-00051H-QJ
	for mip6@ietf.org; Sun, 26 Sep 2004 13:58:02 -0400
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-3.cisco.com with ESMTP; 26 Sep 2004 11:02:44 +0000
X-BrightmailFiltered: true
Received: from mira-sjc5-d.cisco.com (IDENT:mirapoint@mira-sjc5-d.cisco.com
	[171.71.163.28])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i8QHnflr001366;
	Sun, 26 Sep 2004 10:49:42 -0700 (PDT)
Received: from gdommety-w2k04.cisco.com (sjc-vpn4-903.cisco.com [10.21.83.134])
	by mira-sjc5-d.cisco.com (MOS 3.4.6-GR) with ESMTP id AEQ89337;
	Sun, 26 Sep 2004 10:49:42 -0700 (PDT)
Message-Id: <4.3.2.7.2.20040926104610.02c04d18@mira-sjc5-d.cisco.com>
X-Sender: gdommety@mira-sjc5-d.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Sun, 26 Sep 2004 10:49:43 -0700
To: "James Kempf" <kempf@docomolabs-usa.com>
From: Gopal Dommety <gdommety@cisco.com>
Subject: Re: [Mip6] Summary of Justification for
	AlternativeAuthenticationOption
In-Reply-To: <004401c4a2db$6c3e0d40$576015ac@dcml.docomolabsusa.com>
References: <697DAA22C5004B4596E033803A7CEF4403B1BE7C@daebe007.americas.nokia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 36b1f8810cb91289d885dc8ab4fc8172
Cc: mip6@ietf.org, Basavaraj.Patil@nokia.com
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 87a3f533bb300b99e2a18357f3c1563d

James,



>I hope that makes my position clearer. I hope, in the future, that the WG
>chairs will strive to be a little more accurate and objective when
>performing concensus calls.

The email I sent out was a summary of the discussion and not a summary of 
the consensus call. Next time I will be strive to be clearer.

Thanks,
-Gopal




>             jak
>
>----- Original Message -----
>From: <Basavaraj.Patil@nokia.com>
>To: <kempf@docomolabs-usa.com>; <mip6@ietf.org>; <gdommety@cisco.com>
>Sent: Friday, September 24, 2004 8:51 AM
>Subject: RE: [Mip6] Summary of Justification for
>AlternativeAuthenticationOption
>
>
>
>James,
>
>I disagree with the need for having such a mechanism in view of the fact
>that an HA is expected to support both the authentication schemes
>mandatorily.
>
>-BPa
>
> >
> > Gopal,
> >
> > I believe you missed the need for some mechanism to allow an
> > MN to determine
> > which authentication technique to use. Without this, there is an
> > interoperability problem, because the MN cannot infer simply from the
> > failure of the signaling that it should try the other method.
> >
> >             jak
> >
> > ----- Original Message -----
> > From: "Gopal Dommety" <gdommety@cisco.com>
> > To: <mip6@ietf.org>
> > Sent: Thursday, September 23, 2004 2:55 PM
> > Subject: [Mip6] Summary of Justification for Alternative
> > AuthenticationOption
> >
> >
> > > Hello All,
> > >
> > >              I am attaching a summary of the discussion
> > that took place on
> > > justification of an alternate authentication mechanism.
> > Please let me
> > know if
> > > I have left out any important issue in the summary. I could
> > have also
> > mis-read
> > > people opinions, so if there is a correction please let me
> > know. I will
> > > send a follow-up
> > >   email with the next steps.
> > >
> > >
> > > Thanks,
> > > -Gopal
> > >
> > >
> > > Summary
> > > =======
> > >
> > > The WG has been engaged in a discussion over the last week on the
> > > topic of standardizing an authentication date suboption based
> > > mechanism for the purpose of registering an MN with its HA via the
> > > BU/BAck messages.
> > > To summarize the discussion in brief:
> > > 1. The I-D draft-patil-mip6-whyauthdataoption-00.txt was used as the
> > >     baseline for the discussion
> > > 2. Opinion was expressed that the I-D was more inclined in
> > justifying
> > >     why the use of  IKE was a problem for setting up the
> > MN-HA IPsec SA
> > >     and not really providing sufficient justifications for an
> > >     alternative scheme to the use of IPsec for securing the
> > signaling
> > >     messages between the MN and HA
> > > 3. There were a few people who expressed strong views of
> > keeping IPsec
> > >     as the only means for MIP6 security between MN and HA
> > (Francis and
> > > Hesham (?))
> > > 4. There were others who claimed the need for an alternate option to
> > >     MIP6 including one operator who plans to deploy the protocol in
> > >     their network (Raj, James Kempf, Alpesh, Gopal, Kuntal,
> > Vijay, Michael
> > Roe)
> > > 5. There was also a note from an implementers perspective on the
> > >     challenges of integrating MIP6 with IPsec (Michael Roe)
> > > 6. There was discussion about the problem of replay attacks and the
> > >     need for key refreshment
> > > 7. IKEv2 is expected to provide a solution to the problem of setting
> > >     up dynamic SAs in networks that rely on AAA
> > infrastructures. While
> > >     IKEv2 itself has been approved, the details of how IKEv2 is used
> > >     with MIP6 are still being worked out in an I-D that is not ready
> > >     yet.
> > > 8. There was an opinion that the bootstrap work being done in the WG
> > >     would address the needs of the environment claimed in I-D
> > >     draft-patil-mip6-whyauthdataoption-00.txt
> > >
> > >
> > > _______________________________________________
> > > Mip6 mailing list
> > > Mip6@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/mip6
> > >
> >
> >
> >
> > _______________________________________________
> > Mip6 mailing list
> > Mip6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mip6
> >
>
>
>
>_______________________________________________
>Mip6 mailing list
>Mip6@ietf.org
>https://www1.ietf.org/mailman/listinfo/mip6


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6


From mip6-bounces@ietf.org  Sun Sep 26 13:57:40 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21037
	for <mip6-web-archive@ietf.org>; Sun, 26 Sep 2004 13:57:39 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CBdOl-00058N-Dm
	for mip6-web-archive@ietf.org; Sun, 26 Sep 2004 14:05:23 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CBdFx-0002om-90; Sun, 26 Sep 2004 13:56:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CBdCy-0002XC-2y
	for mip6@megatron.ietf.org; Sun, 26 Sep 2004 13:53:12 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20872
	for <mip6@ietf.org>; Sun, 26 Sep 2004 13:53:11 -0400 (EDT)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CBdKQ-00053s-Fm
	for mip6@ietf.org; Sun, 26 Sep 2004 14:00:54 -0400
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-3.cisco.com with ESMTP; 26 Sep 2004 11:05:39 +0000
X-BrightmailFiltered: true
Received: from mira-sjc5-d.cisco.com (IDENT:mirapoint@mira-sjc5-d.cisco.com
	[171.71.163.28])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i8QHqalr002063;
	Sun, 26 Sep 2004 10:52:36 -0700 (PDT)
Received: from gdommety-w2k04.cisco.com (sjc-vpn4-903.cisco.com [10.21.83.134])
	by mira-sjc5-d.cisco.com (MOS 3.4.6-GR) with ESMTP id AEQ89386;
	Sun, 26 Sep 2004 10:52:37 -0700 (PDT)
Message-Id: <4.3.2.7.2.20040926105038.02b7cfe8@mira-sjc5-d.cisco.com>
X-Sender: gdommety@mira-sjc5-d.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Sun, 26 Sep 2004 10:52:38 -0700
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
From: Gopal Dommety <gdommety@cisco.com>
Subject: Re: [Mip6] Summary of Justification for Alternative
	Authentication Option 
In-Reply-To: <200409261727.i8QHR3Sj077583@givry.rennes.enst-bretagne.fr>
References: <Your message of Thu, 23 Sep 2004 14:55:05 PDT.
	<4.3.2.7.2.20040923143829.029e1a48@mira-sjc5-d.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745


Francis,

please see inline...

At 07:27 PM 9/26/2004 +0200, Francis Dupont wrote:
>  In your previous mail you wrote:
>
>    Summary
>    =======
>
>    The WG has been engaged in a discussion over the last week on the
>    topic of standardizing an authentication date suboption based
>
>=> I believe "standardizing" means to make it a Proposed Standard,
>doesn't it?


Yes.


>    mechanism for the purpose of registering an MN with its HA via the
>    BU/BAck messages.
>    To summarize the discussion in brief:
>    1. The I-D draft-patil-mip6-whyauthdataoption-00.txt was used as the
>        baseline for the discussion
>    2. Opinion was expressed that the I-D was more inclined in justifying
>        why the use of  IKE was a problem for setting up the MN-HA IPsec SA
>        and not really providing sufficient justifications for an
>        alternative scheme to the use of IPsec for securing the signaling
>        messages between the MN and HA
>    3. There were a few people who expressed strong views of keeping IPsec
>        as the only means for MIP6 security between MN and HA (Francis and
>    Hesham (?))
>    4. There were others who claimed the need for an alternate option to
>        MIP6 including one operator who plans to deploy the protocol in
>        their network (Raj, James Kempf, Alpesh, Gopal, Kuntal, Vijay,
>        Michael Roe)
>
>=> you should be more accurate: just alternate option or standardized
>alternate option?
>
>    5. There was also a note from an implementers perspective on the
>        challenges of integrating MIP6 with IPsec (Michael Roe)
>    6. There was discussion about the problem of replay attacks and the
>        need for key refreshment
>    7. IKEv2 is expected to provide a solution to the problem of setting
>        up dynamic SAs in networks that rely on AAA infrastructures. While
>        IKEv2 itself has been approved, the details of how IKEv2 is used
>        with MIP6 are still being worked out in an I-D that is not ready
>        yet.
>
>=> IMHO the main problem with an IKEv2 based solution is that there is
>no public implementation... Another point is that IKEv2 does not support
>home agent allocation.
>
>    8. There was an opinion that the bootstrap work being done in the WG
>        would address the needs of the environment claimed in I-D
>        draft-patil-mip6-whyauthdataoption-00.txt
>
>=> some AAA/EAP based solutions are already ready (i.e., implemented)
>and of course they support home agent allocation.
>
>There are some other points:
>  - we were supposed to ask an advice from security area directors
>  - the requirement level of auth data option is still not clear enough
>  - if the auth data option is only for the 3GPP2 environment there is
>    no reason to standardize it at the IETF: the 3GPP2 can require what
>    it wants in its own environment. If it likes to get an IETF document,
>    an informational RFC should be enough and even faster (less possible
>    concerns from the IESG).
>Some of these points were already mentioned on the list...
>
>Regards
>
>Francis.Dupont@enst-bretagne.fr
>
>_______________________________________________
>Mip6 mailing list
>Mip6@ietf.org
>https://www1.ietf.org/mailman/listinfo/mip6


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6


From mip6-bounces@ietf.org  Mon Sep 27 05:24:50 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA14784
	for <mip6-web-archive@ietf.org>; Mon, 27 Sep 2004 05:24:50 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CBrsB-0001bX-Kc
	for mip6-web-archive@ietf.org; Mon, 27 Sep 2004 05:32:43 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CBreS-0007VF-V4; Mon, 27 Sep 2004 05:18:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CBrdu-0007Sm-VJ
	for mip6@megatron.ietf.org; Mon, 27 Sep 2004 05:17:58 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA14611
	for <mip6@ietf.org>; Mon, 27 Sep 2004 05:17:54 -0400 (EDT)
Received: from bundit.graduate.kmitl.ac.th ([161.246.39.3])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CBrlP-0001Ww-10
	for mip6@ietf.org; Mon, 27 Sep 2004 05:25:47 -0400
Received: from graduate.kmitl.ac.th ([161.246.39.95])
	by bundit.graduate.kmitl.ac.th (8.12.8/8.12.5) with ESMTP id
	i8R9Cuhf027931 for <mip6@ietf.org>; Mon, 27 Sep 2004 16:12:57 +0700
Message-ID: <4157DC27.2030108@graduate.kmitl.ac.th>
Date: Mon, 27 Sep 2004 16:23:51 +0700
From: Warodom Werapun <ple@graduate.kmitl.ac.th>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.4a) Gecko/20030401
X-Accept-Language: th, en-us, en
MIME-Version: 1.0
To: mip6@ietf.org
X-Enigmail-Version: 0.75.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=TIS-620; format=flowed
Content-Transfer-Encoding: 7bit
X-Graduate-MailScanner-Information: Please contact the ISP for more information
X-Graduate-MailScanner: Found to be clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Content-Transfer-Encoding: 7bit
Subject: [Mip6] Before BU..
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Content-Transfer-Encoding: 7bit


    Before MIPv6 process Binding update, I saw that there are RR, IPsec 
, IKE.
I heard that IPsec make RR securely (protect man-in-the middle all paths).
And before we use IPsec, we need to setup SA via IKE.  
    So, if we used IKE (may be SKIP (diffie-cert) ) to generate Kbu (Kbm)
and take out IPsec and RR. I think, it may decrease packet delay time 
significantly, isn't it?

-- 
Warodom  Werapun
PGP:  http://plex.coe.psu.ac.th/myPGP.txt



_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6


From mip6-bounces@ietf.org  Mon Sep 27 06:05:44 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA16747
	for <mip6-web-archive@ietf.org>; Mon, 27 Sep 2004 06:05:44 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CBsVm-0002Fk-B8
	for mip6-web-archive@ietf.org; Mon, 27 Sep 2004 06:13:38 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CBsLA-0002XX-3b; Mon, 27 Sep 2004 06:02:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CBsG6-0002KG-TE
	for mip6@megatron.ietf.org; Mon, 27 Sep 2004 05:57:26 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA16481
	for <mip6@ietf.org>; Mon, 27 Sep 2004 05:57:24 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CBsNg-000291-Ok
	for mip6@ietf.org; Mon, 27 Sep 2004 06:05:18 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id i8R9ub004356; Mon, 27 Sep 2004 11:56:37 +0200
Received: from givry.rennes.enst-bretagne.fr
	(localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.12.3/8.12.3) with ESMTP id
	i8R9ubSj080164; Mon, 27 Sep 2004 11:56:37 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200409270956.i8R9ubSj080164@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Warodom Werapun <ple@graduate.kmitl.ac.th>
Subject: Re: [Mip6] Before BU.. 
In-reply-to: Your message of Mon, 27 Sep 2004 16:23:51 +0700.
	<4157DC27.2030108@graduate.kmitl.ac.th> 
Date: Mon, 27 Sep 2004 11:56:37 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9

 In your previous mail you wrote:

       Before MIPv6 process Binding update, I saw that there are RR, IPsec 
   , IKE.

=> do you speak about the MN-HA case, the MN-CN case or both?
Currently:
 - IPsec is mandatory and IKE recommended in the MN-HA case
 - RR is mandatory in the MN-CN case but there are some proposals
   for stronger but dedicated schemes in this case:
   * preconfigured Kbm (draft-ietf-mip6-precfgKbm-00.txt)
   * IPsec (draft-dupont-mipv6-cn-ipsec-01.txt)
   * CGA (draft-haddad-mip6-cga-omipv6-02.txt)
   ...

   I heard that IPsec make RR securely (protect man-in-the middle all paths).

=> yes, RR security relies on IPsec between MN-HA.

   And before we use IPsec, we need to setup SA via IKE.  

=> currently one has the choice between manual keying, automatic keying
using IKE and automatic keying using something else than IKE.
Obviously the last solution is dedicated, i.e., it relies on a
preagreement but this constraint is not a real problem as there should
be some kind of preagreements in any case.

       So, if we used IKE (may be SKIP (diffie-cert) ) to generate Kbu (Kbm)
   and take out IPsec and RR. I think, it may decrease packet delay time 
   significantly, isn't it?
   
=> if I understand well you propose to create a DOI for IKE in order
to build directly a Kbm? I can't see major advantages vs preconf Kbm
or IPsec...

Thanks

Francis.Dupont@enst-bretagne.fr

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6


From mip6-bounces@ietf.org  Mon Sep 27 10:00:10 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00288
	for <mip6-web-archive@ietf.org>; Mon, 27 Sep 2004 10:00:09 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CBwAf-0006Vm-KC
	for mip6-web-archive@ietf.org; Mon, 27 Sep 2004 10:08:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CBvyy-0002gg-E1; Mon, 27 Sep 2004 09:56:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CBvuc-0002Dx-Vn
	for mip6@megatron.ietf.org; Mon, 27 Sep 2004 09:51:31 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29862
	for <mip6@ietf.org>; Mon, 27 Sep 2004 09:51:28 -0400 (EDT)
Received: from mail.flarion.com ([63.103.94.23] helo=ftmailgfi.flariontech.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CBw2E-0006MG-Sq
	for mip6@ietf.org; Mon, 27 Sep 2004 09:59:24 -0400
Received: from ftmailserver.flariontech.com ([10.10.1.140]) by
	ftmailgfi.flariontech.com with Microsoft SMTPSVC(5.0.2195.6713);
	Mon, 27 Sep 2004 09:49:38 -0400
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: RE : [Mip6] Justifications for
	standardizingdraft-ietf-mip6-auth-protocol-00.txt
Date: Mon, 27 Sep 2004 09:49:38 -0400
Message-ID: <A11736FE943F1A408F8BBB1B9F5FE8AD394B52@ftmailserver.flariontech.com>
Thread-Topic: RE : [Mip6] Justifications for
	standardizingdraft-ietf-mip6-auth-protocol-00.txt
Thread-Index: AcSkkxsNOD1e7n01TmOfITzm84Is3wABZx1A
From: "Soliman, Hesham" <H.Soliman@flarion.com>
To: "Vijay Devarapalli" <vijayd@iprg.nokia.com>
X-OriginalArrivalTime: 27 Sep 2004 13:49:38.0992 (UTC)
	FILETIME=[D511E300:01C4A498]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Content-Transfer-Encoding: quoted-printable


=20
 > >  >=20
 > >  > on links, where there is no security on the access links, the MN
 > >  > must support IPsec for Route Optimization.
 > >=20
 > > =3D> ??? Where did this requirement come from, certainly not=20
 > rfc 3775?
 >=20
 > RFC 3776
 >=20
 >     o  ESP encapsulation of the Home Test Init and Home Test messages
 >        tunneled between the mobile node and home agent MUST=20
 > be supported
 >        and SHOULD be used.

=3D> That doesn't say anything about links. This is a requirement
for all cases.

Hesham

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
This email may contain confidential and privileged material for the sole =
use
 of the intended recipient.  Any review or distribution by others is =
strictly
 prohibited.  If you are not the intended recipient please contact the =
sender
 and delete all copies.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6


From mip6-bounces@ietf.org  Mon Sep 27 23:15:05 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA05114
	for <mip6-web-archive@ietf.org>; Mon, 27 Sep 2004 23:15:05 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CC8a3-0007g8-RT
	for mip6-web-archive@ietf.org; Mon, 27 Sep 2004 23:23:09 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CC8Fw-0008Mp-9i; Mon, 27 Sep 2004 23:02:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CC85E-00074X-1b
	for mip6@megatron.ietf.org; Mon, 27 Sep 2004 22:51:16 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA03921
	for <mip6@ietf.org>; Mon, 27 Sep 2004 22:51:12 -0400 (EDT)
Received: from bundit.graduate.kmitl.ac.th ([161.246.39.3])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CC8Cw-0007H8-5c
	for mip6@ietf.org; Mon, 27 Sep 2004 22:59:16 -0400
Received: from graduate.kmitl.ac.th ([161.246.39.95])
	by bundit.graduate.kmitl.ac.th (8.12.8/8.12.5) with ESMTP id
	i8S2k2hf003716; Tue, 28 Sep 2004 09:46:03 +0700
Message-ID: <4158D300.8080801@graduate.kmitl.ac.th>
Date: Tue, 28 Sep 2004 09:57:04 +0700
From: Warodom Werapun <ple@graduate.kmitl.ac.th>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.4a) Gecko/20030401
X-Accept-Language: th, en-us, en
MIME-Version: 1.0
To: mip6@ietf.org
X-Enigmail-Version: 0.75.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=TIS-620; format=flowed
Content-Transfer-Encoding: 7bit
X-Graduate-MailScanner-Information: Please contact the ISP for more information
X-Graduate-MailScanner: Found to be clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Content-Transfer-Encoding: 7bit
Cc: mipl@mobile-ipv6.org
Subject: [Mip6] IPSec in MIPv6
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Content-Transfer-Encoding: 7bit

    If we used IPsec to secure RR, then where Security Association(SA) 
store?
Does SA store in Mobile Node?  or Home agent?

If SA store in HA, then IKEv2 was run between HA with another HA ( in 
another network), is it? for this case, who sent IKE_Request? (MN or HA?)

if SA store in Mobile Node , Does IKEv2 run between MN and CN?

Thank your for reply,
-- 
Warodom  Werapun
PGP:  http://plex.coe.psu.ac.th/myPGP.txt



_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6


From mip6-bounces@ietf.org  Tue Sep 28 06:12:49 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10855
	for <mip6-web-archive@ietf.org>; Tue, 28 Sep 2004 06:12:49 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CCF6O-000622-BF
	for mip6-web-archive@ietf.org; Tue, 28 Sep 2004 06:20:56 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CCExk-0002P7-0C; Tue, 28 Sep 2004 06:12:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CCEsq-0000bq-Cv
	for mip6@megatron.ietf.org; Tue, 28 Sep 2004 06:06:56 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10486
	for <mip6@ietf.org>; Tue, 28 Sep 2004 06:06:53 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CCF0e-0005vY-5V
	for mip6@ietf.org; Tue, 28 Sep 2004 06:15:00 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id i8SA5XO20056; Tue, 28 Sep 2004 12:05:33 +0200
Received: from givry.rennes.enst-bretagne.fr
	(localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.12.3/8.12.3) with ESMTP id
	i8SA5WSj085238; Tue, 28 Sep 2004 12:05:33 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200409281005.i8SA5WSj085238@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Warodom Werapun <ple@graduate.kmitl.ac.th>
Subject: Re: [Mip6] IPSec in MIPv6 
In-reply-to: Your message of Tue, 28 Sep 2004 09:57:04 +0700.
	<4158D300.8080801@graduate.kmitl.ac.th> 
Date: Tue, 28 Sep 2004 12:05:32 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: mip6@ietf.org, mipl@mobile-ipv6.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5

 In your previous mail you wrote:

       If we used IPsec to secure RR, then where Security Association(SA) 
   store?

=> I believe you mean "where are SAs stored?"
There is a SA pair between the MN and the HA (RFC 3776, section 4.1,
item #4) dedicated to the protection of RR. The SAs are "stored"
in both ends, i.e., the MN and the HA.

   Does SA store in Mobile Node?  or Home agent?
   
=> both.

   If SA store in HA, then IKEv2 was run between HA with another HA ( in 
   another network), is it?

=> I don't understand.

   for this case, who sent IKE_Request? (MN or HA?)
   
=> what is IKE_Request? If you ask which is the initiator, it is the MN
but not always (there is a rare case where the initiator is the HA).

   if SA store in Mobile Node , Does IKEv2 run between MN and CN?
   
=> no

Francis.Dupont@enst-bretagne.fr

PS: MIPL does not support IKE.

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6


From mip6-bounces@ietf.org  Tue Sep 28 11:48:17 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00920
	for <mip6-web-archive@ietf.org>; Tue, 28 Sep 2004 11:48:17 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CCKL4-0003ti-Vw
	for mip6-web-archive@ietf.org; Tue, 28 Sep 2004 11:56:27 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CCK2R-0005rf-VB; Tue, 28 Sep 2004 11:37:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CCJwe-0004Eh-Kg
	for mip6@megatron.ietf.org; Tue, 28 Sep 2004 11:31:12 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29935
	for <mip6@ietf.org>; Tue, 28 Sep 2004 11:31:10 -0400 (EDT)
Received: from mail1.is.haw-hamburg.de ([141.22.192.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CCK4R-0003Z3-KJ
	for mip6@ietf.org; Tue, 28 Sep 2004 11:39:19 -0400
Received: from localhost (localhost [127.0.0.1])
	by mail1.is.haw-hamburg.de (Postfix) with ESMTP
	id 2F89961F1D; Tue, 28 Sep 2004 17:30:36 +0200 (CEST)
Received: from mail1.is.haw-hamburg.de ([127.0.0.1])
	by localhost (mail1 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 00943-04; Tue, 28 Sep 2004 17:30:36 +0200 (CEST)
Received: from mailgate.informatik.haw-hamburg.de
	(isis.informatik.haw-hamburg.de [141.22.10.60])
	by mail1.is.haw-hamburg.de (Postfix) with ESMTP
	id 7F2A061CBA; Tue, 28 Sep 2004 17:30:35 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1])
	by mailgate.informatik.haw-hamburg.de (Postfix) with ESMTP id
	5B8E082800F; Tue, 28 Sep 2004 17:30:00 +0200 (CEST)
Received: from mailgate.informatik.haw-hamburg.de ([127.0.0.1])
	by localhost (mailgate.informatik.haw-hamburg.de [127.0.0.1])
	(amavisd-new, port 10024)
	with LMTP id 19689-01-10; Tue, 28 Sep 2004 17:29:59 +0200 (CEST)
Received: from fhtw-berlin.de (unknown [141.22.17.199])
	by mailgate.informatik.haw-hamburg.de (Postfix) with ESMTP id
	720F4828009; Tue, 28 Sep 2004 17:29:59 +0200 (CEST)
Message-ID: <4159837B.7080804@fhtw-berlin.de>
Date: Tue, 28 Sep 2004 17:30:03 +0200
From: Thomas Schmidt <schmidt@fhtw-berlin.de>
User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: mobopts@irtf.org, mip6@ietf.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new at informatik.haw-hamburg.de
X-Virus-Scanned: ClamAV at mailgate.haw-hamburg.de
X-Spam-Score: 2.4 (++)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Content-Transfer-Encoding: 7bit
Cc: Matthias Waehlisch <mw@fhtw-berlin.de>
Subject: [Mip6] Multicast Handover & M-HMIPv6
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: schmidt@fhtw-berlin.de
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org
X-Spam-Score: 2.4 (++)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Content-Transfer-Encoding: 7bit

Hi all,

we just submitted an improved version of the draft

"Seamless Multicast Handover in a Hierarchical Mobile IPv6 
Environment(M-HMIPv6)"

Besides minor corrections a new smooth transition between HMIPv6 
multicast handover and direct remote subscription of a mobile multicast 
receiver has been added.

Abstract

    This document extends the Hierarchical Mobile IPv6 Internet Draft to
    include the reception and transmission of multicast traffic at the
    Mobile Node. It introduces handover mechanisms for IPv6 mobile
    multicast listeners and mobile multicast senders. Operations are
    based on a Mobile IPv6 environment with local mobility anchor points.
    These local anchor points are conformal with a Hierarchical Mobile
    IPv6 proxy infrastructure. Handover latencies in the proposed scheme
    remain bound to link switching delays with respect to these local
    proxy points. Multicast listeners in addition encounter the option to
    optimize multicast routing by turning to a direct data reception.

    The mechanisms described in this document do not rely on assumptions
    of any specific multicast routing protocol in use. The M-HMIPv6
    protocol operations utilize the existing HMIPv6, MIPv6 and MLDv2
    messages under minor extensions.


Looking forward to feedback & discussions

Thomas & Matthias

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6


From mip6-bounces@ietf.org  Thu Sep 30 16:22:15 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28308
	for <mip6-web-archive@ietf.org>; Thu, 30 Sep 2004 16:22:14 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CD7Zg-0002Jl-NP
	for mip6-web-archive@ietf.org; Thu, 30 Sep 2004 16:30:53 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CD7Gg-0007g9-5m; Thu, 30 Sep 2004 16:11:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CAkzl-0001eD-Nj; Fri, 24 Sep 2004 03:59:58 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA17616;
	Fri, 24 Sep 2004 03:59:56 -0400 (EDT)
Received: from mx1.iit.cnr.it ([146.48.98.40] helo=mx.iit.cnr.it)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CAl6h-0004Nq-Lu; Fri, 24 Sep 2004 04:07:08 -0400
Received: from localhost (mx.iit.cnr.it [127.0.0.1])
	by mx.iit.cnr.it (Postfix) with ESMTP
	id 30E172EE65; Fri, 24 Sep 2004 09:59:21 +0200 (CEST)
Received: from mx.iit.cnr.it ([127.0.0.1])
	by localhost (mx.iit.cnr.it [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP
	id 25205-01; Fri, 24 Sep 2004 09:59:18 +0200 (CEST)
Received: from delmastro1 (delmastrof.iit.cnr.it [146.48.98.74])
	by mx.iit.cnr.it (Postfix) with ESMTP
	id C52942EE6F; Fri, 24 Sep 2004 09:59:16 +0200 (CEST)
Message-ID: <001201c4a20c$640dcdb0$4a623092@delmastro1>
From: "Franca Delmastro" <franca.delmastro@iit.cnr.it>
To: "Franca Delmastro" <franca.delmastro@iit.cnr.it>
Date: Fri, 24 Sep 2004 09:59:10 +0200
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Virus-Scanned: by Content Checker at iit.cnr.it
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 398dc098b38497efe55f044562a219e7
X-Mailman-Approved-At: Thu, 30 Sep 2004 16:11:08 -0400
Subject: [Mip6] [WoWMoM 2005] Cfp: IEEE International Symposium on a World
	of Wireless, Mobile and Multimedia Networks
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1044104558=="
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 2d1100b36d83fed07afbc292d8848e10

This is a multi-part message in MIME format.

--===============1044104558==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_000F_01C4A21D.237D9300"

This is a multi-part message in MIME format.

------=_NextPart_000_000F_01C4A21D.237D9300
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable



[Sincere apologies for possible multiple copies of this message]

-------------------------------------------------------------------------=
-------


  WoWMoM 2005


  CALL FOR PAPERS



   IEEE International Symposium on a World of Wireless, Mobile and =
Multimedia Networks

  =20
  http://cnd.iit.cnr.it/wowmom2005
  Taormina, Italy, June 13-16, 2005


-------------------------------------------------------------------------=
-------
                   Sponsored by The IEEE Computer Society and
                      The University of Texas at Arlington

                        Technical sponsored by IEEE TCCC


**** Submission Deadline --- November 10, 2004 ****
-------------------------------------------------------------------------=
-------


Technology evolution is driving toward a world of wireless, mobile, and =
multimedia pervasive communications where users can seamlessly and =
ubiquitously accomplish their tasks, access information or communicate =
with other users all the anytime, everywhere, and from any device. =
Technologies include, among others, IEEE 802.11, 802.15, 802.16, Mobile =
IP, micro-mobility protocols, IP paging, wireless IP QOS, mobile ad hoc =
and sensor networks, and cellular networks. In addition to these, new =
and emerging technologies (e.g., UWB) need to be taken into account. The =
resulting networking environment will constitute the fourth generation =
wireless networks. 4G will integrate different types of wireless =
networks with wire-line backbone network seamlessly, and provide the =
convergence of voice, multimedia and data traffic over a single IP based =
core network.

WoWMoM 2005 technical program committee is soliciting papers addressing =
the research challenges toward a world of wireless, mobile, and =
multimedia pervasive communications. Two types of contributions will be =
accepted:

FULL PAPERS. Full Papers must present original, previously unpublished, =
complete works, validated by experimentation, simulation, or analysis. =
Practical experiences and experimental efforts are welcome.

POSITION PAPERS. Papers in this category must be visionary, innovative =
and forward-looking. They must offer new perspectives opening future =
research directions, rather than by presenting mature work with =
quantitative results. Only a limited number of slots will be available =
for position papers that will be reviewed primarily for relevance and =
originality.


Topics of interest for WOWMOM 2005 include, but are not limited to, the =
following:

- System prototypes and experiences
- Software technologies and systems
- QoS for real-time voice and video in wireless networks
- Interactive broadband television, gaming, and video distribution
- Middleware support for QoS provision
- Caching and content management in WLANs and WMANs
- Differentiated service in wireless multimedia networks
- IP-based multimedia services over wireless networks
- Networking services for ambient intelligent and pervasive environments
- Multicasting and broadcasting problems and solutions
- Handoff and mobility management
- Seamless internetworking
- IP-based mobile networks
- Location mechanism and services
- Wireless BAN, PAN, LAN, and MAN
- Ad hoc and sensor networks
- Vehicular wireless networks
- Access technologies
- Third and fourth generation systems
- Energy-efficient protocols and power management
- Wireless security and authentication
- Pricing and billing
- Modeling and Performance evaluation


PAPER SUBMISSION AND PUBLICATION
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D

Papers should neither have been published elsewhere nor currently under =
review by another conference or journal.  Guidelines on paper submission =
and formatting will be provided on the website.
Accepted papers will appear in the symposium proceedings published by =
IEEE.


IMPORTANT DATES
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Full papers due:        November 10, 2004
Notification:           January 20, 2005
Camera Ready due:       February 15, 2005




ORGANIZING COMMITTEE
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D


GENERAL Co-Chairs:
        Giuseppe Anastasi, University of Pisa, Italy
        Sajal K. Das, The University of Texas at Arlington, USA


PROGRAM Co-Chairs:
        Marco Conti, IIT-CNR, Italy
        Dipankar Raychaudhuri WINLAB/Rutgers University, USA



FINANCE & REGISTRATION Chair:
        Yonghe Liu, The University of Texas at Arlington, USA




PUBLICITY Co-Chairs:
        Mainak Chatterjee, Univ. Central Florida, USA
        Sunghyun Choi, Seoul National University, Korea
        Franca Delmastro, IIT-CNR, Italy



LOCAL ARRANGEMENTS Chair:
        Antonio Puliafito, University of Messina, Italy




WEB DESIGNER & MANAGER:
        Patrizia Andronico, IIT-CNR, Italy




STEERING COMMITTEE
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D


Marco Conti, IIT-CNR, Italy
Sajal K. Das, The University of Texas at Arlington, USA (chair)
Dipankar Raychaudhuri WINLAB/Rutgers University, USA
Satish K. Tripathi, SUNY Buffalo, USA






PROGRAM COMMITTEE
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D


Arup Acharya, IBM T.J. Watson Research, USA
Dharma P. Agrawal, University of Cincinnati, USA
Kevin C. Almeroth, University of California at Santa Barbara, USA
Christian Becker, University of Stuttgart, Germany
Giuseppe Bianchi, University of Rome "Tor Vergata", Italy
Chris Blondia, University of Antwerp, Belgium
Azzedine  Boukerche, University of Ottawa, Canada
Jiannong Cao, Hong Kong Polytechnic University, Hong Kong
Chua Kee Chaing, National University of Singapore, Republic of Singapore
Rajarathnam Chandramouili, Stevens Institute of Technology, USA
Mainak Chatterjee, University of Central Florida, USA
Carla-Fabiana Chiasserini, Polytechnic of Turin, Italy
A. Chockalingam, Indian Institute of Science, Banglore, India
Sunghyun Choi, Seoul National University, Korea
Antonio Corradi, University of Bologna, Italy
Antony Ephremides, University of Maryland, USA
Gabor Fodor, Ericsson, Sweden
Luigi Fratta, Polytechnic of Milan, Italy
Marco Gruteser, Rutgers University, USA
Paul J.M. Havinga, University of Twente, The Netherlands
Kazuo Imai, NTT DoCoMo, Japan
Victor Leung, The University of British Columbia, Canada
Yonghe Liu, Univ. Texas at Arlington, USA
Holger Karl, Technische Universitaet Berlin, Germany
Anurag Kumar, Indian Inst of Science, Bangalore, India
Mohan Kumar, The University of Texas at Arlington, USA
P. R. Kumar, University of Illinois, USA
Masahiro Kuroda, National Institute of Info. and Com. Tech., Japan
Luciano Lenzini, University of Pisa, Italy
K. Ben Letaief, Hong Kong Univ. Science & Technology, Hong Kong
Giri Mandyam, Nokia Research Center, USA
Martin Mauve, University of Dusseldorf, Germany
Archan Misra, IBM T.J. Watson Research, USA
Refik Molva, Institut Eurecom, France
Giacomo Morabito, University of Catania, Italy
Hiroyuki Morikawa, , University of Tokyo, Japan
Stephan Olariu, Old Dominion University, USA
Maximilian Ott, Semandex Networks, USA
Michael Paterakis, Technical University of Crete, Greece
George C. Polyzos, Athens University of Economics and Business, Greece
Antonio Puliafito, University of Messina, Italy
Jochen H. Schiller, Freie Universit=E4t Berlin, Germany
Henning Schulzrinne, Columbia University, USA
Rajeev Shorey, IBM India Research Lab, India
Ivan Stojmenovic, University of Ottawa, Canada
Violet R. Syrotiuk, Arizona State University, USA
Wade Trappe, Rutgers University, USA
Ooi Wei Tsang, National University of Singapore, Singapore
Christian Tschudin, Basel University, Switzerland
Thierry Turletti, INRIA France
Andras Valko, Ericsson, Hungary
Bernard Walke, Aachen University of Technology, Germany
Xingwei Wang, Northeastern Univ, China
Jie Wu, Florida Atlantic University, USA
Gergely Zaruba, The University of Texas at Arlington, USA
Roger Zimmerman, University of Southern California, USA


************************************************************
Franca Delmastro
Pervasive Computing & Networking Lab. (PerLab)

IIT- National Research Council
via G. Moruzzi,1
56124 Pisa, Italy
phone: +39 050 3152407 (direct)
********************************************************
------=_NextPart_000_000F_01C4A21D.237D9300
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1458" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV style=3D"FONT: 10pt arial"><FONT face=3D"Book Antiqua"=20
color=3D#0000ff></FONT>&nbsp;</DIV>
<DIV>[Sincere apologies for possible multiple copies of this =
message]</DIV>
<DIV>&nbsp;</DIV>
<DIV>
<DIV=20
align=3Dcenter>----------------------------------------------------------=
----------<SPAN></SPAN>------------</DIV>
<DIV align=3Dcenter><BR></DIV>
<BLOCKQUOTE align=3D"center">
  <DIV align=3Dcenter>WoWMoM 2005</DIV></BLOCKQUOTE>
<BLOCKQUOTE align=3D"center"><BR></BLOCKQUOTE>
<BLOCKQUOTE align=3D"center">
  <DIV align=3Dcenter>CALL FOR PAPERS</DIV></BLOCKQUOTE>
<BLOCKQUOTE align=3D"center">&nbsp;</BLOCKQUOTE>
<BLOCKQUOTE align=3D"center"><BR></BLOCKQUOTE>
<BLOCKQUOTE align=3D"center">
  <DIV align=3Dcenter>&nbsp;IEEE International Symposium on a World of =
Wireless,=20
  Mobile and Multimedia Networks</DIV></BLOCKQUOTE>
<BLOCKQUOTE align=3D"center">
  <DIV align=3Dcenter><BR>&nbsp;</DIV></BLOCKQUOTE>
<BLOCKQUOTE align=3D"center">
  <DIV align=3Dcenter><A=20
  =
href=3D"http://cnd.iit.cnr.it/wowmom2005">http://cnd.iit.cnr.it/wowmom200=
5</A></DIV></BLOCKQUOTE>
<BLOCKQUOTE align=3D"center">
  <DIV align=3Dcenter>Taormina, Italy, June 13-16, =
2005</DIV></BLOCKQUOTE>
<DIV align=3Dcenter><BR></DIV>
<DIV=20
align=3Dcenter>----------------------------------------------------------=
----------<SPAN></SPAN>------------</DIV>
<DIV=20
align=3Dcenter>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;<SPAN></SPAN>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Sponsored by The IEEE Computer Society=20
and<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
<SPAN></SPAN>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
=20
The University of Texas at Arlington<BR></DIV>
<DIV=20
align=3Dcenter>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;<SPAN></SPAN>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<X-TAB>&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</X-TAB>Technical sponsored by IEEE TCCC</DIV>
<DIV align=3Dcenter><BR></DIV>
<DIV align=3Dcenter>**** Submission Deadline --- November 10, 2004 =
****</DIV>
<DIV=20
align=3Dcenter>----------------------------------------------------------=
----------<SPAN></SPAN>------------</DIV>
<DIV><BR></DIV>
<DIV><FONT color=3D#000000>Technology evolution is driving toward a =
world of=20
wireless, mobile, and multimedia pervasive communications where users =
can=20
seamlessly and ubiquitously accomplish their tasks, access information =
or=20
communicate with other users all the anytime, everywhere, and from any =
device.=20
Technologies include, among others, IEEE 802.11, 802.15, 802.16, Mobile =
IP,=20
micro-mobility protocols, IP paging, wireless IP QOS, mobile ad hoc and =
sensor=20
networks, and cellular networks. In addition to these, new and emerging=20
technologies (e.g., UWB) need to be taken into account. The resulting =
networking=20
environment will constitute the fourth generation wireless networks. 4G =
will=20
integrate different types of wireless networks with wire-line backbone =
network=20
seamlessly, and provide the convergence of voice, multimedia and data =
traffic=20
over a single IP based core network.</FONT><BR></DIV>
<DIV><FONT color=3D#000000>WoWMoM 2005 technical program committee is =
soliciting=20
papers addressing the research challenges toward a world of wireless, =
mobile,=20
and multimedia pervasive communications. Two types of contributions will =
be=20
accepted:<BR><BR>FULL PAPERS. Full Papers must present original, =
previously=20
unpublished, complete works, validated by experimentation, simulation, =
or=20
analysis. Practical experiences and experimental efforts are=20
welcome.<BR><BR>POSITION PAPERS. Papers in this category must be =
visionary,=20
innovative and forward-looking. They must offer new perspectives opening =
future=20
research directions, rather than by presenting mature work with =
quantitative=20
results. Only a limited number of slots will be available for position =
papers=20
that will be reviewed primarily for relevance and =
originality.<BR><BR><BR>Topics=20
of interest for WOWMOM 2005 include, but are not limited to, the=20
following:</FONT><BR></DIV>
<DIV><FONT color=3D#000000>- System prototypes and experiences<BR>- =
Software=20
technologies and systems<BR>- QoS for real-time voice and video in =
wireless=20
networks<BR>- Interactive broadband television, gaming, and video=20
distribution<BR>- Middleware support for QoS provision<BR>- Caching and =
content=20
management in WLANs and WMANs<BR>- Differentiated service in wireless =
multimedia=20
networks<BR>- IP-based multimedia services over wireless networks<BR>-=20
Networking services for ambient intelligent and pervasive=20
environments</FONT></DIV>
<DIV><FONT color=3D#000000>- Multicasting and broadcasting problems and=20
solutions<BR>- Handoff and mobility management<BR>- Seamless=20
internetworking<BR>- IP-based mobile networks<BR>- Location mechanism =
and=20
services<BR>- Wireless BAN, PAN, LAN, and MAN<BR>- Ad hoc and sensor=20
networks<BR>- Vehicular wireless networks<BR>- Access technologies<BR>- =
Third=20
and fourth generation systems<BR>- Energy-efficient protocols and power=20
management<BR>- Wireless security and authentication<BR>- Pricing and=20
billing<BR>- Modeling and Performance evaluation<BR><BR><BR>PAPER =
SUBMISSION AND=20
PUBLICATION</FONT></DIV>
<DIV><FONT =
color=3D#000000>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<BR><BR>Papers should=20
neither have been published elsewhere nor currently under review by =
another=20
conference or journal.&nbsp; Guidelines on paper submission and =
formatting will=20
be provided on the website.<BR>Accepted papers will appear in the =
symposium=20
proceedings published by IEEE.<BR><BR><BR>IMPORTANT=20
DATES<BR>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</FONT><BR></DIV>
<DIV><FONT color=3D#000000>Full papers=20
due:<X-TAB>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </X-TAB>November =
10,=20
2004</FONT></DIV>
<DIV><FONT color=3D#000000>Notification:<X-TAB>&nbsp;&nbsp;=20
</X-TAB><X-TAB>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</X-TAB>January<X-TAB>=20
</X-TAB>20, 2005</FONT></DIV>
<DIV><FONT color=3D#000000>Camera Ready=20
due:<X-TAB>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </X-TAB>February 15,=20
2005</FONT></DIV>
<DIV><BR></DIV>
<DIV><BR></DIV>
<DIV>ORGANIZING COMMITTEE</DIV>
<DIV>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</DIV>
<DIV><BR></DIV>
<DIV>GENERAL Co-Chairs:</DIV>
<DIV>&nbsp;<X-TAB>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </X-TAB>Giuseppe=20
Anastasi, University of Pisa, Italy</DIV>
<DIV>&nbsp;<X-TAB>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </X-TAB>Sajal K. =
Das, The=20
University of Texas at Arlington, USA</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>PROGRAM Co-Chairs:</DIV>
<DIV><X-TAB>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </X-TAB>Marco =
Conti,=20
IIT-CNR, Italy</DIV>
<DIV>&nbsp;<X-TAB>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </X-TAB>Dipankar=20
Raychaudhuri WINLAB/Rutgers University, USA</DIV>
<DIV><BR></DIV>
<DIV>&nbsp;</DIV>
<DIV>FINANCE &amp; REGISTRATION Chair:</DIV>
<DIV>&nbsp;<X-TAB>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </X-TAB>Yonghe =
Liu, The=20
University of Texas at Arlington, USA</DIV>
<DIV><BR></DIV>
<DIV><BR></DIV>
<DIV>PUBLICITY Co-Chairs:</DIV>
<DIV>&nbsp;<X-TAB>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </X-TAB>Mainak=20
Chatterjee, Univ. Central Florida, USA</DIV>
<DIV>&nbsp;<X-TAB>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </X-TAB>Sunghyun =
Choi,=20
Seoul National University, Korea</DIV>
<DIV>&nbsp;<X-TAB>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </X-TAB>Franca =
Delmastro,=20
IIT-CNR, Italy</DIV>
<DIV><BR></DIV>
<DIV>&nbsp;</DIV>
<DIV>LOCAL ARRANGEMENTS Chair:</DIV>
<DIV>&nbsp;<X-TAB>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </X-TAB><FONT=20
color=3D#000000>Antonio Puliafito, University of Messina, =
Italy</FONT></DIV>
<DIV><BR></DIV>
<DIV><BR></DIV>
<DIV>WEB DESIGNER &amp; MANAGER:</DIV>
<DIV>&nbsp;<X-TAB>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </X-TAB>Patrizia=20
Andronico, IIT-CNR, Italy</DIV>
<DIV><BR></DIV>
<DIV><BR></DIV>
<DIV>STEERING COMMITTEE</DIV>
<DIV>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</DIV>
<DIV><BR></DIV>
<DIV>Marco Conti, IIT-CNR, Italy</DIV>
<DIV>Sajal K. Das, The University of Texas at Arlington, USA =
(chair)</DIV>
<DIV>Dipankar Raychaudhuri WINLAB/Rutgers University, USA</DIV>
<DIV><FONT color=3D#000000>Satish K. Tripathi, SUNY Buffalo, =
USA</FONT></DIV>
<DIV><BR></DIV>
<DIV><BR></DIV>
<DIV><BR></DIV>
<DIV>PROGRAM COMMITTEE</DIV>
<DIV>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</DIV>
<DIV><BR></DIV>
<DIV><FONT color=3D#000000>Arup Acharya, IBM T.J. Watson Research, =
USA<BR>Dharma=20
P. Agrawal, University of Cincinnati, USA<BR>Kevin C. Almeroth, =
University of=20
California at Santa Barbara, USA<BR>Christian Becker, University of =
Stuttgart,=20
Germany<BR>Giuseppe Bianchi, University of Rome "Tor Vergata", =
Italy<BR>Chris=20
Blondia, University of Antwerp, Belgium<BR>Azzedine&nbsp; Boukerche, =
University=20
of Ottawa, Canada<BR>Jiannong Cao, Hong Kong Polytechnic University, =
Hong=20
Kong<BR>Chua Kee Chaing, National University of Singapore, Republic of=20
Singapore<BR>Rajarathnam Chandramouili, Stevens Institute of Technology, =

USA<BR>Mainak Chatterjee, University of Central Florida, =
USA<BR>Carla-Fabiana=20
Chiasserini, Polytechnic of Turin, Italy<BR>A. Chockalingam, Indian =
Institute of=20
Science, Banglore, India<BR>Sunghyun Choi, Seoul National University,=20
Korea<BR>Antonio Corradi, University of Bologna, Italy<BR>Antony =
Ephremides,=20
University of Maryland, USA<BR>Gabor Fodor, Ericsson, Sweden<BR>Luigi =
Fratta,=20
Polytechnic of Milan, Italy<BR>Marco Gruteser, Rutgers University, =
USA<BR>Paul=20
J.M. Havinga, University of Twente, The Netherlands<BR>Kazuo Imai, NTT =
DoCoMo,=20
Japan<BR>Victor Leung, The University of British Columbia, =
Canada<BR>Yonghe Liu,=20
Univ. Texas at Arlington, USA<BR>Holger Karl, Technische Universitaet =
Berlin,=20
Germany<BR>Anurag Kumar, Indian Inst of Science, Bangalore, =
India</FONT></DIV>
<DIV><FONT color=3D#000000>Mohan Kumar, The University of Texas at =
Arlington,=20
USA</FONT></DIV>
<DIV><FONT color=3D#000000>P. R. Kumar, University of Illinois, =
USA</FONT></DIV>
<DIV><FONT color=3D#000000>Masahiro Kuroda, National Institute of Info. =
and Com.=20
Tech., Japan<BR>Luciano Lenzini, University of Pisa, Italy<BR>K. Ben =
Letaief,=20
Hong Kong Univ. Science &amp; Technology, Hong Kong<BR>Giri Mandyam, =
Nokia=20
Research Center, USA<BR>Martin Mauve, University of Dusseldorf,=20
Germany<BR>Archan Misra, IBM T.J. Watson Research, USA<BR>Refik Molva, =
Institut=20
Eurecom, France<BR>Giacomo Morabito, University of Catania, =
Italy<BR>Hiroyuki=20
Morikawa, , University of Tokyo, Japan<BR>Stephan Olariu, Old Dominion=20
University, USA<BR>Maximilian Ott, Semandex Networks, USA<BR>Michael =
Paterakis,=20
Technical University of Crete, Greece<BR>George C. Polyzos, Athens =
University of=20
Economics and Business, Greece<BR>Antonio Puliafito, University of =
Messina,=20
Italy<BR>Jochen H. Schiller, Freie Universit=E4t Berlin, =
Germany<BR>Henning=20
Schulzrinne, Columbia University, USA<BR>Rajeev Shorey, IBM India =
Research Lab,=20
India<BR>Ivan Stojmenovic, University of Ottawa, Canada<BR>Violet R. =
Syrotiuk,=20
Arizona State University, USA<BR>Wade Trappe, Rutgers University, =
USA<BR>Ooi Wei=20
Tsang, National University of Singapore, Singapore<BR>Christian =
Tschudin, Basel=20
University, Switzerland<BR>Thierry Turletti, INRIA France<BR>Andras =
Valko,=20
Ericsson, Hungary<BR>Bernard Walke, Aachen University of Technology,=20
Germany<BR>Xingwei Wang, Northeastern Univ, China<BR>Jie Wu, Florida =
Atlantic=20
University, USA</FONT></DIV>
<DIV><FONT color=3D#000000>Gergely Zaruba, The University of Texas at =
Arlington,=20
USA</FONT></DIV>
<DIV><FONT color=3D#000000>Roger Zimmerman, University of Southern =
California,=20
USA</FONT></DIV>
<DIV><BR></DIV></DIV>
<DIV><FONT color=3D#0000ff=20
size=3D2>************************************************************<BR>=
Franca=20
Delmastro<BR>Pervasive Computing &amp; Networking Lab. =
(PerLab)</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT color=3D#0000ff size=3D2>IIT- National Research =
Council<BR>via G.=20
Moruzzi,1<BR>56124 Pisa, Italy<BR>phone: +39 050 3152407=20
(direct)<BR>********************************************************</FON=
T></DIV></BODY></HTML>

------=_NextPart_000_000F_01C4A21D.237D9300--



--===============1044104558==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6

--===============1044104558==--




From mip6-bounces@ietf.org  Thu Sep 30 16:25:27 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28565
	for <mip6-web-archive@ietf.org>; Thu, 30 Sep 2004 16:25:26 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CD7cq-0002PZ-V4
	for mip6-web-archive@ietf.org; Thu, 30 Sep 2004 16:34:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CD7Gh-0007gb-Qn; Thu, 30 Sep 2004 16:11:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CBwmW-0001I6-3A; Mon, 27 Sep 2004 10:47:12 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04652;
	Mon, 27 Sep 2004 10:47:09 -0400 (EDT)
Received: from lennier.cc.vt.edu ([198.82.162.213])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CBwu9-0007MF-Hx; Mon, 27 Sep 2004 10:55:06 -0400
Received: from zidane.cc.vt.edu (IDENT:mirapoint@evil-zidane [10.1.1.13])
	by lennier.cc.vt.edu (8.12.8/8.12.8) with ESMTP id i8REjfhO244517;
	Mon, 27 Sep 2004 10:45:41 -0400 (EDT)
Received: from TomXP.vt.edu (thoupc2.ece.vt.edu [128.173.52.68])
	by zidane.cc.vt.edu (MOS 3.4.8-GR) with ESMTP id BQO38586;
	Mon, 27 Sep 2004 10:45:30 -0400 (EDT)
Message-Id: <6.0.1.1.2.20040927104038.01dc2fc8@pop.vt.edu>
X-Sender: hou@pop.vt.edu (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Mon, 27 Sep 2004 10:46:38 -0400
To: Thomas Hou <thou@vt.edu>
From: Thomas Hou <thou@vt.edu>
Mime-Version: 1.0
X-Junkmail-Status: score=12/50, host=zidane.cc.vt.edu
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 3fbd9b434023f8abfcb1532abaec7a21
X-Mailman-Approved-At: Thu, 30 Sep 2004 16:11:08 -0400
Subject: [Mip6] Call for Participation QShine 2004
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0924064335=="
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 33cc095b503da4365ce57c727e553cf1

--===============0924064335==
Content-Type: multipart/alternative;
	boundary="=====================_-110058718==.ALT"

--=====================_-110058718==.ALT
Content-Type: text/plain; charset="us-ascii"; format=flowed


-----------------------------------------------------------------------------
                     Call for Participation QShine 2004
-----------------------------------------------------------------------------
First International Conference on Quality of Service in
Heterogeneous Wired/Wireless Networks
October 18-20, 2004 Dallas, Texas, USA
Wyndham Hotel, Dallas
-----------------------------------------------------------------------------
http://www.qshine.org/
-----------------------------------------------------------------------------

Recent technological developments in broadband high-speed networks, 
peer-to-peer
networks, wireless and mobile networks, and grid computing have led to newer
challenging problems, such as providing QoS support to the emerging high-speed
Internet and multimedia applications across both wired and wireless networks.

Held in the Dallas, TX, home of the Telecomm Corridor, this conference focuses
on all aspects of QoS support for heterogeneous wired and wireless networks.
It serves as a forum for researchers from both academia and industry for
presenting recent research results in QoS issues for both wired and wireless
networks. The conference features prominent invited speakers as well as papers
by top researchers in the field. Please join us in Dallas for QShine 2004!

This year, QShine include

    - 2 prominent Keynote Speakers:
       * Dr. Sanjoy Paul  Director of Wireless Networking Research
         Bell Laboratories
       * Prof Sajal K. Das, Director, Center for Research in Wireless Mobility
         and Networking (CReWMaN), The University of Texas at Arlington
    - 10 Technical sessions which include:
       * Admission Control and Resource Allocation
       * Ad-hoc and sensor networks
       * QoS and Multimedia Support
       * QoS Routing
       * Wired-Wireless Networks and Hybrid Networks
       * Voice and Multi-Media Protocols
       * Reliability and Resource Management
       * Advanced Routing Techniques

    - 3 Panel sessions:
       * Can WiFi hotspots survive without QoS ?
       * QoS in the Internet: How strong is the need ?
       * QoS for sensor networks: is it an overkill?

    - A Poster Session with works in progress

Please consult www.qshine.org for further details regarding the Technical
Program, Hotel, and Registration.

Organizing Committee:

  General Chair:  Azzedine Boukerche, University of Ottawa, Canada
  Vice Chair:    Michael Fang, University of Florida, USA

  Technical Program Co-Chairs
                  Jorge Cobb, University of Texas at Dallas, USA
                  Shigang Chen, University of Florida, USA

  Steering Committee Chair:
                  Imrich Chlamtac, University of Texas at Dallas, USA



--=====================_-110058718==.ALT
Content-Type: text/html; charset="us-ascii"

<html>
<body>
<font size=3><br>
-----------------------------------------------------------------------------<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Call for Participation QShine 2004<br>
-----------------------------------------------------------------------------<br>
First International Conference on Quality of Service in<br>
Heterogeneous Wired/Wireless Networks<br>
October 18-20, 2004 Dallas, Texas, USA<br>
Wyndham Hotel, Dallas<br>
-----------------------------------------------------------------------------<br>
<a href="http://www.qshine.org/" eudora="autourl">http://www.qshine.org/<br>
</a>-----------------------------------------------------------------------------<br><br>
Recent technological developments in broadband high-speed networks,
peer-to-peer<br>
networks, wireless and mobile networks, and grid computing have led to
newer <br>
challenging problems, such as providing QoS support to the emerging
high-speed <br>
Internet and multimedia applications across both wired and wireless
networks.<br><br>
Held in the Dallas, TX, home of the Telecomm Corridor, this conference
focuses<br>
on all aspects of QoS support for heterogeneous wired and wireless
networks. <br>
It serves as a forum for researchers from both academia and industry for
<br>
presenting recent research results in QoS issues for both wired and
wireless<br>
networks. The conference features prominent invited speakers as well as
papers <br>
by top researchers in the field. Please join us in Dallas for QShine
2004!<br><br>
This year, QShine include<br><br>
&nbsp;&nbsp; - 2 prominent Keynote Speakers: <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Dr. Sanjoy Paul&nbsp; Director of
Wireless Networking Research<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Bell Laboratories<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Prof Sajal K. Das, Director, Center for
Research in Wireless Mobility <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and Networking (CReWMaN), The
University of Texas at Arlington<br>
&nbsp;&nbsp; - 10 Technical sessions which include:<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Admission Control and Resource
Allocation<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Ad-hoc and sensor networks<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * QoS and Multimedia Support<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * QoS Routing<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Wired-Wireless Networks and Hybrid
Networks<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Voice and Multi-Media Protocols<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Reliability and Resource 
Management<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Advanced Routing Techniques<br><br>
&nbsp;&nbsp; - 3 Panel sessions:<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Can WiFi hotspots survive without QoS
?<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * QoS in the Internet: How strong is the
need ?<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * QoS for sensor networks: is it an
overkill?<br><br>
&nbsp;&nbsp; - A Poster Session with works in progress<br><br>
Please consult
<a href="http://www.qshine.org/" eudora="autourl">www.qshine.org</a> for
further details regarding the Technical <br>
Program, Hotel, and Registration.<br><br>
Organizing Committee:<br><br>
&nbsp;General Chair:&nbsp; Azzedine Boukerche, University of Ottawa,
Canada<br>
&nbsp;Vice Chair: <x-tab>&nbsp;&nbsp;&nbsp;</x-tab>Michael Fang,
University of Florida, USA<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>&nbsp;&nbsp;
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><br>
&nbsp;Technical Program Co-Chairs <x-tab>&nbsp;&nbsp;&nbsp;</x-tab><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Jorge Cobb, University of Texas at Dallas, USA<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Shigang Chen, University of Florida, USA<br><br>
&nbsp;Steering Committee Chair:<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Imrich Chlamtac, University of Texas at Dallas, USA<br><br>
</font></body>
<br>
</html>

--=====================_-110058718==.ALT--



--===============0924064335==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6

--===============0924064335==--




