From mip6-bounces@ietf.org Mon Aug 01 09:16:40 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dza9o-0006NS-CT; Mon, 01 Aug 2005 09:16:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Dza9m-0006LF-6w
	for mip6@megatron.ietf.org; Mon, 01 Aug 2005 09:16:38 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07896
	for <mip6@ietf.org>; Mon, 1 Aug 2005 09:16:34 -0400 (EDT)
Received: from bundit.graduate.kmitl.ac.th ([161.246.39.3])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Dzafx-0000AR-Rn
	for mip6@ietf.org; Mon, 01 Aug 2005 09:50:00 -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
	j71DFWX7009413; Mon, 1 Aug 2005 20:15:32 +0700
Message-ID: <42EE2089.4050805@graduate.kmitl.ac.th>
Date: Mon, 01 Aug 2005 20:15:53 +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, mipl@mobile-ipv6.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: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Content-Transfer-Encoding: 7bit
Cc: 
Subject: [Mip6] How long Mobile IPv6 has to wait for NA?
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


    When MN sends NS to perform DAD process, how long MN has to wait for 
NA, in case there is no any multicast node send NA to MN?  50 msec, 100 
msec, 1 sec ???  Does the RFC or interdraft define this time?

Regards,  

-- 
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 Aug 01 09:40:56 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DzaXI-0002Tk-PR; Mon, 01 Aug 2005 09:40:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DzaXG-0002RK-90; Mon, 01 Aug 2005 09:40:54 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA08900;
	Mon, 1 Aug 2005 09:40:52 -0400 (EDT)
Received: from motgate5.mot.com ([144.189.100.105])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Dzb3X-000166-11; Mon, 01 Aug 2005 10:14:16 -0400
Received: from az33exr03.mot.com (az33exr03.mot.com [10.64.251.233])
	by motgate5.mot.com (8.12.11/Motgate5) with ESMTP id j71DlJqh018513;
	Mon, 1 Aug 2005 06:47:19 -0700 (MST)
Received: from [10.182.10.14] (mvp-10-182-10-14.am.mot.com [10.182.10.14])
	by az33exr03.mot.com (8.13.1/8.13.0) with ESMTP id j71DkVQx007808;
	Mon, 1 Aug 2005 08:46:32 -0500 (CDT)
Message-ID: <42EE265A.1040202@motorola.com>
Date: Mon, 01 Aug 2005 15:40:42 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: "Bound, Jim" <Jim.Bound@hp.com>
References: <936A4045C332714F975800409DE09240B31546@tayexc14.americas.cpqcorp.net>
In-Reply-To: <936A4045C332714F975800409DE09240B31546@tayexc14.americas.cpqcorp.net>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Content-Transfer-Encoding: 7bit
Cc: nemo@ietf.org, mip6@ietf.org
Subject: [Mip6] Re: [nemo] v4 traversal slides
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

Bound, Jim wrote:

> Folks,
> 
> I think we need to at least address and discuss the scenario where 
> the HA is on IPv6-Dominant network, meaning IPv4 routing has been 
> shut off per policy of the user on that network.  The MN shows up on 
> IPv4-Only access network.  Bi-directional commo is required between 
> MN and HA, but MN has entered IPv4 net.  We need to consider this in 
> our scenarios.  I have communicated this to some and talking with 
> Pascal T.  This is a real scenario that is being planned today by 
> several large enterpises.

The above scenario (IPv6 MN on an IPv4 network, its HA on an IPv6-only
network) is very relevant.  A traversal protocol where an intermediary
box ("gateway"?) is on both v4 and v6 is necessary.

Alex


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



From mip6-bounces@ietf.org Mon Aug 01 11:55:07 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dzcd9-0002jP-9J; Mon, 01 Aug 2005 11:55:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Dzcd7-0002j5-8j
	for mip6@megatron.ietf.org; Mon, 01 Aug 2005 11:55:05 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20015
	for <mip6@ietf.org>; Mon, 1 Aug 2005 11:55:02 -0400 (EDT)
Received: from mx2.buaa.edu.cn ([219.239.227.26])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Dzd9M-0007t4-Op
	for mip6@ietf.org; Mon, 01 Aug 2005 12:28:28 -0400
Received: from mx1.buaa.edu.cn (unknown [192.168.128.6])
	by mx2.buaa.edu.cn (Postfix) with ESMTP id 469AF37F67
	for <mip6@ietf.org>; Mon,  1 Aug 2005 23:54:13 +0800 (CST)
Received: from [86.255.25.39] by 10.0.0.131 with StormMail ESMTP id
	41176.3049321411; Tue, 2 Aug 2005 00:32:04 +0800 (CST)
Message-ID: <42EE45AC.40907@cse.buaa.edu.cn>
Date: Mon, 01 Aug 2005 17:54:20 +0200
From: Lynch <liqin@cse.buaa.edu.cn>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Warodom Werapun <ple@graduate.kmitl.ac.th>
Subject: Re: [Mip6] How long Mobile IPv6 has to wait for NA?
References: <42EE2089.4050805@graduate.kmitl.ac.th>
In-Reply-To: <42EE2089.4050805@graduate.kmitl.ac.th>
Content-Type: text/plain; charset=TIS-620; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Content-Transfer-Encoding: 7bit
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

Warodom Werapun wrote:

>
>    When MN sends NS to perform DAD process, how long MN has to wait 
> for NA, in case there is no any multicast node send NA to MN?  50 
> msec, 100 msec, 1 sec ???  Does the RFC or interdraft define this time?
>
> Regards, 

try RFC2462,  http://www.ietf.org/rfc/rfc2462.txt
and I think it's 1s


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



From mip6-bounces@ietf.org Tue Aug 02 05:35:29 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DztBJ-0003dn-97; Tue, 02 Aug 2005 05:35:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DztBF-0003dG-Un; Tue, 02 Aug 2005 05:35:26 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02647;
	Tue, 2 Aug 2005 05:35:23 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Dzthh-00051G-4H; Tue, 02 Aug 2005 06:08:58 -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 j729YuJ22074; Tue, 2 Aug 2005 11:34: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.13.1/8.13.1) with ESMTP id
	j729Yu6F011152; Tue, 2 Aug 2005 11:34:56 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200508020934.j729Yu6F011152@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: mipshop@ietf.org
Date: Tue, 02 Aug 2005 11:34:56 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: mip6@ietf.org
Subject: [Mip6] larger options
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

I've just create a 4096 bit RSA key and encode the public part in DER.
The size is 550, draft-arkko-mipshop-cga-cba-01.txt puts CGA parameters
which includes a public key in a MIPv6 option with a maximal length of
255 octets, cf RFC 3775 section 6.2.1 page 47:
   Option Length

      8-bit unsigned integer, representing the length in octets of the
      mobility option, not including the Option Type and Option Length
      fields.

This problem is generic, I believe at least half of the mipshop I-D
use oversized option. How and where to fix this?

Regards

Francis.Dupont@enst-bretagne.fr

PS: a way to fix it: mark size 255 as oversized option: the real length is
in the two next octets.
Another way: use the first bit (length > 127) as oversized option:
length field is extended to two octets and the real length is taken from
them with the first bit masked...
PPS: don't forget to defined what is included in the length (I'd like
to get extended length not included).
PPPS: where is mipshop or mip6 WG. I am strongly in favor of a fast track
document. If I remember well I have a short slot at the end of mip6 WG
session this afternoon... mip6 W chairs?

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



From mip6-bounces@ietf.org Tue Aug 02 06:33:17 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dzu5E-0008EP-VA; Tue, 02 Aug 2005 06:33:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Dzu5D-0008DY-C6
	for mip6@megatron.ietf.org; Tue, 02 Aug 2005 06:33:15 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06812
	for <mip6@ietf.org>; Tue, 2 Aug 2005 06:33:11 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Dzube-0007z4-Iv
	for mip6@ietf.org; Tue, 02 Aug 2005 07:06:48 -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 j72AWoJ25582; Tue, 2 Aug 2005 12:32:50 +0200
Received: from givry.rennes.enst-bretagne.fr
	(localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id
	j72AWogx011438; Tue, 2 Aug 2005 12:32:50 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200508021032.j72AWogx011438@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: mip6@ietf.org
Date: Tue, 02 Aug 2005 12:32:50 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: 
Subject: [Mip6] comments on draft-ietf-mip6-ikev2-ipsec-02.txt
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

The last two requirements of section 4.2 are confusing because they
are not required by this I-D but by RFC 3775. I propose to add
the references.

I am still strongly against the first 4.3 requirements. In fact today
many security gateways don't support protocol (so ports) in traffic selectors
(because this solves the issue of fragment handling, cf the OPAQUE stuff
in 2401bis). I.e., fine gain selectors are fine but should be made
mandatory, so please downgrade to a SHOULD.

... (to be continued)

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Tue Aug 02 08:47:57 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DzwBW-0007Mz-J2; Tue, 02 Aug 2005 08:47:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DzwBT-0007GZ-Tu
	for mip6@megatron.ietf.org; Tue, 02 Aug 2005 08:47:51 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16178
	for <mip6@ietf.org>; Tue, 2 Aug 2005 08:47:49 -0400 (EDT)
Received: from coliposte.enst-bretagne.fr ([192.108.115.12])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Dzwhx-00066T-Gt
	for mip6@ietf.org; Tue, 02 Aug 2005 09:21:26 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by coliposte.enst-bretagne.fr (8.12.10/8.12.10/2004.10.03) with ESMTP
	id j72ClVhs030844; Tue, 2 Aug 2005 14:47:31 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by coliposte.enst-bretagne.fr (8.12.10/8.12.10/2004.09.01) with ESMTP
	id j72ClHZH030809; Tue, 2 Aug 2005 14:47:17 +0200
Received: from givry.rennes.enst-bretagne.fr
	(localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id
	j72ClINf011771; Tue, 2 Aug 2005 14:47:18 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200508021247.j72ClINf011771@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: mip6@ietf.org
Subject: [Mip6] comments on draft-ietf-mip6-ikev2-ipsec-02.txt
Date: Tue, 02 Aug 2005 14:47:18 +0200
X-Virus-Scanned: amavisd-new at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Cc: 
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

4.3 API already exists, cf draft-sugimoto-mip6-pfkey-migrate-00.txt

5.1 & others: please, PLEASE, use the abstract syntax of SPD/SAD!
I consider these sections as not readable until this is done...

6.2: I don't understand why IDi is mandatory: it is not optional at all
in IKEv2 specs. Proposal: remove the MUST, i.e., change the requirement
in a fact!
 BTW, when the home address is used the check against the peer address
(which is the care-of address) has to be disabled. This is discussed
in a pki4ipsec document, I propose to reference it in order to explain
how to deal with the fact the peer address is not the commonly expected one.
 The text about the CREATE_CHILD_SA for RR protection is not clear enough:
there is always one initiator. Usually it is the MN but it can be the HA
when a CN which is mobile begins an RR. This must be explained in order
to avoid "passive" configurations on HAs (note this should only break RR
from outside, so this is not a critical misconfig).
 Last paragraph is ambiguous because it applies only when the whole stuff
is restarted... As in IKEv2 SAs are managed, i.e., IPsec SAs are deleted
when the IKE_SA goes down, I don't believe it is a real case. Perhaps
it applies to previous context and in this case the paragraph should be moved?

6.3: an important detail is forbidden: SPD entries have to be updated
when an endpoint/peer address is changed. In fact, this is even more
critical than to update the SAD entries!

7: we should check but I believe the CERT from the responder/HA is not
optional with EAP authentication, i.e., preshared secret is an alternative
to the standard certificate-based mutual authentication, EAP is an option
of the second. Further text in the I-D seems to say the same thing...
Perhaps we have to choose between IKEv2 ([4]) and EAP/IKEv2 I-D ([8])?
BTW I don't know if there is a real consensus about the second, and
if it could be heavily changed.

[14]: the -01 was published (after this I-D :-)

Regards

Francis.Dupont@enst-bretagne.fr

PS: the beginning of the message for people who lost it:
The last two requirements of section 4.2 are confusing because they
are not required by this I-D but by RFC 3775. I propose to add
the references.

I am still strongly against the first 4.3 requirements. In fact today
many security gateways don't support protocol (so ports) in traffic selectors
(because this solves the issue of fragment handling, cf the OPAQUE stuff
in 2401bis). I.e., fine gain selectors are fine but should be made
mandatory, so please downgrade to a SHOULD.

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



From mip6-bounces@ietf.org Tue Aug 02 08:51:34 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DzwF4-0002N0-9w; Tue, 02 Aug 2005 08:51:34 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DzwF0-0002J6-Ew
	for mip6@megatron.ietf.org; Tue, 02 Aug 2005 08:51:30 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16305
	for <mip6@ietf.org>; Tue, 2 Aug 2005 08:51:28 -0400 (EDT)
Received: from wproxy.gmail.com ([64.233.184.200])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DzwlT-0006GG-LC
	for mip6@ietf.org; Tue, 02 Aug 2005 09:25:04 -0400
Received: by wproxy.gmail.com with SMTP id 37so384403wra
	for <mip6@ietf.org>; Tue, 02 Aug 2005 05:51:18 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=gVWklS5FSENyDgANur/kJdXt5ZBhMLRN9kAnQSqMg29kQly5caAGsvCOG+SeKwnGcIJrxOfxWU9pvmgxuyfijRYaahfaumVNB0cMEvffMc8dZ4ebZwxsovzde3ee2QQwRdSxyHwQb4jbTegIJfzOmK2pWSXKdikjLHUF0mMYDPg=
Received: by 10.54.129.7 with SMTP id b7mr3743623wrd;
	Tue, 02 Aug 2005 05:51:18 -0700 (PDT)
Received: by 10.54.104.14 with HTTP; Tue, 2 Aug 2005 05:51:18 -0700 (PDT)
Message-ID: <f1f4dcdc05080205512265efbe@mail.gmail.com>
Date: Tue, 2 Aug 2005 07:51:18 -0500
From: Vijay Devarapallli <dvijay@gmail.com>
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>, mip6@ietf.org
In-Reply-To: <42EE265A.1040202@motorola.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <936A4045C332714F975800409DE09240B31546@tayexc14.americas.cpqcorp.net>
	<42EE265A.1040202@motorola.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Content-Transfer-Encoding: quoted-printable
Cc: 
Subject: [Mip6] Re: [nemo] v4 traversal slides
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Vijay Devarapallli <dvijay@gmail.com>
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

hi Jim and Alex,=20

this scenario was discussed extensively in the design team. this=20
is a regular IPv6 transition scenario, where an IPv6 node needs to
reach an IPv6 network with a transition gateway sitting somewhere=20
between the v4 and the v6 cloud. regular IPv6 transition=20
mechanisms apply. I feel there is nothing mip6 or nemo specific=20
we can do for this scenario.=20

Vijay

On 8/1/05, Alexandru Petrescu <alexandru.petrescu@motorola.com> wrote:
> Bound, Jim wrote:
>=20
> > Folks,
> >
> > I think we need to at least address and discuss the scenario where
> > the HA is on IPv6-Dominant network, meaning IPv4 routing has been
> > shut off per policy of the user on that network.  The MN shows up on
> > IPv4-Only access network.  Bi-directional commo is required between
> > MN and HA, but MN has entered IPv4 net.  We need to consider this in
> > our scenarios.  I have communicated this to some and talking with
> > Pascal T.  This is a real scenario that is being planned today by
> > several large enterpises.
>=20
> The above scenario (IPv6 MN on an IPv4 network, its HA on an IPv6-only
> network) is very relevant.  A traversal protocol where an intermediary
> box ("gateway"?) is on both v4 and v6 is necessary.
>=20
> Alex
>=20
>=20
>

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



From mip6-bounces@ietf.org Tue Aug 02 09:11:16 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DzwY8-0007FC-LF; Tue, 02 Aug 2005 09:11:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DzwY6-0007EV-Ml
	for mip6@megatron.ietf.org; Tue, 02 Aug 2005 09:11:14 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17539
	for <mip6@ietf.org>; Tue, 2 Aug 2005 09:11:12 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Dzx4a-0007AJ-39
	for mip6@ietf.org; Tue, 02 Aug 2005 09:44:49 -0400
Received: from az33exr03.mot.com ([10.64.251.233])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id j72DKhqp010432;
	Tue, 2 Aug 2005 06:20:43 -0700 (MST)
Received: from [10.182.10.24] (mvp-10-182-10-24.am.mot.com [10.182.10.24])
	by az33exr03.mot.com (8.13.1/8.13.0) with ESMTP id j72DGokE016052;
	Tue, 2 Aug 2005 08:16:51 -0500 (CDT)
Message-ID: <42EF70E1.1080108@motorola.com>
Date: Tue, 02 Aug 2005 15:10:57 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: Vijay Devarapallli <dvijay@gmail.com>
References: <936A4045C332714F975800409DE09240B31546@tayexc14.americas.cpqcorp.net>	
	<42EE265A.1040202@motorola.com>
	<f1f4dcdc05080205512265efbe@mail.gmail.com>
In-Reply-To: <f1f4dcdc05080205512265efbe@mail.gmail.com>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org, Alexandru Petrescu <alexandru.petrescu@motorola.com>
Subject: [Mip6] Re: [nemo] v4 traversal slides
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

Vijay Devarapallli wrote:

> hi Jim and Alex, 
> 
> this scenario was discussed extensively in the design team. this 
> is a regular IPv6 transition scenario, where an IPv6 node needs to
> reach an IPv6 network with a transition gateway sitting somewhere 
> between the v4 and the v6 cloud. regular IPv6 transition 
> mechanisms apply. I feel there is nothing mip6 or nemo specific 
> we can do for this scenario.

Vijay, do you discuss _scenarios_ in the DT?

Otherwise, yes - regular IPv6 transition applies in the case where HA is
 on a v6-exclusively network.  What this should mean to mip6trans IMHO
is that it shouldn't work exclusively with a HA that is connected on
both v4 and v6, and that it should also work with a HA that lives on v6
exclusively.  Or so I think IMHO.

Alex


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



From mip6-bounces@ietf.org Tue Aug 02 09:32:04 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DzwsG-0006Au-CW; Tue, 02 Aug 2005 09:32:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DzwsE-0006Ap-CR
	for mip6@megatron.ietf.org; Tue, 02 Aug 2005 09:32:02 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18899
	for <mip6@ietf.org>; Tue, 2 Aug 2005 09:32:00 -0400 (EDT)
Received: from tayrelbas01.tay.hp.com ([161.114.80.244])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DzxOh-000889-J9
	for mip6@ietf.org; Tue, 02 Aug 2005 10:05:36 -0400
Received: from tayexg11.americas.cpqcorp.net (tayexg11.americas.cpqcorp.net
	[16.103.130.186])
	by tayrelbas01.tay.hp.com (Postfix) with ESMTP id 07C47142;
	Tue,  2 Aug 2005 09:26:28 -0400 (EDT)
Received: from tayexc14.americas.cpqcorp.net ([16.103.130.45]) by
	tayexg11.americas.cpqcorp.net with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 2 Aug 2005 09:31:52 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] Re: [nemo] v4 traversal slides
Date: Tue, 2 Aug 2005 09:31:50 -0400
Message-ID: <936A4045C332714F975800409DE09240B319E7@tayexc14.americas.cpqcorp.net>
Thread-Topic: [Mip6] Re: [nemo] v4 traversal slides
Thread-Index: AcWXZWv1fKjm9nBsTOquOxOaRgLBzQAAQfEA
From: "Bound, Jim" <Jim.Bound@hp.com>
To: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>,
	"Vijay Devarapallli" <dvijay@gmail.com>
X-OriginalArrivalTime: 02 Aug 2005 13:31:52.0010 (UTC)
	FILETIME=[8ABE1AA0:01C59766]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
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

I agree with Alex.  If you are to solve other mipv6trans issues and make
WG statements then you need to work on this issue too.

thanks
/jim=20

> -----Original Message-----
> From: mip6-bounces@ietf.org [mailto:mip6-bounces@ietf.org] On=20
> Behalf Of Alexandru Petrescu
> Sent: Tuesday, August 02, 2005 9:11 AM
> To: Vijay Devarapallli
> Cc: mip6@ietf.org; Alexandru Petrescu
> Subject: [Mip6] Re: [nemo] v4 traversal slides
>=20
> Vijay Devarapallli wrote:
>=20
> > hi Jim and Alex,=20
> >=20
> > this scenario was discussed extensively in the design team. this=20
> > is a regular IPv6 transition scenario, where an IPv6 node needs to
> > reach an IPv6 network with a transition gateway sitting somewhere=20
> > between the v4 and the v6 cloud. regular IPv6 transition=20
> > mechanisms apply. I feel there is nothing mip6 or nemo specific=20
> > we can do for this scenario.
>=20
> Vijay, do you discuss _scenarios_ in the DT?
>=20
> Otherwise, yes - regular IPv6 transition applies in the case=20
> where HA is
>  on a v6-exclusively network.  What this should mean to mip6trans IMHO
> is that it shouldn't work exclusively with a HA that is connected on
> both v4 and v6, and that it should also work with a HA that=20
> lives on v6
> exclusively.  Or so I think IMHO.
>=20
> Alex
>=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 Tue Aug 02 11:24:31 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dzyd5-0002ue-AZ; Tue, 02 Aug 2005 11:24:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dzyd3-0002tZ-ME; Tue, 02 Aug 2005 11:24:29 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28481;
	Tue, 2 Aug 2005 11:24:27 -0400 (EDT)
Received: from alpha9.its.monash.edu.au ([130.194.1.9])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Dzz9X-0005JF-OD; Tue, 02 Aug 2005 11:58:05 -0400
Received: from larry.its.monash.edu.au ([130.194.13.82])
	by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31112)
	with ESMTP id <01LRDGMDBUFE9APV3W@vaxh.its.monash.edu.au>; Wed,
	03 Aug 2005 01:24:13 +1000
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id C789E8000D; Wed,
	03 Aug 2005 01:24:12 +1000 (EST)
Received: from [172.19.242.30]
	(vpn-student-242-30.its.monash.edu.au [172.19.242.30])
	by larry.its.monash.edu.au (Postfix) with ESMTP id 3987C3C013; Wed,
	03 Aug 2005 01:24:10 +1000 (EST)
Date: Wed, 03 Aug 2005 01:24:07 +1000
From: Greg Daley <greg.daley@eng.monash.edu.au>
Subject: Re: [Mip6] larger options
In-reply-to: <200508020934.j729Yu6F011152@givry.rennes.enst-bretagne.fr>
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
Message-id: <42EF9017.8080400@eng.monash.edu.au>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
References: <200508020934.j729Yu6F011152@givry.rennes.enst-bretagne.fr>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Content-Transfer-Encoding: 7BIT
Cc: mip6@ietf.org, mipshop@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

Francis Dupont wrote:
> I've just create a 4096 bit RSA key and encode the public part in DER.
> The size is 550, draft-arkko-mipshop-cga-cba-01.txt puts CGA parameters
> which includes a public key in a MIPv6 option with a maximal length of
> 255 octets, cf RFC 3775 section 6.2.1 page 47:
>    Option Length
> 
>       8-bit unsigned integer, representing the length in octets of the
>       mobility option, not including the Option Type and Option Length
>       fields.
> 
> This problem is generic, I believe at least half of the mipshop I-D
> use oversized option. How and where to fix this?

MIP6 sounds like a good place.

How about the length in the IPv6 header describes the length of the
entire packet including extended options.  Mobility header
length value describes the length of the mobility header with
the original option sizes and format.  This aggregated length defined
in the MH may be smaller than the total packet size (even counting
preceding headers).

An identifier would have to be carried in the mobility header indicating
that following the exlicit length in the MH are "extended" mobility
options.

For example the next header=[MH|None], length =residual length of the
message.

The second MH could only have Extended length options (except pad?)

I'm not sure if overloading the MH protocol number is too evil.  In that
case, there would have to be an allocation of a new protocol number, and
an admission of the problem to IANA...

Does this sound like a good or a bad idea?


Greg



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



From mip6-bounces@ietf.org Tue Aug 02 11:30:06 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DzyiU-0007M6-Lf; Tue, 02 Aug 2005 11:30:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DzyiT-0007Ly-B5
	for mip6@megatron.ietf.org; Tue, 02 Aug 2005 11:30:05 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29038
	for <mip6@ietf.org>; Tue, 2 Aug 2005 11:30:02 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DzzEx-0005a6-O3
	for mip6@ietf.org; Tue, 02 Aug 2005 12:03:41 -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 j72FTgD15608
	for <mip6@ietf.org>; Tue, 2 Aug 2005 17:29:42 +0200
Received: from givry.rennes.enst-bretagne.fr
	(localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id
	j72FTgl1012434
	for <mip6@ietf.org>; Tue, 2 Aug 2005 17:29:42 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200508021529.j72FTgl1012434@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: mip6@ietf.org
Date: Tue, 02 Aug 2005 17:29:42 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Subject: [Mip6] about draft-ietf-mip6-bootstrapping-split-00.txt 
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

I have two concerns:
 the configuration service in IKEv2 was copied from DHCP,
 in fact, you should consider it as a lightweight DHCP service.
 - so in 5.3.2 you cannot use it to validate a HoA configured by
   the MN. BTW in the past I tried to add a validation/registration
   service for stateless autoconfed addresses in DHCPv6, it was
   rejected by the DHC WG.
 - at the contrary this service is the right one for DNS update
   (in the reverse tree: as usual the MN should update the AAAA RR
    because it has the trust over its FQDN, and the guy who allocates
    the address should update the PTR because it has the trust over
    this part of the reverse tree. PS: confirmed as the session).

BTW the DNS HA address discovery is so better than DHAAD that I believe
it is time for a DHAAD considered harmful I-D (co-authors?) !

regards

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Tue Aug 02 11:46:26 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DzyyI-0003IE-7Q; Tue, 02 Aug 2005 11:46:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DzyyG-0003HM-3V
	for mip6@megatron.ietf.org; Tue, 02 Aug 2005 11:46:24 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00155
	for <mip6@ietf.org>; Tue, 2 Aug 2005 11:46:21 -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.43) id 1DzzUl-0006O9-II
	for mip6@ietf.org; Tue, 02 Aug 2005 12:20:00 -0400
Message-ID: <0ac401c59779$5230bd10$596015ac@dcml.docomolabsusa.com>
From: "James Kempf" <Kempf@docomolabs-usa.com>
To: "Francis Dupont" <Francis.Dupont@enst-bretagne.fr>, <mip6@ietf.org>
References: <200508021529.j72FTgl1012434@givry.rennes.enst-bretagne.fr>
Subject: Re: [Mip6] about draft-ietf-mip6-bootstrapping-split-00.txt 
Date: Tue, 2 Aug 2005 08:46:16 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Content-Transfer-Encoding: 7bit
Cc: 
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

Francis,

> I have two concerns:
>  the configuration service in IKEv2 was copied from DHCP,
>  in fact, you should consider it as a lightweight DHCP service.
>  - so in 5.3.2 you cannot use it to validate a HoA configured by
>    the MN. BTW in the past I tried to add a validation/registration
>    service for stateless autoconfed addresses in DHCPv6, it was
>    rejected by the DHC WG.

We had some discussion with IKE folks on this and they recommended that we
introduce a new configuration option for autoconfiguration, which we did.

So would your objection be handled if we remove the text that says that the
IINTERNAL_IPV6_ADDRESS can also be used to confirm an autoconfigured
address?

            jak



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



From mip6-bounces@ietf.org Tue Aug 02 12:34:34 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dzzis-0007Do-JE; Tue, 02 Aug 2005 12:34:34 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dzziq-0007D0-JC; Tue, 02 Aug 2005 12:34:32 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03724;
	Tue, 2 Aug 2005 12:34:29 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1E00FK-0000Ku-I0; Tue, 02 Aug 2005 13:08:08 -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 j72GY9D19505; Tue, 2 Aug 2005 18:34:09 +0200
Received: from givry.rennes.enst-bretagne.fr
	(localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id
	j72GYAOc012693; Tue, 2 Aug 2005 18:34:10 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200508021634.j72GYAOc012693@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Greg Daley <greg.daley@eng.monash.edu.au>
Subject: Re: [Mip6] larger options 
In-reply-to: Your message of Wed, 03 Aug 2005 01:24:07 +1000.
	<42EF9017.8080400@eng.monash.edu.au> 
Date: Tue, 02 Aug 2005 18:34:10 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: mip6@ietf.org, mipshop@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

 In your previous mail you wrote:

   MIP6 sounds like a good place.
   
=> I agree but the answer of mip6 WG chairs did cross your message (:-).

   How about the length in the IPv6 header describes the length of the
   entire packet including extended options.

=> I don't believe the size constraint of MH (2K) is a problem.

   I'm not sure if overloading the MH protocol number is too evil.

=> it is evil.

   Does this sound like a good or a bad idea?
   
=> IMHO we have just to extend option format (and only this).

Regards

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Tue Aug 02 12:44:57 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dzzsv-0006DR-1w; Tue, 02 Aug 2005 12:44:57 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Dzzst-0006AL-Bn
	for mip6@megatron.ietf.org; Tue, 02 Aug 2005 12:44:55 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04162
	for <mip6@ietf.org>; Tue, 2 Aug 2005 12:44:51 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E00PO-0000jK-0f
	for mip6@ietf.org; Tue, 02 Aug 2005 13:18:31 -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 j72GibD20103; Tue, 2 Aug 2005 18:44: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.13.1/8.13.1) with ESMTP id
	j72GibkC012729; Tue, 2 Aug 2005 18:44:37 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200508021644.j72GibkC012729@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "James Kempf" <Kempf@docomolabs-usa.com>
Subject: Re: [Mip6] about draft-ietf-mip6-bootstrapping-split-00.txt 
In-reply-to: Your message of Tue, 02 Aug 2005 08:46:16 PDT.
	<0ac401c59779$5230bd10$596015ac@dcml.docomolabsusa.com> 
Date: Tue, 02 Aug 2005 18:44:37 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
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

 In your previous mail you wrote:

   > I have two concerns:
   >  the configuration service in IKEv2 was copied from DHCP,
   >  in fact, you should consider it as a lightweight DHCP service.
   >  - so in 5.3.2 you cannot use it to validate a HoA configured by
   >    the MN. BTW in the past I tried to add a validation/registration
   >    service for stateless autoconfed addresses in DHCPv6, it was
   >    rejected by the DHC WG.
   
   We had some discussion with IKE folks on this and they recommended that we
   introduce a new configuration option for autoconfiguration, which we did.
   
=> I believe we should have some discussion with DHCP folks too
because it is possible there is an hidden issue (I don't believe
this but to check is better than to be bitten).

   So would your objection be handled if we remove the text that says that the
   IINTERNAL_IPV6_ADDRESS can also be used to confirm an autoconfigured
   address?
   
=> my concern would be handled but the problem not solved. And my
second objection (DNS update in IKE, not via BU) assumes CFG_REQUEST be
used with MN configured HoAs too.

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 Aug 02 12:45:33 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DzztV-0006my-M9; Tue, 02 Aug 2005 12:45:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DzztU-0006mo-DQ
	for mip6@megatron.ietf.org; Tue, 02 Aug 2005 12:45:32 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04217
	for <mip6@ietf.org>; Tue, 2 Aug 2005 12:45:29 -0400 (EDT)
Received: from mail.sfc.wide.ad.jp ([203.178.142.146])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E00Px-0000nS-EN
	for mip6@ietf.org; Tue, 02 Aug 2005 13:19:08 -0400
Received: from [q??IPv6:2001:688:ffff:24:211:24ff:fe21:a941] (unknown
	[IPv6:2001:688:ffff:24:211:24ff:fe21:a941])
	by mail.sfc.wide.ad.jp (Postfix) with ESMTP id AC1714CC11;
	Wed,  3 Aug 2005 01:45:14 +0900 (JST)
In-Reply-To: <Pine.LNX.4.58.0507120633330.19362@rhea.tcs.hut.fi>
References: <42D2F384.6050107@iprg.nokia.com>
	<Pine.LNX.4.58.0507120633330.19362@rhea.tcs.hut.fi>
Mime-Version: 1.0 (Apple Message framework v733)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <06567170-0DCA-421C-BD93-14CD5A1DA834@sfc.wide.ad.jp>
Content-Transfer-Encoding: 7bit
From: Ryuji Wakikawa <ryuji@sfc.wide.ad.jp>
Subject: Re: [Mobopts] Re: [Mip6] [Fwd: FW: resubmit
	draft-irtf-mobopts-location-privacy-ps-00.txt with revised
	boilerplate]
Date: Wed, 3 Aug 2005 01:45:05 +0900
To: Wassim Haddad <whaddad@tcs.hut.fi>
X-Mailer: Apple Mail (2.733)
X-Spam-Score: 2.4 (++)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org, Rajeev Koodli <rajeev@iprg.nokia.com>, mobopts@irtf.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

Hi Wassim

I just saw the Rajeev's presentation.

If a MN can randomly generate a sequence value that is larger than  
the previous value and
within sequence number window, it's hard to track the mobile node.  no?

I agree most of implementation today just increment one for sequence  
number.
Is there any description in RFC3775  saying that MN must increment  
sequentially for Seq number?

ryuji


On 2005/07/12, at 12:50, Wassim Haddad wrote:

> Hi Rajeev,
>
> Thanks for writing this draft.
>
> I just want to add that tracing the BU messages via the sequence  
> number
> can also reveal in real time to an eavesdropper the path taken by an
> unknown mobile node, i.e., by linking the BU messages and consequently
> the pseudo-IP addresses.
> However, the ability to follow the movements in real time, combined  
> with
> some prior infos about one particular target can lead to break the  
> user's
> anonymity.
>
> IMHO, it makes sense to add such scenario in the problem statement.
>
> We have addressed this particular issue in our "anonymity and  
> unlinkability
> solution for omipv6" (draft-haddad-privacy-omipv6-anonymity-00).
>
>
> Regards,
>
> Wassim H.
>
>
> On Mon, 11 Jul 2005, Rajeev Koodli wrote:
>
>
>>
>> Hello folks,
>>
>> I submitted the draft on Friday, I believe with the correct  
>> boilerplate
>> (see attached draft). I still got an error message.
>>
>> Anyway, please find the Location Privacy Problem Statement draft.
>>
>> Regards,
>>
>> -Rajeev
>>
>>
>>
>>> -----Original Message-----
>>>
>>
>>
>>> From:     Koodli Rajeev (Nokia-NRC/MtView)
>>> Sent:    Friday, July 08, 2005 7:42 PM
>>> To:    'internet-drafts@ietf.org'
>>> Subject:    resubmit draft-irtf-mobopts-location-privacy- 
>>> ps-00.txt with revised boilerplate
>>>
>>>
>>> Here it is..
>>>
>>> Thanks,
>>>
>>> -Rajeev Koodli
>>>
>>>
>>>>  <<draft-irtf-mobopts-location-privacy-ps-00.txt>>
>>>>
>>>
>>> http://people.nokia.net/~rajeev
>>>
>>>
>>
>>
>>
>>
>
> _______________________________________________
> Mobopts mailing list
> Mobopts@irtf.org
> https://www1.ietf.org/mailman/listinfo/mobopts
>
>


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



From mip6-bounces@ietf.org Tue Aug 02 12:48:01 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dzzvs-0008Gp-US; Tue, 02 Aug 2005 12:48:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dzzvr-0008GP-Re; Tue, 02 Aug 2005 12:47:59 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04349;
	Tue, 2 Aug 2005 12:47:56 -0400 (EDT)
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1E00SM-0000rn-Kv; Tue, 02 Aug 2005 13:21:36 -0400
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 5193489832;
	Tue,  2 Aug 2005 19:47:43 +0300 (EEST)
Message-ID: <42EFA3B9.9050604@kolumbus.fi>
Date: Tue, 02 Aug 2005 19:47:53 +0300
From: Jari Arkko <jari.arkko@kolumbus.fi>
User-Agent: Mozilla Thunderbird 1.0 (X11/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
References: <200508020934.j729Yu6F011152@givry.rennes.enst-bretagne.fr>
In-Reply-To: <200508020934.j729Yu6F011152@givry.rennes.enst-bretagne.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org, mipshop@ietf.org
Subject: [Mip6] Re: [Mipshop] larger options
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

Francis Dupont wrote:

>PS: a way to fix it: mark size 255 as oversized option: the real length is
>in the two next octets.
>  
>
I don't like this very much, because current code would be
unable to skip it.

>Another way: use the first bit (length > 127) as oversized option:
>length field is extended to two octets and the real length is taken from
>them with the first bit masked...
>  
>
See above. And Greg Daley wrote:

> How about the length in the IPv6 header describes the length of the
> entire packet including extended options.  Mobility header
> length value describes the length of the mobility header with
> the original option sizes and format.  This aggregated length defined
> in the MH may be smaller than the total packet size (even counting
> preceding headers).
>
> An identifier would have to be carried in the mobility header indicating
> that following the exlicit length in the MH are "extended" mobility
> options.

This seems a bit complicated, but I got one idea from
this (more below).

> For example the next header=[MH|None], length =residual length of the
> message.
>
> The second MH could only have Extended length options (except pad?)
>
> I'm not sure if overloading the MH protocol number is too evil.  In that
> case, there would have to be an allocation of a new protocol number, and
> an admission of the problem to IANA... 

Overloading is usually not so good.

Additional ideas:

o    The truly long options are rare, there's likely just one (cga).
      Having a rule in the spec that needs this to concatenate the
      option in question if it appears multiple times would be possible.
      That is, you add, say, four options to carry the lengthy data:
         optionX(...)optionX(...)optionX(...)optionX(...)

o    Negotiation. The things are likely to need this are probably
      going to exchange some other packets prior to this, so you might
      send a negotiation option and get another back to confirm that the
      peer supports an extended format. Then you could send
      your real data by setting a flag in the header, and all options
      would use a new format that uses two byte length field for all
      options.

Not sure how good these are either. My current gut feeling is that
I'd go for the option concatenation.

--Jari



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



From mip6-bounces@ietf.org Tue Aug 02 12:52:08 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dzzzs-0002P8-06; Tue, 02 Aug 2005 12:52:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Dzzzq-0002P0-2K
	for mip6@megatron.ietf.org; Tue, 02 Aug 2005 12:52:06 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04725
	for <mip6@ietf.org>; Tue, 2 Aug 2005 12:52:02 -0400 (EDT)
Received: from smtp.um.es ([155.54.212.105] helo=mail.um.es)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E00WL-000180-74
	for mip6@ietf.org; Tue, 02 Aug 2005 13:25:42 -0400
Received: from localhost (localhost [127.0.0.1])
	by mail.um.es (Postfix) with ESMTP id A1BAA1FA4EF
	for <mip6@ietf.org>; Tue,  2 Aug 2005 18:51:54 +0200 (CEST)
Received: from mail.um.es ([127.0.0.1])
	by localhost (xenon1 [127.0.0.1]) (amavisd-new, port 10024) with LMTP
	id 29501-01-80 for <mip6@ietf.org>;
	Tue, 2 Aug 2005 18:51:44 +0200 (CEST)
Received: from [86.255.28.136] (dibulibu.um.es [155.54.1.250])
	by mail.um.es (Postfix) with ESMTP id F1BDA1FA4F0
	for <mip6@ietf.org>; Tue,  2 Aug 2005 18:51:25 +0200 (CEST)
Message-ID: <42EFA48E.6050208@dif.um.es>
Date: Tue, 02 Aug 2005 18:51:26 +0200
From: "Pedro M. Ruiz" <pedrom@dif.um.es>
User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: mip6@ietf.org
Content-Type: multipart/mixed; boundary="------------010005030900080403060300"
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at telemat.um.es
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 827a2a57ca7ab0837847220f447e8d56
Subject: [Mip6] Call for Participation: AD HOC NOW 2005
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

This is a multi-part message in MIME format.
--------------010005030900080403060300
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


Please, find below the Call for participation for the AD HOC NOW 2005 
conference to be held at Cancun next October 6th-8th

Best wishes,

Pedro M. Ruiz
http://ants.dif.um.es/staff/pedrom/

--------------010005030900080403060300
Content-Type: text/plain; x-mac-type="0"; x-mac-creator="0";
	name="cfparticip.txt"
Content-Disposition: inline;
 filename="cfparticip.txt"
Content-Transfer-Encoding: 7bit

We apologize if you receive the CFP more than once.
----------------------------------------------------------------------------
                 CALL FOR PARTICIPATION - AD HOC NOW 2005
         4th International Conference on Ad hoc Networks and Wireless
                         Cancun, October 6-8, 2005
                     http://fismat.umich.mx/adhocnow/
----------------------------------------------------------------------------

Early registration deadline: August, 31st
Hotel deadline to avail of rooms being held for AD HOC NOW 2005: Sept 24th

ABOUT THE CONFERENCE
--------------------

AD HOC NOW is the fourth of a series of high-quality conferences devoted to 
ad hoc, wireless and mobile networks. The AD HOC NOW committee invites you to
in this new edition, which will be held in Cancun, in October 6th-8th.

The program for this year consist of 28 top-quality papers, and two invited
speaker with a well-deserved recognition in the area:

* Prof. Jorge Urrutia, Univ. Nacional (UNAM), Mexico.
* Prof. J.J. Garcia-Luna-Aceves, Univ. of California, Santa Cruz.

ACCEPTED PAPERS
---------------
Playing CSMA/CA Game to Deter Backoff Attacks in Ad Hoc Wireless LANs 
	Jerzy Konorski

Message Stability and Reliable Broadcasts in Mobile Ad-Hoc Networks 
	Kulpreet Singh, Andronikos Nedos, Gregor Gaertner and Siobhan Clarke

Equilibria for Broadcast Range Assignment Games in Ad-Hoc Networks 
	Pilu Crescenzi, Miriam Di Ianni, Alessandro Lazzoni, Paolo Penna, 
	Gianluca Rossi and Paola Vocca

Performance Analysis of the Hierarchical Layer Graph for Wireless Networks 
	Stefan Ruehrup, Christian Schindelhauer and Klaus Volbert

Cache Placement in Sensor Networks Under Update Constraint 
	Bin Tang, Samir Das, and Himanshu Gupta

Enhancing The Security Of On-demand Routing in Ad Hoc Networks 
	Zhenjiang Li and J.J. Garcia-Luna-Aceves

MIMOMAN: A MIMO Mac protocol for Ad hoc Networks 
	Joon-Sang Park and Mario Gerla

Increasing the Resource-Efficiency of the CSMA/CA Protocol in Directional 
Ad Hoc Networks 
	Matthias Gruenewald, Feng Xu and Ulrich Rueckert

Location Tracking in Mobile Ad Hoc Networks using Particle Filters 
	Rui Huang and Gergely Zaruba

Selective Route Request Scheme for On-Demand Routing Protocols in Ad Hoc
Networks
	Seung Jae Lee

A Key Management Scheme for Commodity Sensor Networks
	Yong Ho Kim, Mu Hyun Kim, and Dong Hoon Lee

Design of a hard real-time guarantee scheme for dual ad hoc mode 
IEEE 802.11 WLANs 
	Junghoon Lee, Mikyung Kang and Yongmoon Jin

Energy*Delay Efficient Routing Scheme in Wireless Sensor Networks 
	Trong Thua Huynh

DPUMA: A Highly Efficient Multicast Routing Protocol for Mobile Ad Hoc Networks 
	Rolando Menchaca-Mendez, Ravindra Vaishampayan, 
	J.J. Garcia-Luna-Aceves and Katia Obraczka

Efficient Mechanisms for Secure Inter-node and Aggregation Processing 
in Sensor Networks 
	Tassos Dimitriou

Probability Distributions for Channel Utilisation 
	Christian Schindelhauer and Kerstin VoB

Approximation Algorithms for Minimum Bandwith Multicast Trees in 
Wireless Mesh Networks 
	Pedro M. Ruiz and Antonio F. Gomez-Skarmeta

Stressing is better than relaxing for negative cost cycle detection in networks 
	K. Subramani

Enhanced power-aware Routing for Mobile Ad-Hoc Networks 
	Il-Hee Shin, Chae-Woo Lee

Randomized AB-Face-AB Routing Algorithms in Mobile Ad Hoc Networks 
	Thomas Fevens, Alaa Eddien Abdallah, and Badr Naciri Bennani

A Gathering Point Detection Scheme for Directed Diffusion in 
Wireless Sensor Networks 
	Jeongho Son, Jinsuk Pak and Kijun Han

Cluster-Based Framework in Vehicular Ad-Hoc Networks 
	Peng Fan, James Haran, Peter Nelson and John Dillenburg

Biology Inspired Distributed Consensus in Massively-Deployed Sensor Networks 
	K.H.Jones, K.N.Lodding, S.Olariu, L.W.Wilson and C.Xin

A Multiple Path Characterization of Ad-Hoc Network Capacity 
	Peter Giese and Ioanis Nikolaidis

Reed-Solomon and Hermitian Code-based Scheduling Protocols for 
Wireless Ad Hoc Networks 
	Carlos H. Rentel and Thomas Kunz

Efficient broadcasting in Self-Organizing Multi-hop Wireless Networks 
	Nathalie Mitton and Eric Fleury

An Intelligent Sensor Network for Oceanographic Data Acquisition. 
	Chris Roadknight, Antonio Gonzalez, Laura. Parrot, 
	Steve Boult and Ian Marshall

A service discovery protocol with maximally area disjoint paths in 
mobile ad hoc networks 
	Shihong Zou, Le Tian, Shiduan Cheng and Yu Lin

REGISTRATION
------------

You can proceed to: http://fismat.umich.mx/adhocnow/?f=registration

After you complete your registration to ADHOCNOW! 2005, you'll be able to download a postcript document which must be filled in with your credit card data and faxed to the number shown in order to secure your reservation to the Oasis Hotel.

The conference will be held at the Oasis Cancun Hotel. The hotel rate for this conference is within an All-inclusive program, which entitles you to all meals (buffet breakfast, lunch and dinner), unlimited drinks, recreational activities, non-motorized water sports, gym facilities, evening shows, disco, all taxes and tips. Rates are as follows:

    Single	US$86.00
    Double	US$140.00
    Triple	US$170.00

FOR ADDITIONAL INFORMATON
-------------------------
For questions regarding obtaining visas, accomodation, etc, please contact
Edgar Chavez (mailto:elchavez@fismat.umich.mx). 



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

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

--------------010005030900080403060300--




From mip6-bounces@ietf.org Tue Aug 02 13:05:05 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E00CP-0005Wu-GX; Tue, 02 Aug 2005 13:05:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1E00CN-0005VJ-VQ
	for mip6@megatron.ietf.org; Tue, 02 Aug 2005 13:05:04 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05894
	for <mip6@ietf.org>; Tue, 2 Aug 2005 13:05:00 -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.43) id 1E00it-0001p1-P3
	for mip6@ietf.org; Tue, 02 Aug 2005 13:38:40 -0400
Message-ID: <0b1401c59784$4f13c4a0$596015ac@dcml.docomolabsusa.com>
From: "James Kempf" <Kempf@docomolabs-usa.com>
To: "Francis Dupont" <Francis.Dupont@enst-bretagne.fr>
References: <200508021644.j72GibkC012729@givry.rennes.enst-bretagne.fr>
Subject: Re: [Mip6] about draft-ietf-mip6-bootstrapping-split-00.txt 
Date: Tue, 2 Aug 2005 10:04:55 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
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

> => I believe we should have some discussion with DHCP folks too
> because it is possible there is an hidden issue (I don't believe
> this but to check is better than to be bitten).
>

OK, we can check with Ralph.

>    So would your objection be handled if we remove the text that says that
the
>    IINTERNAL_IPV6_ADDRESS can also be used to confirm an autoconfigured
>    address?
>
> => my concern would be handled but the problem not solved. And my
> second objection (DNS update in IKE, not via BU) assumes CFG_REQUEST be
> used with MN configured HoAs too.
>

We discussed this and I think one issue is that IKE doesn't require that the
address be defended on the local link, while MIPv6 does. I don't know why
they did this, perhaps they were assuming that it was unnecessary for a
DHCP-like solution. Another is that the HA may reject the BU for some
reason, and then the address would need to be unregistered from the DNS, but
the HA couldn't do that because it would not have the FQDN.

What exactly was the issue you had with having the DNS update done via the
BU?

            jak



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



From mip6-bounces@ietf.org Tue Aug 02 13:26:27 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E00X5-00068i-5N; Tue, 02 Aug 2005 13:26:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E00X3-00066g-C6; Tue, 02 Aug 2005 13:26:25 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06961;
	Tue, 2 Aug 2005 13:26:21 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1E013Y-0002gf-El; Tue, 02 Aug 2005 14:00:01 -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 j72HQ7D23352; Tue, 2 Aug 2005 19:26:07 +0200
Received: from givry.rennes.enst-bretagne.fr
	(localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id
	j72HQ7wP012932; Tue, 2 Aug 2005 19:26:07 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200508021726.j72HQ7wP012932@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Jari Arkko <jari.arkko@kolumbus.fi>
In-reply-to: Your message of Tue, 02 Aug 2005 19:47:53 +0300.
	<42EFA3B9.9050604@kolumbus.fi> 
Date: Tue, 02 Aug 2005 19:26:07 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: mip6@ietf.org, mipshop@ietf.org
Subject: [Mip6] Re: [Mipshop] larger options 
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

 In your previous mail you wrote:

   >PS: a way to fix it: mark size 255 as oversized option: the real length is
   >in the two next octets.

   I don't like this very much, because current code would be
   unable to skip it.
   
=> I am afraid this will be true with any solution, and RFC 3775 requires
to skip unknown options (argh!).

   Additional ideas:
   
   o    The truly long options are rare, there's likely just one (cga).

=> we can get more as nobody have taken care of this problem before today.

         Having a rule in the spec that needs this to concatenate the
         option in question if it appears multiple times would be possible.
         That is, you add, say, four options to carry the lengthy data:
            optionX(...)optionX(...)optionX(...)optionX(...)
   
=> this can be a nice way to avoid the skipping issue, and
this mechanism can be defined per option type. I buy it
if nobody has a better proposal.

   o    Negotiation. The things are likely to need this are probably
         going to exchange some other packets prior to this, so you might
         send a negotiation option and get another back to confirm that the
         peer supports an extended format. Then you could send
         your real data by setting a flag in the header, and all options
         would use a new format that uses two byte length field for all
         options.
   
=> this makes a strong assumption...

   Not sure how good these are either. My current gut feeling is that
   I'd go for the option concatenation.
   
=> I agree and it makes the solution documentation easier. IMHO it
is workable if oversized options are pretty uncommon.

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 Aug 02 13:31:02 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E00bW-0008Lk-J8; Tue, 02 Aug 2005 13:31:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E00bU-0008KV-FH; Tue, 02 Aug 2005 13:31:00 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07281;
	Tue, 2 Aug 2005 13:30:56 -0400 (EDT)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1E017y-0002wS-JE; Tue, 02 Aug 2005 14:04:37 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j72GxMY04606;
	Tue, 2 Aug 2005 09:59:22 -0700
X-mProtect: <200508021659> Nokia Silicon Valley Messaging Protection
Received: from es-nira-27-221.europe.nokia.com (10.162.27.221,
	claiming to be "[127.0.0.1]")
	by darkstar.iprg.nokia.com smtpdcWJlYp; Tue, 02 Aug 2005 09:59:20 PDT
Message-ID: <42EFADAF.3080906@iprg.nokia.com>
Date: Tue, 02 Aug 2005 10:30:23 -0700
From: Rajeev Koodli <rajeev@iprg.nokia.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Ryuji Wakikawa <ryuji@sfc.wide.ad.jp>
Subject: Re: [Mobopts] Re: [Mip6] [Fwd: FW:
	resubmit	draft-irtf-mobopts-location-privacy-ps-00.txt
	with revised	boilerplate]
References: <42D2F384.6050107@iprg.nokia.com>	<Pine.LNX.4.58.0507120633330.19362@rhea.tcs.hut.fi>
	<06567170-0DCA-421C-BD93-14CD5A1DA834@sfc.wide.ad.jp>
In-Reply-To: <06567170-0DCA-421C-BD93-14CD5A1DA834@sfc.wide.ad.jp>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 2.4 (++)
X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e
Content-Transfer-Encoding: 7bit
Cc: Wassim Haddad <whaddad@tcs.hut.fi>, mobopts@irtf.org, 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



Ryuji Wakikawa wrote:

> Hi Wassim
> 
> I agree most of implementation today just increment one for sequence  
> number.
> Is there any description in RFC3775  saying that MN must increment  
> sequentially for Seq number?

I was looking for that. I could not find text that says the Sequence
Number must be incremented by one. The only requirement is that it is
greater than the previous one.

-Rajeev




> 
> ryuji
> 
> 
> On 2005/07/12, at 12:50, Wassim Haddad wrote:
> 
>> Hi Rajeev,
>>
>> Thanks for writing this draft.
>>
>> I just want to add that tracing the BU messages via the sequence  number
>> can also reveal in real time to an eavesdropper the path taken by an
>> unknown mobile node, i.e., by linking the BU messages and consequently
>> the pseudo-IP addresses.
>> However, the ability to follow the movements in real time, combined  with
>> some prior infos about one particular target can lead to break the  
>> user's
>> anonymity.
>>
>> IMHO, it makes sense to add such scenario in the problem statement.
>>
>> We have addressed this particular issue in our "anonymity and  
>> unlinkability
>> solution for omipv6" (draft-haddad-privacy-omipv6-anonymity-00).
>>
>>
>> Regards,
>>
>> Wassim H.
>>
>>
>> On Mon, 11 Jul 2005, Rajeev Koodli wrote:
>>
>>
>>>
>>> Hello folks,
>>>
>>> I submitted the draft on Friday, I believe with the correct  boilerplate
>>> (see attached draft). I still got an error message.
>>>
>>> Anyway, please find the Location Privacy Problem Statement draft.
>>>
>>> Regards,
>>>
>>> -Rajeev
>>>
>>>
>>>
>>>> -----Original Message-----
>>>>
>>>
>>>
>>>> From:     Koodli Rajeev (Nokia-NRC/MtView)
>>>> Sent:    Friday, July 08, 2005 7:42 PM
>>>> To:    'internet-drafts@ietf.org'
>>>> Subject:    resubmit draft-irtf-mobopts-location-privacy- ps-00.txt 
>>>> with revised boilerplate
>>>>
>>>>
>>>> Here it is..
>>>>
>>>> Thanks,
>>>>
>>>> -Rajeev Koodli
>>>>
>>>>
>>>>>  <<draft-irtf-mobopts-location-privacy-ps-00.txt>>
>>>>>
>>>>
>>>> http://people.nokia.net/~rajeev
>>>>
>>>>
>>>
>>>
>>>
>>>
>>
>> _______________________________________________
>> Mobopts mailing list
>> Mobopts@irtf.org
>> https://www1.ietf.org/mailman/listinfo/mobopts
>>
>>
> 
> 
> _______________________________________________
> 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 Wed Aug 03 03:01:33 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E0DFt-00021V-C8; Wed, 03 Aug 2005 03:01:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1E0DFr-00020H-1c
	for mip6@megatron.ietf.org; Wed, 03 Aug 2005 03:01:31 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA19428
	for <mip6@ietf.org>; Wed, 3 Aug 2005 03:01:29 -0400 (EDT)
Received: from neon.tcs.hut.fi ([130.233.215.20])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E0DmT-0007Yz-7P
	for mip6@ietf.org; Wed, 03 Aug 2005 03:35:14 -0400
Received: from rhea.tcs.hut.fi (rhea.tcs.hut.fi [130.233.215.147])
	by neon.tcs.hut.fi (Postfix) with ESMTP
	id A58EF8004B0; Wed,  3 Aug 2005 10:01:16 +0300 (EEST)
Date: Wed, 3 Aug 2005 10:01:16 +0300 (EEST)
From: Wassim Haddad <whaddad@tcs.hut.fi>
To: Ryuji Wakikawa <ryuji@sfc.wide.ad.jp>
Subject: Re: [Mobopts] Re: [Mip6] [Fwd: FW: resubmit
	draft-irtf-mobopts-location-privacy-ps-00.txt with revised boilerplate]
In-Reply-To: <06567170-0DCA-421C-BD93-14CD5A1DA834@sfc.wide.ad.jp>
Message-ID: <Pine.LNX.4.58.0508030949040.454@rhea.tcs.hut.fi>
References: <42D2F384.6050107@iprg.nokia.com>
	<Pine.LNX.4.58.0507120633330.19362@rhea.tcs.hut.fi>
	<06567170-0DCA-421C-BD93-14CD5A1DA834@sfc.wide.ad.jp>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=iso-8859-1
Content-Transfer-Encoding: QUOTED-PRINTABLE
X-Spam-Score: 2.4 (++)
X-Scan-Signature: 3a4bc66230659131057bb68ed51598f8
Content-Transfer-Encoding: QUOTED-PRINTABLE
Cc: mip6@ietf.org, Rajeev Koodli <rajeev@iprg.nokia.com>, mobopts@irtf.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

Hi Ryuji,

On Wed, 3 Aug 2005, Ryuji Wakikawa wrote:

> Hi Wassim
>
> I just saw the Rajeev's presentation.
>
> If a MN can randomly generate a sequence value that is larger than
> the previous value and within sequence number window, it's hard to track
> the mobile node.  no?

=3D> IMHO, this may not be enough. The SQN should appear for an eavesdroppe=
r
as random and not larger than the previous one (i.e., this is still
traceable).
This issue has been addressed in:
draft-haddad-privacy-omipv6-anonymity-00

> I agree most of implementation today just increment one for sequence
> number.

> Is there any description in RFC3775  saying that MN must increment
> sequentially for Seq number?

=3D> I think RFC3775 just mention that it should be larger.


Regards,

Wassim H.


> On 2005/07/12, at 12:50, Wassim Haddad wrote:
>
> > Hi Rajeev,
> >
> > Thanks for writing this draft.
> >
> > I just want to add that tracing the BU messages via the sequence
> > number
> > can also reveal in real time to an eavesdropper the path taken by an
> > unknown mobile node, i.e., by linking the BU messages and consequently
> > the pseudo-IP addresses.
> > However, the ability to follow the movements in real time, combined
> > with
> > some prior infos about one particular target can lead to break the
> > user's
> > anonymity.
> >
> > IMHO, it makes sense to add such scenario in the problem statement.
=C3> >
> > We have addressed this particular issue in our "anonymity and
> > unlinkability
> > solution for omipv6" (draft-haddad-privacy-omipv6-anonymity-00).
> >
> >
> > Regards,
> >
> > Wassim H.
> >
> >
> > On Mon, 11 Jul 2005, Rajeev Koodli wrote:
> >
> >
> >>
> >> Hello folks,
> >>
> >> I submitted the draft on Friday, I believe with the correct
> >> boilerplate
> >> (see attached draft). I still got an error message.
> >>
> >> Anyway, please find the Location Privacy Problem Statement draft.
> >>
> >> Regards,
> >>
> >> -Rajeev
> >>
> >>
> >>
> >>> -----Original Message-----
> >>>
> >>
> >>
> >>> From:     Koodli Rajeev (Nokia-NRC/MtView)
> >>> Sent:    Friday, July 08, 2005 7:42 PM
> >>> To:    'internet-drafts@ietf.org'
> >>> Subject:    resubmit draft-irtf-mobopts-location-privacy-
> >>> ps-00.txt with revised boilerplate
> >>>
> >>>
> >>> Here it is..
> >>>
> >>> Thanks,
> >>>
> >>> -Rajeev Koodli
> >>>
> >>>
> >>>>  <<draft-irtf-mobopts-location-privacy-ps-00.txt>>
> >>>>
> >>>
> >>> http://people.nokia.net/~rajeev
> >>>
> >>>
> >>
> >>
> >>
> >>
> >
> > _______________________________________________
> > Mobopts mailing list
> > Mobopts@irtf.org
> > https://www1.ietf.org/mailman/listinfo/mobopts
> >
> >
>
>
>

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



From mip6-bounces@ietf.org Wed Aug 03 03:07:38 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E0DLm-0007W3-9w; Wed, 03 Aug 2005 03:07:38 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1E0DLf-0007F9-F8
	for mip6@megatron.ietf.org; Wed, 03 Aug 2005 03:07:36 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA19834
	for <mip6@ietf.org>; Wed, 3 Aug 2005 03:07:30 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E0DsH-0007qK-Uh
	for mip6@ietf.org; Wed, 03 Aug 2005 03:41:15 -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 j73773D04282; Wed, 3 Aug 2005 09:07: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.13.1/8.13.1) with ESMTP id
	j73772cG014695; Wed, 3 Aug 2005 09:07:03 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200508030707.j73772cG014695@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "James Kempf" <Kempf@docomolabs-usa.com>
Subject: Re: [Mip6] about draft-ietf-mip6-bootstrapping-split-00.txt 
In-reply-to: Your message of Tue, 02 Aug 2005 10:04:55 PDT.
	<0b1401c59784$4f13c4a0$596015ac@dcml.docomolabsusa.com> 
Date: Wed, 03 Aug 2005 09:07:02 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
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

 In your previous mail you wrote:

   >    So would your objection be handled if we remove the text that says that
   the
   >    IINTERNAL_IPV6_ADDRESS can also be used to confirm an autoconfigured
   >    address?
   >
   > => my concern would be handled but the problem not solved. And my
   > second objection (DNS update in IKE, not via BU) assumes CFG_REQUEST be
   > used with MN configured HoAs too.
   
   We discussed this and I think one issue is that IKE doesn't require that the
   address be defended on the local link, while MIPv6 does.

=> this is not a problem for DNS update as it always checks if an RR or
a name already exists, and if it is not required it is not forbidden
(in fact it is a good idea as the client is by definition remote and
cannot defend its addresses on the link).

   I don't know why they did this, perhaps they were assuming that it
   was unnecessary for a DHCP-like solution.

=> I believe they just forgot (they are not specialists of IPv6 at all,
and IPv6 people thought that CFG_REQUEST would never be enough).

   Another is that the HA may reject the BU for some reason,

=> this is not a problem: if the MN gives up it can ask the removal
of the RR and has to close the IKE session (i.e., delete the SAs).

   and then the address would need to be unregistered from the DNS,

=> yes, the PTR needs to be deleted.

   but the HA couldn't do that because it would not have the FQDN.

=> I disagree: first the FQDN is not needed as the PTR is for the address
in the reversed name format, and the FQDN is given for registration
so there is no problem to give it for deregistration too.
Perhaps you think about automatic deregistration when the IKE session
goes down (so my first argument applies)?
   
   What exactly was the issue you had with having the DNS update done via the
   BU?
   
=> this is not the job of the MIPv6 code and is clearly the job of the
tool which allocates the HoA: IKE CFG_REQUEST stuff. Here I apply
my idea that IKE CFG_REQUEST is DHCP-like and DNS update is a classical
service offered by DHCP. BTW the DNS update must be secured i.e. the
tools performing it be trusted, so it is not simple...

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 Aug 03 03:44:16 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E0DvE-0000zh-NC; Wed, 03 Aug 2005 03:44:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1E0DvC-0000zX-Qv
	for mip6@megatron.ietf.org; Wed, 03 Aug 2005 03:44:15 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA21963
	for <mip6@ietf.org>; Wed, 3 Aug 2005 03:44:13 -0400 (EDT)
Received: from rodin.i2r.a-star.edu.sg ([192.122.139.27])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E0ERn-0001BO-DH
	for mip6@ietf.org; Wed, 03 Aug 2005 04:17:59 -0400
Received: from rodin.i2r.a-star.edu.sg (localhost [127.0.0.1])
	by rodin.i2r.a-star.edu.sg (8.13.1/8.13.1) with ESMTP id j737hx73014193
	for <mip6@ietf.org>; Wed, 3 Aug 2005 15:43:59 +0800 (SGT)
Received: from newmailhost.i2r.a-star.edu.sg ([192.122.134.76])by rodin.i2r.
	a-star.edu.sg (8.13.1/8.13.1) with ESMTP id j737hwvv014180for
	<mip6@ietf.or g>; Wed, 3 Aug 2005 15:43:58 +0800 (SGT)
Received: from i2r.a-star.edu.sg (localhost [127.0.0.1])by mailhost.lit.org.
	sg (Sun Java System Messaging Server 6.1 HotFix 0.06(built Nov 11
	2004)) wi
	th ESMTP id <0IKM009AAYTFHU00@mailhost.lit.org.sg> formip6@ietf.org;
	Wed, 0 3 Aug 2005 15:44:03 +0800 (SGT)
Received: from [192.122.139.152] by mailhost.lit.org.sg (mshttpd); Wed,03 Au
	g 2005 15:44:03 +0800
Date: Wed, 03 Aug 2005 15:44:03 +0800
From: Qiu Ying <qiuying@i2r.a-star.edu.sg>
Subject: Re: [Mobopts] Re: [Mip6] [Fwd: FW:resubmit	draft-irtf-mobopts-locat
	ion-privacy-ps-00.txtwith revised	boilerplate]
To: Rajeev Koodli <rajeev@iprg.nokia.com>
Message-id: <866fa8ca76aa.42f0e643@i2r.a-star.edu.sg>
MIME-version: 1.0
X-Mailer: Sun Java(tm) System Messenger Express 6.1 HotFix 0.06 (built Nov 1
	12004)
Content-type: text/plain;
	charset=us-ascii
Content-language: en
Content-transfer-encoding: 7BIT
Content-disposition: inline
X-Accept-Language: en
Priority: normal
X-imss-version: 2.29
X-imss-result: Passed
X-imss-scores: Clean:99.90000 C:2 M:3 S:5 R:5
X-imss-settings: Baseline:5 C:4 M:4 S:4 R:4 (1.5000 1.5000)
X-Spam-Score: 2.4 (++)
X-Scan-Signature: a1852b4f554b02e7e4548cc7928acc1f
Content-Transfer-Encoding: 7BIT
Cc: mip6@ietf.org, Wassim Haddad <whaddad@tcs.hut.fi>,
	Ryuji Wakikawa <ryuji@sfc.wide.ad.jp>, mobopts@irtf.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

Hi,
Yes, RFC3775 only mentions that the SQN should be larger than the previous one. The new issue is how to let the receiver know the increment if we does not use a fixed one..
-- Qiu Ying

----- Original Message -----
From: Rajeev Koodli <rajeev@iprg.nokia.com>
Date: Wednesday, August 3, 2005 1:30 am
Subject: Re: [Mobopts] Re: [Mip6] [Fwd: FW:resubmit	draft-irtf-mobopts-locat ion-privacy-ps-00.txtwith revised	boilerplate]

> 
> 
> Ryuji Wakikawa wrote:
> 
> > Hi Wassim
> > 
> > I agree most of implementation today just increment one for 
> sequence  
> > number.
> > Is there any description in RFC3775  saying that MN must 
> increment  
> > sequentially for Seq number?
> 
> I was looking for that. I could not find text that says the Sequence
> Number must be incremented by one. The only requirement is that it is
> greater than the previous one.
> 
> -Rajeev
> 
> 
> 
> 
> > 
> > ryuji
> > 
> > 
> > On 2005/07/12, at 12:50, Wassim Haddad wrote:
> > 
> >> Hi Rajeev,
> >>
> >> Thanks for writing this draft.
> >>
> >> I just want to add that tracing the BU messages via the sequence 
> number
> >> can also reveal in real time to an eavesdropper the path taken 
> by an
> >> unknown mobile node, i.e., by linking the BU messages and 
> consequently>> the pseudo-IP addresses.
> >> However, the ability to follow the movements in real time, 
> combined  with
> >> some prior infos about one particular target can lead to break 
> the  
> >> user's
> >> anonymity.
> >>
> >> IMHO, it makes sense to add such scenario in the problem statement.
> >>
> >> We have addressed this particular issue in our "anonymity and  
> >> unlinkability
> >> solution for omipv6" (draft-haddad-privacy-omipv6-anonymity-00).
> >>
> >>
> >> Regards,
> >>
> >> Wassim H.
> >>
> >>
> >> On Mon, 11 Jul 2005, Rajeev Koodli wrote:
> >>
> >>
> >>>
> >>> Hello folks,
> >>>
> >>> I submitted the draft on Friday, I believe with the correct  
> boilerplate>>> (see attached draft). I still got an error message.
> >>>
> >>> Anyway, please find the Location Privacy Problem Statement draft.
> >>>
> >>> Regards,
> >>>
> >>> -Rajeev
> >>>
> >>>
> >>>
> >>>> -----Original Message-----
> >>>>
> >>>
> >>>
> >>>> From:     Koodli Rajeev (Nokia-NRC/MtView)
> >>>> Sent:    Friday, July 08, 2005 7:42 PM
> >>>> To:    'internet-drafts@ietf.org'
> >>>> Subject:    resubmit draft-irtf-mobopts-location-privacy- ps-
> 00.txt 
> >>>> with revised boilerplate
> >>>>
> >>>>
> >>>> Here it is..
> >>>>
> >>>> Thanks,
> >>>>
> >>>> -Rajeev Koodli
> >>>>
> >>>>
> >>>>>  <<draft-irtf-mobopts-location-privacy-ps-00.txt>>
> >>>>>
> >>>>
> >>>> http://people.nokia.net/~rajeev
> >>>>
> >>>>
> >>>
> >>>
> >>>
> >>>
> >>
> >> _______________________________________________
> >> Mobopts mailing list
> >> Mobopts@irtf.org
> >> https://www1.ietf.org/mailman/listinfo/mobopts
> >>
> >>
> > 
> > 
> > _______________________________________________
> > Mip6 mailing list
> > Mip6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mip6
> 
> 
> _______________________________________________
> Mobopts mailing list
> Mobopts@irtf.org
> https://www1.ietf.org/mailman/listinfo/mobopts
> 


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



From mip6-bounces@ietf.org Wed Aug 03 03:45:35 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E0DwV-0001ME-Ro; Wed, 03 Aug 2005 03:45:35 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1E0DwU-0001M8-Tc
	for mip6@megatron.ietf.org; Wed, 03 Aug 2005 03:45:34 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22030
	for <mip6@ietf.org>; Wed, 3 Aug 2005 03:45:30 -0400 (EDT)
Received: from rodin.i2r.a-star.edu.sg ([192.122.139.27])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E0ET5-0001GI-Qi
	for mip6@ietf.org; Wed, 03 Aug 2005 04:19:16 -0400
Received: from rodin.i2r.a-star.edu.sg (localhost [127.0.0.1])
	by rodin.i2r.a-star.edu.sg (8.13.1/8.13.1) with ESMTP id j737jLcs014651
	for <mip6@ietf.org>; Wed, 3 Aug 2005 15:45:21 +0800 (SGT)
Received: from newmailhost.i2r.a-star.edu.sg ([192.122.134.76])by rodin.i2r.
	a-star.edu.sg (8.13.1/8.13.1) with ESMTP id j737jLRN014646for
	<mip6@ietf.or g>; Wed, 3 Aug 2005 15:45:21 +0800 (SGT)
Received: from i2r.a-star.edu.sg (localhost [127.0.0.1])by mailhost.lit.org.
	sg (Sun Java System Messaging Server 6.1 HotFix 0.06(built Nov 11
	2004)) wi
	th ESMTP id <0IKM009BAYVQHU00@mailhost.lit.org.sg> formip6@ietf.org;
	Wed, 0 3 Aug 2005 15:45:26 +0800 (SGT)
Received: from [192.122.139.152] by mailhost.lit.org.sg (mshttpd); Wed,03 Au
	g 2005 15:45:26 +0800
Date: Wed, 03 Aug 2005 15:45:26 +0800
From: Qiu Ying <qiuying@i2r.a-star.edu.sg>
Subject: Re: [Mobopts] Re: [Mip6] [Fwd: FW:resubmit	draft-irtf-mobopts-locat
	ion-privacy-ps-00.txtwith revised	boilerplate]
To: Rajeev Koodli <rajeev@iprg.nokia.com>
Message-id: <8674a0272826.42f0e696@i2r.a-star.edu.sg>
MIME-version: 1.0
X-Mailer: Sun Java(tm) System Messenger Express 6.1 HotFix 0.06 (built Nov 1
	12004)
Content-type: text/plain;
	charset=us-ascii
Content-language: en
Content-transfer-encoding: 7BIT
Content-disposition: inline
X-Accept-Language: en
Priority: normal
X-imss-version: 2.29
X-imss-result: Passed
X-imss-scores: Clean:99.90000 C:2 M:3 S:5 R:5
X-imss-settings: Baseline:5 C:4 M:4 S:4 R:4 (1.5000 1.5000)
X-Spam-Score: 2.4 (++)
X-Scan-Signature: 68ba2b07ef271dba6ee42a93832cfa4c
Content-Transfer-Encoding: 7BIT
Cc: mip6@ietf.org, Wassim Haddad <whaddad@tcs.hut.fi>,
	Ryuji Wakikawa <ryuji@sfc.wide.ad.jp>, mobopts@irtf.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

Hi,
Yes, RFC3775 only mentions that the SQN should be larger than the previous one. The new issue is how to let the receiver know the increment if we does not use a fixed one..
-- Qiu Ying


----- Original Message -----
From: Rajeev Koodli <rajeev@iprg.nokia.com>
Date: Wednesday, August 3, 2005 1:30 am
Subject: Re: [Mobopts] Re: [Mip6] [Fwd: FW:resubmit	draft-irtf-mobopts-locat ion-privacy-ps-00.txtwith revised	boilerplate]

> 
> 
> Ryuji Wakikawa wrote:
> 
> > Hi Wassim
> > 
> > I agree most of implementation today just increment one for 
> sequence  
> > number.
> > Is there any description in RFC3775  saying that MN must 
> increment  
> > sequentially for Seq number?
> 
> I was looking for that. I could not find text that says the Sequence
> Number must be incremented by one. The only requirement is that it is
> greater than the previous one.
> 
> -Rajeev
> 
> 
> 
> 
> > 
> > ryuji
> > 
> > 
> > On 2005/07/12, at 12:50, Wassim Haddad wrote:
> > 
> >> Hi Rajeev,
> >>
> >> Thanks for writing this draft.
> >>
> >> I just want to add that tracing the BU messages via the sequence 
> number
> >> can also reveal in real time to an eavesdropper the path taken 
> by an
> >> unknown mobile node, i.e., by linking the BU messages and 
> consequently>> the pseudo-IP addresses.
> >> However, the ability to follow the movements in real time, 
> combined  with
> >> some prior infos about one particular target can lead to break 
> the  
> >> user's
> >> anonymity.
> >>
> >> IMHO, it makes sense to add such scenario in the problem statement.
> >>
> >> We have addressed this particular issue in our "anonymity and  
> >> unlinkability
> >> solution for omipv6" (draft-haddad-privacy-omipv6-anonymity-00).
> >>
> >>
> >> Regards,
> >>
> >> Wassim H.
> >>
> >>
> >> On Mon, 11 Jul 2005, Rajeev Koodli wrote:
> >>
> >>
> >>>
> >>> Hello folks,
> >>>
> >>> I submitted the draft on Friday, I believe with the correct  
> boilerplate>>> (see attached draft). I still got an error message.
> >>>
> >>> Anyway, please find the Location Privacy Problem Statement draft.
> >>>
> >>> Regards,
> >>>
> >>> -Rajeev
> >>>
> >>>
> >>>
> >>>> -----Original Message-----
> >>>>
> >>>
> >>>
> >>>> From:     Koodli Rajeev (Nokia-NRC/MtView)
> >>>> Sent:    Friday, July 08, 2005 7:42 PM
> >>>> To:    'internet-drafts@ietf.org'
> >>>> Subject:    resubmit draft-irtf-mobopts-location-privacy- ps-
> 00.txt 
> >>>> with revised boilerplate
> >>>>
> >>>>
> >>>> Here it is..
> >>>>
> >>>> Thanks,
> >>>>
> >>>> -Rajeev Koodli
> >>>>
> >>>>
> >>>>>  <<draft-irtf-mobopts-location-privacy-ps-00.txt>>
> >>>>>
> >>>>
> >>>> http://people.nokia.net/~rajeev
> >>>>
> >>>>
> >>>
> >>>
> >>>
> >>>
> >>
> >> _______________________________________________
> >> Mobopts mailing list
> >> Mobopts@irtf.org
> >> https://www1.ietf.org/mailman/listinfo/mobopts
> >>
> >>
> > 
> > 
> > _______________________________________________
> > Mip6 mailing list
> > Mip6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mip6
> 
> 
> _______________________________________________
> Mobopts mailing list
> Mobopts@irtf.org
> https://www1.ietf.org/mailman/listinfo/mobopts
> 


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



From mip6-bounces@ietf.org Wed Aug 03 04:05:01 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E0EFI-0007Bw-3D; Wed, 03 Aug 2005 04:05:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1E0EFF-0007Br-Q1
	for mip6@megatron.ietf.org; Wed, 03 Aug 2005 04:04:58 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA23201
	for <mip6@ietf.org>; Wed, 3 Aug 2005 04:04:56 -0400 (EDT)
Received: from yui.nc.u-tokyo.ac.jp ([130.69.251.116])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E0Els-000285-PL
	for mip6@ietf.org; Wed, 03 Aug 2005 04:38:42 -0400
Received: from wired-6-22.ietf63.ietf.org.sfc.wide.ad.jp
	(wired-6-22.ietf63.ietf.org [86.255.6.22]) (authenticated bits=0)
	by yui.nc.u-tokyo.ac.jp (8.12.10/8.12.3/Debian-6.4) with ESMTP id
	j7384J64011929; Wed, 3 Aug 2005 17:04:23 +0900
Date: Wed, 03 Aug 2005 17:04:16 +0900
Message-ID: <m2r7db30qn.wl%ryuji@sfc.wide.ad.jp>
From: Ryuji Wakikawa <ryuji@sfc.wide.ad.jp>
To: Wassim Haddad <whaddad@tcs.hut.fi>
Subject: Re: [Mobopts] Re: [Mip6] [Fwd: FW: resubmit
	draft-irtf-mobopts-location-privacy-ps-00.txt with revised
	boilerplate]
In-Reply-To: <Pine.LNX.4.58.0508030949040.454@rhea.tcs.hut.fi>
References: <42D2F384.6050107@iprg.nokia.com>
	<Pine.LNX.4.58.0507120633330.19362@rhea.tcs.hut.fi>
	<06567170-0DCA-421C-BD93-14CD5A1DA834@sfc.wide.ad.jp>
	<Pine.LNX.4.58.0508030949040.454@rhea.tcs.hut.fi>
User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.6
	(Marutamachi) APEL/10.6 Emacs/22.0.50
	(powerpc-apple-darwin8.1.0) MULE/5.0 (SAKAKI)
Organization: Keio University/WIDE
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 2.4 (++)
X-Scan-Signature: dbb8771284c7a36189745aa720dc20ab
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org, Ryuji Wakikawa <ryuji@sfc.wide.ad.jp>,
	Rajeev Koodli <rajeev@iprg.nokia.com>, mobopts@irtf.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


Hello Wassim

At Wed, 3 Aug 2005 10:01:16 +0300 (EEST),
Wassim Haddad wrote:
>=20
> Hi Ryuji,
>=20
> On Wed, 3 Aug 2005, Ryuji Wakikawa wrote:
>=20
> > Hi Wassim
> >
> > I just saw the Rajeev's presentation.
> >
> > If a MN can randomly generate a sequence value that is larger than
> > the previous value and within sequence number window, it's hard to track
> > the mobile node.  no?
>=20
> =3D> IMHO, this may not be enough. The SQN should appear for an eavesdrop=
per
> as random and not larger than the previous one (i.e., this is still
> traceable).
> This issue has been addressed in:
> draft-haddad-privacy-omipv6-anonymity-00

Well, it's worth to look SQN trace, but we may solve this
by operations.=20
MIP6 has the notion of window for SQN.  In some case, the SQN is
smaller than the previous one for eavesdropper, but still valid due to
SQN turnover (within SQN window).

> > I agree most of implementation today just increment one for sequence
> > number.
>=20
> > Is there any description in RFC3775  saying that MN must increment
> > sequentially for Seq number?
>=20
> =3D> I think RFC3775 just mention that it should be larger.

Ok

ryuji

>=20
> Regards,
>=20
> Wassim H.
>=20
>=20
> > On 2005/07/12, at 12:50, Wassim Haddad wrote:
> >
> > > Hi Rajeev,
> > >
> > > Thanks for writing this draft.
> > >
> > > I just want to add that tracing the BU messages via the sequence
> > > number
> > > can also reveal in real time to an eavesdropper the path taken by an
> > > unknown mobile node, i.e., by linking the BU messages and consequently
> > > the pseudo-IP addresses.
> > > However, the ability to follow the movements in real time, combined
> > > with
> > > some prior infos about one particular target can lead to break the
> > > user's
> > > anonymity.
> > >
> > > IMHO, it makes sense to add such scenario in the problem statement.
> =C3> >
> > > We have addressed this particular issue in our "anonymity and
> > > unlinkability
> > > solution for omipv6" (draft-haddad-privacy-omipv6-anonymity-00).
> > >
> > >
> > > Regards,
> > >
> > > Wassim H.
> > >
> > >
> > > On Mon, 11 Jul 2005, Rajeev Koodli wrote:
> > >
> > >
> > >>
> > >> Hello folks,
> > >>
> > >> I submitted the draft on Friday, I believe with the correct
> > >> boilerplate
> > >> (see attached draft). I still got an error message.
> > >>
> > >> Anyway, please find the Location Privacy Problem Statement draft.
> > >>
> > >> Regards,
> > >>
> > >> -Rajeev
> > >>
> > >>
> > >>
> > >>> -----Original Message-----
> > >>>
> > >>
> > >>
> > >>> From:     Koodli Rajeev (Nokia-NRC/MtView)
> > >>> Sent:    Friday, July 08, 2005 7:42 PM
> > >>> To:    'internet-drafts@ietf.org'
> > >>> Subject:    resubmit draft-irtf-mobopts-location-privacy-
> > >>> ps-00.txt with revised boilerplate
> > >>>
> > >>>
> > >>> Here it is..
> > >>>
> > >>> Thanks,
> > >>>
> > >>> -Rajeev Koodli
> > >>>
> > >>>
> > >>>>  <<draft-irtf-mobopts-location-privacy-ps-00.txt>>
> > >>>>
> > >>>
> > >>> http://people.nokia.net/~rajeev
> > >>>
> > >>>
> > >>
> > >>
> > >>
> > >>
> > >
> > > _______________________________________________
> > > Mobopts mailing list
> > > Mobopts@irtf.org
> > > https://www1.ietf.org/mailman/listinfo/mobopts
> > >
> > >
> >
> >
> >
>=20

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



From mip6-bounces@ietf.org Wed Aug 03 05:04:37 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E0FAz-0002vL-0N; Wed, 03 Aug 2005 05:04:37 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1E0FAw-0002tZ-3r
	for mip6@megatron.ietf.org; Wed, 03 Aug 2005 05:04:34 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA26471
	for <mip6@ietf.org>; Wed, 3 Aug 2005 05:04:31 -0400 (EDT)
Received: from neon.tcs.hut.fi ([130.233.215.20])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E0FhZ-0004sB-AW
	for mip6@ietf.org; Wed, 03 Aug 2005 05:38:18 -0400
Received: from rhea.tcs.hut.fi (rhea.tcs.hut.fi [130.233.215.147])
	by neon.tcs.hut.fi (Postfix) with ESMTP
	id 8671E8004B0; Wed,  3 Aug 2005 12:04:22 +0300 (EEST)
Date: Wed, 3 Aug 2005 12:04:22 +0300 (EEST)
From: Wassim Haddad <whaddad@tcs.hut.fi>
To: Qiu Ying <qiuying@i2r.a-star.edu.sg>
Subject: Re: [Mobopts] Re: [Mip6] [Fwd: FW:resubmit draft-irtf-mobopts-locat
	ion-privacy-ps-00.txtwith revised boilerplate]
In-Reply-To: <866fa8ca76aa.42f0e643@i2r.a-star.edu.sg>
Message-ID: <Pine.LNX.4.58.0508031158140.1505@rhea.tcs.hut.fi>
References: <866fa8ca76aa.42f0e643@i2r.a-star.edu.sg>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 2.4 (++)
X-Scan-Signature: 789c141a303c09204b537a4078e2a63f
Cc: mip6@ietf.org, Ryuji Wakikawa <ryuji@sfc.wide.ad.jp>,
	Rajeev Koodli <rajeev@iprg.nokia.com>, mobopts@irtf.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

On Wed, 3 Aug 2005, Qiu Ying wrote:

> Hi,
> Yes, RFC3775 only mentions that the SQN should be larger than the previous one. The new issue is how to let
> the receiver know the increment if we does not use a fixed one..

=> IMHO, the CN can compute the "next", i.e., expected SQN, in the same way as the MN. In this case, if the
new BU message sent by the MN does not carry the expected SQN, then it will be rejected.


Regards,

Wassim H.


> -- Qiu Ying
>
> ----- Original Message -----
> From: Rajeev Koodli <rajeev@iprg.nokia.com>
> Date: Wednesday, August 3, 2005 1:30 am
> Subject: Re: [Mobopts] Re: [Mip6] [Fwd: FW:resubmit	draft-irtf-mobopts-locat ion-privacy-ps-00.txtwith revised	boilerplate]
>
> >
> >
> > Ryuji Wakikawa wrote:
> >
> > > Hi Wassim
> > >
> > > I agree most of implementation today just increment one for
> > sequence
> > > number.
> > > Is there any description in RFC3775  saying that MN must
> > increment
> > > sequentially for Seq number?
> >
> > I was looking for that. I could not find text that says the Sequence
> > Number must be incremented by one. The only requirement is that it is
> > greater than the previous one.
> >
> > -Rajeev
> >
> >
> >
> >
> > >
> > > ryuji
> > >
> > >
> > > On 2005/07/12, at 12:50, Wassim Haddad wrote:
> > >
> > >> Hi Rajeev,
> > >>
> > >> Thanks for writing this draft.
> > >>
> > >> I just want to add that tracing the BU messages via the sequence
> > number
> > >> can also reveal in real time to an eavesdropper the path taken
> > by an
> > >> unknown mobile node, i.e., by linking the BU messages and
> > consequently>> the pseudo-IP addresses.
> > >> However, the ability to follow the movements in real time,
> > combined  with
> > >> some prior infos about one particular target can lead to break
> > the
> > >> user's
> > >> anonymity.
> > >>
> > >> IMHO, it makes sense to add such scenario in the problem statement.
> > >>
> > >> We have addressed this particular issue in our "anonymity and
> > >> unlinkability
> > >> solution for omipv6" (draft-haddad-privacy-omipv6-anonymity-00).
> > >>
> > >>
> > >> Regards,
> > >>
> > >> Wassim H.
> > >>
> > >>
> > >> On Mon, 11 Jul 2005, Rajeev Koodli wrote:
> > >>
> > >>
> > >>>
> > >>> Hello folks,
> > >>>
> > >>> I submitted the draft on Friday, I believe with the correct
> > boilerplate>>> (see attached draft). I still got an error message.
> > >>>
> > >>> Anyway, please find the Location Privacy Problem Statement draft.
> > >>>
> > >>> Regards,
> > >>>
> > >>> -Rajeev
> > >>>
> > >>>
> > >>>
> > >>>> -----Original Message-----
> > >>>>
> > >>>
> > >>>
> > >>>> From:     Koodli Rajeev (Nokia-NRC/MtView)
> > >>>> Sent:    Friday, July 08, 2005 7:42 PM
> > >>>> To:    'internet-drafts@ietf.org'
> > >>>> Subject:    resubmit draft-irtf-mobopts-location-privacy- ps-
> > 00.txt
> > >>>> with revised boilerplate
> > >>>>
> > >>>>
> > >>>> Here it is..
> > >>>>
> > >>>> Thanks,
> > >>>>
> > >>>> -Rajeev Koodli
> > >>>>
> > >>>>
> > >>>>>  <<draft-irtf-mobopts-location-privacy-ps-00.txt>>
> > >>>>>
> > >>>>
> > >>>> http://people.nokia.net/~rajeev
> > >>>>
> > >>>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>
> > >> _______________________________________________
> > >> Mobopts mailing list
> > >> Mobopts@irtf.org
> > >> https://www1.ietf.org/mailman/listinfo/mobopts
> > >>
> > >>
> > >
> > >
> > > _______________________________________________
> > > Mip6 mailing list
> > > Mip6@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/mip6
> >
> >
> > _______________________________________________
> > Mobopts mailing list
> > Mobopts@irtf.org
> > https://www1.ietf.org/mailman/listinfo/mobopts
> >
>
>
>

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



From mip6-bounces@ietf.org Wed Aug 03 05:16:02 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E0FM2-000898-RC; Wed, 03 Aug 2005 05:16:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1E0FM0-00087u-5K
	for mip6@megatron.ietf.org; Wed, 03 Aug 2005 05:16:00 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA27188
	for <mip6@ietf.org>; Wed, 3 Aug 2005 05:15:57 -0400 (EDT)
Received: from rodin.i2r.a-star.edu.sg ([192.122.139.27])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E0Fsd-0005PN-69
	for mip6@ietf.org; Wed, 03 Aug 2005 05:49:44 -0400
Received: from rodin.i2r.a-star.edu.sg (localhost [127.0.0.1])
	by rodin.i2r.a-star.edu.sg (8.13.1/8.13.1) with ESMTP id j739Fg66012532
	for <mip6@ietf.org>; Wed, 3 Aug 2005 17:15:42 +0800 (SGT)
Received: from newmailhost.i2r.a-star.edu.sg ([192.122.134.76])by rodin.i2r.
	a-star.edu.sg (8.13.1/8.13.1) with ESMTP id j739Fgou012520for
	<mip6@ietf.or g>; Wed, 3 Aug 2005 17:15:42 +0800 (SGT)
Received: from i2r.a-star.edu.sg ([192.168.137.63])by mailhost.lit.org.sg (S
	un Java System Messaging Server 6.1 HotFix 0.06(built Nov 11 2004))
	with ES
	MTP id <0IKN009UC32AHU10@mailhost.lit.org.sg> formip6@ietf.org;
	Wed, 03 Aug 2005 17:15:46 +0800 (SGT)
Date: Wed, 03 Aug 2005 17:15:23 +0800
From: Jianying Zhou <jyzhou@i2r.a-star.edu.sg>
Subject: Re: [Mobopts] Re: [Mip6] [Fwd: FW:resubmit draft-irtf-mobopts-locat
	ion-privacy-ps-00.txtwith revised boilerplate]
To: Wassim Haddad <whaddad@tcs.hut.fi>
Message-id: <42F08B2B.5010909@i2r.a-star.edu.sg>
MIME-version: 1.0
Content-type: text/plain;
	charset=us-ascii;
	format=flowed
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en
References: <866fa8ca76aa.42f0e643@i2r.a-star.edu.sg><Pine.LNX.4.58.05080311
	58140.1505@rhea.tcs.hut.fi>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.1)Gecko/2
	0020823 Netscape/7.0
X-imss-version: 2.29
X-imss-result: Passed
X-imss-scores: Clean:99.90000 C:2 M:3 S:5 R:5
X-imss-settings: Baseline:5 C:4 M:4 S:4 R:4 (1.5000 1.5000)
X-Spam-Score: 2.4 (++)
X-Scan-Signature: c83ccb5cc10e751496398f1233ca9c3a
Content-Transfer-Encoding: 7BIT
Cc: mip6@ietf.org, Qiu Ying <qiuying@i2r.a-star.edu.sg>,
	Rajeev Koodli <rajeev@iprg.nokia.com>, mobopts@irtf.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

Is the algorithm confidential (only known to MN and CN)?

- If yes, how to share the secret?
- If not, an eavesdropper can calculate in the same way.

Jianying Zhou



Wassim Haddad wrote:

>On Wed, 3 Aug 2005, Qiu Ying wrote:
>
>  
>
>>Hi,
>>Yes, RFC3775 only mentions that the SQN should be larger than the previous one. The new issue is how to let
>>the receiver know the increment if we does not use a fixed one..
>>    
>>
>
>=> IMHO, the CN can compute the "next", i.e., expected SQN, in the same way as the MN. In this case, if the
>new BU message sent by the MN does not carry the expected SQN, then it will be rejected.
>
>
>Regards,
>
>Wassim H.
>
>
>  
>
>>-- Qiu Ying
>>
>>----- Original Message -----
>>From: Rajeev Koodli <rajeev@iprg.nokia.com>
>>Date: Wednesday, August 3, 2005 1:30 am
>>Subject: Re: [Mobopts] Re: [Mip6] [Fwd: FW:resubmit	draft-irtf-mobopts-locat ion-privacy-ps-00.txtwith revised	boilerplate]
>>
>>    
>>
>>>Ryuji Wakikawa wrote:
>>>
>>>      
>>>
>>>>Hi Wassim
>>>>
>>>>I agree most of implementation today just increment one for sequence number.
>>>>Is there any description in RFC3775  saying that MN must increment
>>>>        
>>>>
>>>>sequentially for Seq number?
>>>>        
>>>>
>>>I was looking for that. I could not find text that says the Sequence
>>>Number must be incremented by one. The only requirement is that it is
>>>greater than the previous one.
>>>
>>>-Rajeev
>>>
>>>
>>>
>>>
>>>      
>>>
>>>>ryuji
>>>>
>>>>
>>>>On 2005/07/12, at 12:50, Wassim Haddad wrote:
>>>>
>>>>        
>>>>
>>>>>Hi Rajeev,
>>>>>
>>>>>Thanks for writing this draft.
>>>>>
>>>>>I just want to add that tracing the BU messages via the sequence number
>>>>>          
>>>>>
>>>>>can also reveal in real time to an eavesdropper the path taken by an
>>>>>          
>>>>>
>>>>>unknown mobile node, i.e., by linking the BU messages and
>>>>>          
>>>>>
>>>consequently>> the pseudo-IP addresses.
>>>      
>>>
>>>>>However, the ability to follow the movements in real time, combined  with
>>>>>          
>>>>>
>>>>>some prior infos about one particular target can lead to break the
>>>>>          
>>>>>
>>>>>user's anonymity.
>>>>>
>>>>>IMHO, it makes sense to add such scenario in the problem statement.
>>>>>
>>>>>We have addressed this particular issue in our "anonymity and
>>>>>unlinkability
>>>>>solution for omipv6" (draft-haddad-privacy-omipv6-anonymity-00).
>>>>>
>>>>>
>>>>>Regards,
>>>>>
>>>>>Wassim H.
>>>>>
>>>>>
>>>>>          
>>>>>



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



From mip6-bounces@ietf.org Wed Aug 03 05:18:32 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E0FOS-0001eZ-2x; Wed, 03 Aug 2005 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 1E0FOP-0001Yl-VB
	for mip6@megatron.ietf.org; Wed, 03 Aug 2005 05:18:30 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA27382
	for <mip6@ietf.org>; Wed, 3 Aug 2005 05:18:27 -0400 (EDT)
Received: from neon.tcs.hut.fi ([130.233.215.20])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E0Fv4-0005W7-Gd
	for mip6@ietf.org; Wed, 03 Aug 2005 05:52:15 -0400
Received: from rhea.tcs.hut.fi (rhea.tcs.hut.fi [130.233.215.147])
	by neon.tcs.hut.fi (Postfix) with ESMTP
	id 3EAAC8004B0; Wed,  3 Aug 2005 12:18:20 +0300 (EEST)
Date: Wed, 3 Aug 2005 12:18:20 +0300 (EEST)
From: Wassim Haddad <whaddad@tcs.hut.fi>
To: Jianying Zhou <jyzhou@i2r.a-star.edu.sg>
Subject: Re: [Mobopts] Re: [Mip6] [Fwd: FW:resubmit draft-irtf-mobopts-locat
	ion-privacy-ps-00.txtwith revised boilerplate]
In-Reply-To: <42F08B2B.5010909@i2r.a-star.edu.sg>
Message-ID: <Pine.LNX.4.58.0508031216400.1505@rhea.tcs.hut.fi>
References: <866fa8ca76aa.42f0e643@i2r.a-star.edu.sg><Pine.LNX.4.58.05080311
	58140.1505@rhea.tcs.hut.fi> <42F08B2B.5010909@i2r.a-star.edu.sg>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 2.4 (++)
X-Scan-Signature: 1676547e4f33b5e63227e9c02bd359e3
Cc: mip6@ietf.org, Qiu Ying <qiuying@i2r.a-star.edu.sg>,
	Rajeev Koodli <rajeev@iprg.nokia.com>, mobopts@irtf.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

On Wed, 3 Aug 2005, Jianying Zhou wrote:

> Is the algorithm confidential (only known to MN and CN)?
>
> - If yes, how to share the secret?

=> Yes it is confidential. Please check draft-haddad-privacy-omipv6-anonymity-00


Regards,

Wassim H.



> Wassim Haddad wrote:
>
> >On Wed, 3 Aug 2005, Qiu Ying wrote:
> >
> >
> >
> >>Hi,
> >>Yes, RFC3775 only mentions that the SQN should be larger than the previous one. The new issue is how to let
> >>the receiver know the increment if we does not use a fixed one..
> >>
> >>
> >
> >=> IMHO, the CN can compute the "next", i.e., expected SQN, in the same way as the MN. In this case, if the
> >new BU message sent by the MN does not carry the expected SQN, then it will be rejected.
> >
> >
> >Regards,
> >
> >Wassim H.
> >
> >
> >
> >
> >>-- Qiu Ying
> >>
> >>----- Original Message -----
> >>From: Rajeev Koodli <rajeev@iprg.nokia.com>
> >>Date: Wednesday, August 3, 2005 1:30 am
> >>Subject: Re: [Mobopts] Re: [Mip6] [Fwd: FW:resubmit	draft-irtf-mobopts-locat ion-privacy-ps-00.txtwith revised	boilerplate]
> >>
> >>
> >>
> >>>Ryuji Wakikawa wrote:
> >>>
> >>>
> >>>
> >>>>Hi Wassim
> >>>>
> >>>>I agree most of implementation today just increment one for sequence number.
> >>>>Is there any description in RFC3775  saying that MN must increment
> >>>>
> >>>>
> >>>>sequentially for Seq number?
> >>>>
> >>>>
> >>>I was looking for that. I could not find text that says the Sequence
> >>>Number must be incremented by one. The only requirement is that it is
> >>>greater than the previous one.
> >>>
> >>>-Rajeev
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>>ryuji
> >>>>
> >>>>
> >>>>On 2005/07/12, at 12:50, Wassim Haddad wrote:
> >>>>
> >>>>
> >>>>
> >>>>>Hi Rajeev,
> >>>>>
> >>>>>Thanks for writing this draft.
> >>>>>
> >>>>>I just want to add that tracing the BU messages via the sequence number
> >>>>>
> >>>>>
> >>>>>can also reveal in real time to an eavesdropper the path taken by an
> >>>>>
> >>>>>
> >>>>>unknown mobile node, i.e., by linking the BU messages and
> >>>>>
> >>>>>
> >>>consequently>> the pseudo-IP addresses.
> >>>
> >>>
> >>>>>However, the ability to follow the movements in real time, combined  with
> >>>>>
> >>>>>
> >>>>>some prior infos about one particular target can lead to break the
> >>>>>
> >>>>>
> >>>>>user's anonymity.
> >>>>>
> >>>>>IMHO, it makes sense to add such scenario in the problem statement.
> >>>>>
> >>>>>We have addressed this particular issue in our "anonymity and
> >>>>>unlinkability
> >>>>>solution for omipv6" (draft-haddad-privacy-omipv6-anonymity-00).
> >>>>>
> >>>>>
> >>>>>Regards,
> >>>>>
> >>>>>Wassim H.
> >>>>>
> >>>>>
> >>>>>
> >>>>>
>
>
>
>

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



From mip6-bounces@ietf.org Wed Aug 03 09:09:18 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E0Izm-0008OV-DJ; Wed, 03 Aug 2005 09:09:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DyzWA-0006dI-D3; Sat, 30 Jul 2005 18:09:18 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01741;
	Sat, 30 Jul 2005 18:09:16 -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.43)
	id 1Dz026-0003C3-Dl; Sat, 30 Jul 2005 18:42:19 -0400
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-3.cisco.com with ESMTP; 30 Jul 2005 15:09:03 -0700
X-IronPort-AV: i="3.95,155,1120460400"; 
	d="scan'208"; a="327549375:sNHT32322660"
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j6UM93Is027742;
	Sat, 30 Jul 2005 15:09:03 -0700 (PDT)
Received: from xmb-rtp-211.amer.cisco.com ([64.102.31.118]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Sat, 30 Jul 2005 18:09:02 -0400
Received: from 10.86.240.20 ([10.86.240.20]) by xmb-rtp-211.amer.cisco.com
	([64.102.31.118]) via Exchange Front-End Server email.cisco.com
	([144.254.231.73]) with Microsoft Exchange Server HTTP-DAV ; 
	Sat, 30 Jul 2005 22:09:01 +0000
Received: from 98.20.242.10.in-addr.arpa by email.cisco.com;
	30 Jul 2005 22:09:44 +0000
From: Ralph Droms <rdroms@cisco.com>
To: shim6@psg.com, mipshop@ietf.org, ipv6@ietf.org, mip6@ietf.org
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Date: Sat, 30 Jul 2005 18:09:43 -0400
Message-Id: <1122761384.5750.29.camel@98.20.242.10.in-addr.arpa>
Mime-Version: 1.0
X-Mailer: Evolution 2.0.4 (2.0.4-2) 
X-OriginalArrivalTime: 30 Jul 2005 22:09:02.0703 (UTC)
	FILETIME=[4B3CD7F0:01C59553]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 03 Aug 2005 09:09:17 -0400
Cc: 
Subject: [Mip6] Report on IPv6 network renumbering at v6ops WG
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

At the v6ops WG meeting (1400 Mon), there will be a report from the
participants in a recently completed project in IPv6 network
renumbering.  I've included a description of the report below.  Anyone
interested in hearing the results of this project and participating in a
discussion about what we should consider as next steps to build on these
results is invited to attend.

- Ralph Droms

                Discussion of IPv6 Network Renumbering
                --------------------------------------

Baker, et al., have written a description a process for IPv6 network
renumbering in "Procedures for Renumbering an IPv6 Network without a
Flag Day" <draft-ietf-v6ops-renumbering-procedure-05.txt>.  Teams from
University of Southampton, the JOIN Project at University of Muenster,
Renater, PSNC and Loria-Inria have conducted a series of experiments
in network renumbering, based on the process described by Baker.
Results from the study include operational experience with the network
renumbering procedure, identification of the effects of network
renumbering on network management tools and other applications and
recommendations for updates to the network renumbering procedure, and
advice for network administrators, application developers and others
to ameliorate the effects of network renumbering.

The purpose of this discussion is to disseminate results and
conclusions from these experiments, stimulate discussion of IPv6
network renumbering and consider future work in this area.  The draft
agenda for the discussion is:

Introduction                             Ralph Droms         ( 5 mins)

Prior art and tools, backbone            JOIN/Univ. Muenster ( 5 mins)
renumbering and BGP issues, SOHO renumbering

Enterprise experiments and               Univ. Southampton   ( 5 mins)
recommendations

Router renumbering protocol, renumbering Renater             ( 5 mins)
procedure gap analysis

Impact of renumbering on management      PSNC                ( 5 mins)
tools

Maintaining management plane during      Loria-Inria         ( 5 mins)
renumbering, monitoring renumbering 

Conclusions                              Ralph Droms         ( 5 mins) 

Discussion                                                   (15 mins)

Next steps?                              Ralph Droms         (10 mins)



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



From mip6-bounces@ietf.org Wed Aug 03 09:09:21 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E0Izm-0008P1-Vi; Wed, 03 Aug 2005 09:09:19 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DzQWq-0002V7-SL
	for mip6@megatron.ietf.org; Sun, 31 Jul 2005 22:59:48 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA03005
	for <mip6@ietf.org>; Sun, 31 Jul 2005 22:59:44 -0400 (EDT)
Received: from ms-smtp-01.nyroc.rr.com ([24.24.2.55])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DzR31-00067G-Mp
	for mip6@ietf.org; Sun, 31 Jul 2005 23:33:04 -0400
Received: from hpn307pc2 (cpe-69-204-120-221.rochester.res.rr.com
	[69.204.120.221])
	by ms-smtp-01.nyroc.rr.com (8.12.10/8.12.10) with SMTP id
	j712xiDX027907
	for <mip6@ietf.org>; Sun, 31 Jul 2005 22:59:44 -0400 (EDT)
Message-ID: <022c01c59645$11554d40$6801a8c0@hpn307pc2>
From: "Wendi Heinzelman" <wheinzel@ece.rochester.edu>
To: <mip6@ietf.org>
Date: Sun, 31 Jul 2005 22:59:43 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Virus-Scanned: Symantec AntiVirus Scan Engine
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 03 Aug 2005 09:09:17 -0400
Subject: [Mip6] MobiCom 2005 discounted registration deadline August 5
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

The deadline for early discounted registration to attend
MobiCom 2005, the Eleventh Annual International Conference
on Mobile Computing and Networking, is August 5, 2005. 
Registration after this date is still available but at the
non-discounted rate.  Registration is available at 
http://www.regmaster.com/mobicom2005.html.


*******************************************************************

                          Call for Participation

   11th Annual International Conference on Mobile Computing and Networking

                    August 28 - September 2, 2005
                          Cologne, Germany

                 http://www.sigmobile.org/mobicom/2005/

*******************************************************************

ACM MobiCom is a highly-selective international conference on mobile
computing and wireless and mobile networking. It serves as the premier 
forum for presenting and discussing research results on networks, systems, 
algorithms, and applications supporting the symbiosis of mobile computing 
and wireless networking. Each year, the conference attracts about 500 
researchers, practitioners, students, and executives. MobiCom 2005 will 
be held in beautiful Cologne, Germany.

Technical Program. The program consists of a single track with 23 
papers.  The authors present cutting-edge results on various topics, such 
as new architectures, content-based and geometric routing, self-management, 
cross-layer optimization. The papers cover ad hoc networks, mesh networks, 
wireless sensor networks, WLANs, and cellular networks. A list of accepted 
papers can be found at http://www.sigmobile.org/mobicom/2005/program.html.

Tutorials. Four tutorials will be offered: (a) Wireless sensor and actuator 
networks, (b) 802.11 WLAN MAC and smart antennas: issues and directions, 
(c) Security in sensor and ad hoc networks: perspectives and status, and (d) 
Wide area wireless networks: 3G and beyond.

The conference will also feature two invited talks by leaders in our field: 
(a) "Secure, Natural Communications," by Jeffrey M. Jaffe, President, Bell 
Labs Research and Advanced Technologies, and (b) "Communicating Vehicles - 
Communicating Roadways: New Approaches to Driver Information and Road 
Safety," by Ralf Guido Herrtwich, Director Vehicle IT and Services Research, 
DaimlerChrysler AG.

Cologne is very popular, especially in August due to World Youth Day 2005 
taking place there. Because Pope Benedict XVI organizes this event, he will 
be in town just the week before MobiCom. Thus, we ask you to make your 
hotel and flight reservations as early as possible. For more travel info 
please visit http://www.sigmobile.org/mobicom/2005/travel.html.




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



From mip6-bounces@ietf.org Wed Aug 03 09:09:22 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E0Izq-0008PQ-5p; Wed, 03 Aug 2005 09:09:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DzV9C-0004BR-Bb; Mon, 01 Aug 2005 03:55:42 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02643;
	Mon, 1 Aug 2005 03:55:38 -0400 (EDT)
Received: from rodin.i2r.a-star.edu.sg ([192.122.139.27])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1DzVfL-00027l-PI; Mon, 01 Aug 2005 04:28:59 -0400
Received: from rodin.i2r.a-star.edu.sg (localhost [127.0.0.1])
	by rodin.i2r.a-star.edu.sg (8.13.1/8.13.1) with ESMTP id j717tFRr023780;
	Mon, 1 Aug 2005 15:55:15 +0800 (SGT)
Received: from newmailhost.i2r.a-star.edu.sg ([192.122.134.76])by rodin.i2r.
	a-star.edu.sg (8.13.1/8.13.1) with ESMTP id j717tEac023762;
	Mon, 1 Aug 2005 15:55:14 +0800 (SGT)
Received: from bearty1 ([192.168.152.200])by mailhost.lit.org.sg (Sun Java S
	ystem Messaging Server 6.1 HotFix 0.06(built Nov 11 2004)) with SMTP id
	<0I KJ00DKGA020200@mailhost.lit.org.sg>;
	Mon,01 Aug 2005 15:55:14 +0800 (SGT)
Date: Mon, 01 Aug 2005 15:55:16 +0800
From: Boon Sain Yeo <yeobs@i2r.a-star.edu.sg>
To: <Undisclosed-Recipient:@ietf.org;>
Message-id: <002301c5966e$5b735060$c898a8c0@bearty1>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-Priority: 3
X-MSMail-priority: Normal
X-imss-version: 2.29
X-imss-result: Passed
X-imss-scores: Clean:99.90000 C:2 M:3 S:5 R:5
X-imss-settings: Baseline:5 C:4 M:4 S:4 R:4 (1.5000 1.5000)
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 4b66a1e94d7d92973ece9e5da449ff80
X-Mailman-Approved-At: Wed, 03 Aug 2005 09:09:16 -0400
Cc: 
Subject: [Mip6] CFP - SensorWare 06
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="===============0845881665=="
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0845881665==
Content-type: multipart/alternative;
	boundary="Boundary_(ID_DwCuYlEEv7aT7u4VrVPOzQ)"

This is a multi-part message in MIME format.

--Boundary_(ID_DwCuYlEEv7aT7u4VrVPOzQ)
Content-type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7BIT


(My apologies if you receive multiple copies of this message)

***********************************************************
1st International Workshop on Software for Sensor Networks (SensorWare) - CFP
***********************************************************
 

Welcome to the 1st International Workshop on Software for Sensor Networks (SensorWare) to be held on the 8 January 2006. The workshop is held in conjunction with COMSWARE 2006 in the beautiful and historical city of New Delhi.


Advances in technology have made deployment of miniature sensors a realistic proposition. These sensors are low-power, inexpensive, smart devices with multiple on-board sensors, and are connected through wireless links, so as to form a collaborative sensor network to perform a specific task. As a result, it opens up a new paradigm of ubiquitous computing and enables a range of applications that are previously unrealizable or too costly to be realized. However, given the limitation of on-board hardware, one of the key areas towards achieving superior performance is through the software implementation. The workshop is intended for the presentation and discussion of novel algorithms and software implementation for sensor networks. This workshop, intends to bring together engineering experts and academicians to discuss the current status, technical challenges, standards, fundamental issues, and future services and applications in the form of panels and technical presentation.



Topics of interest include but are not limited to the following:



Operating System 
Efficient algorithms 
Protocol design 
Performance analysis 
Performance related issues 
Sensor applications 
Deployment issues and scenarios 
Middleware 
Sensor security 
Sensor network design and modeling 
 

Workshop co-chairs:

Nirmala Shenoy (ns@rit.edu), RIT, USA
Boon Sain Yeo (boonyeo@ieee.org), Institute for Infocomm Research, Singapore 



TPC Members:

Holger Karl, University of Paderborn, Germany,
Ling-Jyh Chen, Academia Sinica, Taiwan
Kui Wu, University of Victoria, Canada,
Daeyoung Kim, ICU, Korea
Leonard Barolli, Fukuoka Institute of Technology, Japan,
Wei-Peng, Fujitsu Labs of America, USA
Jason Redi, BBN Technologies, USA      
Biao Chen, Syracuse University, USA
Hairong  Qi, University of Tennessee, USA
Xiaojun Cao, Rochester Institute of Technology, USA
Xin Wang, University of Buffalo, USA
James Minseok Kwon, RIT, USA
Wenye Wang, North Carolina State University, USA
Fei Hu, RIT, USA
Robin Chellappa, Deakin Univeristy, Australia  

Technical Papers has to be submitted to the co-chairs at boonyeo@ieee.org. 

Papers should be written in English and should preferably follow the instructions in template.pdf. Preferred maximum paper length is 6 printed pages (10-point font) including figures.


Important Dates:

Paper Submission Deadline: 1 September 2005
Notification Acceptance/Rejection: 1 October 2005
Final Camera-Ready Paper Submission: 1 November 2005

Please visit the workshop website at http://www.sensorware.org for more info.

We look forward to seeing you at SensorWare.

Many thanks
Best regards,

Boon and Nirmala
Workshop co-chairs

--Boundary_(ID_DwCuYlEEv7aT7u4VrVPOzQ)
Content-type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns:o =3D "urn:schemas-microsoft-com:office:office" xmlns:st1 =
=3D=20
"urn:schemas-microsoft-com:office:smarttags"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2668" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>(My apologies if you receive multiple =
copies of=20
this message)</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial=20
size=3D2>***********************************************************<BR>1=
st=20
International Workshop on Software for Sensor Networks (SensorWare) =96=20
CFP<BR>***********************************************************<BR>&nb=
sp;</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Welcome to the 1st International =
Workshop on=20
Software for Sensor Networks (SensorWare) to be held on the 8 January =
2006. The=20
workshop is held in conjunction with COMSWARE 2006 in the beautiful and=20
historical city of New Delhi.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Advances in technology have made =
deployment of=20
miniature sensors a realistic proposition. These sensors are low-power,=20
inexpensive, smart devices with multiple on-board sensors, and are =
connected=20
through wireless links, so as to form a collaborative sensor network to =
perform=20
a specific task. As a result, it opens up a new paradigm of ubiquitous =
computing=20
and enables a range of applications that are previously unrealizable or =
too=20
costly to be realized. However, given the limitation of on-board =
hardware, one=20
of the key areas towards achieving superior performance is through the =
software=20
implementation. The workshop is intended for the presentation and =
discussion of=20
novel algorithms and software implementation for sensor networks. This =
workshop,=20
intends to bring together engineering experts and academicians to =
discuss the=20
current status, technical challenges, standards, fundamental issues, and =
future=20
services and applications in the form of panels and technical=20
presentation.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Topics of interest include but are not =
limited to=20
the following:</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Operating System <BR>Efficient =
algorithms=20
<BR>Protocol design <BR>Performance analysis <BR>Performance related =
issues=20
<BR>Sensor applications <BR>Deployment issues and scenarios =
<BR>Middleware=20
<BR>Sensor security <BR>Sensor network design and=20
modeling&nbsp;<BR>&nbsp;</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Workshop co-chairs:</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Nirmala Shenoy (<A=20
href=3D"mailto:ns@rit.edu">ns@rit.edu</A>), RIT, USA<BR>Boon Sain Yeo =
(<A=20
href=3D"mailto:boonyeo@ieee.org">boonyeo@ieee.org</A>), Institute for =
Infocomm=20
Research, Singapore </FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>TPC Members:</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Holger Karl, University of Paderborn,=20
Germany,<BR>Ling-Jyh Chen, Academia Sinica, Taiwan<BR>Kui Wu, University =
of=20
Victoria, Canada,<BR>Daeyoung Kim, ICU, Korea<BR>Leonard Barolli, =
Fukuoka=20
Institute of Technology, Japan,<BR>Wei-Peng, Fujitsu Labs of America,=20
USA<BR>Jason Redi, BBN Technologies, USA&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<BR>Biao=20
Chen, Syracuse University, USA<BR>Hairong&nbsp; Qi, University of =
Tennessee,=20
USA<BR>Xiaojun Cao, Rochester Institute of Technology, USA<BR>Xin Wang,=20
University of Buffalo, USA<BR>James Minseok Kwon, RIT, USA<BR>Wenye =
Wang, North=20
Carolina State University, USA<BR>Fei Hu, RIT, USA<BR>Robin Chellappa, =
Deakin=20
Univeristy, Australia&nbsp; </FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Technical Papers has to be submitted to =
the=20
co-chairs at <A href=3D"mailto:boonyeo@ieee.org">boonyeo@ieee.org</A>.=20
</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Papers should be written in English and =
should=20
preferably follow the instructions in template.pdf. Preferred maximum =
paper=20
length is 6 printed pages (10-point font) including =
figures.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><BR>Important Dates:</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Paper Submission Deadline: 1 September=20
2005<BR>Notification Acceptance/Rejection: 1 October 2005<BR>Final =
Camera-Ready=20
Paper Submission: 1 November 2005</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Please visit the workshop website at <A =

href=3D"http://www.sensorware.org">http://www.sensorware.org</A> for =
more=20
info.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>We look forward to seeing you at=20
SensorWare.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Many thanks<BR>Best =
regards,</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Boon and Nirmala<BR>Workshop=20
co-chairs</FONT></DIV></BODY></HTML>

--Boundary_(ID_DwCuYlEEv7aT7u4VrVPOzQ)--


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

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

--===============0845881665==--




From mip6-bounces@ietf.org Wed Aug 03 09:09:22 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E0Izq-0008Pp-PO; Wed, 03 Aug 2005 09:09:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dzd8j-0000Fd-DE; Mon, 01 Aug 2005 12:27:45 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22150;
	Mon, 1 Aug 2005 12:27:42 -0400 (EDT)
Received: from mantis.cs.colorado.edu ([128.138.206.34])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Dzdf1-000113-Hb; Mon, 01 Aug 2005 13:01:08 -0400
Received: from mantis.cs.colorado.edu (localhost [127.0.0.1])
	by mantis.cs.colorado.edu (Postfix) with ESMTP id 05AF9127052;
	Mon,  1 Aug 2005 10:26:09 -0600 (MDT)
X-Original-To: securecomm-cfp@mantis.cs.colorado.edu
Delivered-To: securecomm-cfp@mantis.cs.colorado.edu
Received: from research.cs.colorado.edu (research.cs.colorado.edu
	[128.138.242.225])
	by mantis.cs.colorado.edu (Postfix) with ESMTP id 9EB4512704B
	for <securecomm-cfp@mantis.cs.colorado.edu>;
	Mon,  1 Aug 2005 10:23:57 -0600 (MDT)
Received: from [127.0.0.1] (c-24-8-166-41.hsd1.co.comcast.net [24.8.166.41])
	by research.cs.colorado.edu (8.12.10/8.12.6) with ESMTP id
	j71GP30h002301 for <securecomm-cfp@mantis.cs.colorado.edu>;
	Mon, 1 Aug 2005 10:25:04 -0600 (MDT)
Message-ID: <42EE4CD6.4000009@cs.colorado.edu>
Date: Mon, 01 Aug 2005 10:24:54 -0600
From: Richard Han <Richard.Han@Colorado.EDU>
Organization: University of Colorado at Boulder
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: securecomm-cfp@mantis.cs.colorado.edu
Content-Type: text/plain; charset=windows-1252; format=flowed
X-Mailman-Approved-At: Mon, 01 Aug 2005 10:26:06 -0600
X-BeenThere: securecomm-cfp@mantis.cs.colorado.edu
X-Mailman-Version: 2.1.5
Precedence: list
List-Archive: <http://mantis.cs.colorado.edu/pipermail/securecomm-cfp>
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 8eeb555810cda1f2c5989480370dc4ca
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Wed, 03 Aug 2005 09:09:16 -0400
Cc: 
Subject: [Mip6] [Securecomm-cfp] Call For Participation - IEEE/CreateNet
	SecureComm 2005
X-BeenThere: mip6@ietf.org
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

Dear Colleague,

  Please find attached the call for participation for the First
  IEEE/CreateNet International Conference on Security and Privacy for
  Emerging Areas in Communication Networks (SecureComm 2005) to be held
  in Athens, Greece from Sep. 5-9, 2005.

  The conference program consists of 32 full papers and 20 short
  papers, keynote and invited talks, and a panel. In addition, there
  are four workshops on related topics. The complete information is
  available on the website: www.securecomm.org

  Note that Early Conference Registration Ends August 25, 2005!
  Discounted Hotel Reservation Rates end August 22, 2005.

  We apologize if you receive multiple copies of this message. Please
  feel free to distribute this to colleagues who might be interested.

regards,

SecureComm 2005 Organizing  Committee

    ***************************************************************
			CALL FOR PARTICIPATION

       First IEEE/CreateNet International Conference on Security
        and Privacy for Emerging Areas in Communication Networks

        Athens, Greece / Hotel Amarilia / 5 - 9 September, 2005
			  www.securecomm.org

	       EARLY REGISTRATION ENDS August 25, 2005

			   CO-SPONSORED BY:
	     IEEE Communications Society (www.comsoc.org)
		    CreateNet (www.create-net.it)

		    Corporate/Government Sponsors:

	     National Science Foundation (Travel Grants)
	       Telcordia Technologies (Silver sponsor)
		     Toshiba TARI(Bronze sponsor)

In Cooperation With the IEEE Computer Society TC on Security and Privacy
		    In Cooperation with ACM SIGSAC

    ***************************************************************

TENTATIVE TECHNICAL PROGRAM

Monday, Sep 5, 2005

First IEEE/CreateNet International Workshop on Computer Network=20
Forensics Research
(CNFR): www.cnfr.org

First IEEE/CreateNet International Workshop on Trust and Security in=20
Pervasive
Networking: http://www.securecomm.org/pervasivetrust/

***************************************************************

Tuesday, Sep 6, 2005

8.30AM - 9.00 AM: Welcome, Introduction, Best Paper award

9.00AM - 10.30AM: Plenary Session:

         Bill Cheswick, Lumeta, Title: Pondering and Patrolling Network
         Perimeters

         Andrea Servida, EU, Title: Security, privacy and dependability
	in Information  Society: key challenges for European R&D in FP7

10.30AM - 11.00AM: Break

11.00AM - 12.40PM: Full Paper Session 1: Insecurity

Implications of Unlicensed Mobile Access (UMA) for  GSM security
		Sandro Grech, Pasi Eronen=09

Computationally, Memory and Bandwidth Efficient Distillation Codes to
Mitigate DoS in  Multicast
		Roberto Di Pietro, Stefano Chessa, Piero Maestrini
	=09
Spread Identity mechanisms for Security
		Dhananjay Phatak
	=09
On the Security of Distributed Position Services
		Xiaoxin Wu, Cristina Nita-Rotaru
	=09
12.40PM - 2:00PM: Lunch

2:00PM - 2.45PM: Invited talk: David Wagner, Berkeley, Title: Privacy
in pervasive  computing: What can technologists do?

3:00 PM - 4:40 PM: Full Paper Session 2: RFID

Picking Virtual Pockets using Relay Attacks on Contactless Smartcard Syst=
ems
		Ziv Kfir, Avishai Wool
	=09
A Lightweight RFID Protocol to protect against Traceability and Cloning=20
attacks
		Tassos Dimitriou
	=09
An RFID distance bounding protocol
		Gerhard Hancke, Markus Kuhn
=09
Security and Privacy Issues in e-Passports
		Ari Juels, David Molnar, David Wagner

5:00 PM - 6.30PM: Panel 1: RFID Security and Privacy,

	Panelists: (Lead) Gene Tsudik, University of California, Irvine
		   David Wagner, University of California, Berkeley
		   Avishai Wool, Tel Aviv University
		   Tassos D. Dimitriou, Athens Information Technology
		   Markus Kuhn, University of Cambridge

***************************************************************

Wednesday, Sep 7, 2005

8.30AM - 9.15 AM: Keynote: Jean Pierre-Hubaux, EPFL, Title: The Security =
of
Vehicular Networks

DEMOS: 10:45AM - 1:00PM and 2:45PM - 5:00PM
(In parallel with other sessions)=09

"MANET-DFA: Distributed Firewall Architecture for MANET networks,"
Federico Frosali, Giorgio Freguglia, Luciana Costa from Business
Application & Services - Telecomitalia LAB - ITALY

"Demonstration of Ubiquitous Roaming Technology,"
Hiroyoshi Takiguchi, Masami Ueno, Yoshiko Sudeda, Satashi Yagi,
Hirokazu Kitami, Toru Kobayashi, Yoshikazu Kondo from NTT Information
Sharing Platform Laboratories - Tokyo - Japan

9.30AM - 10.45AM: Full Paper Session 3: Sensor Networks

DICAS: Detection, Diagnosis and Isolation of Control Attacks in Sensor=20
Networks
		Issa Khalil, Saurabh Bagchi, Cristina Nita-Rotaru
	=09
Securing Topology Maintenance Protocols for sensor networks: attacks
and counter-measures
		Andrea Gabrielli, Luigi Mancini, Sanjeev Setia, Sushil Jajodia
	=09
Countermeasures Against Traffic Analysis Attacks in Wireless Sensor Netwo=
rks
		Jing Deng, Richard Han, Shivakant Mishra
	=09
11.00AM - 12.40PM: Full Paper Session 4: Authentication

Improving Cross-domain Authentication over Wireless Local Area Networks
		Hahnsang Kim, Kang Shin, Walid Dabbous
	=09
Reducing Reauthentication Delay in Wireless Networks
		Tuomas Aura, Michael Roe

Providing Distributed Certificate Authority Service in Mobile Ad Hoc=20
Networks
		Ying Dong, Wing Go, Aifen Sui, Victor Li, Lucas C.K. Hui, Siu Ming Yiu
	=09
On Improving the Performance of Role-Based Cascaded Delegation in=20
Ubiquitous
Computing
		Danfeng Yao, Roberto Tamassia, Seth Proctor
=09
12.40PM - 2:00PM: Lunch

2:00PM - 2:45PM: Invited Talk: William Arbaugh, Title: Ad-hoc network
security: is  it a real problem?

3:00PM - 4:40PM: Full Paper Session 5: Privacy

A Privacy Preserving Reputation System for Mobile Information=20
Dissemination Networks
		Marco Voss, Andreas Heinemann, Max M=9Fhlh=8Auser
=09
A Privacy Service for Context-Aware Mobile Computing
		Vagner Sacramento, Markus Endler, Fernando Nascimento
	=09
Protecting Location Privacy Through Path Confusion
		Baik Hoh, Marco Gruteser

A Solution for Wireless Privacy and Payments based on E-cash
		Yiannis Tsiounis, Tom Karygiannis, Aggelos Kiayias
=09
5:00PM - 6:40PM: Short paper Session 1

A Signal Fingerprinting Paradigm for Physical Layer Security in=20
Conventional and
Sensor Networks,
		Thomas Daniels, Mani Mina, Steve Russell

Location Privacy with IP Mobility
		Rajeev Koodli, Vijay Devarapalli, Hannu Flinck, Charles Perkins

Fellowship in Mobile Ad hoc Networks,
		Venkatesan Balakrishnan, Vijay Varadharajan

802.11 Active Attack Traffic Profile Classification Using Management=20
Frame Clustering
		Wenzhe Zhou, Alan Marshall, Qiang Gu
	=09
A Secure Interworking Scheme for UMTS-WLAN
		Yen-Chieh Ouyang, Chung-Hua Chu, Chang-Bu Jang

bufSTAT - A Tool for Early Detection and Classification
		of Buffer Overflow Attacks
		Svetlana Radosavac, Karl Seamon, John S. Baras

LRBAC: A Location-Aware Role-Based Access Control Model
		Indrakshi Ray,Lijun Yu

Tri-party TLS Adaptation for Trust Delegation in Home Networks
		Khaled Masmoudi, Mureed Hussain, Hossam Afifi, Dominique Seret
	=09
PATRIOT: a Policy-Based, Multi-level Security Protocol for Safekeeping=20
Audit Logs on
Wireless Devices,
		Wassim Itani, Ayman Kayssi, Ali Chehab

Harnessing Emergent Ubiquitous Computing Properties to Prevent Malicious=20
Code
Propagation,
		David Llewellyn-Jones, Madjid Merabti, Qi Shi, Bob Askwith

***************************************************************

Thursday, Sep 8, 2005

8.30AM - 10.35 AM: Full Paper Session 6: Key management

A Level Key Infrastructure for Secure and Efficient Group Communication=20
in Wireless
Sensor Networks
		Jyh-How Huang, Jason Buckingham, Richard Han

A Modified Secure Remote Password (SRP) Protocol for Key Initialization=20
and Exchange
in Bluetooth Systems
		Amir Sayegh, Mahmoud El-hadidi

Hi-KD: An Efficient Key Management Algorithm for Hierarchical Group
		Hani Ragab Hassan, Abdelmadjid Bouabdallah, Hatem Bettahar, Yacine
Challal
	=09
A Deterministic Pairwise Key Pre-distribution Scheme for Mobile Sensor=20
Networks
		David Sanchez, Heribert Baldus
	=09
A Practical Study of Transitory Master Key Establishment For Wireless=20
Sensor Networks
		Jing Deng, Carl Hartung, Richard Han, Shivakant Mishra
	=09
11:00 - 12:40: Full Paper Session 7:  Routing

Applying emergence to the design of routing protocols for the security=20
of wireless ad hoc
networks,
		Ioannis Pavlosoglou, Mark Leeson, Roger Green

SPINAT: Integrating IPsec into Overlay Routing
		Jukka Ylitalo, Patrik Salmela, Hannes Tschofenig

On the Survivability of Routing Protocols in Ad Hoc Wireless Networks
		Baruch Awerbuch, Reza Curtmola, David Holmer,
		Cristina Nita-Rotaru, Herbert Rubens
	=09
An Extensible Environment for Evaluating Secure MANET,
		Yongguang Zhang, Yi-an Huang, Wenke Lee
	=09
12.40PM - 2:00PM: Lunch

2:00PM - 3:40 PM: Full Paper Session 8: Cryptographic algorithms and=20
protocols

Soft-Timeout Distributed Key Generation for Digital Signature based on=20
Elliptic Curve D-
log for Low-power Devices,
		Caimu Tang, Anthony T. Chronopoulos and Cauligi S. Raghavendra
	=09
A Uniform Framework for Cryptanalysis of the Bluetooth E_0 Cipher,
		Ophir Levy, Avishai Wool
	=09
MOTET: Mobile Transactions using Electronic Tickets
		Daniele Quercia, Stephen Hailes
	=09
Exploiting Hierarchical Identity-Based Encryption
		for Access Control to Pervasive Computing Information
		Urs Hengartner, Peter Steenkiste

3:40PM - 4:00 PM: Break

4:00PM - 5:40 PM: Short paper Session 2

GKE: Efficient Group-based Key Establishment for Large Sensor Networks
		Li Zhou,Jinfeng Ni, Chinya Ravishankar

Practically Unbounded One-Way Chains for Authentication
		with Backward Secrecy
		Vishwas Patil, Luigi Mancini, Antonio Durante, Roberto Di Pietro

Limitations of Key Escrow in Identity-Based Schemes in Ad Hoc Networks
		Katrin Hoeper, Guang Gong

Enhanced 1-D Chaotic Key-Based Algorithm for Image Encryption
		Daniel Socek, Shujun Li, Spyros Magliveras, Borko Furht

Schemes for Enhancing the Denial-of-Service Tolerance of SRTP
		Sachin Garg, Navjot Singh, Timothy Tsai

Thor: The Hybrid Online Repository
		Timothy van der Horst, Kent Seamons

Random IDs for preserving location privacy
		Stefan Schlott, Frank Kargl, Michael Weber

Denial-of-Service Countermeasure with Immunization and Regulation
		Qin Yu, Hong Liu

A Distributed Cross-Layer Intrusion Detection System for Ad Hoc Networks
		Yu Liu, Yang Li, Hong Man

A Control Formulation of the Network Security Problem via a Risk Manageme=
nt
Approach
		Nicholas Bambos

    ***************************************************************

Friday, Sep 9, 2005

First IEEE/CreateNet International Workshop on The Value of Security=20
through
Collaboration (SECOVAL): www.secoval.org

First IEEE/CreateNet International Workshop on Integration of Security=20
and Quality of
Service (SecQoS): www.secqos.org

    ***************************************************************



_______________________________________________
Securecomm-cfp mailing list
Securecomm-cfp@mantis.cs.colorado.edu
http://mantis.cs.colorado.edu/mailman/listinfo/securecomm-cfp

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



From mip6-bounces@ietf.org Wed Aug 03 11:30:09 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E0LC5-0000vs-AT; Wed, 03 Aug 2005 11:30:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1E0LC4-0000vn-2i
	for mip6@megatron.ietf.org; Wed, 03 Aug 2005 11:30:08 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25779
	for <mip6@ietf.org>; Wed, 3 Aug 2005 11:29:59 -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.43) id 1E0Lie-0006le-Jb
	for mip6@ietf.org; Wed, 03 Aug 2005 12:03:50 -0400
Message-ID: <0e0001c59840$2cfa3090$596015ac@dcml.docomolabsusa.com>
From: "James Kempf" <Kempf@docomolabs-usa.com>
To: "Francis Dupont" <Francis.Dupont@enst-bretagne.fr>
References: <200508030707.j73772cG014695@givry.rennes.enst-bretagne.fr>
Subject: Re: [Mip6] about draft-ietf-mip6-bootstrapping-split-00.txt 
Date: Wed, 3 Aug 2005 08:29:43 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
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

>    Another is that the HA may reject the BU for some reason,
>
> => this is not a problem: if the MN gives up it can ask the removal
> of the RR and has to close the IKE session (i.e., delete the SAs).
>

If the HoA  configured through IKE is registered with the BU rather than
with the IKE transaction - and the HA rejects it - the MN can keep up the SA
and do mobile prefix discovery within the SA, then send a BU for a newly
autoconfigured address. The HA will then DAD it. So I don't think the SA
needs to be taken down if the address is rejected, unless it is for some
reason the SA identifier (which of course it shouldn't be in the MIP case).

I think to be able to do DNS within the IKE transaction, the VPN tunnel
endpoint would have to DAD the address. I suppose we could specify DAD as
part of the new IKE config option we'll be requesting but we would also need
to include a DNS config option within IKE too for this purpose.

>    and then the address would need to be unregistered from the DNS,
>
> => yes, the PTR needs to be deleted.
>
>    but the HA couldn't do that because it would not have the FQDN.
>
> => I disagree: first the FQDN is not needed as the PTR is for the address
> in the reversed name format, and the FQDN is given for registration
> so there is no problem to give it for deregistration too.
> Perhaps you think about automatic deregistration when the IKE session
> goes down (so my first argument applies)?
>

No, I was thinking that the HA would have to cache the FQDN between the
close of the IKE transaction and the BU transaction. I think this might be
awkward from an implementation perspective.

>    What exactly was the issue you had with having the DNS update done via
the
>    BU?
>
> => this is not the job of the MIPv6 code and is clearly the job of the
> tool which allocates the HoA: IKE CFG_REQUEST stuff. Here I apply
> my idea that IKE CFG_REQUEST is DHCP-like and DNS update is a classical
> service offered by DHCP. BTW the DNS update must be secured i.e. the
> tools performing it be trusted, so it is not simple...
>

Well, if the IKE-configed address gets rejected and the MN configs a new
address through prefex discovery and the BU, the HA will have to do the DNS
update anyway, so it seems like it might be a good idea to have that
capability in any event.

            jak



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



From mip6-bounces@ietf.org Thu Aug 04 03:53:52 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E0aY4-000580-K1; Thu, 04 Aug 2005 03:53:52 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1E0aXx-00056N-1h
	for mip6@megatron.ietf.org; Thu, 04 Aug 2005 03:53:50 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09231
	for <mip6@ietf.org>; Thu, 4 Aug 2005 03:53:43 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E0b4m-00037o-B2
	for mip6@ietf.org; Thu, 04 Aug 2005 04:27:41 -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 j747qVD00813; Thu, 4 Aug 2005 09:52: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.13.1/8.13.1) with ESMTP id
	j747qVgx018797; Thu, 4 Aug 2005 09:52:31 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200508040752.j747qVgx018797@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "James Kempf" <Kempf@docomolabs-usa.com>
Subject: Re: [Mip6] about draft-ietf-mip6-bootstrapping-split-00.txt 
In-reply-to: Your message of Wed, 03 Aug 2005 08:29:43 PDT.
	<0e0001c59840$2cfa3090$596015ac@dcml.docomolabsusa.com> 
Date: Thu, 04 Aug 2005 09:52:31 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
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

 In your previous mail you wrote:

   >    Another is that the HA may reject the BU for some reason,
   >
   > => this is not a problem: if the MN gives up it can ask the removal
   > of the RR and has to close the IKE session (i.e., delete the SAs).

=> note that by to give up I really mean to give up, not to retry
with another HoA. BTW in this case we have to explain what happens
to the previous HoA, even when it was allocated by IKE CFG_REQUEST,
so this cannot be used as an argument in favor (or against) registering
by BU.
   
   If the HoA  configured through IKE is registered with the BU rather than
   with the IKE transaction - and the HA rejects it - the MN can keep up the SA
   and do mobile prefix discovery within the SA,

=> MPD is a junk function: renumbering time scale is in months and
the mobile prefix is likely discovered by DNS or something like.
BTW I'd like to know how you can get the HA address without the prefix (:-).

   then send a BU for a newly
   autoconfigured address. The HA will then DAD it.

=> I believed you'd like to do allocation or validation in IKE CFG_REQUEST
in order to avoid the DAD... But even it is not part of the whole idea,
we should agree that to try another address needs to change the SA pair
before so this can always be done with some IKE interaction.

   So I don't think the SA
   needs to be taken down if the address is rejected,

=> perhaps for the IKE SA but the IPsec SA pairs must be changed.

   unless it is for some
   reason the SA identifier (which of course it shouldn't be in the MIP case).
   
=> so you are talking about the IKE SA

   I think to be able to do DNS within the IKE transaction, the VPN tunnel
   endpoint would have to DAD the address.

=> not necessary but IMHO I am in favor of this.

   I suppose we could specify DAD as
   part of the new IKE config option we'll be requesting but we would also need
   to include a DNS config option within IKE too for this purpose.
   
=> I can't see a problem here: DNS update is a well known service offered
by DHCP so in the idea of IKE CFG_REQUEST.

   No, I was thinking that the HA would have to cache the FQDN between the
   close of the IKE transaction

=> what is the close of the IKE transaction?

   and the BU transaction. I think this might be
   awkward from an implementation perspective.
   
=> I don't understand...

   Well, if the IKE-configed address gets rejected and the MN configs a new
   address through prefex discovery and the BU, the HA will have to do the DNS
   update anyway,

=> the MIPv6 code or the IKE code on the HA? As I've explained both will
be involved.

   so it seems like it might be a good idea to have that
   capability in any event.
   
Regards

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Thu Aug 04 10:17:18 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E0gX8-0000MD-DC; Thu, 04 Aug 2005 10:17:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1E0gX6-0000Lx-8W
	for mip6@megatron.ietf.org; Thu, 04 Aug 2005 10:17:16 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14094
	for <mip6@ietf.org>; Thu, 4 Aug 2005 10:17:11 -0400 (EDT)
Received: from wproxy.gmail.com ([64.233.184.195])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E0h3u-0004ik-CT
	for mip6@ietf.org; Thu, 04 Aug 2005 10:51:13 -0400
Received: by wproxy.gmail.com with SMTP id 37so366514wra
	for <mip6@ietf.org>; Thu, 04 Aug 2005 07:17:01 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=E4rgBeYPuzi53XcKKzLMxpAnZzFD/xHBMy2FDvuXGfDfxJZOBfRa/UyH4jI6dM4sMCUJWY8rQ5K2YcmwcEhZ584GXXYTBtDk80MwzNQNP+7gfG3vJ8Q5VgDnbG+OH1PtVLOUBpDsYs19W8072HYjDoNsqwyp7ID7af4UOMcn2CY=
Received: by 10.54.29.28 with SMTP id c28mr1604621wrc;
	Thu, 04 Aug 2005 07:17:00 -0700 (PDT)
Received: by 10.54.104.14 with HTTP; Thu, 4 Aug 2005 07:16:59 -0700 (PDT)
Message-ID: <f1f4dcdc050804071652345429@mail.gmail.com>
Date: Thu, 4 Aug 2005 07:16:59 -0700
From: Vijay Devarapallli <dvijay@gmail.com>
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
Subject: Re: [Mip6] about draft-ietf-mip6-bootstrapping-split-00.txt
In-Reply-To: <200508030707.j73772cG014695@givry.rennes.enst-bretagne.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <0b1401c59784$4f13c4a0$596015ac@dcml.docomolabsusa.com>
	<200508030707.j73772cG014695@givry.rennes.enst-bretagne.fr>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org, James Kempf <Kempf@docomolabs-usa.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Vijay Devarapallli <dvijay@gmail.com>
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

hi Francis,

On 8/3/05, Francis Dupont <Francis.Dupont@enst-bretagne.fr> wrote:

>    What exactly was the issue you had with having the DNS update done via=
 the
>    BU?
>=20
> =3D> this is not the job of the MIPv6 code and is clearly the job of the
> tool which allocates the HoA: IKE CFG_REQUEST stuff. Here I apply
> my idea that IKE CFG_REQUEST is DHCP-like and DNS update is a classical
> service offered by DHCP. BTW the DNS update must be secured i.e. the
> tools performing it be trusted, so it is not simple...

there are two issues. first, this would mean he MN is not in control of=20
the DNS update. the HA does it everytime it replies with a HoA in a=20
CFG_REPLY message. not sure thats a good idea. in some cases,=20
the MN may not want the HoA published in the DNS. it would be=20
good to get an indication from the MN before doing the DNS update.
second, we want to support HoA auto-configuration (RFC 2462, RFC=20
3041, CGA). when the MN autoconfigures a HoA, we dont use=20
CFG_REPLY. the HA doing the update when it sends CFG_REPLY
message supports only assigned HoA.

Vijay

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



From mip6-bounces@ietf.org Thu Aug 04 10:31:00 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E0gkO-0005Q6-3e; Thu, 04 Aug 2005 10:31:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1E0gkM-0005Q1-Iu
	for mip6@megatron.ietf.org; Thu, 04 Aug 2005 10:30:58 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15234
	for <mip6@ietf.org>; Thu, 4 Aug 2005 10:30:56 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E0hHF-0005KC-GC
	for mip6@ietf.org; Thu, 04 Aug 2005 11:04:59 -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 j74EUTD24201; Thu, 4 Aug 2005 16:30:29 +0200
Received: from givry.rennes.enst-bretagne.fr
	(localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id
	j74EUTpm020436; Thu, 4 Aug 2005 16:30:29 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200508041430.j74EUTpm020436@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Vijay Devarapallli <dvijay@gmail.com>
Subject: Re: [Mip6] about draft-ietf-mip6-bootstrapping-split-00.txt 
In-reply-to: Your message of Thu, 04 Aug 2005 07:16:59 PDT.
	<f1f4dcdc050804071652345429@mail.gmail.com> 
Date: Thu, 04 Aug 2005 16:30:29 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: mip6@ietf.org, James Kempf <Kempf@docomolabs-usa.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

 In your previous mail you wrote:

   there are two issues. first, this would mean he MN is not in control of 
   the DNS update. the HA does it everytime it replies with a HoA in a 
   CFG_REPLY message.

=> no, the MN asks the HA to update the reverse tree. The discussion is
about where to put the DNS updater code (IKE or MIPv6).

   not sure thats a good idea. in some cases, 
   the MN may not want the HoA published in the DNS.

=> of course it will be done at the request of MN. We can even imagine
ways where only a bit is enough. IMHO we need a new CFG_REQUEST (SET?)
with an optional parameter to carry the MN's FQDN if it is not yet
available (in the CERT or ID for instance).

   it would be 
   good to get an indication from the MN before doing the DNS update.

=> we agree

   second, we want to support HoA auto-configuration (RFC 2462, RFC 
   3041, CGA). when the MN autoconfigures a HoA, we dont use 
   CFG_REPLY. the HA doing the update when it sends CFG_REPLY
   message supports only assigned HoA.
   
=> I can't parse everything here but my proposal is based on a
positive answer (which are still waiting for) about a new "validation"
service from the IKE CFG_REQUEST stuff.

Regards

Francis.Dupont@enst-bretagne.fr
   

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



From mip6-bounces@ietf.org Thu Aug 04 12:01:15 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E0i9j-00064G-6S; Thu, 04 Aug 2005 12:01:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1E0i9e-00063k-Lr
	for mip6@megatron.ietf.org; Thu, 04 Aug 2005 12:01:13 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21457
	for <mip6@ietf.org>; Thu, 4 Aug 2005 12:01:08 -0400 (EDT)
Received: from wproxy.gmail.com ([64.233.184.192])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E0igW-0008En-GP
	for mip6@ietf.org; Thu, 04 Aug 2005 12:35:11 -0400
Received: by wproxy.gmail.com with SMTP id 37so389746wra
	for <mip6@ietf.org>; Thu, 04 Aug 2005 09:00:55 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=MYGnuuyodaRp8OiWKD6/ZKV+EJfIJhZ2WcOE3v3L37XnqNX/QUoqzbGCfyR4B1fmArF8ncNDnacJ5wzXOVUx7cTFJVv5Au1JMglYm0egSigA6ijCx4Vpapo0b7kH6QF6E7G2tRd9h7/QuT+7f0x3vEfNGtfUN6Q8A0MC9hqJgOw=
Received: by 10.54.43.79 with SMTP id q79mr1686598wrq;
	Thu, 04 Aug 2005 09:00:54 -0700 (PDT)
Received: by 10.54.104.14 with HTTP; Thu, 4 Aug 2005 09:00:54 -0700 (PDT)
Message-ID: <f1f4dcdc0508040900484ad160@mail.gmail.com>
Date: Thu, 4 Aug 2005 09:00:54 -0700
From: Vijay Devarapallli <dvijay@gmail.com>
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
Subject: Re: [Mip6] about draft-ietf-mip6-bootstrapping-split-00.txt
In-Reply-To: <200508041430.j74EUTpm020436@givry.rennes.enst-bretagne.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <f1f4dcdc050804071652345429@mail.gmail.com>
	<200508041430.j74EUTpm020436@givry.rennes.enst-bretagne.fr>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org, James Kempf <Kempf@docomolabs-usa.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Vijay Devarapallli <dvijay@gmail.com>
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

On 8/4/05, Francis Dupont <Francis.Dupont@enst-bretagne.fr> wrote:
>  In your previous mail you wrote:
>=20
>    there are two issues. first, this would mean he MN is not in control o=
f
>    the DNS update. the HA does it everytime it replies with a HoA in a
>    CFG_REPLY message.
>=20
> =3D> no, the MN asks the HA to update the reverse tree. The discussion is
> about where to put the DNS updater code (IKE or MIPv6).

putting it in IKE means, we need to modify CFG_REQUEST to include
an indication from the MN. IMHO, we should avoid that.

then there is the authentication option protocol. IMO, we should eventually
have a bootstrap solution for the authentication option protocol too. an
IKE specific extension for the MN indication might not work when the
authentication option protocol is used. so its better to put the indication
in the binding update.

>    second, we want to support HoA auto-configuration (RFC 2462, RFC
>    3041, CGA). when the MN autoconfigures a HoA, we dont use
>    CFG_REPLY. the HA doing the update when it sends CFG_REPLY
>    message supports only assigned HoA.
>=20
> =3D> I can't parse everything here but my proposal is based on a
> positive answer (which are still waiting for) about a new "validation"
> service from the IKE CFG_REQUEST stuff.

I was talking about HoA auto-configuration which is slightly different
from HoA assignment. in the former, the home prefix is obtained first,
the MN auto-configures the HoA and then sets up security=20
associations using CREATE_CHILD_SA exchange. in the latter,
HoA is assigned during the CFG_REQ/CFG_REPLY exchange.

Vijay

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



From mip6-bounces@ietf.org Thu Aug 04 12:18:04 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E0iNZ-0003FW-W4; Thu, 04 Aug 2005 12:15:34 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1E0iNW-0003DC-Ta
	for mip6@megatron.ietf.org; Thu, 04 Aug 2005 12:15:31 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22559
	for <mip6@ietf.org>; Thu, 4 Aug 2005 12:15:28 -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.43) id 1E0iuQ-0000J2-TV
	for mip6@ietf.org; Thu, 04 Aug 2005 12:49:32 -0400
Message-ID: <10ce01c5990f$b3ff0140$596015ac@dcml.docomolabsusa.com>
From: "James Kempf" <Kempf@docomolabs-usa.com>
To: "Francis Dupont" <Francis.Dupont@enst-bretagne.fr>,
	"Vijay Devarapallli" <dvijay@gmail.com>
References: <200508041430.j74EUTpm020436@givry.rennes.enst-bretagne.fr>
Subject: Re: [Mip6] about draft-ietf-mip6-bootstrapping-split-00.txt 
Date: Thu, 4 Aug 2005 09:15:15 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
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

> => no, the MN asks the HA to update the reverse tree. The discussion is
> about where to put the DNS updater code (IKE or MIPv6).
>

Are we only talking about the reverse tree here? That case is less
interesting, since, AFIKT from talking with DNS folks the reverse tree is
not well maintained.

            jak




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



From mip6-bounces@ietf.org Thu Aug 04 12:26:23 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E0iY3-0006Aa-C5; Thu, 04 Aug 2005 12:26:23 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1E0iY1-0006AU-5Z
	for mip6@megatron.ietf.org; Thu, 04 Aug 2005 12:26:21 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23122
	for <mip6@ietf.org>; Thu, 4 Aug 2005 12:26:18 -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.43) id 1E0j4v-0000Zf-5T
	for mip6@ietf.org; Thu, 04 Aug 2005 13:00:22 -0400
Message-ID: <000d01c59911$3a750b10$596015ac@dcml.docomolabsusa.com>
From: "James Kempf" <Kempf@docomolabs-usa.com>
To: "Francis Dupont" <Francis.Dupont@enst-bretagne.fr>
References: <200508040752.j747qVgx018797@givry.rennes.enst-bretagne.fr>
Subject: Re: [Mip6] about draft-ietf-mip6-bootstrapping-split-00.txt 
Date: Thu, 4 Aug 2005 09:26:10 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
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

> => MPD is a junk function: renumbering time scale is in months and
> the mobile prefix is likely discovered by DNS or something like.
> BTW I'd like to know how you can get the HA address without the prefix
(:-).

Remember we are dealing with IPv6 here and the home link could have multiple
prefixes. Now why exactly the MN might want to select one prefix over
another is a different question.


>    No, I was thinking that the HA would have to cache the FQDN between the
>    close of the IKE transaction
>
> => what is the close of the IKE transaction?
>

Sorry, I meant during the IKE_AUTH or CREATE_CHILD_SA. The address
configuration could occur during either. If the former, then there would be
an issue with doing another address under the IKE SA, I would think.

>    and the BU transaction. I think this might be
>    awkward from an implementation perspective.
>
> => I don't understand...
>

The HA would have to maintain the FQDN in some kind of table accessable to
the IKE code and the MIP code, so that MIP could remove the DNS PTR if the
BU failed.

>    Well, if the IKE-configed address gets rejected and the MN configs a
new
>    address through prefex discovery and the BU, the HA will have to do the
DNS
>    update anyway,
>
> => the MIPv6 code or the IKE code on the HA? As I've explained both will
> be involved.
>

If the MN autoconfigs the address after the IKE_AUTH/CREATE_CHILD_SA is done
and while it is doing the BU, then the MN may want the HA to do the DNS
update.

            jak



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



From mip6-bounces@ietf.org Thu Aug 04 12:39:23 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E0ikd-0000ng-BZ; Thu, 04 Aug 2005 12:39:23 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1E0ikc-0000nb-Ds
	for mip6@megatron.ietf.org; Thu, 04 Aug 2005 12:39:22 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23635
	for <mip6@ietf.org>; Thu, 4 Aug 2005 12:39:19 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E0jHV-0000sJ-Jk
	for mip6@ietf.org; Thu, 04 Aug 2005 13:13:24 -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 j74GcsW14194; Thu, 4 Aug 2005 18:38:54 +0200
Received: from givry.rennes.enst-bretagne.fr
	(localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id
	j74Gct8W020932; Thu, 4 Aug 2005 18:38:55 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200508041638.j74Gct8W020932@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Vijay Devarapallli <dvijay@gmail.com>
Subject: Re: [Mip6] about draft-ietf-mip6-bootstrapping-split-00.txt 
In-reply-to: Your message of Thu, 04 Aug 2005 09:00:54 PDT.
	<f1f4dcdc0508040900484ad160@mail.gmail.com> 
Date: Thu, 04 Aug 2005 18:38:55 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Cc: mip6@ietf.org, James Kempf <Kempf@docomolabs-usa.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

 In your previous mail you wrote:

   > => no, the MN asks the HA to update the reverse tree. The discussion is
   > about where to put the DNS updater code (IKE or MIPv6).
   
   putting it in IKE means, we need to modify CFG_REQUEST to include
   an indication from the MN. IMHO, we should avoid that.
   
=> CFG_REQUEST is already modified to add the MPD stuff and the validation
function.

   then there is the authentication option protocol.

=> the thing the 3GPP2 will drop as soon as it will discover it will
stay informational for ever (:-)?

   IMO, we should eventually have a bootstrap solution for the
   authentication option protocol too.

=> my opinion is simple: the tool in charge of the (optional) allocation
of the HoA should be in charge of the DNS update in the reverse tree.

   an IKE specific extension for the MN indication might not work when the
   authentication option protocol is used. so its better to put the indication
   in the binding update.

=> note that my argument works even when there is no security at all
as it is today I am afraid...

   > => I can't parse everything here but my proposal is based on a
   > positive answer (which are still waiting for) about a new "validation"
   > service from the IKE CFG_REQUEST stuff.
   
   I was talking about HoA auto-configuration which is slightly different
   from HoA assignment.

=> the draft begins with assignment and extends things with auto-config.
IMHO this is not a silly idea.

   in the former, the home prefix is obtained first,

=> or the home agent address is obtained first and the home prefix is
taken from it.

   the MN auto-configures the HoA and then sets up security 
   associations using CREATE_CHILD_SA exchange.

=> in the middle the I-D adds a validation phase using the CFG_REQUEST.
This was my first concern as this validation function is not standard
in DHCP (the model of the CFG_REQUEST services).

   in the latter,
   HoA is assigned during the CFG_REQ/CFG_REPLY exchange.
   
Regards

Francis.Dupont@enst-bretagne.fr

PS: BTW if you talk about authentication the tool which performs it
is IKE and it is the only tool which can check if the MN is presenting
a fake FQDN, i.e., DNS update by IKE CFG_REQUEST has a small security
advantage over any other solution, in particular over solutions which
are not bounded to authentication/authorization.

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



From mip6-bounces@ietf.org Thu Aug 04 12:43:32 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E0ioe-00026W-2y; Thu, 04 Aug 2005 12:43:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1E0ioc-00022X-GS
	for mip6@megatron.ietf.org; Thu, 04 Aug 2005 12:43:30 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23899
	for <mip6@ietf.org>; Thu, 4 Aug 2005 12:43:27 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E0jLX-000116-MS
	for mip6@ietf.org; Thu, 04 Aug 2005 13:17:32 -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 j74GhEW14630; Thu, 4 Aug 2005 18:43:14 +0200
Received: from givry.rennes.enst-bretagne.fr
	(localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id
	j74GhEPV020965; Thu, 4 Aug 2005 18:43:14 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200508041643.j74GhEPV020965@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "James Kempf" <Kempf@docomolabs-usa.com>
Subject: Re: [Mip6] about draft-ietf-mip6-bootstrapping-split-00.txt 
In-reply-to: Your message of Thu, 04 Aug 2005 09:15:15 PDT.
	<10ce01c5990f$b3ff0140$596015ac@dcml.docomolabsusa.com> 
Date: Thu, 04 Aug 2005 18:43:14 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
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

 In your previous mail you wrote:

   > => no, the MN asks the HA to update the reverse tree. The discussion is
   > about where to put the DNS updater code (IKE or MIPv6).
   >
   
   Are we only talking about the reverse tree here?

=> yes, remember: I asked during the session two days ago.

   That case is less interesting, since, AFIKT from talking with DNS
   folks the reverse tree is not well maintained.
   
=> I agree. The question to simply drop the reverse tree for IPv6 is
still open.

Regards

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Thu Aug 04 12:56:50 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E0j1V-0005wd-UA; Thu, 04 Aug 2005 12:56:49 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1E0j1S-0005wF-Cj
	for mip6@megatron.ietf.org; Thu, 04 Aug 2005 12:56:46 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA24504
	for <mip6@ietf.org>; Thu, 4 Aug 2005 12:56:43 -0400 (EDT)
Received: from dns2.tilab.com ([163.162.42.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E0jYL-0001LO-Mj
	for mip6@ietf.org; Thu, 04 Aug 2005 13:30:48 -0400
Received: from iowa2k01b.cselt.it ([163.162.242.202])
	by dns2.cselt.it (PMDF V6.1 #38895)
	with ESMTP id <0IKP0093GIEYPV@dns2.cselt.it> for mip6@ietf.org; Thu,
	04 Aug 2005 18:42:34 +0200 (MEST)
Received: from EXC01B.cselt.it ([163.162.4.199]) by iowa2k01b.cselt.it with
	Microsoft SMTPSVC(6.0.3790.211); Thu, 04 Aug 2005 18:54:43 +0200
Date: Thu, 04 Aug 2005 18:56:26 +0200
From: Gerardo Giaretta <Gerardo.Giaretta@TILAB.COM>
Subject: RE: [Mip6] about draft-ietf-mip6-bootstrapping-split-00.txt
To: James Kempf <Kempf@docomolabs-usa.com>,
	Francis Dupont <Francis.Dupont@enst-bretagne.fr>,
	Vijay Devarapallli <dvijay@gmail.com>
Message-id: <DA62A6E0CDD1B34A84557FF1AC850C5769E759@EXC01B.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.326
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: quoted-printable
Importance: normal
Priority: normal
Thread-Topic: [Mip6] about draft-ietf-mip6-bootstrapping-split-00.txt
thread-index: AcWZEWSOz7LG3sECQb2UB75efJOvQwAA3i7g
Content-class: urn:content-classes:message
X-OriginalArrivalTime: 04 Aug 2005 16:54:43.0375 (UTC)
	FILETIME=[364483F0:01C59915]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
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

>=20
> > =3D> no, the MN asks the HA to update the reverse tree. The=20
> discussion is
> > about where to put the DNS updater code (IKE or MIPv6).
> >
>=20

I still think it should be part of MIPv6 code. As Vijay mentioned,
auht-protocol should be bootstrapped too. And in integrated scenario we
may come up with solutions that uses IKEv1 to setup the IPsec SA or with
scenarios where the HoA is not assigned by the Home Agent. I think we
should not have a different DNS update solution for all these
bootstrapping approaches.

--Gerardo
=20
>             jak
>=20
>=20
>=20
>=20
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>=20


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
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 Aug 04 13:08:42 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E0jD0-0000a5-PV; Thu, 04 Aug 2005 13:08:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1E0jCx-0000a0-HB
	for mip6@megatron.ietf.org; Thu, 04 Aug 2005 13:08:40 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25061
	for <mip6@ietf.org>; Thu, 4 Aug 2005 13:08:36 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E0jjo-0001ee-Sg
	for mip6@ietf.org; Thu, 04 Aug 2005 13:42:38 -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 j74H8EW15963; Thu, 4 Aug 2005 19:08:14 +0200
Received: from givry.rennes.enst-bretagne.fr
	(localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id
	j74H8Fc5021046; Thu, 4 Aug 2005 19:08:15 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200508041708.j74H8Fc5021046@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "James Kempf" <Kempf@docomolabs-usa.com>
Subject: Re: [Mip6] about draft-ietf-mip6-bootstrapping-split-00.txt 
In-reply-to: Your message of Thu, 04 Aug 2005 09:26:10 PDT.
	<000d01c59911$3a750b10$596015ac@dcml.docomolabsusa.com> 
Date: Thu, 04 Aug 2005 19:08:15 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
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

 In your previous mail you wrote:

   > => MPD is a junk function: renumbering time scale is in months and
   > the mobile prefix is likely discovered by DNS or something like.
   > BTW I'd like to know how you can get the HA address without the prefix
   (:-).
   
   Remember we are dealing with IPv6 here and the home link could have multiple
   prefixes. Now why exactly the MN might want to select one prefix over
   another is a different question.
   
=> we'll talk about this tomorrow but today the home agent address is in
the home prefix. I even believe some implementations verify this...
   
   >    No, I was thinking that the HA would have to cache the FQDN between the
   >    close of the IKE transaction
   >
   > => what is the close of the IKE transaction?
   
   Sorry, I meant during the IKE_AUTH or CREATE_CHILD_SA. The address
   configuration could occur during either. If the former, then there would be
   an issue with doing another address under the IKE SA, I would think.
   
=> the IKEv2 draft explains the CFG_REQUEST should only fail with
an error notification for hard errors like bad format. So retries
seems to be acceptable.

   >    and the BU transaction. I think this might be
   >    awkward from an implementation perspective.
   >
   > => I don't understand...

   The HA would have to maintain the FQDN in some kind of table accessable to
   the IKE code and the MIP code, so that MIP could remove the DNS PTR if the
   BU failed.
   
=> I disagree but what happens when things are finished is not clearly
defined. IMHO when the IKE SA is closed:
 - IPsec SAs are closed (IKEv2 management of SAs)
 - PTR RR is deleted by DNS update (and as a side effect the name can be
   deleted too)
 - allocated HoA is returned to the pool
 - (MIP interaction) BCE is deleted, proxy ND disabled
If you'd like to expire allocated HoAs only at their term (DHCP supports
both style), the PTR RR should be deleted at this moment. IMHO the first
style does a better usage of the pool but both work.

   If the MN autoconfigs the address after the IKE_AUTH/CREATE_CHILD_SA is done

=> so the IPsec SAs are not established with the new address???

   and while it is doing the BU, then the MN may want the HA to do the DNS
   update.
   
=> look at my last "killing" argument: the entity doing the authentication/
authorization is in a better place to verify the FQDN. Don't forget that
in fact the only info of this kind the MIPv6 code has is about the HoA,
for instance you can change the CoA between IKE and the BU in theory.

Regards

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Thu Aug 04 13:21:48 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E0jPg-00043U-GN; Thu, 04 Aug 2005 13:21:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1E0jPe-000413-JK
	for mip6@megatron.ietf.org; Thu, 04 Aug 2005 13:21:46 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25657
	for <mip6@ietf.org>; Thu, 4 Aug 2005 13:21:43 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E0jwZ-0001zm-4x
	for mip6@ietf.org; Thu, 04 Aug 2005 13:55:48 -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 j74HLTW16590; Thu, 4 Aug 2005 19:21:29 +0200
Received: from givry.rennes.enst-bretagne.fr
	(localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id
	j74HLTmU021102; Thu, 4 Aug 2005 19:21:29 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200508041721.j74HLTmU021102@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Gerardo Giaretta <Gerardo.Giaretta@tilab.com>
Subject: Re: [Mip6] about draft-ietf-mip6-bootstrapping-split-00.txt 
In-reply-to: Your message of Thu, 04 Aug 2005 18:56:26 +0200.
	<DA62A6E0CDD1B34A84557FF1AC850C5769E759@EXC01B.cselt.it> 
Date: Thu, 04 Aug 2005 19:21:29 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: mip6@ietf.org, James Kempf <Kempf@docomolabs-usa.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

 In your previous mail you wrote:

   I still think it should be part of MIPv6 code. As Vijay mentioned,
   auht-protocol should be bootstrapped too. And in integrated scenario we
   may come up with solutions that uses IKEv1 to setup the IPsec SA or with
   scenarios where the HoA is not assigned by the Home Agent. I think we
   should not have a different DNS update solution for all these
   bootstrapping approaches.
   
=> Gerardo, you are forgetting an important part of the context:
DNS update makes sense only when HoA allocation/assignment (best term
please?) is possible. With IKEv1 this is not the case and PTR RRs
are simply static.
So I repeat my argument: the DNS update should be part of the tool
which already is in charge of allocation/assignment and by the
proposed but not yet extension in charge of the validation of MN
auto-configured & co HoAs.
When this tool includes the authentication (of the MN) / authorization
(to use the mobility service including the HoA) it likely can check
the FQDN too.
So please don't extra burden on the shoulders of the MIPv6 code...

Regards

Francis.Dupont@enst-bretagne.fr

PS: as noted this issue is a second order one: the IPv6 reverse tree
is so poorly managed than it is nearly useless... IMHO to replace
the intrinsicly DHAAD mechanism by DNS SRV is far more important
(and I am running out of power :-).

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



From mip6-bounces@ietf.org Thu Aug 04 13:23:24 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E0jRE-0004X6-16; Thu, 04 Aug 2005 13:23:24 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1E0jRC-0004Wy-8C
	for mip6@megatron.ietf.org; Thu, 04 Aug 2005 13:23:22 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25701
	for <mip6@ietf.org>; Thu, 4 Aug 2005 13:23:19 -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.43) id 1E0jy6-000220-PY
	for mip6@ietf.org; Thu, 04 Aug 2005 13:57:24 -0400
Message-ID: <002601c59919$3196b680$596015ac@dcml.docomolabsusa.com>
From: "James Kempf" <Kempf@docomolabs-usa.com>
To: "Francis Dupont" <Francis.Dupont@enst-bretagne.fr>,
	"Vijay Devarapallli" <dvijay@gmail.com>
References: <200508041638.j74Gct8W020932@givry.rennes.enst-bretagne.fr>
Subject: Re: [Mip6] about draft-ietf-mip6-bootstrapping-split-00.txt 
Date: Thu, 4 Aug 2005 10:23:11 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
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

Francis,

> => in the middle the I-D adds a validation phase using the CFG_REQUEST.
> This was my first concern as this validation function is not standard
> in DHCP (the model of the CFG_REQUEST services).

I asked Ralph whether the IKEv2 folks had consulted the DHCP WG on the
config and he said no. Perhaps there was some discussion amongst themselves
on this, but he hadn't heard of it. So it is not clear to me that the IKEv2
folks used any specific model of address configuration.

            jak



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



From mip6-bounces@ietf.org Fri Aug 05 02:54:39 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E0w6J-0000yZ-Iy; Fri, 05 Aug 2005 02:54:39 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1E0w6H-0000yU-8w
	for mip6@megatron.ietf.org; Fri, 05 Aug 2005 02:54:37 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA19021
	for <mip6@ietf.org>; Fri, 5 Aug 2005 02:54:30 -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.43) id 1E0wdD-0004Es-G1
	for mip6@ietf.org; Fri, 05 Aug 2005 03:28:41 -0400
Message-ID: <003b01c5998a$7f9365b0$596015ac@dcml.docomolabsusa.com>
From: "James Kempf" <Kempf@docomolabs-usa.com>
To: "Francis Dupont" <Francis.Dupont@enst-bretagne.fr>
References: <200508041708.j74H8Fc5021046@givry.rennes.enst-bretagne.fr>
Subject: Re: [Mip6] about draft-ietf-mip6-bootstrapping-split-00.txt 
Date: Thu, 4 Aug 2005 23:54:16 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
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

>    If the MN autoconfigs the address after the IKE_AUTH/CREATE_CHILD_SA is
done
>
> => so the IPsec SAs are not established with the new address???
>

We talked about having the MN autoconfig an address if it needed it during
the MIP transaction, but you bring up a good point. The MN would need to go
back and redo the CREATE_CHILD_SA with the address before registering it, to
make sure IKE knew about it. We should say something about that in the
document

>    and while it is doing the BU, then the MN may want the HA to do the DNS
>    update.
>
> => look at my last "killing" argument: the entity doing the
authentication/
> authorization is in a better place to verify the FQDN. Don't forget that
> in fact the only info of this kind the MIPv6 code has is about the HoA,
> for instance you can change the CoA between IKE and the BU in theory.
>

But after CREATE_CHILD_SA, the HA has a link to an authorized NAI through
the IPsec SA SPI for the MN. So, in theory, the HA could use that to check
the authorization (in fact, we probably should have stated that in the
document).

            jak



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



From mip6-bounces@ietf.org Fri Aug 05 03:10:48 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E0wLw-0005rS-Rx; Fri, 05 Aug 2005 03:10:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1E0wLv-0005rI-3s
	for mip6@megatron.ietf.org; Fri, 05 Aug 2005 03:10:47 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA21107
	for <mip6@ietf.org>; Fri, 5 Aug 2005 03:10:45 -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.43) id 1E0wsx-00057e-UL
	for mip6@ietf.org; Fri, 05 Aug 2005 03:44:56 -0400
Message-ID: <00b801c5998c$cb152940$596015ac@dcml.docomolabsusa.com>
From: "James Kempf" <Kempf@docomolabs-usa.com>
To: <mip6@ietf.org>
Date: Fri, 5 Aug 2005 00:10:42 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Content-Transfer-Encoding: 7bit
Subject: [Mip6] MN-HA Reliability Work?
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

So the outcome of the meeting on Tues. for HA reliability seems
inconclusive, but I am interested whether the WG has any interest in
continuing work on MN-HA reliability? My suggestion would be to combine
draft-haley and draft-li into a draft that covered new HA initiated IKE (in
case the existing HA crashes) and existing HA initiated switching (for
controlled shutdown).

            jak



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



From mip6-bounces@ietf.org Fri Aug 05 03:51:41 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E0wzV-0007ut-Pc; Fri, 05 Aug 2005 03:51:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1E0wzT-0007uk-Qw
	for mip6@megatron.ietf.org; Fri, 05 Aug 2005 03:51:39 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA23056
	for <mip6@ietf.org>; Fri, 5 Aug 2005 03:51:37 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E0xWV-0006Op-1C
	for mip6@ietf.org; Fri, 05 Aug 2005 04:25:49 -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 j757p3W22700; Fri, 5 Aug 2005 09:51: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.13.1/8.13.1) with ESMTP id
	j757p4Hg023057; Fri, 5 Aug 2005 09:51:04 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200508050751.j757p4Hg023057@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "James Kempf" <Kempf@docomolabs-usa.com>
Subject: Re: [Mip6] MN-HA Reliability Work? 
In-reply-to: Your message of Fri, 05 Aug 2005 00:10:42 PDT.
	<00b801c5998c$cb152940$596015ac@dcml.docomolabsusa.com> 
Date: Fri, 05 Aug 2005 09:51:04 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
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

 In your previous mail you wrote:

   So the outcome of the meeting on Tues. for HA reliability seems
   inconclusive, but I am interested whether the WG has any interest in
   continuing work on MN-HA reliability? My suggestion would be to combine
   draft-haley and draft-li into a draft that covered new HA initiated IKE (in
   case the existing HA crashes) and existing HA initiated switching (for
   controlled shutdown).
   
=> I've just done a comment about MOBIKE at the MONAMI6 BOF...
Unfortunately it seems I can do the same about MN-HA Reliability,
for instance the HA initiated IKE should not be compatible with
the "initiator decides" of MOBIKE. Of course this applies only with
IKEv2 but I believe everybody will switch to it as soon as it will
become widely available (error #33 ? :-)   
   
Thanks

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Fri Aug 05 04:31:55 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E0xcQ-00025P-VA; Fri, 05 Aug 2005 04:31:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1E0xcK-00023z-RO
	for mip6@megatron.ietf.org; Fri, 05 Aug 2005 04:31:53 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA25696
	for <mip6@ietf.org>; Fri, 5 Aug 2005 04:31:46 -0400 (EDT)
Received: from dns1.tilab.com ([163.162.42.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E0y9O-0007s6-3w
	for mip6@ietf.org; Fri, 05 Aug 2005 05:05:58 -0400
Received: from iowa2k01a.cselt.it ([163.162.242.201])
	by dns1.cselt.it (PMDF V6.0-025 #38895)
	with ESMTP id <0IKQ00G3DQ7L9U@dns1.cselt.it> for mip6@ietf.org; Fri,
	05 Aug 2005 10:28:33 +0200 (MEST)
Received: from EXC01B.cselt.it ([163.162.4.199]) by iowa2k01a.cselt.it with
	Microsoft SMTPSVC(6.0.3790.211); Fri, 05 Aug 2005 10:35:04 +0200
Date: Fri, 05 Aug 2005 10:31:29 +0200
From: Gerardo Giaretta <Gerardo.Giaretta@TILAB.COM>
Subject: RE: [Mip6] about draft-ietf-mip6-bootstrapping-split-00.txt
To: Francis.Dupont@enst-bretagne.fr
Message-id: <DA62A6E0CDD1B34A84557FF1AC850C5769E75F@EXC01B.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.326
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: quoted-printable
Importance: normal
Priority: normal
Thread-Topic: [Mip6] about draft-ietf-mip6-bootstrapping-split-00.txt
thread-index: AcWZGbtj4q2rJhmkTvyWpSik9s0otAAdh27g
Content-Class: urn:content-classes:message
X-OriginalArrivalTime: 05 Aug 2005 08:35:04.0109 (UTC)
	FILETIME=[93A54DD0:01C59998]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org, James Kempf <Kempf@docomolabs-usa.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

 >  In your previous mail you wrote:
>=20
>    I still think it should be part of MIPv6 code. As Vijay mentioned,
>    auht-protocol should be bootstrapped too. And in=20
> integrated scenario we
>    may come up with solutions that uses IKEv1 to setup the=20
> IPsec SA or with
>    scenarios where the HoA is not assigned by the Home Agent.=20
> I think we
>    should not have a different DNS update solution for all these
>    bootstrapping approaches.
>   =20
> =3D> Gerardo, you are forgetting an important part of the context:
> DNS update makes sense only when HoA allocation/assignment (best term
> please?) is possible. With IKEv1 this is not the case and PTR RRs
> are simply static.

I was not referring to IKEv1 as a tool to assign the HoA. My point is
that there could be other mechanisms (different from IKEv2) to assign a
HoA. Examples are DHCPv6 or HoA assignment during network access
authentication (e.g. using EAP or PANA).=20

--Gerardo

> So I repeat my argument: the DNS update should be part of the tool
> which already is in charge of allocation/assignment and by the
> proposed but not yet extension in charge of the validation of MN
> auto-configured & co HoAs.
> When this tool includes the authentication (of the MN) / authorization
> (to use the mobility service including the HoA) it likely can check
> the FQDN too.
> So please don't extra burden on the shoulders of the MIPv6 code...
>=20
> Regards
>=20
> Francis.Dupont@enst-bretagne.fr
>=20
> PS: as noted this issue is a second order one: the IPv6 reverse tree
> is so poorly managed than it is nearly useless... IMHO to replace
> the intrinsicly DHAAD mechanism by DNS SRV is far more important
> (and I am running out of power :-).
>=20


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 Fri Aug 05 04:51:46 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E0xve-00009Q-Ij; Fri, 05 Aug 2005 04:51:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1E0xvc-00009J-MX
	for mip6@megatron.ietf.org; Fri, 05 Aug 2005 04:51:44 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26884
	for <mip6@ietf.org>; Fri, 5 Aug 2005 04:51:42 -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.43) id 1E0ySf-00006B-Di
	for mip6@ietf.org; Fri, 05 Aug 2005 05:25:54 -0400
Message-ID: <014501c5999a$e273f270$596015ac@dcml.docomolabsusa.com>
From: "James Kempf" <Kempf@docomolabs-usa.com>
To: "Francis Dupont" <Francis.Dupont@enst-bretagne.fr>
References: <200508050751.j757p4Hg023057@givry.rennes.enst-bretagne.fr>
Subject: Re: [Mip6] MN-HA Reliability Work? 
Date: Fri, 5 Aug 2005 01:51:34 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
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

Francis,

Could you elaborate how you think this affects Qin's draft idea of having an
HA be able to initiate the SA?


        jak

----- Original Message -----
From: "Francis Dupont" <Francis.Dupont@enst-bretagne.fr>
To: "James Kempf" <Kempf@docomolabs-usa.com>
Cc: <mip6@ietf.org>
Sent: Friday, August 05, 2005 12:51 AM
Subject: Re: [Mip6] MN-HA Reliability Work?


> In your previous mail you wrote:
>
>    So the outcome of the meeting on Tues. for HA reliability seems
>    inconclusive, but I am interested whether the WG has any interest in
>    continuing work on MN-HA reliability? My suggestion would be to combine
>    draft-haley and draft-li into a draft that covered new HA initiated IKE
(in
>    case the existing HA crashes) and existing HA initiated switching (for
>    controlled shutdown).
>
> => I've just done a comment about MOBIKE at the MONAMI6 BOF...
> Unfortunately it seems I can do the same about MN-HA Reliability,
> for instance the HA initiated IKE should not be compatible with
> the "initiator decides" of MOBIKE. Of course this applies only with
> IKEv2 but I believe everybody will switch to it as soon as it will
> become widely available (error #33 ? :-)
>
> Thanks
>
> Francis.Dupont@enst-bretagne.fr
>



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



From mip6-bounces@ietf.org Fri Aug 05 04:53:27 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E0xxH-0000Qo-Jo; Fri, 05 Aug 2005 04:53:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1E0xxF-0000Qg-WA
	for mip6@megatron.ietf.org; Fri, 05 Aug 2005 04:53:26 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26959
	for <mip6@ietf.org>; Fri, 5 Aug 2005 04:53:23 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E0yUH-00008V-MY
	for mip6@ietf.org; Fri, 05 Aug 2005 05:27:36 -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 j758qxW28406; Fri, 5 Aug 2005 10:52:59 +0200
Received: from givry.rennes.enst-bretagne.fr
	(localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id
	j758qxLp023282; Fri, 5 Aug 2005 10:52:59 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200508050852.j758qxLp023282@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Gerardo Giaretta <Gerardo.Giaretta@tilab.com>
Subject: Re: [Mip6] about draft-ietf-mip6-bootstrapping-split-00.txt 
In-reply-to: Your message of Fri, 05 Aug 2005 10:31:29 +0200.
	<DA62A6E0CDD1B34A84557FF1AC850C5769E75F@EXC01B.cselt.it> 
Date: Fri, 05 Aug 2005 10:52:59 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Cc: mip6@ietf.org, James Kempf <Kempf@docomolabs-usa.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


 In your previous mail you wrote:

    >  In your previous mail you wrote:
   > 
   >    I still think it should be part of MIPv6 code. As Vijay mentioned,
   >    auht-protocol should be bootstrapped too. And in 
   > integrated scenario we
   >    may come up with solutions that uses IKEv1 to setup the 
   > IPsec SA or with
   >    scenarios where the HoA is not assigned by the Home Agent. 
   > I think we
   >    should not have a different DNS update solution for all these
   >    bootstrapping approaches.
   >    
   > => Gerardo, you are forgetting an important part of the context:
   > DNS update makes sense only when HoA allocation/assignment (best term
   > please?) is possible. With IKEv1 this is not the case and PTR RRs
   > are simply static.
   
   I was not referring to IKEv1 as a tool to assign the HoA.

=> I cited IKEv1 because you did.

   My point is that there could be other mechanisms (different from
   IKEv2) to assign a HoA.

=> I agree: my argument is these other mechanisms provide DNS update
of the PTR RR.

   Examples are DHCPv6

=> DHCPv6 has it.

   or HoA assignment during network access
   authentication (e.g. using EAP or PANA). 
   
=> in general they are front ends to DHCPv6 for this function (just
there are no good reasons to reinvent the wheel). BTW it will be
likely the case of IKE CFG_REQUEST implementations, and surely
for all the other DHCP over IPsec/IKE/...
   
Regards

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Mon Aug 08 09:01:06 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E27FZ-0004NC-VA; Mon, 08 Aug 2005 09:01:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E27FX-0004MI-FB; Mon, 08 Aug 2005 09:01:03 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18888;
	Mon, 8 Aug 2005 09:01:01 -0400 (EDT)
Received: from omgo.iij.ad.jp ([202.232.30.157])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1E27nD-0007C2-37; Mon, 08 Aug 2005 09:35:53 -0400
Received: OTM-MO id j78D0n7x004442; Mon, 8 Aug 2005 22:00:49 +0900 (JST)
Received: OTM-MIX0 id j78D0mrH009510; Mon, 8 Aug 2005 22:00:48 +0900 (JST)
Received: from localhost (jc-ssh.iij.ad.jp [192.168.174.22])
	by jc-smtp.iij.ad.jp (JC-SMTP/jc-smtp) id j78D0k9u019002;
	Mon, 8 Aug 2005 22:00:47 +0900 (JST)
Date: Mon, 08 Aug 2005 15:00:50 +0200 (CEST)
Message-Id: <20050808.150050.259287104.keiichi@iijlab.net>
To: mip6@ietf.org, nemo@ietf.org
From: Keiichi SHIMA <keiichi@iijlab.net>
X-Mailer: Mew version 4.2.53 on Emacs 22.0.50 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Content-Transfer-Encoding: 7bit
Cc: 
Subject: [Mip6] carrying IPv4 traffic using MIP6/NEMO
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

Hi all,

At the IETF MIP6 WG session, the design team talked about the
mechanism to bind an IPv4 home address to an IPv6 care-of address as a
transission mechanism.

I have submitted very similar mechanism for IPv4 networks as
draft-shima-nemo-v4prefix-00.txt, which binds IPv4 prefixes to an IPv6
care-of address of a mobile router and provides IPv4 mobile network
functionarity on top of NEMO.

I wonder if we should consider to integrate these two mechanism to
provide a single way to provide the mechanism to carry IPv4 traffic
for both a mobile host and a mobile router.

What do you think?

---
Keiichi SHIMA
IIJ Research Laboratory <keiichi@iijlab.net>
KAME Project <keiichi@kame.net>


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



From mip6-bounces@ietf.org Mon Aug 08 09:59:04 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E289g-0003Pg-3Y; Mon, 08 Aug 2005 09:59:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E289e-0003PQ-Cl; Mon, 08 Aug 2005 09:59:02 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21764;
	Mon, 8 Aug 2005 09:59:00 -0400 (EDT)
Received: from motgate5.mot.com ([144.189.100.105])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1E28hL-0000Je-N3; Mon, 08 Aug 2005 10:33:53 -0400
Received: from az33exr01.mot.com (az33exr01.mot.com [10.64.251.231])
	by motgate5.mot.com (8.12.11/Motgate5) with ESMTP id j78E5WHK010234;
	Mon, 8 Aug 2005 07:05:37 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by az33exr01.mot.com (8.13.1/8.13.0) with ESMTP id j78E6uJK010803;
	Mon, 8 Aug 2005 09:06:58 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 019AF865980; Mon,  8 Aug 2005 15:58:48 +0200 (CEST)
Message-ID: <42F76517.8050502@motorola.com>
Date: Mon, 08 Aug 2005 15:58:47 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: Keiichi SHIMA <keiichi@iijlab.net>
References: <20050808.150050.259287104.keiichi@iijlab.net>
In-Reply-To: <20050808.150050.259287104.keiichi@iijlab.net>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Content-Transfer-Encoding: 7bit
Cc: nemo@ietf.org, mip6@ietf.org
Subject: [Mip6] Re: [nemo] carrying IPv4 traffic using MIP6/NEMO
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

Hello Keiichi,

Keiichi SHIMA wrote:
> At the IETF MIP6 WG session, the design team talked about the
> mechanism to bind an IPv4 home address to an IPv6 care-of address as a
> transission mechanism.
> 
> I have submitted very similar mechanism for IPv4 networks as
> draft-shima-nemo-v4prefix-00.txt, which binds IPv4 prefixes to an IPv6
> care-of address of a mobile router and provides IPv4 mobile network
> functionarity on top of NEMO.
> 
> I wonder if we should consider to integrate these two mechanism to
> provide a single way to provide the mechanism to carry IPv4 traffic
> for both a mobile host and a mobile router.
> 
> What do you think?

Generally it looks like an interesting idea.  Why restraining the
binding to a fixed /32 full v4 address when binding a variable prefix
(1...32) could bring the benefit of giving v4 access to all nodes in the
moving network (not only to the MR).  So this may look as an obvious
advantage.

However, I was wondering how much would this addition extend the current
scope of the DT work, whose goal was mainly to give v6 (not v4) access
to MR and mobile nodes when MR connects to a v4 network.

Giving continuous v4 access to mobile nodes in a moving network whose MR
connects to a v4 access network can naturally be obtained by running
Mobile IPv4 on the MR, too.

What does the DT think?

IMHO.

Alex


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



From mip6-bounces@ietf.org Mon Aug 08 10:53:46 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E290c-0003kE-Hk; Mon, 08 Aug 2005 10:53:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E290a-0003jh-2u; Mon, 08 Aug 2005 10:53:44 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26378;
	Mon, 8 Aug 2005 10:53:41 -0400 (EDT)
Received: from mail.flarion.com ([63.103.94.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1E29YI-0001yg-1Z; Mon, 08 Aug 2005 11:28:35 -0400
Received: from ftmailserver.flariontech.com ([10.10.1.140]) by
	mail.flarion.com with Microsoft SMTPSVC(5.0.2195.6713);
	Mon, 8 Aug 2005 10:53:27 -0400
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 8 Aug 2005 10:53:27 -0400
Message-ID: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCAC1@ftmailserver.flariontech.com>
Thread-Topic: [nemo] carrying IPv4 traffic using MIP6/NEMO
Thread-Index: AcWcIbYL/CtaHmsZR0GsgMV1aBY/fwABuMjQ
From: "Soliman, Hesham" <H.Soliman@flarion.com>
To: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>,
	"Keiichi SHIMA" <keiichi@iijlab.net>
X-OriginalArrivalTime: 08 Aug 2005 14:53:27.0963 (UTC)
	FILETIME=[EF6FBEB0:01C59C28]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Content-Transfer-Encoding: quoted-printable
Cc: nemo@ietf.org, mip6@ietf.org
Subject: [Mip6] RE: [nemo] carrying IPv4 traffic using MIP6/NEMO
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

 >=20
 > Generally it looks like an interesting idea.  Why restraining the
 > binding to a fixed /32 full v4 address when binding a variable prefix
 > (1...32) could bring the benefit of giving v4 access to all=20
 > nodes in the
 > moving network (not only to the MR).  So this may look as an obvious
 > advantage.
 >=20
 > However, I was wondering how much would this addition extend=20
 > the current
 > scope of the DT work, whose goal was mainly to give v6 (not=20
 > v4) access
 > to MR and mobile nodes when MR connects to a v4 network.
 >=20
 > Giving continuous v4 access to mobile nodes in a moving=20
 > network whose MR
 > connects to a v4 access network can naturally be obtained by running
 > Mobile IPv4 on the MR, too.
 >=20
 > What does the DT think?

=3D> We discussed this and I had extended draft-soliman to represent
the IP address as : address/prefixlen, where prefixlen is anything up
to 32. It's a useful feature that only adds another 5 mins of work so =
why
not.=20

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 Aug 08 11:12:11 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E29IR-0000bm-JU; Mon, 08 Aug 2005 11:12:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E29IO-0000bc-Vo; Mon, 08 Aug 2005 11:12:09 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27448;
	Mon, 8 Aug 2005 11:12:06 -0400 (EDT)
Received: from mail.sfc.wide.ad.jp ([203.178.142.146])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1E29q3-0002XT-6A; Mon, 08 Aug 2005 11:47:00 -0400
Received: from [192.168.0.11] (p4080-ipbf903marunouchi.tokyo.ocn.ne.jp
	[58.88.27.80])
	by mail.sfc.wide.ad.jp (Postfix) with ESMTP id 4F1064C63D;
	Tue,  9 Aug 2005 00:11:31 +0900 (JST)
In-Reply-To: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCAC1@ftmailserver.flariontech.com>
References: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCAC1@ftmailserver.flariontech.com>
Mime-Version: 1.0 (Apple Message framework v733)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <7BFD95A3-59C8-4AA5-98DC-C81AE00379CB@sfc.wide.ad.jp>
Content-Transfer-Encoding: 7bit
From: Ryuji Wakikawa <ryuji@sfc.wide.ad.jp>
Date: Tue, 9 Aug 2005 00:11:28 +0900
To: "Soliman, Hesham" <H.Soliman@flarion.com>
X-Mailer: Apple Mail (2.733)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Content-Transfer-Encoding: 7bit
Cc: nemo@ietf.org, mip6@ietf.org, Keiichi SHIMA <keiichi@iijlab.net>,
	Alexandru Petrescu <alexandru.petrescu@motorola.com>
Subject: [Mip6] Re: [nemo] carrying IPv4 traffic using MIP6/NEMO
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

Hello Hesham

I thought you were opposed to support NEMOv4 during the discussion in  
DT.

Are there any big differences between draft-soliman(w/prefixlen)
and draft-keiichi for NEMO support?

regards,
ryuji

On 2005/08/08, at 23:53, Soliman, Hesham wrote:

>>
>> Generally it looks like an interesting idea.  Why restraining the
>> binding to a fixed /32 full v4 address when binding a variable prefix
>> (1...32) could bring the benefit of giving v4 access to all
>> nodes in the
>> moving network (not only to the MR).  So this may look as an obvious
>> advantage.
>>
>> However, I was wondering how much would this addition extend
>> the current
>> scope of the DT work, whose goal was mainly to give v6 (not
>> v4) access
>> to MR and mobile nodes when MR connects to a v4 network.
>>
>> Giving continuous v4 access to mobile nodes in a moving
>> network whose MR
>> connects to a v4 access network can naturally be obtained by running
>> Mobile IPv4 on the MR, too.
>>
>> What does the DT think?
>>
>
> => We discussed this and I had extended draft-soliman to represent
> the IP address as : address/prefixlen, where prefixlen is anything up
> to 32. It's a useful feature that only adds another 5 mins of work  
> so why
> not.
>
> Hesham
>
> ===========================================================
> 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.
> ===========================================================
>
>


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



From mip6-bounces@ietf.org Mon Aug 08 13:37:45 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2BZI-0003eL-Jc; Mon, 08 Aug 2005 13:37:44 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2BZG-0003dh-L5; Mon, 08 Aug 2005 13:37:43 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04932;
	Mon, 8 Aug 2005 13:37:39 -0400 (EDT)
Received: from mail.flarion.com ([63.103.94.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1E2C6z-0006Zw-NU; Mon, 08 Aug 2005 14:12:35 -0400
Received: from ftmailserver.flariontech.com ([10.10.1.140]) by
	mail.flarion.com with Microsoft SMTPSVC(5.0.2195.6713); 
	Mon, 8 Aug 2005 13:37:32 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C59C3F.DAFA9498"
Date: Mon, 8 Aug 2005 13:37:32 -0400
Message-ID: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCAC4@ftmailserver.flariontech.com>
X-MS-Has-Attach: yes
Thread-Topic: [nemo] carrying IPv4 traffic using MIP6/NEMO
Thread-Index: AcWcK3aqCs8bw2elSQa9ZTsg6BulqwAE43VA
From: "Soliman, Hesham" <H.Soliman@flarion.com>
To: "Ryuji Wakikawa" <ryuji@sfc.wide.ad.jp>
X-OriginalArrivalTime: 08 Aug 2005 17:37:32.0433 (UTC)
	FILETIME=[DB32A810:01C59C3F]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a92270ba83d7ead10c5001bb42ec3221
Cc: nemo@ietf.org, mip6@ietf.org, Keiichi SHIMA <keiichi@iijlab.net>,
	Alexandru Petrescu <alexandru.petrescu@motorola.com>
Subject: [Mip6] RE: [nemo] carrying IPv4 traffic using MIP6/NEMO
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

This is a multi-part message in MIME format.

------_=_NextPart_001_01C59C3F.DAFA9498
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Hi Ryuji,=20

 > I thought you were opposed to support NEMOv4 during the=20
 > discussion in =20
 > DT.

=3D> I'm including my last email on that topic. What I was opposed
to was discussing injecting routes over the tunnel in the=20
requirement because it's an orthogonal issue.

 >=20
 > Are there any big differences between draft-soliman(w/prefixlen)
 > and draft-keiichi for NEMO support?

=3D> I haven't read draft-keiichi but if it only adds an IPv4 prefix
to the BU then there are differences, draft-soliman deals with=20
IPv4 HoAs/prefix as well as IPv4 CoAs for MIP6 and nemo.=20

Hesham

 >=20
 > regards,
 > ryuji
 >=20
 > On 2005/08/08, at 23:53, Soliman, Hesham wrote:
 >=20
 > >>
 > >> Generally it looks like an interesting idea.  Why restraining the
 > >> binding to a fixed /32 full v4 address when binding a=20
 > variable prefix
 > >> (1...32) could bring the benefit of giving v4 access to all
 > >> nodes in the
 > >> moving network (not only to the MR).  So this may look as=20
 > an obvious
 > >> advantage.
 > >>
 > >> However, I was wondering how much would this addition extend
 > >> the current
 > >> scope of the DT work, whose goal was mainly to give v6 (not
 > >> v4) access
 > >> to MR and mobile nodes when MR connects to a v4 network.
 > >>
 > >> Giving continuous v4 access to mobile nodes in a moving
 > >> network whose MR
 > >> connects to a v4 access network can naturally be obtained=20
 > by running
 > >> Mobile IPv4 on the MR, too.
 > >>
 > >> What does the DT think?
 > >>
 > >
 > > =3D> We discussed this and I had extended draft-soliman to =
represent
 > > the IP address as : address/prefixlen, where prefixlen is=20
 > anything up
 > > to 32. It's a useful feature that only adds another 5 mins=20
 > of work =20
 > > so why
 > > not.
 > >
 > > 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=20
 > material for the =20
 > > sole use
 > >  of the intended recipient.  Any review or distribution by others =20
 > > is strictly
 > >  prohibited.  If you are not the intended recipient please=20
 > contact =20
 > > 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
 > >
 > >
 >=20
 >=20

------_=_NextPart_001_01C59C3F.DAFA9498
Content-Type: message/rfc822

X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
Received: from mail.flarion.com ([10.10.1.90]) by ftmailserver.flariontech.com
	with Microsoft SMTPSVC(5.0.2195.6713);
	Fri, 22 Jul 2005 21:09:55 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Received: from mail.mobileip.jp ([203.178.140.166]) by mail.flarion.com with
	Microsoft SMTPSVC(5.0.2195.6713); Fri, 22 Jul 2005 21:09:54 -0400
Received: from mobilegravity.sfc.wide.ad.jp (localhost [127.0.0.1]) by
	mail.mobileip.jp (Postfix) with ESMTP id B4A5264F2B;
	Sat, 23 Jul 2005 10:55:12 +0900 (JST)
Received: from mail.flarion.com (mail.flarion.com [63.103.94.23]) by
	mail.mobileip.jp (Postfix) with ESMTP id D72E864F27 for
	<mip6trans@mobileip.jp>; Sat, 23 Jul 2005 10:55:11 +0900 (JST)
Received: from ftmailserver.flariontech.com ([10.10.1.140]) by
	mail.flarion.com with Microsoft SMTPSVC(5.0.2195.6713);
	Fri, 22 Jul 2005 21:09:50 -0400
Content-class: urn:content-classes:message
Subject: RE: [Mip6trans] Requirements 6 and 8
Date: Fri, 22 Jul 2005 21:09:50 -0400
Message-ID: <A11736FE943F1A408F8BBB1B9F5FE8AD029F31EF@ftmailserver.flariontech.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6trans] Requirements 6 and 8
Thread-Index: AcWO6UikaebrpZ8yR0mt1qFmA6oPCAAOb7OA
List-Help: <mailto:mip6trans-request@mobileip.jp?subject=help>
List-Subscribe: <http://www.mobileip.jp/mailman/listinfo/mip6trans>,
	<mailto:mip6trans-request@mobileip.jp?subject=subscribe>
List-Unsubscribe: <http://www.mobileip.jp/mailman/listinfo/mip6trans>,
	<mailto:mip6trans-request@mobileip.jp?subject=unsubscribe>
From: "Soliman, Hesham" <H.Soliman@flarion.com>
Sender: <mip6trans-bounces@mobileip.jp>
To: "Vijay Devarapalli" <vijayd@iprg.nokia.com>,
	<mip6trans@mobileip.jp>
Content-Transfer-Encoding: quoted-printable



 > requirement 6 was about whether we should provide support
 > for IPv4 sessions initiated by the MN/MR without having
 > to use MIPv4. I guess everybody agrees that using MIPv4
 > and MIPv6 at the same time is not a good idea. so if a
 > MIPv6 MN or a NEMO MR, irrespective of whether it is on
 > an IPv4 or an IPv6 access network, wants to setup an IPv4
 > session with a CN we should enable it through our
 > mip6trans tunnel. the problem is described very clearly in
 > http://people.nokia.net/vijayd/mip6trans/relevant_drafts/draf
 > t-tsirtsis-dsmip-problem-01.txt
 > IMO, we should address requirement 6.

=3D> Sure.

 >=20
 > requirement 8 is about extending this to the MNNs in the
 > mobile network, so that the MNNs can also setup IPv4
 > sessions with their CNs. this does not mean we are doing
 > a NEMO solution for IPv4, just using NEMO IPv6 solution
 > for IPv4 mobile networks too. currently NEMO assumes IPv6
 > mobile network prefix. for requirement 8, we assume there
 > is an IPv4 mobile network prefix in addition and we are
 > able to carry the IPv4 traffic from the MNN to its CN over
 > the tunnel between the MR and the HA.
 >=20
 > we can address requirement 8 either here in this design
 > team or separately. I am tending towards doing it
 > separately.

=3D> Fine with me either way. My only comment was that the=20
requirement should not take about injecting routes because
it's an orthogonal issue.

Hesham

 >=20
 > Ryuji, Hesham, does this sound good?
 >=20
 > Vijay
 > _______________________________________________
 > Mip6trans mailing list
 > Mip6trans@mobileip.jp
 > http://www.mobileip.jp/mailman/listinfo/mip6trans
 >=20

=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

_______________________________________________
Mip6trans mailing list
Mip6trans@mobileip.jp
http://www.mobileip.jp/mailman/listinfo/mip6trans

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

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

------_=_NextPart_001_01C59C3F.DAFA9498--




From mip6-bounces@ietf.org Mon Aug 08 14:15:54 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2CAD-00082e-Uq; Mon, 08 Aug 2005 14:15:53 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E0tRP-0000dl-DI; Fri, 05 Aug 2005 00:04:15 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA28562;
	Fri, 5 Aug 2005 00:04:12 -0400 (EDT)
Received: from gator9.hostgator.com ([67.18.141.194])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1E0tyO-0000fx-Ba; Fri, 05 Aug 2005 00:38:22 -0400
Received: from pool-71-96-167-218.dfw.dsl-w.verizon.net ([71.96.167.218]:50098
	helo=cow) by gator9.hostgator.com with esmtpa (Exim 4.50)
	id 1E0tQ3-0007aG-8f; Thu, 04 Aug 2005 23:02:51 -0500
From: "Dawn " <dawn@icst.org>
To: <dawn@icst.org>
Date: Thu, 4 Aug 2005 23:02:54 -0500
Message-ID: <002001c59972$90fdf0d0$f922fea9@cow>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.6626
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Importance: Normal
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator9.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - icst.org
X-Spam-Score: 0.6 (/)
X-Scan-Signature: bc6181926481d86059e678c9f7cb8b34
X-Mailman-Approved-At: Mon, 08 Aug 2005 14:15:51 -0400
Cc: 
Subject: [Mip6] Call for Participation - BroadNets 2005
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="===============0105714237=="
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0105714237==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0021_01C59948.A827E8D0"

This is a multi-part message in MIME format.

------=_NextPart_000_0021_01C59948.A827E8D0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

*** We apologize if you have received multiple copies of this message =
***

=20

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

IEEE Second Annual International Conference on Broadband Networks=20
(IEEE BroadNets 2005)
October 3 - 7, 2005
Radisson Hotel Boston, Massachusetts, USA
http://www.broadnets.org/  <http://www.broadnets.org/>=20
-----------------------------------------------------------------------

IEEE BroadNets 2005 is an international conference focusing on broadband
networking and covers the entire gamut of next generation networks with =
high
bandwidth available for both wireless and wireline networks. The =
conference
consists of the following three symposia:

** Broadband Optical Networking Symposium: It covers WDM technologies,
Ethernet and MPLS integration into the optical layer, Next-Generation
SONET/SDH, as well as SAN extensions over DWDM/SONET/SDH.

** Broadband Wireless Networking Symposium: It covers mobility, routing =
for
multihop, multimedia QoS and traffic management, cross-layer =
optimization,
MAC and emerging physical layer technologies (UWB, MIMO) for high-speed
wireless networking.

** Broadband Applications/Services Symposium: It covers middleware and
service architectures for broadband applications, pervasive computing =
and
ubiquitous communications, and universal broadband access for =
information
services.

BroadNets 2005 thus offers a unique forum for researchers from academia,
government and industry to share ideas and disseminate new results in =
these
important areas.

The technical program as well registration information is available on =
the
conference website at http://www.broadnets.org/

=20

=20

=20


------=_NextPart_000_0021_01C59948.A827E8D0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">


<meta name=3DGenerator content=3D"Microsoft Word 10 (filtered)">

<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Georgia;
	panose-1:2 4 5 2 5 4 5 2 3 3;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p
	{margin-right:0in;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle17
	{font-family:Georgia;
	color:windowtext;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>*** We =
apologize if you
have received multiple copies of this message ***</span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;</span></font></p>

<p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>----------------------------------------------=
-------------------------<br>
CALL FOR PARTICIPATION</span></font></p>

<p align=3Dcenter style=3D'text-align:center'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>IEEE Second Annual International Conference =
on
Broadband Networks <br>
(</span></font>IEEE BroadNets 2005)<br>
 October 3 - 7, 2005<br>
 Radisson Hotel Boston, Massachusetts, USA<br>
<a href=3D"http://www.broadnets.org/">http://www.broadnets.org/ </a><br>
-----------------------------------------------------------------------</=
p>

<p><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>IEEE
BroadNets 2005 is an international conference focusing on broadband =
networking
and covers the entire gamut of next generation networks with high =
bandwidth
available for both wireless and wireline networks.&nbsp;The conference =
consists
of the following three symposia:</span></font></p>

<p><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>**
Broadband Optical Networking Symposium: It covers WDM technologies, =
Ethernet
and MPLS integration into the optical layer, Next-Generation SONET/SDH, =
as well
as SAN extensions over DWDM/SONET/SDH.</span></font></p>

<p><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>**
Broadband Wireless Networking Symposium: It covers mobility, routing for
multihop, multimedia QoS and traffic management, cross-layer =
optimization, MAC
and emerging physical layer technologies (UWB, MIMO) for high-speed =
wireless
networking.</span></font></p>

<p><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>**
Broadband Applications/Services Symposium: It covers middleware and =
service
architectures for broadband applications, pervasive computing and =
ubiquitous
communications, and universal broadband access for information =
services.</span></font></p>

<p><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>BroadNets
2005 thus offers a unique forum for researchers from academia, =
government and
industry to share ideas and disseminate new results in these important =
areas.</span></font></p>

<p><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>The
technical program as well registration information is available on the
conference website at <a =
href=3D"http://www.broadnets.org/">http://www.broadnets.org/</a></span></=
font></p>

<p align=3Dcenter style=3D'text-align:center'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>

<p align=3Dcenter style=3D'text-align:center'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>

<p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D2
face=3DGeorgia><span =
style=3D'font-size:11.0pt;font-family:Georgia'>&nbsp;</span></font></p>

</div>

</body>

</html>

------=_NextPart_000_0021_01C59948.A827E8D0--



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

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

--===============0105714237==--





From mip6-bounces@ietf.org Mon Aug 08 14:15:54 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2CAE-000833-IK; Mon, 08 Aug 2005 14:15:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1E0vXw-0001uk-7z
	for mip6@megatron.ietf.org; Fri, 05 Aug 2005 02:19:08 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA16731
	for <mip6@ietf.org>; Fri, 5 Aug 2005 02:19:06 -0400 (EDT)
Received: from mail2.microsoft.com ([131.107.3.124])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E0w4w-0003IQ-7s
	for mip6@ietf.org; Fri, 05 Aug 2005 02:53:17 -0400
Received: from mailout1.microsoft.com ([157.54.1.117]) by mail2.microsoft.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 4 Aug 2005 23:18:54 -0700
Received: from RED-MSG-42.redmond.corp.microsoft.com ([157.54.12.202]) by
	mailout1.microsoft.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 4 Aug 2005 23:18:53 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 4 Aug 2005 23:18:58 -0700
Message-ID: <B2A3566DA98E7B4E84B14709B640A193072A6F3B@RED-MSG-42.redmond.corp.microsoft.com>
Thread-Topic: Call For Papers: Workshop on emerging services delivery
	platforms and software models for Next Generation Network
	Services
thread-index: AcWZhZBfSV2FPQEhSB6+nT3d/ibEuw==
From: "Joshy Joseph" <jojoseph@microsoft.com>
To: <mip6@ietf.org>
X-OriginalArrivalTime: 05 Aug 2005 06:18:53.0856 (UTC)
	FILETIME=[8DCBA200:01C59985]
X-Spam-Score: 0.5 (/)
X-Scan-Signature: a5d64674af3d12893846a18a44c07b83
X-Mailman-Approved-At: Mon, 08 Aug 2005 14:15:51 -0400
Subject: [Mip6] Call For Papers: Workshop on emerging services delivery
	platforms and software models for Next Generation Network Services
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="===============2019436083=="
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

This is a multi-part message in MIME format.

--===============2019436083==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C59985.8E73024A"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C59985.8E73024A
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

=20

Apologies, if you receive multiple copies of this request.

=20

Call For Papers:  Workshop on emerging services delivery platforms and
software models for Next Generation Network Services
(http://www.softplatforms.org)

This workshop will be held in conjunction with the FIRST International
Conference on COMmunication System softWAre and MiddlewaRE (COMSWARE
2006) at New Delhi, India (http://www.comsware.org/) from Jan 8-12 2006.


=20

The exact date of the workshop will be made available on the workshop's
Web site http://www.softplatforms.org.

=20

Workshop Objectives:=20

The next generation services networks deliver enhanced business
capabilities such as data, video, messaging and business functions for
wired and wireless consumers. These new sets of services enhance the
business opportunities by integrating with core business services,
including: supply chain management, customer management, and consumer
applications. This workshop aims to discuss topics related to emerging
next generation services and service delivery platforms to host/support
such complex application environments.=20

=20

The workshop focuses on:

* How next generation service delivery platforms deliver enhanced QoS
management, operational efficiencies, flexible services composability,
faster time-to-market, efficient trust models and flexible pricing
models.

* Technical and business factors influencing the services composability
and network services delivery environments. The associated revenue and
cost models for consumers, suppliers and application providers.

* The influences of emerging distributed computing architecture styles
(loosely-coupled, asynchronous, compos able, collaborative,
decentralized and parallel services) related to service delivery models.

* Emerging middleware platforms for network services, service
composability, distributed architecture models and programming models.

* New services models (communication services, presence-enabled
services, content/media services and enterprise/legacy services) and
value creation environments that represents new business opportunities
for operators and providers.

=20

This workshop invites papers from research and business communities on
the different aspects of service delivery platforms and emerging
services models. The workshop will include papers that examine
interesting practical problems, case studies, best practices, middleware
platforms and innovative messaging architectures.=20

=20

Submission Guidelines:

All papers are limited to 5 pages and must be in standard IEEE
double-column format. All submissions must be sent by email to the
workshops co-chairs with the e-mail addresses given above.=20

=20

Important Dates:=20

Paper Submission Deadline: September 23, 2005=20

Notification of Acceptance: October 28, 2005=20

Camera-Ready Papers: November 25, 2005=20

=20

Contact and organization:

For any questions regarding the workshop feel free to contact=20

1. Craig Fellenstein, IBM (cfellen@us.ibm.com)=20

2. Joshy Joseph, Microsoft (jojoseph@microsoft.com)=20

=20

Submission requirements:

All papers are limited to 5 pages and must be in standard IEEE
double-column format. All submissions must be sent by email to the
workshops co-chairs.


------_=_NextPart_001_01C59985.8E73024A
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"country-region"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"City"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place" downloadurl=3D"http://www.5iantlavalamp.com/"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Apologies, if you receive multiple copies of this =
request.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Call For Papers:&nbsp; Workshop on emerging services =
delivery
platforms and software models for Next Generation Network Services
(http://www.softplatforms.org)<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>This workshop will be held in conjunction with the =
FIRST
International Conference on COMmunication System softWAre and MiddlewaRE
(COMSWARE 2006) at <st1:place w:st=3D"on"><st1:City w:st=3D"on">New =
Delhi</st1:City>,
 <st1:country-region w:st=3D"on">India</st1:country-region></st1:place>
(http://www.comsware.org/) from Jan 8-12 2006. =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>The exact date of the workshop will be made available =
on the
workshop's Web site =
http://www.softplatforms.org.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Workshop Objectives: <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>The next generation services networks deliver =
enhanced
business capabilities such as data, video, messaging and business =
functions for
wired and wireless consumers. These new sets of services enhance the =
business
opportunities by integrating with core business services, including: =
supply
chain management, customer management, and consumer applications. This =
workshop
aims to discuss topics related to emerging next generation services and =
service
delivery platforms to host/support such complex application =
environments. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>The workshop focuses on:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>* How next generation service delivery platforms =
deliver
enhanced QoS management, operational efficiencies, flexible services
composability, faster time-to-market, efficient trust models and =
flexible
pricing models.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>* Technical and business factors influencing the =
services
composability and network services delivery environments. The associated
revenue and cost models for consumers, suppliers and application =
providers.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>* The influences of emerging distributed computing
architecture styles (loosely-coupled, asynchronous, compos able, =
collaborative,
decentralized and parallel services) related to service delivery =
models.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>* Emerging middleware platforms for network services,
service composability, distributed architecture models and programming =
models.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>* New services models (communication services,
presence-enabled services, content/media services and enterprise/legacy
services) and value creation environments that represents new business
opportunities for operators and providers.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>This workshop invites papers from research and =
business
communities on the different aspects of service delivery platforms and =
emerging
services models. The workshop will include papers that examine =
interesting
practical problems, case studies, best practices, middleware platforms =
and
innovative messaging architectures. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Submission Guidelines:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>All papers are limited to 5 pages and must be in =
standard
IEEE double-column format. All submissions must be sent by email to the
workshops co-chairs with the e-mail addresses given above. =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Important Dates: <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Paper Submission Deadline: September 23, 2005 =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Notification of Acceptance: October 28, 2005 =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Camera-Ready Papers: November 25, 2005 =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Contact and =
organization:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>For any questions regarding the workshop feel free to
contact <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>1. Craig Fellenstein, IBM (cfellen@us.ibm.com) =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>2. Joshy Joseph, Microsoft (jojoseph@microsoft.com) =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Submission requirements:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>All papers are limited to 5 pages and must be in =
standard
IEEE double-column format. All submissions must be sent by email to the
workshops co-chairs.<o:p></o:p></span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C59985.8E73024A--


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

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

--===============2019436083==--




From mip6-bounces@ietf.org Tue Aug 09 03:11:06 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2OGQ-0004iZ-1j; Tue, 09 Aug 2005 03:11:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1E2OGO-0004i1-1a
	for mip6@megatron.ietf.org; Tue, 09 Aug 2005 03:11:04 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA16293
	for <mip6@ietf.org>; Tue, 9 Aug 2005 03:10:59 -0400 (EDT)
Received: from bundit.graduate.kmitl.ac.th ([161.246.39.3])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E2Oo5-0004tZ-Np
	for mip6@ietf.org; Tue, 09 Aug 2005 03:46:01 -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
	j7978uwD009241; Tue, 9 Aug 2005 14:09:01 +0700
Message-ID: <42F856C3.7030504@graduate.kmitl.ac.th>
Date: Tue, 09 Aug 2005 14:09:55 +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
Cc: Francis.Dupont@enst-bretagne.fr
Subject: [Mip6] Using IPsec between mobile and correspondent IPv6 node
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


    I have read draft-dupont-mipv6-cn-ipsec-00.txt, they sugguests to 
use IPsec to protect Return routability (RR) method before process 
binding update.  It solves man in the middle attack problems in HA-CN 
and  MN-CN path,right?  So, The Kbm using in BU and BA are safed now.
    But Instead of using IPSec to protect RR method, why we don't use 
IPSec to protect BU? Does it make handoff process faster? :-)

Thank you for your 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 Aug 09 05:31:41 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2QST-0007fF-L9; Tue, 09 Aug 2005 05:31:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2QSR-0007f7-Lb; Tue, 09 Aug 2005 05:31:39 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA24519;
	Tue, 9 Aug 2005 05:31:37 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1E2R0J-00019v-4n; Tue, 09 Aug 2005 06:06:40 -0400
Received: from il06exr02.mot.com (il06exr02.mot.com [129.188.137.132])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id j799fGpl001554;
	Tue, 9 Aug 2005 02:41:20 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by il06exr02.mot.com (8.13.1/8.13.0) with ESMTP id j799bPjI022320;
	Tue, 9 Aug 2005 04:37:26 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 310EF865980; Tue,  9 Aug 2005 11:31:22 +0200 (CEST)
Message-ID: <42F877E9.8010304@motorola.com>
Date: Tue, 09 Aug 2005 11:31:21 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: "Soliman, Hesham" <H.Soliman@flarion.com>
References: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCAC1@ftmailserver.flariontech.com>
In-Reply-To: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCAC1@ftmailserver.flariontech.com>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Content-Transfer-Encoding: 7bit
Cc: nemo@ietf.org, mip6@ietf.org, Keiichi SHIMA <keiichi@iijlab.net>
Subject: [Mip6] Re: [nemo] carrying IPv4 traffic using MIP6/NEMO
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

Hello Hesham,

Soliman, Hesham wrote:
>> 
>> Generally it looks like an interesting idea.  Why restraining the 
>> binding to a fixed /32 full v4 address when binding a variable 
>> prefix (1...32) could bring the benefit of giving v4 access to all 
>> nodes in the moving network (not only to the MR).  So this may look
>> as an obvious advantage.
>> 
>> However, I was wondering how much would this addition extend the 
>> current scope of the DT work, whose goal was mainly to give v6 (not
>>  v4) access to MR and mobile nodes when MR connects to a v4 
>> network.
>> 
>> Giving continuous v4 access to mobile nodes in a moving network 
>> whose MR connects to a v4 access network can naturally be obtained 
>> by running Mobile IPv4 on the MR, too.
>> 
>> What does the DT think?
> 
> => We discussed this

Great, does the DT have a requirement for giving v4 access to nodes in a
moving network whose MR runs Mobile IPv6 and connects to a v4 access
network?

If yes, does the requirement include v4 session continuity?  Does the
requirement include reachability at a permanent v4 address?  These
aspects are important, at least for deciding on whether or not to use
NAT within the moving network (see draft-shima).

> and I had extended draft-soliman to represent the IP address as :
> address/prefixlen, where prefixlen is anything up to 32. It's a
> useful feature that only adds another 5 mins of work so why not.

Hesham, did you encode the prefixlen on 8 or 5 bits?  Anyways, I don't
think simply adding a v4 prefixlen into a message format is as easy as
it may look.  Conceptually - yes, just use a prefixlen, but from there
to a protocol may be a longer way.  For example, what happens when MR's
v4 Home Address is independent of the Mobile Network Prefix (they differ
starting at the 0th bit).

I think giving v4 access to nodes in the moving network would best be
done by a NEMOv4 protocol.

Alex

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



From mip6-bounces@ietf.org Tue Aug 09 07:18:59 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2S8J-000565-MQ; Tue, 09 Aug 2005 07:18:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1E2S8I-000560-Di
	for mip6@megatron.ietf.org; Tue, 09 Aug 2005 07:18:58 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA29010
	for <mip6@ietf.org>; Tue, 9 Aug 2005 07:18:55 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E2SgA-0003jw-Sz
	for mip6@ietf.org; Tue, 09 Aug 2005 07:54: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 j79BIXn23844; Tue, 9 Aug 2005 13:18: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.13.1/8.13.1) with ESMTP id
	j79BIUes041291; Tue, 9 Aug 2005 13:18:34 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200508091118.j79BIUes041291@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Warodom Werapun <ple@graduate.kmitl.ac.th>
In-reply-to: Your message of Tue, 09 Aug 2005 14:09:55 +0700.
	<42F856C3.7030504@graduate.kmitl.ac.th> 
Date: Tue, 09 Aug 2005 13:18:30 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: mip6@ietf.org
Subject: [Mip6] Re: Using IPsec between mobile and correspondent IPv6 node 
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

 In your previous mail you wrote:

       I have read draft-dupont-mipv6-cn-ipsec-00.txt, they sugguests to 

=> it is draft-ietf-mip6-cn-ipsec-01.txt now.

   use IPsec to protect Return routability (RR) method before process 

=> no, IPsec is used to verify HoA option and to protect RO signaling
in this draft.

   binding update.  It solves man in the middle attack problems in HA-CN 
   and  MN-CN path,right?  So, The Kbm using in BU and BA are safed now.

=> I believe you make some confusion between RFC 377[56] which uses
IPsec to protect some RR messages and the draft which protects directly
the BU/BA,

       But Instead of using IPSec to protect RR method, why we don't use 
   IPSec to protect BU?

=> this is the idea of the draft.

    Does it make handoff process faster? :-)

=> of course it is faster because there is no RR phase (.5 RTT in place
of >1.5 RTT).
   
Can you read the last version and if you find it is not clear enough
propose improvements? I know the wording is not so good and as it will
be last called soon...

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 Aug 09 09:56:17 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2UaX-0001sv-1k; Tue, 09 Aug 2005 09: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 1E2UaT-0001sL-MB; Tue, 09 Aug 2005 09:56:14 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07985;
	Tue, 9 Aug 2005 09:56:11 -0400 (EDT)
Received: from mail.flarion.com ([63.103.94.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1E2V8N-00008f-Ob; Tue, 09 Aug 2005 10:31:16 -0400
Received: from ftmailserver.flariontech.com ([10.10.1.140]) by
	mail.flarion.com with Microsoft SMTPSVC(5.0.2195.6713);
	Tue, 9 Aug 2005 09:56:03 -0400
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 9 Aug 2005 09:56:03 -0400
Message-ID: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCACB@ftmailserver.flariontech.com>
Thread-Topic: [nemo] carrying IPv4 traffic using MIP6/NEMO
Thread-Index: AcWcxR7QtS9w1k4VT/OSe8cAMOI69gAJIZfg
From: "Soliman, Hesham" <H.Soliman@flarion.com>
To: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>
X-OriginalArrivalTime: 09 Aug 2005 13:56:03.0577 (UTC)
	FILETIME=[14D5E690:01C59CEA]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Content-Transfer-Encoding: quoted-printable
Cc: nemo@ietf.org, mip6@ietf.org, Keiichi SHIMA <keiichi@iijlab.net>
Subject: [Mip6] RE: [nemo] carrying IPv4 traffic using MIP6/NEMO
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


 > Great, does the DT have a requirement for giving v4 access=20
 > to nodes in a
 > moving network whose MR runs Mobile IPv6 and connects to a v4 access
 > network?
 >=20
 > If yes, does the requirement include v4 session continuity?  Does the
 > requirement include reachability at a permanent v4 address?  These
 > aspects are important, at least for deciding on whether or not to use
 > NAT within the moving network (see draft-shima).

=3D> I think Vijay included all our requirements so far in the=20
slides in Paris. So there is nothing more than what's in those=20
slides.

 > Hesham, did you encode the prefixlen on 8 or 5 bits? =20
 > Anyways, I don't
 > think simply adding a v4 prefixlen into a message format is=20
 > as easy as
 > it may look.  Conceptually - yes, just use a prefixlen, but=20
 > from there
 > to a protocol may be a longer way.  For example, what=20
 > happens when MR's
 > v4 Home Address is independent of the Mobile Network Prefix=20
 > (they differ
 > starting at the 0th bit).

=3D> That's no different to the IPv6 case.=20

 >=20
 > I think giving v4 access to nodes in the moving network would best be
 > done by a NEMOv4 protocol.

=3D> It's not about giving v4 access to those nodes, it's about=20
updating the MR's v4 home address/prefix to its current CoA.=20
What happens inside the network is not in scope of transition =
mechanisms.

Hesham

 >=20
 > Alex
 >=20

=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 Tue Aug 09 10:05:26 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2UjO-0005Xn-6Z; Tue, 09 Aug 2005 10: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 1E2UjM-0005Xf-J1; Tue, 09 Aug 2005 10:05:24 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08538;
	Tue, 9 Aug 2005 10:05:22 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1E2VHH-0000Nm-KQ; Tue, 09 Aug 2005 10:40:27 -0400
Received: from az33exr04.mot.com ([10.64.251.234])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id j79EFGhW020779;
	Tue, 9 Aug 2005 07:15:16 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by az33exr04.mot.com (8.13.1/8.13.0) with ESMTP id j79EA1Rs003015;
	Tue, 9 Aug 2005 09:10:02 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 81648865980; Tue,  9 Aug 2005 16:05:20 +0200 (CEST)
Message-ID: <42F8B820.1040607@motorola.com>
Date: Tue, 09 Aug 2005 16:05:20 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Organization: Motorola Labs, Paris, France
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: "Soliman, Hesham" <H.Soliman@flarion.com>
References: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCACB@ftmailserver.flariontech.com>
In-Reply-To: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCACB@ftmailserver.flariontech.com>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Content-Transfer-Encoding: 7bit
Cc: nemo@ietf.org, mip6@ietf.org,
	Alexandru Petrescu <alexandru.petrescu@motorola.com>
Subject: [Mip6] Re: [nemo] carrying IPv4 traffic using MIP6/NEMO
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

Soliman, Hesham wrote:

>> Great, does the DT have a requirement for giving v4 access to nodes
>> in a moving network whose MR runs Mobile IPv6 and connects to a v4
>> access network?
>> 
>> If yes, does the requirement include v4 session continuity?  Does
>> the requirement include reachability at a permanent v4 address?
>> These aspects are important, at least for deciding on whether or
>> not to use NAT within the moving network (see draft-shima).
> 
> => I think Vijay included all our requirements so far in the slides
> in Paris. So there is nothing more than what's in those slides.
> 
>> Hesham, did you encode the prefixlen on 8 or 5 bits? Anyways, I
>> don't think simply adding a v4 prefixlen into a message format is 
>> as easy as it may look.  Conceptually - yes, just use a prefixlen,
>> but from there to a protocol may be a longer way.  For example,
>> what happens when MR's v4 Home Address is independent of the Mobile
>> Network Prefix (they differ starting at the 0th bit).
> 
> => That's no different to the IPv6 case.

Yes it is.  In v6 one gets the v6 Home Address from the DO, and that can
be different than the address and prefixlen that is in the BU.

With a NEMOv6 that supports a v4 MNP the v6 HA can't find a v4 Home
Address other than the one on which you attached a prefix len.

If I am making myself clear...

>> I think giving v4 access to nodes in the moving network would best
>> be done by a NEMOv4 protocol.
> 
> => It's not about giving v4 access to those nodes, it's about 
> updating the MR's v4 home address/prefix to its current CoA. What
> happens inside the network is not in scope of transition mechanisms.

Is mip6trans doing a "transition mechanism"?  I don't get the above.

Alex

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



From mip6-bounces@ietf.org Tue Aug 09 10:09:35 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2UnP-0006p5-Oe; Tue, 09 Aug 2005 10:09:35 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2UnN-0006o3-PQ; Tue, 09 Aug 2005 10:09:33 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09079;
	Tue, 9 Aug 2005 10:09:31 -0400 (EDT)
Received: from mail.flarion.com ([63.103.94.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1E2VLH-0000WX-Pt; Tue, 09 Aug 2005 10:44:37 -0400
Received: from ftmailserver.flariontech.com ([10.10.1.140]) by
	mail.flarion.com with Microsoft SMTPSVC(5.0.2195.6713);
	Tue, 9 Aug 2005 10:09:23 -0400
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 9 Aug 2005 10:09:23 -0400
Message-ID: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCACC@ftmailserver.flariontech.com>
Thread-Topic: [nemo] carrying IPv4 traffic using MIP6/NEMO
Thread-Index: AcWc62LKIuVLYUyvTlm9otiz0t6wzgAAE+Cg
From: "Soliman, Hesham" <H.Soliman@flarion.com>
To: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>
X-OriginalArrivalTime: 09 Aug 2005 14:09:23.0770 (UTC)
	FILETIME=[F1C9A9A0:01C59CEB]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Content-Transfer-Encoding: quoted-printable
Cc: nemo@ietf.org, mip6@ietf.org
Subject: [Mip6] RE: [nemo] carrying IPv4 traffic using MIP6/NEMO
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


 > > =3D> That's no different to the IPv6 case.
 >=20
 > Yes it is.  In v6 one gets the v6 Home Address from the DO,=20
 > and that can
 > be different than the address and prefixlen that is in the BU.

=3D> And the DO can contain an IPv4-mapped IPv6 address. So again
there is no difference. It is only tricky if you have both
v4 and v6 addresses and need to contain more than one of those.=20

 > >> I think giving v4 access to nodes in the moving network would best
 > >> be done by a NEMOv4 protocol.
 > >=20
 > > =3D> It's not about giving v4 access to those nodes, it's about=20
 > > updating the MR's v4 home address/prefix to its current CoA. What
 > > happens inside the network is not in scope of transition=20
 > mechanisms.
 >=20
 > Is mip6trans doing a "transition mechanism"?  I don't get the above.

=3D> That's what "trans" stands for in "miptrans".

Hesham


 >=20
 > Alex
 >=20

=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 Tue Aug 09 10:11:32 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2UpI-0007kP-GD; Tue, 09 Aug 2005 10:11:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2UpG-0007k7-Rh; Tue, 09 Aug 2005 10:11:30 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09346;
	Tue, 9 Aug 2005 10:11:28 -0400 (EDT)
Received: from omgo.iij.ad.jp ([202.232.30.157])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1E2VNA-0000bu-Mq; Tue, 09 Aug 2005 10:46:34 -0400
Received: OTM-MO id j79EBFOt028449; Tue, 9 Aug 2005 23:11:15 +0900 (JST)
Received: OTM-MIX0 id j79EBElY001251; Tue, 9 Aug 2005 23:11:14 +0900 (JST)
Received: from localhost (jc-ssh.iij.ad.jp [192.168.174.22])
	by jc-smtp.iij.ad.jp (JC-SMTP/jc-smtp) id j79EBA2D022869;
	Tue, 9 Aug 2005 23:11:11 +0900 (JST)
Date: Tue, 09 Aug 2005 16:11:15 +0200 (CEST)
Message-Id: <20050809.161115.104154887.keiichi@iijlab.net>
To: H.Soliman@flarion.com
Subject: Re: [Mip6] RE: [nemo] carrying IPv4 traffic using MIP6/NEMO
From: Keiichi SHIMA <keiichi@iijlab.net>
In-Reply-To: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCAC4@ftmailserver.flariontech.com>
References: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCAC4@ftmailserver.flariontech.com>
X-Mailer: Mew version 4.2.53 on Emacs 22.0.50 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Content-Transfer-Encoding: 7bit
Cc: nemo@ietf.org, mip6@ietf.org, ryuji@sfc.wide.ad.jp,
	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

Hello Hesham,

From: "Soliman, Hesham" <H.Soliman@flarion.com>
Date: Mon, 8 Aug 2005 13:37:32 -0400

>  > Are there any big differences between draft-soliman(w/prefixlen)
>  > and draft-keiichi for NEMO support?
> 
> => I haven't read draft-keiichi but if it only adds an IPv4 prefix
> to the BU then there are differences, draft-soliman deals with 
> IPv4 HoAs/prefix as well as IPv4 CoAs for MIP6 and nemo. 

The IPv4 CoAs are for IPv6 Mobility over IPv4 access networks, and the
IPv4 HoAs/Prefixes are for IPv4 Mobility over IPv6 networks, if I
understand correctly.

Then, the above two things are orthogonal and should be split into two
separate specifications?

Regards,
---
Keiichi SHIMA
IIJ Research Laboratory <keiichi@iijlab.net>
KAME Project <keiichi@kame.net>


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



From mip6-bounces@ietf.org Tue Aug 09 10:14:38 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2UsI-0000JU-CS; Tue, 09 Aug 2005 10:14:38 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2UsF-0000J0-68; Tue, 09 Aug 2005 10:14:35 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09664;
	Tue, 9 Aug 2005 10:14:32 -0400 (EDT)
Received: from mail.flarion.com ([63.103.94.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1E2VQA-0000i5-9y; Tue, 09 Aug 2005 10:49:38 -0400
Received: from ftmailserver.flariontech.com ([10.10.1.140]) by
	mail.flarion.com with Microsoft SMTPSVC(5.0.2195.6713);
	Tue, 9 Aug 2005 10:14:26 -0400
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
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] RE: [nemo] carrying IPv4 traffic using MIP6/NEMO
Date: Tue, 9 Aug 2005 10:14:25 -0400
Message-ID: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCACD@ftmailserver.flariontech.com>
Thread-Topic: [Mip6] RE: [nemo] carrying IPv4 traffic using MIP6/NEMO
Thread-Index: AcWc7DXr18KaNS66SWmQY4m8mmxQGQAAA4HA
From: "Soliman, Hesham" <H.Soliman@flarion.com>
To: "Keiichi SHIMA" <keiichi@iijlab.net>
X-OriginalArrivalTime: 09 Aug 2005 14:14:26.0084 (UTC)
	FILETIME=[A5FB1E40:01C59CEC]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Content-Transfer-Encoding: quoted-printable
Cc: nemo@ietf.org, mip6@ietf.org, ryuji@sfc.wide.ad.jp,
	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


 > From: "Soliman, Hesham" <H.Soliman@flarion.com>
 > Date: Mon, 8 Aug 2005 13:37:32 -0400
 >=20
 > >  > Are there any big differences between draft-soliman(w/prefixlen)
 > >  > and draft-keiichi for NEMO support?
 > >=20
 > > =3D> I haven't read draft-keiichi but if it only adds an IPv4 =
prefix
 > > to the BU then there are differences, draft-soliman deals with=20
 > > IPv4 HoAs/prefix as well as IPv4 CoAs for MIP6 and nemo.=20
 >=20
 > The IPv4 CoAs are for IPv6 Mobility over IPv4 access=20
 > networks, and the
 > IPv4 HoAs/Prefixes are for IPv4 Mobility over IPv6 networks, if I
 > understand correctly.

=3D> Not really. There is no need for that binding. If you have=20
a HoA you always want to use it regardless of the access network
you are on. So if you have a v6 HoA you'll use it whether you're=20
in an IPv4 or an IPv6 or dual stack access. The same goes for the=20
v4 home address.=20

 >=20
 > Then, the above two things are orthogonal and should be=20
 > split into two
 > separate specifications?

=3D> Not necessarily. It's one problem that the DT is trying to address.
There are different permutations depending on the scenario, but that
doesn't mean each permutation should be documented separately. That
would make life very complex.

Hesham


 >=20
 > Regards,
 > ---
 > Keiichi SHIMA
 > IIJ Research Laboratory <keiichi@iijlab.net>
 > KAME Project <keiichi@kame.net>
 >=20
 >=20

=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 Tue Aug 09 10:28:42 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2V5u-0006HV-Ch; Tue, 09 Aug 2005 10:28:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1E2V5o-0006G1-14
	for mip6@megatron.ietf.org; Tue, 09 Aug 2005 10:28:40 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11138
	for <mip6@ietf.org>; Tue, 9 Aug 2005 10:28:33 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E2Vdi-00018q-13
	for mip6@ietf.org; Tue, 09 Aug 2005 11:03:39 -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 j79ESEn04721; Tue, 9 Aug 2005 16:28:14 +0200
Received: from givry.rennes.enst-bretagne.fr
	(localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id
	j79ESE8l042264; Tue, 9 Aug 2005 16:28:14 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200508091428.j79ESE8l042264@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "James Kempf" <Kempf@docomolabs-usa.com>
Subject: Re: [Mip6] MN-HA Reliability Work? 
In-reply-to: Your message of Fri, 05 Aug 2005 01:51:34 PDT.
	<TAIBAIreBBsQwY6YHki00000053@exchange.adaptix.com> 
Date: Tue, 09 Aug 2005 16:28:14 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
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

 In your previous mail you wrote:

   Could you elaborate how you think this affects Qin's draft idea of having an
   HA be able to initiate the SA?
   
=> the I-D is draft-li-mip6-ha-init-bootstrap-00.txt, isn't it?

I can see some issues with the idea to get the HA as the initiator:
 - as I already wrote, current Mobike proposed protocol assumes the
   initiator is the mobile side, what I summaried by "the initiator decides"
 - IKEv2 itself has less facilities, for instance:
   * IDr from the initiator (shouldn't matter)
   * no EAP for the responder (this should really matter but EAP over IKEv2
     could be extended)
   * no CFG_REQUEST for the responder (this makes sense but should matter too)

Regards

Francis.Dupont@enst-bretagne.fr

PS: IMHO it could be better to design some kind of callbacks in order
to launch IKE the "right way".

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



From mip6-bounces@ietf.org Tue Aug 09 10:31:50 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2V8w-0007t8-Ix; Tue, 09 Aug 2005 10:31:50 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2V8u-0007t0-Fq; Tue, 09 Aug 2005 10:31:48 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11300;
	Tue, 9 Aug 2005 10:31:46 -0400 (EDT)
Received: from omgo.iij.ad.jp ([202.232.30.157])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1E2Vgo-0001G8-DS; Tue, 09 Aug 2005 11:06:52 -0400
Received: OTM-MO id j79EVheN029519; Tue, 9 Aug 2005 23:31:43 +0900 (JST)
Received: OTM-MIX0 id j79EVggB007304; Tue, 9 Aug 2005 23:31:42 +0900 (JST)
Received: from localhost (jc-ssh.iij.ad.jp [192.168.174.22])
	by jc-smtp.iij.ad.jp (JC-SMTP/jc-smtp) id j79EVdMt023359;
	Tue, 9 Aug 2005 23:31:40 +0900 (JST)
Date: Tue, 09 Aug 2005 16:31:44 +0200 (CEST)
Message-Id: <20050809.163144.108677394.keiichi@iijlab.net>
To: H.Soliman@flarion.com
Subject: Re: [Mip6] RE: [nemo] carrying IPv4 traffic using MIP6/NEMO
From: Keiichi SHIMA <keiichi@iijlab.net>
In-Reply-To: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCACD@ftmailserver.flariontech.com>
References: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCACD@ftmailserver.flariontech.com>
X-Mailer: Mew version 4.2.53 on Emacs 22.0.50 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Content-Transfer-Encoding: 7bit
Cc: nemo@ietf.org, mip6@ietf.org, ryuji@sfc.wide.ad.jp,
	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

Hi Hesham,

From: "Soliman, Hesham" <H.Soliman@flarion.com>
Date: Tue, 9 Aug 2005 10:14:25 -0400
>  > 
>  > The IPv4 CoAs are for IPv6 Mobility over IPv4 access 
>  > networks, and the
>  > IPv4 HoAs/Prefixes are for IPv4 Mobility over IPv6 networks, if I
>  > understand correctly.
> 
> => Not really. There is no need for that binding. If you have 
> a HoA you always want to use it regardless of the access network
> you are on. So if you have a v6 HoA you'll use it whether you're 
> in an IPv4 or an IPv6 or dual stack access. The same goes for the 
> v4 home address. 

I think I understand what you mean.  You are trying to provide the
mechanism Mobile IPv4 (network) over IPv4 access networks using
MIP6/NEMO signaling mechanisms, correct?

I thought that kind of configuration was not the scope of the DT team.
I even thought Mobile IPv4 over IPv6 was also out of scope, since I
though the DT team were discussing the mechanism to provide IPv6
mobility over IPv4 access networks.

Are such configurations are still in the v4traversal DT scope?

Regards,
---
Keiichi SHIMA
IIJ Research Laboratory <keiichi@iijlab.net>
KAME Project <keiichi@kame.net>



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



From mip6-bounces@ietf.org Tue Aug 09 10:36:39 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2VDb-0001v2-Bk; Tue, 09 Aug 2005 10:36:39 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2VDY-0001uQ-RB; Tue, 09 Aug 2005 10:36:37 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11746;
	Tue, 9 Aug 2005 10:36:34 -0400 (EDT)
Received: from mail.flarion.com ([63.103.94.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1E2VlT-0001Os-8N; Tue, 09 Aug 2005 11:11:40 -0400
Received: from ftmailserver.flariontech.com ([10.10.1.140]) by
	mail.flarion.com with Microsoft SMTPSVC(5.0.2195.6713);
	Tue, 9 Aug 2005 10:36:26 -0400
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
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] RE: [nemo] carrying IPv4 traffic using MIP6/NEMO
Date: Tue, 9 Aug 2005 10:36:26 -0400
Message-ID: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCACE@ftmailserver.flariontech.com>
Thread-Topic: [Mip6] RE: [nemo] carrying IPv4 traffic using MIP6/NEMO
Thread-Index: AcWc7xHOBENvg2a4SgWH8t4b9bmiQQAAC+Wg
From: "Soliman, Hesham" <H.Soliman@flarion.com>
To: "Keiichi SHIMA" <keiichi@iijlab.net>
X-OriginalArrivalTime: 09 Aug 2005 14:36:26.0811 (UTC)
	FILETIME=[B93210B0:01C59CEF]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Content-Transfer-Encoding: quoted-printable
Cc: nemo@ietf.org, mip6@ietf.org, ryuji@sfc.wide.ad.jp,
	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

Hi Keichi,

 > > =3D> Not really. There is no need for that binding. If you have=20
 > > a HoA you always want to use it regardless of the access network
 > > you are on. So if you have a v6 HoA you'll use it whether you're=20
 > > in an IPv4 or an IPv6 or dual stack access. The same goes for the=20
 > > v4 home address.=20
 >=20
 > I think I understand what you mean.  You are trying to provide the
 > mechanism Mobile IPv4 (network) over IPv4 access networks using
 > MIP6/NEMO signaling mechanisms, correct?
 >=20
 > I thought that kind of configuration was not the scope of=20
 > the DT team.
 > I even thought Mobile IPv4 over IPv6 was also out of scope, since I
 > though the DT team were discussing the mechanism to provide IPv6
 > mobility over IPv4 access networks.

=3D> We're not doing anything with MIPv4 in the DT. We're trying to
allow the MN (that includes MR), using MIPv6, to be able to use=20
an IPv4 or IPv6 home address in any access network that it might be=20
in.
I think this summarizes the problem that the DT is addressing.

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 Tue Aug 09 10:53:50 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2VUE-0000vT-8c; Tue, 09 Aug 2005 10:53:50 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2VUC-0000vL-KA; Tue, 09 Aug 2005 10:53:48 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13070;
	Tue, 9 Aug 2005 10:53:46 -0400 (EDT)
Received: from motgate5.mot.com ([144.189.100.105])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1E2W25-00020c-2V; Tue, 09 Aug 2005 11:28:52 -0400
Received: from az33exr04.mot.com (az33exr04.mot.com [10.64.251.234])
	by motgate5.mot.com (8.12.11/Motgate5) with ESMTP id j79F0FuR008196;
	Tue, 9 Aug 2005 08:00:15 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by az33exr04.mot.com (8.13.1/8.13.0) with ESMTP id j79EwAq5017769;
	Tue, 9 Aug 2005 09:58:11 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 4E038865980; Tue,  9 Aug 2005 16:53:05 +0200 (CEST)
Message-ID: <42F8C351.3090502@motorola.com>
Date: Tue, 09 Aug 2005 16:53:05 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Organization: Motorola Labs, Paris, France
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: "Soliman, Hesham" <H.Soliman@flarion.com>
References: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCACC@ftmailserver.flariontech.com>
In-Reply-To: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCACC@ftmailserver.flariontech.com>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Content-Transfer-Encoding: 7bit
Cc: nemo@ietf.org, mip6@ietf.org,
	Alexandru Petrescu <alexandru.petrescu@motorola.com>
Subject: [Mip6] Re: [nemo] carrying IPv4 traffic using MIP6/NEMO
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

Soliman, Hesham wrote:
>>> => That's no different to the IPv6 case.
>> 
>> Yes it is.  In v6 one gets the v6 Home Address from the DO, and
>> that can be different than the address and prefixlen that is in the
>> BU.
> 
> => And the DO can contain an IPv4-mapped IPv6 address. So again there
> is no difference. It is only tricky if you have both v4 and v6
> addresses and need to contain more than one of those.

So it is acknowledged that this may become tricky.  I agree.

Alex

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



From mip6-bounces@ietf.org Tue Aug 09 11:00:01 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2VaD-00039h-QQ; Tue, 09 Aug 2005 11:00:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2VaC-00039Y-RW; Tue, 09 Aug 2005 11:00:00 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13729;
	Tue, 9 Aug 2005 10:59:58 -0400 (EDT)
Received: from motgate5.mot.com ([144.189.100.105])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1E2W87-0002Jt-OX; Tue, 09 Aug 2005 11:35:04 -0400
Received: from az33exr03.mot.com (az33exr03.mot.com [10.64.251.233])
	by motgate5.mot.com (8.12.11/Motgate5) with ESMTP id j79F6dIY011667;
	Tue, 9 Aug 2005 08:06:39 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by az33exr03.mot.com (8.13.1/8.13.0) with ESMTP id j79F625e014919;
	Tue, 9 Aug 2005 10:06:03 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 0126A865980; Tue,  9 Aug 2005 16:59:54 +0200 (CEST)
Message-ID: <42F8C4E9.7050705@motorola.com>
Date: Tue, 09 Aug 2005 16:59:53 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Organization: Motorola Labs, Paris, France
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: "Soliman, Hesham" <H.Soliman@flarion.com>
Subject: Re: [Mip6] RE: [nemo] carrying IPv4 traffic using MIP6/NEMO
References: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCACE@ftmailserver.flariontech.com>
In-Reply-To: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCACE@ftmailserver.flariontech.com>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Content-Transfer-Encoding: 7bit
Cc: nemo@ietf.org, mip6@ietf.org, ryuji@sfc.wide.ad.jp,
	Keiichi SHIMA <keiichi@iijlab.net>,
	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

Soliman, Hesham wrote:

> Hi Keichi,
> 
>>> => Not really. There is no need for that binding. If you have a
>>> HoA you always want to use it regardless of the access network 
>>> you are on. So if you have a v6 HoA you'll use it whether you're
>>>  in an IPv4 or an IPv6 or dual stack access. The same goes for
>>> the v4 home address.
>> 
>> I think I understand what you mean.  You are trying to provide the 
>> mechanism Mobile IPv4 (network) over IPv4 access networks using 
>> MIP6/NEMO signaling mechanisms, correct?
>> 
>> I thought that kind of configuration was not the scope of the DT
>> team. I even thought Mobile IPv4 over IPv6 was also out of scope,
>> since I though the DT team were discussing the mechanism to provide
>> IPv6 mobility over IPv4 access networks.
> 
> => We're not doing anything with MIPv4 in the DT. We're trying to 
> allow the MN (that includes MR), using MIPv6, to be able to use an
> IPv4 or IPv6 home address in any access network that it might be in. 
> I think this summarizes the problem that the DT is addressing.

I think some of the things that are addressed by the mip6trans DT could
be addressed outside the mip6trans DT.  More specifically the v4 MR stuff.

I also think that there is one thing to support continuous IPv6 sessions
on a Mobile IPv6 MH connecting to a v4 network and it is a totally
different thing to support continuous IPv4 sessions on the same node.

Alex


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



From mip6-bounces@ietf.org Tue Aug 09 11:10:13 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2Vk5-0000fX-2A; Tue, 09 Aug 2005 11:10:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2Vk2-0000am-NY; Tue, 09 Aug 2005 11:10:11 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA14515;
	Tue, 9 Aug 2005 11:10:08 -0400 (EDT)
Received: from mail.flarion.com ([63.103.94.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1E2WHx-0002hf-CV; Tue, 09 Aug 2005 11:45:14 -0400
Received: from ftmailserver.flariontech.com ([10.10.1.140]) by
	mail.flarion.com with Microsoft SMTPSVC(5.0.2195.6713);
	Tue, 9 Aug 2005 11:09:57 -0400
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
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] RE: [nemo] carrying IPv4 traffic using MIP6/NEMO
Date: Tue, 9 Aug 2005 11:09:57 -0400
Message-ID: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCACF@ftmailserver.flariontech.com>
Thread-Topic: [Mip6] RE: [nemo] carrying IPv4 traffic using MIP6/NEMO
Thread-Index: AcWc8wIiemeI4YrxSaihzpSf08zE9gAASCqA
From: "Soliman, Hesham" <H.Soliman@flarion.com>
To: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>
X-OriginalArrivalTime: 09 Aug 2005 15:09:57.0574 (UTC)
	FILETIME=[67B42660:01C59CF4]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Content-Transfer-Encoding: quoted-printable
Cc: nemo@ietf.org, mip6@ietf.org, ryuji@sfc.wide.ad.jp,
	Keiichi SHIMA <keiichi@iijlab.net>
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


 > > =3D> We're not doing anything with MIPv4 in the DT. We're trying to =

 > > allow the MN (that includes MR), using MIPv6, to be able to use an
 > > IPv4 or IPv6 home address in any access network that it=20
 > might be in.=20
 > > I think this summarizes the problem that the DT is addressing.
 >=20
 > I think some of the things that are addressed by the=20
 > mip6trans DT could
 > be addressed outside the mip6trans DT.  More specifically=20
 > the v4 MR stuff.

=3D> So let me explain it again: We're *not* doing "v4 MR stuff".
We're allowing the MR to have a v4 HoA/P. There is no difference
between that and allowing a host to have a v4 HoA..

Hesham

 >=20
 > I also think that there is one thing to support continuous=20
 > IPv6 sessions
 > on a Mobile IPv6 MH connecting to a v4 network and it is a totally
 > different thing to support continuous IPv4 sessions on the same node.
 >=20
 > Alex
 >=20
 >=20

=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 Tue Aug 09 11:27:06 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2W0Q-0007Lt-Q0; Tue, 09 Aug 2005 11:27:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2W0P-0007Ll-O9; Tue, 09 Aug 2005 11:27:05 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15642;
	Tue, 9 Aug 2005 11:27:02 -0400 (EDT)
Received: from ftpbox.mot.com ([129.188.136.101])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1E2WYK-0003FE-1Z; Tue, 09 Aug 2005 12:02:09 -0400
Received: from az33exr01.mot.com (az33exr01.mot.com [10.64.251.231])
	by ftpbox.mot.com (Motorola/Ftpbox) with ESMTP id j79FQxtZ012580;
	Tue, 9 Aug 2005 08:26:59 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by az33exr01.mot.com (8.13.1/8.13.0) with ESMTP id j79FZ8TY001527;
	Tue, 9 Aug 2005 10:35:10 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 8EA6C8637E6; Tue,  9 Aug 2005 17:26:56 +0200 (CEST)
Message-ID: <42F8CB40.3060405@motorola.com>
Date: Tue, 09 Aug 2005 17:26:56 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Organization: Motorola Labs, Paris, France
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: "Soliman, Hesham" <H.Soliman@flarion.com>
Subject: Re: [Mip6] RE: [nemo] carrying IPv4 traffic using MIP6/NEMO
References: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCACF@ftmailserver.flariontech.com>
In-Reply-To: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCACF@ftmailserver.flariontech.com>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Content-Transfer-Encoding: 7bit
Cc: nemo@ietf.org, mip6@ietf.org, ryuji@sfc.wide.ad.jp,
	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

Soliman, Hesham wrote:

>>> => We're not doing anything with MIPv4 in the DT. We're trying to
>>>  allow the MN (that includes MR), using MIPv6, to be able to use
>>> an IPv4 or IPv6 home address in any access network that it
>> might be in.
>>> I think this summarizes the problem that the DT is addressing.
>> 
>> I think some of the things that are addressed by the mip6trans DT
>> could be addressed outside the mip6trans DT.  More specifically the
>> v4 MR stuff.
> 
> => So let me explain it again: We're *not* doing "v4 MR stuff". We're
> allowing the MR to have a v4 HoA/P. There is no difference between
> that and allowing a host to have a v4 HoA..

Yes there is.  We've both just said it may become tricky.

Why is the DT looking into the complexity (that was previously named
"tricky") to allow the MR to have a v4 HoA/P?  Isn't the DT facing
enough complexity in allowing MH to have a permanent v6 Home Address
when connected to a v4 network?  To me, at least the NAT traversal part
gives enough headache.

Alex


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



From mip6-bounces@ietf.org Tue Aug 09 11:39:51 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2WCl-0004en-1B; Tue, 09 Aug 2005 11:39:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2WCi-0004eG-Aj; Tue, 09 Aug 2005 11:39:48 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16290;
	Tue, 9 Aug 2005 11:39:45 -0400 (EDT)
Received: from mail.flarion.com ([63.103.94.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1E2Wkd-0003cO-Q5; Tue, 09 Aug 2005 12:14:52 -0400
Received: from ftmailserver.flariontech.com ([10.10.1.140]) by
	mail.flarion.com with Microsoft SMTPSVC(5.0.2195.6713);
	Tue, 9 Aug 2005 11:39:38 -0400
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
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] RE: [nemo] carrying IPv4 traffic using MIP6/NEMO
Date: Tue, 9 Aug 2005 11:39:38 -0400
Message-ID: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCAD1@ftmailserver.flariontech.com>
Thread-Topic: [Mip6] RE: [nemo] carrying IPv4 traffic using MIP6/NEMO
Thread-Index: AcWc9snsEZ/n5nHZSzibLQCXwnjXXAAATvqw
From: "Soliman, Hesham" <H.Soliman@flarion.com>
To: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>
X-OriginalArrivalTime: 09 Aug 2005 15:39:38.0195 (UTC)
	FILETIME=[8D095A30:01C59CF8]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Content-Transfer-Encoding: quoted-printable
Cc: nemo@ietf.org, mip6@ietf.org, ryuji@sfc.wide.ad.jp
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



 > >>> =3D> We're not doing anything with MIPv4 in the DT. We're trying =
to
 > >>>  allow the MN (that includes MR), using MIPv6, to be able to use
 > >>> an IPv4 or IPv6 home address in any access network that it
 > >> might be in.
 > >>> I think this summarizes the problem that the DT is addressing.
 > >>=20
 > >> I think some of the things that are addressed by the mip6trans DT
 > >> could be addressed outside the mip6trans DT.  More=20
 > specifically the
 > >> v4 MR stuff.
 > >=20
 > > =3D> So let me explain it again: We're *not* doing "v4 MR=20
 > stuff". We're
 > > allowing the MR to have a v4 HoA/P. There is no difference between
 > > that and allowing a host to have a v4 HoA..
 >=20
 > Yes there is.  We've both just said it may become tricky.

=3D> You're confusing two separate issues. I said it's tricky to=20
have multiple instances of the HAO. For example today we're not=20
allowed to have multiple HAOs for an IPv6 address...
This has nothing to do with whether you can support an IPv4 prefix.
There are lots of tricky issues in mobility and it doesn't mean
we can't do it.=20

 >=20
 > Why is the DT looking into the complexity (that was previously named
 > "tricky") to allow the MR to have a v4 HoA/P?  Isn't the DT facing
 > enough complexity in allowing MH to have a permanent v6 Home Address
 > when connected to a v4 network?  To me, at least the NAT=20
 > traversal part
 > gives enough headache.

=3D> When you see the solution you can assess whether it's complex or =
not.=20
For now I was referring to an update to draft-soliman. The DT hasn't
decided what the solution is based on, so I was referring to =
draft-soliman
as an example of how this is done, whether it is the final solution or =
not
is not up to me obviously.=20

Hesham

 >=20
 > Alex
 >=20
 >=20

=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 Tue Aug 09 11:56:14 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2WSb-00017F-Vk; Tue, 09 Aug 2005 11:56:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1E2WSa-00016s-Nw
	for mip6@megatron.ietf.org; Tue, 09 Aug 2005 11:56:12 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18020
	for <mip6@ietf.org>; Tue, 9 Aug 2005 11:56: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.43) id 1E2X0V-0004QN-Uz
	for mip6@ietf.org; Tue, 09 Aug 2005 12:31:16 -0400
Message-ID: <018401c59cfa$ddf19000$196115ac@dcml.docomolabsusa.com>
From: "James Kempf" <Kempf@docomolabs-usa.com>
To: "Francis Dupont" <Francis.Dupont@enst-bretagne.fr>
References: <200508091428.j79ESE8l042264@givry.rennes.enst-bretagne.fr>
Subject: Re: [Mip6] MN-HA Reliability Work? 
Date: Tue, 9 Aug 2005 08:56:12 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
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

Your second issue seems a problem, especially the EAP part. I'm not
convinced that MIP necessarily needs to conform with Mobike, though.

Still, it would be useful if we could figure out some way to allow an HA
that is not the current HA to inform a MN that its current HA has gone down
unexpectedly.

            jak

----- Original Message -----
From: "Francis Dupont" <Francis.Dupont@enst-bretagne.fr>
To: "James Kempf" <Kempf@docomolabs-usa.com>
Cc: <mip6@ietf.org>
Sent: Tuesday, August 09, 2005 7:28 AM
Subject: Re: [Mip6] MN-HA Reliability Work?


> In your previous mail you wrote:
>
>    Could you elaborate how you think this affects Qin's draft idea of
having an
>    HA be able to initiate the SA?
>
> => the I-D is draft-li-mip6-ha-init-bootstrap-00.txt, isn't it?
>
> I can see some issues with the idea to get the HA as the initiator:
>  - as I already wrote, current Mobike proposed protocol assumes the
>    initiator is the mobile side, what I summaried by "the initiator
decides"
>  - IKEv2 itself has less facilities, for instance:
>    * IDr from the initiator (shouldn't matter)
>    * no EAP for the responder (this should really matter but EAP over
IKEv2
>      could be extended)
>    * no CFG_REQUEST for the responder (this makes sense but should matter
too)
>
> Regards
>
> Francis.Dupont@enst-bretagne.fr
>
> PS: IMHO it could be better to design some kind of callbacks in order
> to launch IKE the "right way".
>



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



From mip6-bounces@ietf.org Tue Aug 09 12:27:21 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2Wwj-0002tW-7O; Tue, 09 Aug 2005 12:27:21 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2Wwh-0002tL-01; Tue, 09 Aug 2005 12:27:19 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20610;
	Tue, 9 Aug 2005 12:27:15 -0400 (EDT)
Received: from motgate4.mot.com ([144.189.100.102])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1E2XUc-0005ct-Uu; Tue, 09 Aug 2005 13:02:23 -0400
Received: from az33exr04.mot.com (az33exr04.mot.com [10.64.251.234])
	by motgate4.mot.com (8.12.11/Motgate4) with ESMTP id j79GYlEC004126;
	Tue, 9 Aug 2005 09:34:47 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by az33exr04.mot.com (8.13.1/8.13.0) with ESMTP id j79GViWZ018411;
	Tue, 9 Aug 2005 11:31:45 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 024DB865980; Tue,  9 Aug 2005 18:27:02 +0200 (CEST)
Message-ID: <42F8D955.9010605@motorola.com>
Date: Tue, 09 Aug 2005 18:27:01 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Organization: Motorola Labs, Paris, France
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: "Soliman, Hesham" <H.Soliman@flarion.com>
Subject: Re: [Mip6] RE: [nemo] carrying IPv4 traffic using MIP6/NEMO
References: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCAD1@ftmailserver.flariontech.com>
In-Reply-To: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCAD1@ftmailserver.flariontech.com>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by motgate4.mot.com id
	j79GYlEC004126
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Content-Transfer-Encoding: quoted-printable
Cc: nemo@ietf.org, mip6@ietf.org, ryuji@sfc.wide.ad.jp,
	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

Soliman, Hesham wrote:

>=20
>>>>> =3D> We're not doing anything with MIPv4 in the DT. We're=20
>>>>> trying to allow the MN (that includes MR), using MIPv6, to be
>>>>>  able to use an IPv4 or IPv6 home address in any access=20
>>>>> network that it
>>>> might be in.
>>>>> I think this summarizes the problem that the DT is=20
>>>>> addressing.
>>>>=20
>>>> I think some of the things that are addressed by the mip6trans
>>>>  DT could be addressed outside the mip6trans DT.  More
>> specifically the
>>>> v4 MR stuff.
>>>=20
>>> =3D> So let me explain it again: We're *not* doing "v4 MR
>> stuff". We're
>>> allowing the MR to have a v4 HoA/P. There is no difference=20
>>> between that and allowing a host to have a v4 HoA..
>>=20
>> Yes there is.  We've both just said it may become tricky.
>=20
> =3D> You're confusing two separate issues. I said it's tricky to have=20
> multiple instances of the HAO. For example today we're not allowed to
>  have multiple HAOs for an IPv6 address...

I see, you're right.

Having a v6-mapped v4 address in the HAO would probably lead to sending
two BUs: one for v4, one for v6.  But then draft-dsmip-problem would be
failing too because dsmip suddenly does double signalling.

> There are lots of tricky issues in mobility and it doesn't mean we=20
> can't do it.

That sounds like overconfidence to me, IMHO.  Or I may be confused, as
you say.

>> Why is the DT looking into the complexity (that was previously=20
>> named "tricky") to allow the MR to have a v4 HoA/P?  Isn't the DT=20
>> facing enough complexity in allowing MH to have a permanent v6 Home
>>  Address when connected to a v4 network?  To me, at least the NAT=20
>> traversal part gives enough headache.
>=20
> =3D> When you see the solution you can assess whether it's complex or=20
> not.

When I see arguments adding a prefixlen field is 5 minutes work I tend
to believe complexity is still hidden.

> For now I was referring to an update to draft-soliman. The DT hasn't
> decided what the solution is based on, so I was referring to=20
> draft-soliman as an example of how this is done, whether it is the=20
> final solution or not is not up to me obviously.

Ok, so we'd probably be more productive on feeding back about the Vijay
Paris slides, about which requirements and scenarios are needed
immediately, rather than pitting documents one against another.

Paris slides:
> Connect an IPv6 mobile node to its IPv6 Home Agent and services from
> an IPv4-only access network

> 1 Support NAT traversal, NAT detection and the ability to turn offthe
> NAT traversal mechanism when not required

> 2 Support the scenario where the Home Agent is behind a NAT and not
> accessible through a public address

> 3 Support dynamic discovery of the HA=92s IPv4 address

> 4 Enable IPsec protection for the mip6trans tunnel. The Home Agentand
> the mobile node must be able to negotiate tunnel security
> associations for the mip6trans tunnel

> 5 Enable the mobile node to use its IPv4 Home Address for IPv4
> sessions over the mip6trans tunnel

> 6 Support dynamic allocation of the IPv4 Home Address

I'm for 1 and 4 and not for 2, 3, 5, 6.  And I'd like to add requirement
0: support IPv6 session continuity at a permanent publicly-routable v6
Home Address when the MH connects to a v4-exclusively network.

The requirements 2, 3, 5 and 6 are interesting - ok - but may represent
too much work.

Alex

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



From mip6-bounces@ietf.org Tue Aug 09 12:53:05 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2XLd-0005KD-4Y; Tue, 09 Aug 2005 12:53:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1E2XLW-0005Iu-Pf
	for mip6@megatron.ietf.org; Tue, 09 Aug 2005 12:53:03 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23969
	for <mip6@ietf.org>; Tue, 9 Aug 2005 12:52:55 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E2XtS-0006TQ-6N
	for mip6@ietf.org; Tue, 09 Aug 2005 13:28:03 -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 j79GqSn16784; Tue, 9 Aug 2005 18:52:28 +0200
Received: from givry.rennes.enst-bretagne.fr
	(localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id
	j79GqTJr042850; Tue, 9 Aug 2005 18:52:29 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200508091652.j79GqTJr042850@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "James Kempf" <Kempf@docomolabs-usa.com>
Subject: Re: [Mip6] MN-HA Reliability Work? 
In-reply-to: Your message of Tue, 09 Aug 2005 08:56:12 PDT.
	<018401c59cfa$ddf19000$196115ac@dcml.docomolabsusa.com> 
Date: Tue, 09 Aug 2005 18:52:29 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
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

 In your previous mail you wrote:

   Your second issue seems a problem, especially the EAP part.

=> the EAP and CF_REQUEST were obviously designed with the
assumption the MN/VPN client is always the initiator...

   I'm not
   convinced that MIP necessarily needs to conform with Mobike, though.
   
=> I'm convinced that Mobike should conform with MIP in this case (:-).

   Still, it would be useful if we could figure out some way to allow an HA
   that is not the current HA to inform a MN that its current HA has gone down
   unexpectedly.
   
=> I agree but it seems to reverse the way IKE is used is a bit too much.
Perhaps a new ICMP error to indicate a possible problem is the best solution:
the MN should check the previous is no more available and could get a hint
about the new HA from the ICMP message. In fact, the only reason we can't
reuse a standard unreachable is because we have no real extra info to put
in the message as the triggering packet... If we accept a synthetized BRR,
i.e., for instance:
 ICMP:
  src: new HA
  dst: MN CoA
  type: unreachable (1)
  code: address unreachable (3) ?
 embedded IPv6 "triggering" packet
  src: MN HoA
  dst: previous HA
  MH type: BRR (0)

(there is a problem with the previous HA, binding refreshed is needed,
the 4 involved addresses are in the message at not too stupid positions...)

Regards

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Wed Aug 10 08:30:50 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2pjO-0007fo-3b; Wed, 10 Aug 2005 08:30:50 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1E2pjL-0007fh-MO
	for mip6@megatron.ietf.org; Wed, 10 Aug 2005 08:30:48 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA23957
	for <mip6@ietf.org>; Wed, 10 Aug 2005 08:30:46 -0400 (EDT)
Received: from mail.sfc.wide.ad.jp ([203.178.142.146])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E2qHL-0004h1-Sx
	for mip6@ietf.org; Wed, 10 Aug 2005 09:06:02 -0400
Received: from [10.0.2.15] (unknown [168.126.248.3])
	by mail.sfc.wide.ad.jp (Postfix) with ESMTP id 0414F4C93E;
	Wed, 10 Aug 2005 21:30:10 +0900 (JST)
In-Reply-To: <018401c59cfa$ddf19000$196115ac@dcml.docomolabsusa.com>
References: <200508091428.j79ESE8l042264@givry.rennes.enst-bretagne.fr>
	<018401c59cfa$ddf19000$196115ac@dcml.docomolabsusa.com>
Mime-Version: 1.0 (Apple Message framework v733)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <9A2FE8AB-BFE8-42C3-9B02-636456254513@sfc.wide.ad.jp>
Content-Transfer-Encoding: 7bit
From: Ryuji Wakikawa <ryuji@sfc.wide.ad.jp>
Subject: Re: [Mip6] MN-HA Reliability Work? 
Date: Wed, 10 Aug 2005 21:30:04 +0900
To: James Kempf <Kempf@docomolabs-usa.com>
X-Mailer: Apple Mail (2.733)
X-Spam-Score: 2.9 (++)
X-Scan-Signature: 386e0819b1192672467565a524848168
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org, Francis Dupont <Francis.Dupont@enst-bretagne.fr>
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

Hi James

On 2005/08/10, at 0:56, James Kempf wrote:

> Your second issue seems a problem, especially the EAP part. I'm not
> convinced that MIP necessarily needs to conform with Mobike, though.
>
> Still, it would be useful if we could figure out some way to allow  
> an HA
> that is not the current HA to inform a MN that its current HA has  
> gone down
> unexpectedly.

This is very limited scenario. Defining only signal is not efficient.

We should consider how to detect the failed HA and how to  know
the mobile nodes which the new HA must send the HAswitch message.
There is no scheme to know which mobile nodes are associated with  
which HA. (except for HAHA).

There are also several issues for this topic. Proxy ND consistency is  
one example.
Before a new HA receiving a new BU, the failed HA must be detached  
from the home link or
stop proxy ND for mobile nodes which bindings were registered on.   
Otherwise, DAD will be
occurred.

Your suggestion is just partial solution for the big problem.
I disagree to work on MN-HA reliability only without investigating  
the whole picture.

ryuji

>             jak
>
> ----- Original Message -----
> From: "Francis Dupont" <Francis.Dupont@enst-bretagne.fr>
> To: "James Kempf" <Kempf@docomolabs-usa.com>
> Cc: <mip6@ietf.org>
> Sent: Tuesday, August 09, 2005 7:28 AM
> Subject: Re: [Mip6] MN-HA Reliability Work?
>
>
>
>> In your previous mail you wrote:
>>
>>    Could you elaborate how you think this affects Qin's draft idea of
>>
> having an
>
>>    HA be able to initiate the SA?
>>
>> => the I-D is draft-li-mip6-ha-init-bootstrap-00.txt, isn't it?
>>
>> I can see some issues with the idea to get the HA as the initiator:
>>  - as I already wrote, current Mobike proposed protocol assumes the
>>    initiator is the mobile side, what I summaried by "the initiator
>>
> decides"
>
>>  - IKEv2 itself has less facilities, for instance:
>>    * IDr from the initiator (shouldn't matter)
>>    * no EAP for the responder (this should really matter but EAP over
>>
> IKEv2
>
>>      could be extended)
>>    * no CFG_REQUEST for the responder (this makes sense but should  
>> matter
>>
> too)
>
>>
>> Regards
>>
>> Francis.Dupont@enst-bretagne.fr
>>
>> PS: IMHO it could be better to design some kind of callbacks in order
>> to launch IKE the "right way".
>>
>>
>
>
>
> _______________________________________________
> 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 Wed Aug 10 08:49:19 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2q1D-00041A-21; Wed, 10 Aug 2005 08:49:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2q1B-00040x-6g; Wed, 10 Aug 2005 08:49:13 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24917;
	Wed, 10 Aug 2005 08:49:11 -0400 (EDT)
Received: from mail.sfc.wide.ad.jp ([203.178.142.146])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1E2qZH-0005Bj-Hf; Wed, 10 Aug 2005 09:24:28 -0400
Received: from [10.0.2.15] (unknown [168.126.248.3])
	by mail.sfc.wide.ad.jp (Postfix) with ESMTP id 31C414CA55;
	Wed, 10 Aug 2005 21:49:02 +0900 (JST)
In-Reply-To: <42F8D955.9010605@motorola.com>
References: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCAD1@ftmailserver.flariontech.com>
	<42F8D955.9010605@motorola.com>
Mime-Version: 1.0 (Apple Message framework v733)
Content-Type: text/plain; charset=SHIFT_JIS; delsp=yes; format=flowed
Message-Id: <7F1AD8E3-716A-45C3-9F03-179CA14E38B5@sfc.wide.ad.jp>
Content-Transfer-Encoding: quoted-printable
From: Ryuji Wakikawa <ryuji@sfc.wide.ad.jp>
Subject: Re: [Mip6] RE: [nemo] carrying IPv4 traffic using MIP6/NEMO
Date: Wed, 10 Aug 2005 21:48:52 +0900
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
X-Mailer: Apple Mail (2.733)
X-Spam-Score: 2.9 (++)
X-Scan-Signature: 789c141a303c09204b537a4078e2a63f
Content-Transfer-Encoding: quoted-printable
Cc: "Soliman, Hesham" <H.Soliman@flarion.com>, nemo@ietf.org, 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

Hi Alex and Hesham

On 2005/08/10, at 1:27, Alexandru Petrescu wrote:

> Soliman, Hesham wrote:
>
>
>>
>>
>>>>>> =3D> We're not doing anything with MIPv4 in the DT. We're
>>>>>> trying to allow the MN (that includes MR), using MIPv6, to be
>>>>>>  able to use an IPv4 or IPv6 home address in any access
>>>>>> network that it
>>>>>>
>>>>> might be in.
>>>>>
>>>>>> I think this summarizes the problem that the DT is
>>>>>> addressing.
>>>>>>
>>>>>
>>>>> I think some of the things that are addressed by the mip6trans
>>>>>  DT could be addressed outside the mip6trans DT.  More
>>>>>
>>> specifically the
>>>
>>>>> v4 MR stuff.
>>>>>
>>>>
>>>> =3D> So let me explain it again: We're *not* doing "v4 MR
>>>>
>>> stuff". We're
>>>
>>>> allowing the MR to have a v4 HoA/P. There is no difference
>>>> between that and allowing a host to have a v4 HoA..
>>>>
>>>
>>> Yes there is.  We've both just said it may become tricky.
>>>
>>
>> =3D> You're confusing two separate issues. I said it's tricky to have
>> multiple instances of the HAO. For example today we're not allowed to
>>  have multiple HAOs for an IPv6 address...
>>
>
> I see, you're right.
>
> Having a v6-mapped v4 address in the HAO would probably lead to =20
> sending
> two BUs: one for v4, one for v6.  But then draft-dsmip-problem =20
> would be
> failing too because dsmip suddenly does double signalling.

We are not discussing a solution yet. So it is irrelevant  to discuss =20=

such details.

>
>> There are lots of tricky issues in mobility and it doesn't mean we
>> can't do it.
>>
>
> That sounds like overconfidence to me, IMHO.  Or I may be confused, as
> you say.
>
>
>>> Why is the DT looking into the complexity (that was previously
>>> named "tricky") to allow the MR to have a v4 HoA/P?  Isn't the DT
>>> facing enough complexity in allowing MH to have a permanent v6 Home
>>>  Address when connected to a v4 network?  To me, at least the NAT
>>> traversal part gives enough headache.
>>>
>>
>> =3D> When you see the solution you can assess whether it's complex or
>> not.
>>
>
> When I see arguments adding a prefixlen field is 5 minutes work I tend
> to believe complexity is still hidden.
>
>
>> For now I was referring to an update to draft-soliman. The DT hasn't
>> decided what the solution is based on, so I was referring to
>> draft-soliman as an example of how this is done, whether it is the
>> final solution or not is not up to me obviously.
>>
>
> Ok, so we'd probably be more productive on feeding back about the =20
> Vijay
> Paris slides, about which requirements and scenarios are needed
> immediately, rather than pitting documents one against another.
>
> Paris slides:
>
>> Connect an IPv6 mobile node to its IPv6 Home Agent and services from
>> an IPv4-only access network
>>
>
>
>> 1 Support NAT traversal, NAT detection and the ability to turn offthe
>> NAT traversal mechanism when not required
>>
>
>
>> 2 Support the scenario where the Home Agent is behind a NAT and not
>> accessible through a public address
>>
>
>
>> 3 Support dynamic discovery of the HA=81fs IPv4 address
>>
>
>
>> 4 Enable IPsec protection for the mip6trans tunnel. The Home Agentand
>> the mobile node must be able to negotiate tunnel security
>> associations for the mip6trans tunnel
>>
>
>
>> 5 Enable the mobile node to use its IPv4 Home Address for IPv4
>> sessions over the mip6trans tunnel
>>
>
>
>> 6 Support dynamic allocation of the IPv4 Home Address
>>
>
> I'm for 1 and 4 and not for 2, 3, 5, 6.  And I'd like to add =20
> requirement
> 0: support IPv6 session continuity at a permanent publicly-routable v6
> Home Address when the MH connects to a v4-exclusively network.
>
> The requirements 2, 3, 5 and 6 are interesting - ok - but may =20
> represent
> too much work.

Alex, I disagree on your proposition.
I don't know how do you line between 1,4 and 2,3,5,6.
The requirements listed here were from the DT consensus.

On the other hand, one thing where keiichi pointed out is
whether we should include IPv4 MNP in No.5. And Hesham agreed.

Then, the next question was that should we split documents for v4 =20
traversal
and v4 session continuity.

regards,
ryuji

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



From mip6-bounces@ietf.org Wed Aug 10 08:55:18 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2q74-0005X6-0d; Wed, 10 Aug 2005 08:55:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2q72-0005VD-LQ; Wed, 10 Aug 2005 08:55:16 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25148;
	Wed, 10 Aug 2005 08:55:15 -0400 (EDT)
Received: from mail.sfc.wide.ad.jp ([203.178.142.146])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1E2qf6-0005KJ-RH; Wed, 10 Aug 2005 09:30:32 -0400
Received: from [10.0.2.15] (unknown [168.126.248.3])
	by mail.sfc.wide.ad.jp (Postfix) with ESMTP id B073A4C6B7;
	Wed, 10 Aug 2005 21:55:02 +0900 (JST)
In-Reply-To: <42F877E9.8010304@motorola.com>
References: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCAC1@ftmailserver.flariontech.com>
	<42F877E9.8010304@motorola.com>
Mime-Version: 1.0 (Apple Message framework v733)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <6ED12209-2B69-4F0D-84FA-489A5AC05E49@sfc.wide.ad.jp>
Content-Transfer-Encoding: 7bit
From: Ryuji Wakikawa <ryuji@sfc.wide.ad.jp>
Subject: Re: [Mip6] Re: [nemo] carrying IPv4 traffic using MIP6/NEMO
Date: Wed, 10 Aug 2005 21:54:54 +0900
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
X-Mailer: Apple Mail (2.733)
X-Spam-Score: 2.9 (++)
X-Scan-Signature: 36b1f8810cb91289d885dc8ab4fc8172
Content-Transfer-Encoding: 7bit
Cc: "Soliman, Hesham" <H.Soliman@flarion.com>, nemo@ietf.org,
	Keiichi SHIMA <keiichi@iijlab.net>, 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

Hi Alex.

On 2005/08/09, at 18:31, Alexandru Petrescu wrote:

> Hello Hesham,
>
> Soliman, Hesham wrote:
>
>>>
>>> Generally it looks like an interesting idea.  Why restraining the
>>> binding to a fixed /32 full v4 address when binding a variable
>>> prefix (1...32) could bring the benefit of giving v4 access to all
>>> nodes in the moving network (not only to the MR).  So this may look
>>> as an obvious advantage.
>>>
>>> However, I was wondering how much would this addition extend the
>>> current scope of the DT work, whose goal was mainly to give v6 (not
>>>  v4) access to MR and mobile nodes when MR connects to a v4
>>> network.
>>>
>>> Giving continuous v4 access to mobile nodes in a moving network
>>> whose MR connects to a v4 access network can naturally be obtained
>>> by running Mobile IPv4 on the MR, too.
>>>
>>> What does the DT think?
>>>
>>
>> => We discussed this
>>
>
> Great, does the DT have a requirement for giving v4 access to nodes  
> in a
> moving network whose MR runs Mobile IPv6 and connects to a v4 access
> network?
>
> If yes, does the requirement include v4 session continuity?  Does the
> requirement include reachability at a permanent v4 address?  These
> aspects are important, at least for deciding on whether or not to use
> NAT within the moving network (see draft-shima).

Using NAT in the mobile network is possible if MR has at least one  
global v4 address.
I attach discussion in DT ML.

ryuji

>
>> and I had extended draft-soliman to represent the IP address as :
>> address/prefixlen, where prefixlen is anything up to 32. It's a
>> useful feature that only adds another 5 mins of work so why not.
>>
>
> Hesham, did you encode the prefixlen on 8 or 5 bits?  Anyways, I don't
> think simply adding a v4 prefixlen into a message format is as easy as
> it may look.  Conceptually - yes, just use a prefixlen, but from there
> to a protocol may be a longer way.  For example, what happens when  
> MR's
> v4 Home Address is independent of the Mobile Network Prefix (they  
> differ
> starting at the 0th bit).
>
> I think giving v4 access to nodes in the moving network would best be
> done by a NEMOv4 protocol.
>
> Alex
>
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>
>






On 2005/07/22, at 8:26, Soliman, Hesham wrote:

>
>
>
>>>> If a MR uses IPv4 feature of MIP6, it may use the IPv4
>>>> global address
>>>> for NATed mobile network.
>>>> This is one way to provide v4 connectivity to NEMO, but I prefer
>>>> clean solution.
>>>>
>>>>
>>>
>>> => Please elaborate on the scenario you're describing, a picture
>>> might help. If the MR has an IPv4 prefix for the MNNs behind it,
>>>
>>
>> something like this.
>>
>>                                IPv4 global            IPv4 private
>> HA----Internet --- MR (NAT) -------Mobile Networks
>>
>> MR sends BU including IPv4 global address to HA as you proposed and
>> uses the IPv4 global address for NATed mobile network.
>> MR acts as NAT BOX for mobile network.
>>
>
> => Ok, this is exactly the same as a mobile host. The same should
> work regardless of it being an MR.
>
>
>> If NEMO is operated with implicit mode and dynamic routing protocol
>> like OSPF,
>> it fines. However, if MR sends BU with MNP options (no OSPF
>> running),
>> how can MR notify the IPv4 prefix to HA?
>> This is the same problem with MIP6, isn't this?
>>
>
> => You just showed an example where the MR is a NAT. If
> you want to propose a nemo basic solution for IPv4 then
> this is not the right place to solve it. IF there is a nemo
> solution for v4 we can easily add the IPv4 prefix option.
> This is a 5 min job, *if* that solution exists.
>
> Hesham
>
> ===========================================================
> 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.
> ===========================================================
>





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



From mip6-bounces@ietf.org Wed Aug 10 09:17:24 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2qSS-0002iX-Hf; Wed, 10 Aug 2005 09:17:24 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2qSR-0002iM-5m; Wed, 10 Aug 2005 09:17:23 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26587;
	Wed, 10 Aug 2005 09:17:21 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1E2r0X-0005yO-91; Wed, 10 Aug 2005 09:52:38 -0400
Received: from il06exr01.mot.com (il06exr01.mot.com [129.188.137.131])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id j7ADQvVp012046;
	Wed, 10 Aug 2005 06:26:57 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by il06exr01.mot.com (8.13.1/8.13.0) with ESMTP id j7ADO17i014247;
	Wed, 10 Aug 2005 08:24:02 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 9674C865980; Wed, 10 Aug 2005 15:17:01 +0200 (CEST)
Message-ID: <42F9FE4D.6030406@motorola.com>
Date: Wed, 10 Aug 2005 15:17:01 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Organization: Motorola Labs, Paris, France
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: Ryuji Wakikawa <ryuji@sfc.wide.ad.jp>
Subject: Re: [Mip6] Re: [nemo] carrying IPv4 traffic using MIP6/NEMO
References: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCAC1@ftmailserver.flariontech.com>
	<42F877E9.8010304@motorola.com>
	<6ED12209-2B69-4F0D-84FA-489A5AC05E49@sfc.wide.ad.jp>
In-Reply-To: <6ED12209-2B69-4F0D-84FA-489A5AC05E49@sfc.wide.ad.jp>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Content-Transfer-Encoding: 7bit
Cc: "Soliman, Hesham" <H.Soliman@flarion.com>, nemo@ietf.org,
	Keiichi SHIMA <keiichi@iijlab.net>,
	Alexandru Petrescu <alexandru.petrescu@motorola.com>, 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

Hi Ryuji,

Ryuji Wakikawa wrote:

> Hi Alex.
> 
> On 2005/08/09, at 18:31, Alexandru Petrescu wrote:
> 
>> Hello Hesham,
>> 
>> Soliman, Hesham wrote:
>> 
>>>> 
>>>> Generally it looks like an interesting idea.  Why restraining
>>>> the binding to a fixed /32 full v4 address when binding a
>>>> variable prefix (1...32) could bring the benefit of giving v4
>>>> access to all nodes in the moving network (not only to the MR).
>>>> So this may look as an obvious advantage.
>>>> 
>>>> However, I was wondering how much would this addition extend
>>>> the current scope of the DT work, whose goal was mainly to give
>>>> v6 (not v4) access to MR and mobile nodes when MR connects to a
>>>> v4 network.
>>>> 
>>>> Giving continuous v4 access to mobile nodes in a moving network
>>>>  whose MR connects to a v4 access network can naturally be
>>>> obtained by running Mobile IPv4 on the MR, too.
>>>> 
>>>> What does the DT think?
>>>> 
>>> 
>>> => We discussed this
>>> 
>> 
>> Great, does the DT have a requirement for giving v4 access to nodes
>> in a moving network whose MR runs Mobile IPv6 and connects to a v4
>> access network?
>> 
>> If yes, does the requirement include v4 session continuity?  Does
>> the requirement include reachability at a permanent v4 address?
>> These aspects are important, at least for deciding on whether or
>> not to use NAT within the moving network (see draft-shima).
> 
> 
> Using NAT in the mobile network is possible if MR has at least one 
> global v4 address.

I agree using NAT in the mobile network is possible.  I also agree that
if NAT is used in the mobile network then there can be no mip6trans
requirement for reachability at a permanent v4 address (behind NAT the
v4 nodes are not reachable, somebody can't connect() to them).

All in all, IMHO, mip6trans should not waste effort on giving v4 access
to nodes in the moving network; if it does (because consensus) then
shouldn't do it with NAT.

My oppinion,

Alex


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



From mip6-bounces@ietf.org Wed Aug 10 09:30:19 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2qex-0006V0-RK; Wed, 10 Aug 2005 09:30:19 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2qew-0006Uo-37; Wed, 10 Aug 2005 09:30:18 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA27235;
	Wed, 10 Aug 2005 09:30:16 -0400 (EDT)
Received: from mail.sfc.wide.ad.jp ([203.178.142.146])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1E2rD0-0006ML-Uz; Wed, 10 Aug 2005 10:05:33 -0400
Received: from [192.168.1.2] (unknown [168.126.248.3])
	by mail.sfc.wide.ad.jp (Postfix) with ESMTP id D3C4A4CBF0;
	Wed, 10 Aug 2005 22:30:04 +0900 (JST)
In-Reply-To: <42F9FE4D.6030406@motorola.com>
References: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCAC1@ftmailserver.flariontech.com>
	<42F877E9.8010304@motorola.com>
	<6ED12209-2B69-4F0D-84FA-489A5AC05E49@sfc.wide.ad.jp>
	<42F9FE4D.6030406@motorola.com>
Mime-Version: 1.0 (Apple Message framework v733)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <4CC22A36-030D-4816-B86F-9E3D0BB3B345@sfc.wide.ad.jp>
Content-Transfer-Encoding: 7bit
From: Ryuji Wakikawa <ryuji@sfc.wide.ad.jp>
Subject: Re: [Mip6] Re: [nemo] carrying IPv4 traffic using MIP6/NEMO
Date: Wed, 10 Aug 2005 22:29:57 +0900
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
X-Mailer: Apple Mail (2.733)
X-Spam-Score: 2.9 (++)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Content-Transfer-Encoding: 7bit
Cc: "Soliman, Hesham" <H.Soliman@flarion.com>, nemo@ietf.org,
	Keiichi SHIMA <keiichi@iijlab.net>, 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

Hi Alex

On 2005/08/10, at 22:17, Alexandru Petrescu wrote:

> Hi Ryuji,
>
> Ryuji Wakikawa wrote:
>
>
>> Hi Alex.
>>
>> On 2005/08/09, at 18:31, Alexandru Petrescu wrote:
>>
>>
>>> Hello Hesham,
>>>
>>> Soliman, Hesham wrote:
>>>
>>>
>>>>>
>>>>> Generally it looks like an interesting idea.  Why restraining
>>>>> the binding to a fixed /32 full v4 address when binding a
>>>>> variable prefix (1...32) could bring the benefit of giving v4
>>>>> access to all nodes in the moving network (not only to the MR).
>>>>> So this may look as an obvious advantage.
>>>>>
>>>>> However, I was wondering how much would this addition extend
>>>>> the current scope of the DT work, whose goal was mainly to give
>>>>> v6 (not v4) access to MR and mobile nodes when MR connects to a
>>>>> v4 network.
>>>>>
>>>>> Giving continuous v4 access to mobile nodes in a moving network
>>>>>  whose MR connects to a v4 access network can naturally be
>>>>> obtained by running Mobile IPv4 on the MR, too.
>>>>>
>>>>> What does the DT think?
>>>>>
>>>>>
>>>>
>>>> => We discussed this
>>>>
>>>>
>>>
>>> Great, does the DT have a requirement for giving v4 access to nodes
>>> in a moving network whose MR runs Mobile IPv6 and connects to a v4
>>> access network?
>>>
>>> If yes, does the requirement include v4 session continuity?  Does
>>> the requirement include reachability at a permanent v4 address?
>>> These aspects are important, at least for deciding on whether or
>>> not to use NAT within the moving network (see draft-shima).
>>>
>>
>>
>> Using NAT in the mobile network is possible if MR has at least one
>> global v4 address.
>>
>
> I agree using NAT in the mobile network is possible.  I also agree  
> that
> if NAT is used in the mobile network then there can be no mip6trans
> requirement for reachability at a permanent v4 address (behind NAT the
> v4 nodes are not reachable, somebody can't connect() to them).

Well, that is limitation of NAT...

> All in all, IMHO, mip6trans should not waste effort on giving v4  
> access
> to nodes in the moving network; if it does (because consensus) then

We should work on v4 reachability, because MIP6 WG already has the
problem statement draft (draft-ietf-dsmip),
And It makes sense to have a similar/common solution, because
both goals are to establish tunnel between HA-MN after all.

The question may be whether we should split document or not?!

> shouldn't do it with NAT.

Do you mean doing NAT in mobile networks?

ryuji

> My oppinion,
>
> Alex
>
>


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



From mip6-bounces@ietf.org Wed Aug 10 09:54:35 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2r2R-00052g-Rp; Wed, 10 Aug 2005 09:54:35 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2r2P-00052Y-2k; Wed, 10 Aug 2005 09:54:34 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28921;
	Wed, 10 Aug 2005 09:54:31 -0400 (EDT)
Received: from motgate3.mot.com ([144.189.100.103])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1E2raV-0007Ow-8h; Wed, 10 Aug 2005 10:29:48 -0400
Received: from az33exr02.mot.com (az33exr02.mot.com [10.64.251.232])
	by motgate3.mot.com (8.12.11/Motgate3) with ESMTP id j7AE7QGv000845;
	Wed, 10 Aug 2005 07:07:27 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by az33exr02.mot.com (8.13.1/8.13.0) with ESMTP id j7ADxG98027397;
	Wed, 10 Aug 2005 08:59:17 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 26255865980; Wed, 10 Aug 2005 15:54:18 +0200 (CEST)
Message-ID: <42FA0709.1060208@motorola.com>
Date: Wed, 10 Aug 2005 15:54:17 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Organization: Motorola Labs, Paris, France
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: Ryuji Wakikawa <ryuji@sfc.wide.ad.jp>
References: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCAD1@ftmailserver.flariontech.com>
	<42F8D955.9010605@motorola.com>
	<7F1AD8E3-716A-45C3-9F03-179CA14E38B5@sfc.wide.ad.jp>
In-Reply-To: <7F1AD8E3-716A-45C3-9F03-179CA14E38B5@sfc.wide.ad.jp>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=Shift_JIS
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by motgate3.mot.com id
	j7AE7QGv000845
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Content-Transfer-Encoding: quoted-printable
Cc: "Soliman, Hesham" <H.Soliman@flarion.com>, nemo@ietf.org,
	Alexandru Petrescu <alexandru.petrescu@motorola.com>, mip6@ietf.org
Subject: [Mip6] Re: mip6trans requirements (was: carrying IPv4 traffic using
	MIP6/NEMO)
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

Vijay Paris slides and Ryuji Wakikawa wrote:
>>> 1 Support NAT traversal, NAT detection and the ability to turn=20
>>> offthe NAT traversal mechanism when not required
>>=20
>>> 2 Support the scenario where the Home Agent is behind a NAT and=20
>>> not accessible through a public address
>>=20
>>> 3 Support dynamic discovery of the HA=81fs IPv4 address
>>=20
>>> 4 Enable IPsec protection for the mip6trans tunnel. The Home=20
>>> Agentand the mobile node must be able to negotiate tunnel=20
>>> security associations for the mip6trans tunnel
>>=20
>>> 5 Enable the mobile node to use its IPv4 Home Address for IPv4=20
>>> sessions over the mip6trans tunnel
>>=20
>>> 6 Support dynamic allocation of the IPv4 Home Address
>>>=20
>>=20
>> I'm for 1 and 4 and not for 2, 3, 5, 6.  And I'd like to add=20
>> requirement 0: support IPv6 session continuity at a permanent=20
>> publicly-routable v6 Home Address when the MH connects to a=20
>> v4-exclusively network.
>>=20
>> The requirements 2, 3, 5 and 6 are interesting - ok - but may=20
>> represent too much work.
>=20
> Alex, I disagree on your proposition. I don't know how do you line=20
> between 1,4 and 2,3,5,6.

I draw the line like this.  2 (Support HA behind NAT) has no potential
solution as far as I know.  3 (DHAADv4) is an unknown protocol.  5 (v4
Home Address for MH) was out of scope initially, the scope was enable v6
Home Address for MH.  6 (dynamic allocation for v4 Home Address) is
something that DHCP can do.

Otherwise, do you agree with inserting a requirement number 0 that says
"give IPv6 Home Address for session continuity and reachability to a MH
that connects to an IPv4 access network"?

Another requirement that was agreeingly proposed on the MIP6 mailing
list was to support v6 HA that has no v4 connectivity.  Do you agree
with this requirement?

> The requirements listed here were from the DT consensus.

I acknowledge that. That's the way they were presented to the WG meeting.

> On the other hand, one thing where keiichi pointed out is whether we
>  should include IPv4 MNP in No.5. And Hesham agreed.

I agree they may have agreed on that point.

> Then, the next question was that should we split documents for v4=20
> traversal and v4 session continuity.

Let me try to understand.  Do you mean splitting DT documents?
Initially the DT was supposed to produce 1 scenario/reqs draft and 1
solution draft.  Do you mean that instead of the one solution draft
there'd be two complimentary solution drafts?

I understand draft-soliman and draft-dsmip are not DT output.

Alex

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



From mip6-bounces@ietf.org Wed Aug 10 10:04:55 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2rCR-0000MA-9W; Wed, 10 Aug 2005 10:04:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2rCP-0000M2-9b; Wed, 10 Aug 2005 10:04:53 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29604;
	Wed, 10 Aug 2005 10:04:51 -0400 (EDT)
Received: from motgate.mot.com ([129.188.136.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1E2rkS-0007jq-TJ; Wed, 10 Aug 2005 10:40:09 -0400
Received: from az33exr03.mot.com (az33exr03.mot.com [10.64.251.233])
	by motgate.mot.com (Motorola/Motgate) with ESMTP id j7AE4lLZ004405;
	Wed, 10 Aug 2005 07:04:47 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by az33exr03.mot.com (8.13.1/8.13.0) with ESMTP id j7AEAsGP023239;
	Wed, 10 Aug 2005 09:10:55 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id DCF64865980; Wed, 10 Aug 2005 16:04:43 +0200 (CEST)
Message-ID: <42FA097B.1070904@motorola.com>
Date: Wed, 10 Aug 2005 16:04:43 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Organization: Motorola Labs, Paris, France
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: Ryuji Wakikawa <ryuji@sfc.wide.ad.jp>
Subject: Re: [Mip6] Re: [nemo] carrying IPv4 traffic using MIP6/NEMO
References: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCAC1@ftmailserver.flariontech.com>
	<42F877E9.8010304@motorola.com>
	<6ED12209-2B69-4F0D-84FA-489A5AC05E49@sfc.wide.ad.jp>
	<42F9FE4D.6030406@motorola.com>
	<4CC22A36-030D-4816-B86F-9E3D0BB3B345@sfc.wide.ad.jp>
In-Reply-To: <4CC22A36-030D-4816-B86F-9E3D0BB3B345@sfc.wide.ad.jp>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Content-Transfer-Encoding: 7bit
Cc: "Soliman, Hesham" <H.Soliman@flarion.com>, nemo@ietf.org,
	Keiichi SHIMA <keiichi@iijlab.net>,
	Alexandru Petrescu <alexandru.petrescu@motorola.com>, 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

Ryuji Wakikawa wrote:
>> All in all, IMHO, mip6trans should not waste effort on giving v4 
>> access to nodes in the moving network; if it does (because 
>> consensus) then
> 
> We should work on v4 reachability, because MIP6 WG already has the 
> problem statement draft (draft-ietf-dsmip), And It makes sense to 
> have a similar/common solution, because both goals are to establish 
> tunnel between HA-MN after all.

I am confused.  dsmip problem statement is not mip6trans
problem-statement/reqs/scenarios.

The mip6trans and dsmip problem statements are different at least in size.

In my understanding, I was thinking that the problem mip6trans is trying
to solve was to give IPv6 access to a MH connecting to a v4 network.
Or, this requirement is not even listed now in the mp6trans requirements.

dsmip problem statement looks more wider reach, doing all v4/v6 mobility
by extending only the Mobile IPv6 protocol.

> The question may be whether we should split document or not?!

If "split" means separate the dsmip documents and the mip6trans
documents, goals, requirements, scenarios, I'd vote for it.

If "split" means separate draft-soliman from draft-shima with respect to
v4 access, I'd vote against.  Better have a unique document that does
Mobile IPv6-based dsmip-v4-access than two.  But not for mip6trans.

>> shouldn't do it with NAT.
> 
> 
> Do you mean doing NAT in mobile networks?

Yes, that's what I meant.  In detail, if v4 access to nodes in the
mobile network is to be developped anywhere, then don't do it in
mip6trans and don't do it with NAT in the mobile network.

Alex

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



From mip6-bounces@ietf.org Wed Aug 10 10:08:03 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2rFT-00010U-OD; Wed, 10 Aug 2005 10:08:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2rFT-00010M-3J; Wed, 10 Aug 2005 10:08:03 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00083;
	Wed, 10 Aug 2005 10:08:01 -0400 (EDT)
Received: from mail.sfc.wide.ad.jp ([203.178.142.146])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1E2rnX-0007pe-Qn; Wed, 10 Aug 2005 10:43:19 -0400
Received: from [192.168.1.2] (unknown [168.126.248.3])
	by mail.sfc.wide.ad.jp (Postfix) with ESMTP id 8584C4CD21;
	Wed, 10 Aug 2005 23:07:40 +0900 (JST)
In-Reply-To: <42FA0709.1060208@motorola.com>
References: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCAD1@ftmailserver.flariontech.com>
	<42F8D955.9010605@motorola.com>
	<7F1AD8E3-716A-45C3-9F03-179CA14E38B5@sfc.wide.ad.jp>
	<42FA0709.1060208@motorola.com>
Mime-Version: 1.0 (Apple Message framework v733)
Content-Type: text/plain; charset=SHIFT_JIS; delsp=yes; format=flowed
Message-Id: <A2EAD521-A7A8-4862-8B3B-F1A3D708F75F@sfc.wide.ad.jp>
Content-Transfer-Encoding: quoted-printable
From: Ryuji Wakikawa <ryuji@sfc.wide.ad.jp>
Date: Wed, 10 Aug 2005 23:07:34 +0900
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
X-Mailer: Apple Mail (2.733)
X-Spam-Score: 2.9 (++)
X-Scan-Signature: 2086112c730e13d5955355df27e3074b
Content-Transfer-Encoding: quoted-printable
Cc: "Soliman, Hesham" <H.Soliman@flarion.com>, nemo@ietf.org, mip6@ietf.org
Subject: [Mip6] Re: [nemo] Re: mip6trans requirements (was: carrying IPv4
	traffic using MIP6/NEMO)
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

Hi Alex


On 2005/08/10, at 22:54, Alexandru Petrescu wrote:

> Vijay Paris slides and Ryuji Wakikawa wrote:
>
>>>> 1 Support NAT traversal, NAT detection and the ability to turn
>>>> offthe NAT traversal mechanism when not required
>>>>
>>>
>>>
>>>> 2 Support the scenario where the Home Agent is behind a NAT and
>>>> not accessible through a public address
>>>>
>>>
>>>
>>>> 3 Support dynamic discovery of the HA=81fs IPv4 address
>>>>
>>>
>>>
>>>> 4 Enable IPsec protection for the mip6trans tunnel. The Home
>>>> Agentand the mobile node must be able to negotiate tunnel
>>>> security associations for the mip6trans tunnel
>>>>
>>>
>>>
>>>> 5 Enable the mobile node to use its IPv4 Home Address for IPv4
>>>> sessions over the mip6trans tunnel
>>>>
>>>
>>>
>>>> 6 Support dynamic allocation of the IPv4 Home Address
>>>>
>>>>
>>>
>>> I'm for 1 and 4 and not for 2, 3, 5, 6.  And I'd like to add
>>> requirement 0: support IPv6 session continuity at a permanent
>>> publicly-routable v6 Home Address when the MH connects to a
>>> v4-exclusively network.
>>>
>>> The requirements 2, 3, 5 and 6 are interesting - ok - but may
>>> represent too much work.
>>>
>>
>> Alex, I disagree on your proposition. I don't know how do you line
>> between 1,4 and 2,3,5,6.
>>
>
> I draw the line like this.  2 (Support HA behind NAT) has no potential
> solution as far as I know.

There were some comments to support this scenario.

> 3 (DHAADv4) is an unknown protocol.

we never say DHAADv4:-)

> 5 (v4
> Home Address for MH) was out of scope initially, the scope was =20
> enable v6
> Home Address for MH.

OK

> 6 (dynamic allocation for v4 Home Address) is
> something that DHCP can do.

We may give just guideline how to acquire the address with existing =20
solutions.
Nobody knows yet.

> Otherwise, do you agree with inserting a requirement number 0 that =20
> says
> "give IPv6 Home Address for session continuity and reachability to =20
> a MH
> that connects to an IPv4 access network"?

this is the base requirement.

> Another requirement that was agreeingly proposed on the MIP6 mailing
> list was to support v6 HA that has no v4 connectivity.  Do you agree
> with this requirement?

No, I personally don't.
>
>> The requirements listed here were from the DT consensus.
>>
>
> I acknowledge that. That's the way they were presented to the WG =20
> meeting.
>
>
>> On the other hand, one thing where keiichi pointed out is whether we
>>  should include IPv4 MNP in No.5. And Hesham agreed.
>>
>
> I agree they may have agreed on that point.
>
>
>> Then, the next question was that should we split documents for v4
>> traversal and v4 session continuity.
>>
>
> Let me try to understand.  Do you mean splitting DT documents?
> Initially the DT was supposed to produce 1 scenario/reqs draft and 1
> solution draft.  Do you mean that instead of the one solution draft
> there'd be two complimentary solution drafts?

Sorry, it was not so clear. I refer the comment of Keiichi.
What i thought  was that DT produce a base spec for v4 traversal =20
(maybe tunnel establishment) and
define additional document how to bind v4 HoA/MNP to the tunnel (MIP =20
tunnel/v4 traversal tunnel, whatever).
This is just personal idea and hopefully catch the intention of keiichi.

ryuji

> I understand draft-soliman and draft-dsmip are not DT output.
>
> Alex
>
>


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



From mip6-bounces@ietf.org Wed Aug 10 10:21:21 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2rSL-00068z-8r; Wed, 10 Aug 2005 10:21:21 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2rSJ-00068o-3t; Wed, 10 Aug 2005 10:21:19 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01702;
	Wed, 10 Aug 2005 10:21:17 -0400 (EDT)
Received: from mail.sfc.wide.ad.jp ([203.178.142.146])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1E2s0N-0008I3-IJ; Wed, 10 Aug 2005 10:56:35 -0400
Received: from [192.168.1.2] (unknown [168.126.248.3])
	by mail.sfc.wide.ad.jp (Postfix) with ESMTP id 49E344CCBB;
	Wed, 10 Aug 2005 23:20:59 +0900 (JST)
In-Reply-To: <42FA097B.1070904@motorola.com>
References: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCAC1@ftmailserver.flariontech.com>
	<42F877E9.8010304@motorola.com>
	<6ED12209-2B69-4F0D-84FA-489A5AC05E49@sfc.wide.ad.jp>
	<42F9FE4D.6030406@motorola.com>
	<4CC22A36-030D-4816-B86F-9E3D0BB3B345@sfc.wide.ad.jp>
	<42FA097B.1070904@motorola.com>
Mime-Version: 1.0 (Apple Message framework v733)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <AA2CFF5E-9792-4F77-A480-43F966819F6B@sfc.wide.ad.jp>
Content-Transfer-Encoding: 7bit
From: Ryuji Wakikawa <ryuji@sfc.wide.ad.jp>
Subject: Re: [Mip6] Re: [nemo] carrying IPv4 traffic using MIP6/NEMO
Date: Wed, 10 Aug 2005 23:20:52 +0900
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
X-Mailer: Apple Mail (2.733)
X-Spam-Score: 2.9 (++)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Content-Transfer-Encoding: 7bit
Cc: "Soliman, Hesham" <H.Soliman@flarion.com>, nemo@ietf.org, 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

Alex

On 2005/08/10, at 23:04, Alexandru Petrescu wrote:

> Ryuji Wakikawa wrote:
>
>>> All in all, IMHO, mip6trans should not waste effort on giving v4
>>> access to nodes in the moving network; if it does (because
>>> consensus) then
>>>
>>
>> We should work on v4 reachability, because MIP6 WG already has the
>> problem statement draft (draft-ietf-dsmip), And It makes sense to
>> have a similar/common solution, because both goals are to establish
>> tunnel between HA-MN after all.
>>
>
> I am confused.  dsmip problem statement is not mip6trans
> problem-statement/reqs/scenarios.
>
> The mip6trans and dsmip problem statements are different at least  
> in size.
> In my understanding, I was thinking that the problem mip6trans is  
> trying
> to solve was to give IPv6 access to a MH connecting to a v4 network.
> Or, this requirement is not even listed now in the mp6trans  
> requirements.

it is included.

> dsmip problem statement looks more wider reach, doing all v4/v6  
> mobility
> by extending only the Mobile IPv6 protocol.
>
>> The question may be whether we should split document or not?!
>>
>
> If "split" means separate the dsmip documents and the mip6trans
> documents, goals, requirements, scenarios, I'd vote for it.
>
> If "split" means separate draft-soliman from draft-shima with  
> respect to
> v4 access, I'd vote against.  Better have a unique document that does
> Mobile IPv6-based dsmip-v4-access than two.  But not for mip6trans.

I just tried to get back to the original question of keiichi:-)
If we have a unique solution for MIP6 and NEMO v4 access, I am fine  
either way.

>>> shouldn't do it with NAT.
>>>
>>
>>
>> Do you mean doing NAT in mobile networks?
>>
>
> Yes, that's what I meant.  In detail, if v4 access to nodes in the
> mobile network is to be developped anywhere, then don't do it in
> mip6trans and don't do it with NAT in the mobile network.

If MR can get v4 HoA through Hesham idea, MR can do NAT without any  
modifications.
I don't know whether we need additional modification after v4 HoA  
assignment. NAT is NAT:-)

ryuji

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



From mip6-bounces@ietf.org Wed Aug 10 10:24:02 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2rUv-0006eQ-VA; Wed, 10 Aug 2005 10:24:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2rUu-0006du-Hw; Wed, 10 Aug 2005 10:24:00 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01892;
	Wed, 10 Aug 2005 10:23:58 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1E2s2z-0008My-8i; Wed, 10 Aug 2005 10:59:16 -0400
Received: from il06exr04.mot.com (il06exr04.mot.com [129.188.137.134])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id j7AEXYHd025612;
	Wed, 10 Aug 2005 07:33:38 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by il06exr04.mot.com (8.13.1/8.13.0) with ESMTP id j7AETAum009052;
	Wed, 10 Aug 2005 09:29:15 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id C5D3D8637E6; Wed, 10 Aug 2005 16:23:34 +0200 (CEST)
Message-ID: <42FA0DE6.2040104@motorola.com>
Date: Wed, 10 Aug 2005 16:23:34 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Organization: Motorola Labs, Paris, France
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: Keiichi SHIMA <keiichi@iijlab.net>
References: <20050808.150050.259287104.keiichi@iijlab.net>
In-Reply-To: <20050808.150050.259287104.keiichi@iijlab.net>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Content-Transfer-Encoding: 7bit
Cc: nemo@ietf.org, mip6@ietf.org
Subject: [Mip6] Re: [nemo] carrying IPv4 traffic using MIP6/NEMO
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

Hi Keiichi, Ryuji (thanks for clarifying),

Keiichi SHIMA wrote:
> At the IETF MIP6 WG session, the design team talked about the 
> mechanism to bind an IPv4 home address to an IPv6 care-of address as
> a transission mechanism.

I think giving v6 access to a Mobile IPv6 MH connecting to a v4 access
network should be the main requirement for the mip6trans DT.  How this
is achieved is another matter.

The above paragraph proposes to bind an IPv4 Home Address to an IPv6
CoA.  I would not propose to do so.  The reason is that if MH is behind
NAT (most likely v4 access networks that I think of are NAT'ed) so it
makes no sense to bind a 192.168 CoA for a Global IPv6 Home Address.

On the contrary, I'd propose use UDP NAT traversal from Mobile IPv4 and
keep an IPv6 CoA on the tunnel.

> I have submitted very similar mechanism for IPv4 networks as 
> draft-shima-nemo-v4prefix-00.txt, which binds IPv4 prefixes to an
> IPv6 care-of address of a mobile router and provides IPv4 mobile
> network functionarity on top of NEMO.
> 
> I wonder if we should consider to integrate these two mechanism to 
> provide a single way to provide the mechanism to carry IPv4 traffic 
> for both a mobile host and a mobile router.

Generally, adding a prefixlen field too is preferable.  If WG and
mip6trans decide to go with v4 CoA then try to look at prefixes too, so
"integrate" yes.  But, big but, I am against the mip6trans requiremnent
that offers v4 access to MH; mip6trans just solve the case v6 access for
Mobile IPv6 MH connecting to v4 network.

Alex


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



From mip6-bounces@ietf.org Wed Aug 10 10:28:40 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2rZP-0007Cu-VE; Wed, 10 Aug 2005 10:28:39 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2rZO-0007Cj-Iu; Wed, 10 Aug 2005 10:28:38 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02210;
	Wed, 10 Aug 2005 10:28:36 -0400 (EDT)
From: Basavaraj.Patil@nokia.com
Received: from mgw-ext01.nokia.com ([131.228.20.93])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1E2s7S-0008VM-TA; Wed, 10 Aug 2005 11:03:54 -0400
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-ext01.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id
	j7AESRAF021893; Wed, 10 Aug 2005 17:28:30 +0300
Received: from daebh101.NOE.Nokia.com ([10.241.35.111]) by
	esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 10 Aug 2005 17:28:30 +0300
Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by
	daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 10 Aug 2005 09:28:28 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] Re: [nemo] carrying IPv4 traffic using MIP6/NEMO
Date: Wed, 10 Aug 2005 09:28:29 -0500
Message-ID: <456943D540CFC14A8D7138E64843F853016B9066@daebe101.NOE.Nokia.com>
Thread-Topic: [Mip6] Re: [nemo] carrying IPv4 traffic using MIP6/NEMO
Thread-Index: AcWdr4BRgmCbt8DgSgu7LP8eRi72xQAB7p/Q
To: <alexandru.petrescu@motorola.com>, <ryuji@sfc.wide.ad.jp>
X-OriginalArrivalTime: 10 Aug 2005 14:28:28.0890 (UTC)
	FILETIME=[C6BEDBA0:01C59DB7]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Content-Transfer-Encoding: quoted-printable
Cc: H.Soliman@flarion.com, nemo@ietf.org, keiichi@iijlab.net, 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


Hi Alex,

>
>I agree using NAT in the mobile network is possible.  I also agree that
>if NAT is used in the mobile network then there can be no mip6trans
>requirement for reachability at a permanent v4 address (behind NAT the
>v4 nodes are not reachable, somebody can't connect() to them).

Well reachability using an IP(v4) address is difficult in the case the
MN has a NATed address. However for various types of applications and
scenarios the v4 address is useful to have for the MN (even if it is
not a globally routable address).

>
>All in all, IMHO, mip6trans should not waste effort on giving v4 access
>to nodes in the moving network; if it does (because consensus) then
>shouldn't do it with NAT.

Enabling a MIP6 node to send/receive v4 packets is useful and worth
doing in the current scope.

-Raj

>
>My oppinion,
>
>Alex
>
>
>_______________________________________________
>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 Wed Aug 10 10:54:04 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2ry0-0007Md-7l; Wed, 10 Aug 2005 10:54:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2rxx-0007Lb-D1; Wed, 10 Aug 2005 10:54:02 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03963;
	Wed, 10 Aug 2005 10:53:59 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1E2sW4-0000so-3R; Wed, 10 Aug 2005 11:29:17 -0400
Received: from az33exr02.mot.com ([10.64.251.232])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id j7AF3q93002709;
	Wed, 10 Aug 2005 08:03:52 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by az33exr02.mot.com (8.13.1/8.13.0) with ESMTP id j7AEwrnt005420;
	Wed, 10 Aug 2005 09:58:54 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 2FD45865980; Wed, 10 Aug 2005 16:53:55 +0200 (CEST)
Message-ID: <42FA1503.9080903@motorola.com>
Date: Wed, 10 Aug 2005 16:53:55 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Organization: Motorola Labs, Paris, France
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: Basavaraj.Patil@nokia.com
Subject: Re: [Mip6] Re: [nemo] carrying IPv4 traffic using MIP6/NEMO
References: <456943D540CFC14A8D7138E64843F853016B9066@daebe101.NOE.Nokia.com>
In-Reply-To: <456943D540CFC14A8D7138E64843F853016B9066@daebe101.NOE.Nokia.com>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Content-Transfer-Encoding: 7bit
Cc: nemo@ietf.org, mip6@ietf.org,
	Alexandru Petrescu <alexandru.petrescu@motorola.com>,
	H.Soliman@flarion.com, ryuji@sfc.wide.ad.jp, keiichi@iijlab.net
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

Hi Raj,

Basavaraj.Patil@nokia.com wrote:
>> I agree using NAT in the mobile network is possible.  I also agree
>> that if NAT is used in the mobile network then there can be no
>> mip6trans requirement for reachability at a permanent v4 address
>> (behind NAT the v4 nodes are not reachable, somebody can't
>> connect() to them).
> 
> 
> Well reachability using an IP(v4) address is difficult in the case
> the MN has a NATed address. However for various types of applications
> and scenarios the v4 address is useful to have for the MN (even if it
> is not a globally routable address).

I agree.

>> All in all, IMHO, mip6trans should not waste effort on giving v4
>> access to nodes in the moving network; if it does (because
>> consensus) then shouldn't do it with NAT.
> 
> 
> Enabling a MIP6 node to send/receive v4 packets is useful and worth 
> doing in the current scope.

Raj, I do not oppose an IPv6 MH connecting to the v4 access network to
also have v4 access (just as it did until now).  That access can be
withou reachability, without session continuity, as it is today.

It's just that I don't feel there should be a requirement on mip6trans
to "support" or "enable" this in any way.  It just is there and
mip6trans protocol  shouldn't block it.

Making a mip6trans requirement for v4 access on MH leads to v4 access to
nodes in moving network too, etc.  This is clearly out of scope for
mip6trans, IMHO.

Alex

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



From mip6-bounces@ietf.org Wed Aug 10 11:09:07 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2sCZ-0004QO-LD; Wed, 10 Aug 2005 11:09:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E2sCY-0004QA-5o; Wed, 10 Aug 2005 11:09:06 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04911;
	Wed, 10 Aug 2005 11:09:01 -0400 (EDT)
Received: from motgate5.mot.com ([144.189.100.105])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1E2skc-0001Li-4b; Wed, 10 Aug 2005 11:44:19 -0400
Received: from az33exr04.mot.com (az33exr04.mot.com [10.64.251.234])
	by motgate5.mot.com (8.12.11/Motgate5) with ESMTP id j7AFFet4006981;
	Wed, 10 Aug 2005 08:15:40 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by az33exr04.mot.com (8.13.1/8.13.0) with ESMTP id j7AFDaKA009615;
	Wed, 10 Aug 2005 10:13:37 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 3DCBF865980; Wed, 10 Aug 2005 17:08:53 +0200 (CEST)
Message-ID: <42FA1885.2090800@motorola.com>
Date: Wed, 10 Aug 2005 17:08:53 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Organization: Motorola Labs, Paris, France
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: Ryuji Wakikawa <ryuji@sfc.wide.ad.jp>
Subject: Re: [Mip6] Re: [nemo] carrying IPv4 traffic using MIP6/NEMO
References: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCAC1@ftmailserver.flariontech.com>
	<42F877E9.8010304@motorola.com>
	<6ED12209-2B69-4F0D-84FA-489A5AC05E49@sfc.wide.ad.jp>
	<42F9FE4D.6030406@motorola.com>
	<4CC22A36-030D-4816-B86F-9E3D0BB3B345@sfc.wide.ad.jp>
	<42FA097B.1070904@motorola.com>
	<AA2CFF5E-9792-4F77-A480-43F966819F6B@sfc.wide.ad.jp>
In-Reply-To: <AA2CFF5E-9792-4F77-A480-43F966819F6B@sfc.wide.ad.jp>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Content-Transfer-Encoding: 7bit
Cc: "Soliman, Hesham" <H.Soliman@flarion.com>, nemo@ietf.org,
	Alexandru Petrescu <alexandru.petrescu@motorola.com>, 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

Ryuji Wakikawa wrote:

> Alex
> 
> On 2005/08/10, at 23:04, Alexandru Petrescu wrote:
> 
>> Ryuji Wakikawa wrote:
>>
>>>> All in all, IMHO, mip6trans should not waste effort on giving v4
>>>> access to nodes in the moving network; if it does (because
>>>> consensus) then
>>>>
>>>
>>> We should work on v4 reachability, because MIP6 WG already has the
>>> problem statement draft (draft-ietf-dsmip), And It makes sense to
>>> have a similar/common solution, because both goals are to establish
>>> tunnel between HA-MN after all.
>>>
>>
>> I am confused.  dsmip problem statement is not mip6trans
>> problem-statement/reqs/scenarios.
>>
>> The mip6trans and dsmip problem statements are different at least  in
>> size.
>> In my understanding, I was thinking that the problem mip6trans is  trying
>> to solve was to give IPv6 access to a MH connecting to a v4 network.
>> Or, this requirement is not even listed now in the mp6trans 
>> requirements.
> 
> 
> it is included.

Sorry, mistake, I think I've missed it when copy/paste.  I've looked
again and it's there.

Alex


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



From mip6-bounces@ietf.org Tue Aug 16 04:51:05 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E4xA1-0006vH-IU; Tue, 16 Aug 2005 04:51:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E4x9z-0006v9-Di; Tue, 16 Aug 2005 04:51:03 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA28211;
	Tue, 16 Aug 2005 04:51:01 -0400 (EDT)
Received: from omgo.iij.ad.jp ([202.232.30.157])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1E4xjH-0002g1-8c; Tue, 16 Aug 2005 05:27:32 -0400
Received: OTM-MO id j7G8olKV023752; Tue, 16 Aug 2005 17:50:47 +0900 (JST)
Received: OTM-MIX0 id j7G8okBn011151; Tue, 16 Aug 2005 17:50:46 +0900 (JST)
Received: from localhost (keiichi00.osaka.iij.ad.jp [192.168.64.45])
	by jc-smtp.iij.ad.jp (JC-SMTP/jc-smtp) id j7G8okEN003538;
	Tue, 16 Aug 2005 17:50:46 +0900 (JST)
Date: Tue, 16 Aug 2005 17:52:02 +0900 (JST)
Message-Id: <20050816.175202.22797246.keiichi@iijlab.net>
To: ryuji@sfc.wide.ad.jp
From: Keiichi SHIMA <keiichi@iijlab.net>
In-Reply-To: <A2EAD521-A7A8-4862-8B3B-F1A3D708F75F@sfc.wide.ad.jp>
References: <7F1AD8E3-716A-45C3-9F03-179CA14E38B5@sfc.wide.ad.jp>
	<42FA0709.1060208@motorola.com>
	<A2EAD521-A7A8-4862-8B3B-F1A3D708F75F@sfc.wide.ad.jp>
X-Mailer: Mew version 4.1.50 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Content-Transfer-Encoding: 7bit
Cc: H.Soliman@flarion.com, nemo@ietf.org, alexandru.petrescu@motorola.com,
	mip6@ietf.org
Subject: [Mip6] Re: [nemo] Re: mip6trans requirements
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

From: Ryuji Wakikawa <ryuji@sfc.wide.ad.jp>
Date: Wed, 10 Aug 2005 23:07:34 +0900

> > Let me try to understand.  Do you mean splitting DT documents?
> > Initially the DT was supposed to produce 1 scenario/reqs draft and 1
> > solution draft.  Do you mean that instead of the one solution draft
> > there'd be two complimentary solution drafts?
> 
> Sorry, it was not so clear. I refer the comment of Keiichi.
> What i thought  was that DT produce a base spec for v4 traversal  
> (maybe tunnel establishment) and
> define additional document how to bind v4 HoA/MNP to the tunnel (MIP  
> tunnel/v4 traversal tunnel, whatever).
> This is just personal idea and hopefully catch the intention of keiichi.

Yes, the above comment catches my intention.

I think providing an IPv4 HoA and (multiple) IPv4 home networks to a
mobile router is an important feature.  The question is whether the
specification must be discussed with traversal mechanisms or not.

I personally think these ideas (the mechanism for v4traversal and the
mechanism to provide v4 access) can be documented separately.  The v4
traversal document specifies the mechanism to provide an IPv4 address
as a CoA.  The v4 access document will provide the mechanism to put
additional identifiers (a v4 HoA and v4 MNPs).

I don't think these two mechanisms depend each other tightly.
(or, does it?)

Both specifications may be produced inside the DT or may not.  It
depends on the decision of the DT members.  (BTW, I personally think v4
access mechanisms are out of scope of the DT for v4traversal, though)

But, at least splitting orthogonal (it looks so to me) ideas are a
good way to keep specs simple..

Regards,
---
Keiichi SHIMA
IIJ Research Laboratory <keiichi@iijlab.net>
KAME Project <keiichi@kame.net>


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



From mip6-bounces@ietf.org Thu Aug 18 04:50:04 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E5g67-0002JB-VZ; Thu, 18 Aug 2005 04:50:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1E5g66-0002GP-Ri
	for mip6@megatron.ietf.org; Thu, 18 Aug 2005 04:50:02 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA20147
	for <mip6@ietf.org>; Thu, 18 Aug 2005 04:50:00 -0400 (EDT)
Received: from nav2.lgsoftindia.com ([203.200.13.13] helo=nav2.lgdomain.com)
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1E5gfl-0000lT-VT
	for mip6@ietf.org; Thu, 18 Aug 2005 05:26:57 -0400
Received: from appolo.lgdomain.com ([192.168.1.21])
	by nav2.lgdomain.com (SMSSMTP 4.1.2.20) with SMTP id
	M2005081814195321359
	for <mip6@ietf.org>; Thu, 18 Aug 2005 14:19:53 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 18 Aug 2005 14:20:46 +0530
Message-ID: <EC9E4C8E76FEF944B5C0711496A10728028D6BB6@APPOLO.lgdomain.com>
Thread-Topic: Binding Authorization Data option query
Thread-Index: AcWj0ezBQxwkCO84TEiKfE1OqdzMUg==
From: "Sameer T." <sameer.t@lgsoftindia.com>
To: <mip6@ietf.org>
X-Spam-Score: 3.3 (+++)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Subject: [Mip6] Binding Authorization Data option query
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="===============1662816455=="
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1662816455==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C5A3D1.F627175E"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C5A3D1.F627175E
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: base64

SGksDQpDYW4gYW55b25lIHBsZWFzZSBleHBsYWluIG1lLCB3aHkgdGhlIGF1dGhlbnRpY2F0
b3IgZmllbGQgaW4gQmluaWRpbmcgYXV0aG9yaXphdGlvbiBkYXRhIG1vYmlsaXR5IG9wdGlv
biBpcyBhIHZhcmlhYmxlIGxlbmd0aCBmaWVsZD8gZXZlbnRob3VnaCByZmMgMzc3NSBzdGF0
ZXMgIiAgIHRoZSBmaXJzdCA5NiBiaXRzIGZyb20gdGhlIE1BQyByZXN1bHQgYXJlIHVzZWQg
YXMgdGhlIEF1dGhlbnRpY2F0b3IgZmllbGQgLi4uICBBdXRoZW50aWNhdG9yID0gRmlyc3Qg
KDk2LCBITUFDX1NIQTEgKEtibSwgTW9iaWxpdHkgRGF0YSkpLiIgIA0KU28gd2h5IGlzIGl0
IE5PVCBjb25zaWRlcmVkIGFzIGZpeGVkIGxlbmd0aCAoMTIpPyANCg0KVGhhbmtzLA0KU2Ft
ZWVyDQoNCiMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMj
IyMjIyMjIyMjIyMjIyMjIyMjIyMjIw0KVEhJUyBFTUFJTCBNRVNTQUdFIElTIEZPUiBUSEUg
U09MRSBVU0UgT0YgVEhFIElOVEVOREVEIFJFQ0lQSUVOVChTKSBBTkQgTUFZIENPTlRBSU4g
Q09ORklERU5USUFMIEFORCBQUklWSUxFR0VEIElORk9STUFUSU9OLiBBTlkgVU5BVVRIT1JJ
WkVEIFJFVklFVywgVVNFLCBESVNDTE9TVVJFIE9SIERJU1RSSUJVVElPTiBJUyBQUk9ISUJJ
VEVELiBCRUZPUkUgT1BFTklORyBBTlkgQVRUQUNITUVOVFMgUExFQVNFIENIRUNLIEZPUiBW
SVJVU0VTIEFORCBERUZFQ1RTLiBJRiBZT1UgQVJFIE5PVCBUSEUgSU5URU5ERUQgUkVDSVBJ
RU5ULCBQTEVBU0UgTk9USUZZIFVTIElNTUVESUFURUxZIEJZIFJFUExZIEVNQUlMIEFORCBE
RUxFVEUgVEhFIE9SSUdJTkFMIE1FU1NBR0UuDQojIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMj
IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyM=

------_=_NextPart_001_01C5A3D1.F627175E
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDMuMi8vRU4iPg0KPEhU
TUw+DQo8SEVBRD4NCjxNRVRBIEhUVFAtRVFVSVY9IkNvbnRlbnQtVHlwZSIgQ09OVEVOVD0i
dGV4dC9odG1sOyBjaGFyc2V0PWlzby04ODU5LTEiPg0KPE1FVEEgTkFNRT0iR2VuZXJhdG9y
IiBDT05URU5UPSJNUyBFeGNoYW5nZSBTZXJ2ZXIgdmVyc2lvbiA2LjUuNzIyNi4wIj4NCjxU
SVRMRT5CaW5kaW5nIEF1dGhvcml6YXRpb24gRGF0YSBvcHRpb24gcXVlcnk8L1RJVExFPg0K
PC9IRUFEPg0KPEJPRFk+DQo8IS0tIENvbnZlcnRlZCBmcm9tIHRleHQvcnRmIGZvcm1hdCAt
LT4NCg0KPFA+PEZPTlQgRkFDRT0iVGltZXMgTmV3IFJvbWFuIj5IaSw8L0ZPTlQ+DQoNCjxC
Uj48Rk9OVCBGQUNFPSJUaW1lcyBOZXcgUm9tYW4iPkNhbiBhbnlvbmUgcGxlYXNlIGV4cGxh
aW4gbWUsIHdoeSB0aGUgYXV0aGVudGljYXRvciBmaWVsZCBpbiBCaW5pZGluZyBhdXRob3Jp
emF0aW9uIGRhdGEgbW9iaWxpdHkgb3B0aW9uIGlzIGEgdmFyaWFibGUgbGVuZ3RoIGZpZWxk
PyBldmVudGhvdWdoIHJmYyAzNzc1IHN0YXRlcyAmcXVvdDsmbmJzcDsmbmJzcDs8ST4gdGhl
IGZpcnN0IDk2IGJpdHMgZnJvbSB0aGUgTUFDIHJlc3VsdCBhcmUgdXNlZCBhcyB0aGUgQXV0
aGVudGljYXRvciBmaWVsZCAuLi4mbmJzcDsgQXV0aGVudGljYXRvciA9IEZpcnN0ICg5Niwg
SE1BQ19TSEExIChLYm0sIE1vYmlsaXR5IERhdGEpKS4mcXVvdDsmbmJzcDs8L0k+IDwvRk9O
VD48L1A+DQoNCjxQPjxGT05UIEZBQ0U9IlRpbWVzIE5ldyBSb21hbiI+U28gd2h5IGlzIGl0
IE5PVCBjb25zaWRlcmVkIGFzIGZpeGVkIGxlbmd0aCAoMTIpPyA8L0ZPTlQ+DQo8L1A+DQoN
CjxQPjxGT05UIEZBQ0U9IlRpbWVzIE5ldyBSb21hbiI+VGhhbmtzLDwvRk9OVD4NCg0KPEJS
PjxGT05UIEZBQ0U9IlRpbWVzIE5ldyBSb21hbiI+U2FtZWVyPC9GT05UPg0KPC9QPg0KDQo8
L0JPRFk+DQo8L0hUTUw+PHByZT4jIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMj
IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMNClRISVMgRU1BSUwgTUVTU0FH
RSBJUyBGT1IgVEhFIFNPTEUgVVNFIE9GIFRIRSBJTlRFTkRFRCBSRUNJUElFTlQoUykgQU5E
IE1BWSBDT05UQUlOIENPTkZJREVOVElBTCBBTkQgUFJJVklMRUdFRCBJTkZPUk1BVElPTi4g
QU5ZIFVOQVVUSE9SSVpFRCBSRVZJRVcsIFVTRSwgRElTQ0xPU1VSRSBPUiBESVNUUklCVVRJ
T04gSVMgUFJPSElCSVRFRC4gQkVGT1JFIE9QRU5JTkcgQU5ZIEFUVEFDSE1FTlRTIFBMRUFT
RSBDSEVDSyBGT1IgVklSVVNFUyBBTkQgREVGRUNUUy4gSUYgWU9VIEFSRSBOT1QgVEhFIElO
VEVOREVEIFJFQ0lQSUVOVCwgUExFQVNFIE5PVElGWSBVUyBJTU1FRElBVEVMWSBCWSBSRVBM
WSBFTUFJTCBBTkQgREVMRVRFIFRIRSBPUklHSU5BTCBNRVNTQUdFLg0KIyMjIyMjIyMjIyMj
IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMj
IyMjPC9wcmU+

------_=_NextPart_001_01C5A3D1.F627175E--


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

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

--===============1662816455==--




From mip6-bounces@ietf.org Thu Aug 18 07:43:36 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E5io4-0001XN-2R; Thu, 18 Aug 2005 07:43:36 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1E5io1-0001Vm-RX
	for mip6@megatron.ietf.org; Thu, 18 Aug 2005 07:43:33 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28335
	for <mip6@ietf.org>; Thu, 18 Aug 2005 07:43:32 -0400 (EDT)
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E5jNk-0005vF-Sm
	for mip6@ietf.org; Thu, 18 Aug 2005 08:20:30 -0400
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id E720589852;
	Thu, 18 Aug 2005 14:43:18 +0300 (EEST)
Message-ID: <43047463.8030401@kolumbus.fi>
Date: Thu, 18 Aug 2005 14:43:31 +0300
From: Jari Arkko <jari.arkko@kolumbus.fi>
User-Agent: Mozilla Thunderbird 1.0 (X11/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Sameer T." <sameer.t@lgsoftindia.com>
Subject: Re: [Mip6] Binding Authorization Data option query
References: <EC9E4C8E76FEF944B5C0711496A10728028D6BB6@APPOLO.lgdomain.com>
In-Reply-To: <EC9E4C8E76FEF944B5C0711496A10728028D6BB6@APPOLO.lgdomain.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
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

Sameer T. wrote:

> Hi,
> Can anyone please explain me, why the authenticator field in Biniding 
> authorization data mobility option is a variable length field? 
> eventhough rfc 3775 states "  / the first 96 bits from the MAC result 
> are used as the Authenticator field ...  Authenticator = First (96, 
> HMAC_SHA1 (Kbm, Mobility Data))." /
>
> So why is it NOT considered as fixed length (12)?
>
Two answers:

1) Considering the mobility option layer formatting, all options except 
Pad1 have
a lenth field. This is necessary just to be able to process the options 
in a clean
manner without necessarily having to understand all options.

2) Considering the BAD option definition itself, it does say that the
length has to be 96 bits. If you are asking why the length field
is still included, see answer #1. Also, its not impossible that
at some future time we choose a new algorithm and need to
use some other number of bits. An update to the BAD
option definition would allow this, without breaking the
format itself.

Hope this clarifies it,

Jari


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



From mip6-bounces@ietf.org Sun Aug 21 21:51:13 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E71Sz-0007CB-ED; Sun, 21 Aug 2005 21:51:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1E71Sx-0007C3-Iu
	for mip6@megatron.ietf.org; Sun, 21 Aug 2005 21:51:11 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA00958
	for <mip6@ietf.org>; Sun, 21 Aug 2005 21:51:09 -0400 (EDT)
Received: from smtp.um.es ([155.54.212.105] helo=mail.um.es)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E723Q-00075H-Rm
	for mip6@ietf.org; Sun, 21 Aug 2005 22:28:53 -0400
Received: from localhost (localhost [127.0.0.1])
	by mail.um.es (Postfix) with ESMTP id 30ABA1FA3E7
	for <mip6@ietf.org>; Mon, 22 Aug 2005 03:51:02 +0200 (CEST)
Received: from mail.um.es ([127.0.0.1])
	by localhost (xenon1 [127.0.0.1]) (amavisd-new, port 10024) with LMTP
	id 08311-01-43 for <mip6@ietf.org>;
	Mon, 22 Aug 2005 03:51:01 +0200 (CEST)
Received: from [192.150.187.162] (dibulibu.um.es [155.54.1.250])
	by mail.um.es (Postfix) with ESMTP id 23D7D1FA3E3
	for <mip6@ietf.org>; Mon, 22 Aug 2005 03:51:00 +0200 (CEST)
Message-ID: <43092F83.9050806@dif.um.es>
Date: Sun, 21 Aug 2005 18:50:59 -0700
From: "Pedro M. Ruiz" <pedrom@dif.um.es>
User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: mip6@ietf.org
Content-Type: multipart/mixed; boundary="------------000506070801050402020707"
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at telemat.um.es
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d16ce744298aacf98517bc7c108bd198
Subject: [Mip6] Call for Participation AD HOC NOW 2005
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

This is a multi-part message in MIME format.
--------------000506070801050402020707
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit



--------------000506070801050402020707
Content-Type: text/plain; x-mac-type="0"; x-mac-creator="0";
	name="cfparticip.txt"
Content-Disposition: inline;
 filename="cfparticip.txt"
Content-Transfer-Encoding: 7bit

We apologize if you receive the CFP more than once.
----------------------------------------------------------------------------
                 CALL FOR PARTICIPATION - AD HOC NOW 2005
         4th International Conference on Ad hoc Networks and Wireless
                         Cancun, October 6-8, 2005
                     http://fismat.umich.mx/adhocnow/
----------------------------------------------------------------------------

Early registration deadline: August, 31st
Hotel deadline to avail of rooms being held for AD HOC NOW 2005: Sept 24th

ABOUT THE CONFERENCE
--------------------

AD HOC NOW is the fourth of a series of high-quality conferences devoted to 
ad hoc, wireless and mobile networks. The AD HOC NOW committee invites you to
in this new edition, which will be held in Cancun, in October 6th-8th.

The program for this year consist of 27 top-quality papers, and two invited
speaker with a well-deserved recognition in the area:

* Prof. Jorge Urrutia, Univ. Nacional (UNAM), Mexico.
* Prof. J.J. Garcia-Luna-Aceves, Univ. of California, Santa Cruz.

ACCEPTED PAPERS
---------------
Playing CSMA/CA Game to Deter Backoff Attacks in Ad Hoc Wireless LANs 
	Jerzy Konorski

Message Stability and Reliable Broadcasts in Mobile Ad-Hoc Networks 
	Kulpreet Singh, Andronikos Nedos, Gregor Gaertner and Siobhan Clarke

Equilibria for Broadcast Range Assignment Games in Ad-Hoc Networks 
	Pilu Crescenzi, Miriam Di Ianni, Alessandro Lazzoni, Paolo Penna, 
	Gianluca Rossi and Paola Vocca

Performance Analysis of the Hierarchical Layer Graph for Wireless Networks 
	Stefan Ruehrup, Christian Schindelhauer and Klaus Volbert

Cache Placement in Sensor Networks Under Update Constraint 
	Bin Tang, Samir Das, and Himanshu Gupta

Enhancing The Security Of On-demand Routing in Ad Hoc Networks 
	Zhenjiang Li and J.J. Garcia-Luna-Aceves

MIMOMAN: A MIMO Mac protocol for Ad hoc Networks 
	Joon-Sang Park and Mario Gerla

Increasing the Resource-Efficiency of the CSMA/CA Protocol in Directional 
Ad Hoc Networks 
	Matthias Gruenewald, Feng Xu and Ulrich Rueckert

Location Tracking in Mobile Ad Hoc Networks using Particle Filters 
	Rui Huang and Gergely Zaruba

Selective Route Request Scheme for On-Demand Routing Protocols in Ad Hoc
Networks
	Seung Jae Lee

A Key Management Scheme for Commodity Sensor Networks
	Yong Ho Kim, Mu Hyun Kim, and Dong Hoon Lee

Design of a hard real-time guarantee scheme for dual ad hoc mode 
IEEE 802.11 WLANs 
	Junghoon Lee, Mikyung Kang and Yongmoon Jin

DPUMA: A Highly Efficient Multicast Routing Protocol for Mobile Ad Hoc Networks 
	Rolando Menchaca-Mendez, Ravindra Vaishampayan, 
	J.J. Garcia-Luna-Aceves and Katia Obraczka

Efficient Mechanisms for Secure Inter-node and Aggregation Processing 
in Sensor Networks 
	Tassos Dimitriou

Probability Distributions for Channel Utilisation 
	Christian Schindelhauer and Kerstin VoB

Approximation Algorithms for Minimum Bandwith Multicast Trees in 
Wireless Mesh Networks 
	Pedro M. Ruiz and Antonio F. Gomez-Skarmeta

Stressing is better than relaxing for negative cost cycle detection in networks 
	K. Subramani

Enhanced power-aware Routing for Mobile Ad-Hoc Networks 
	Il-Hee Shin, Chae-Woo Lee

Randomized AB-Face-AB Routing Algorithms in Mobile Ad Hoc Networks 
	Thomas Fevens, Alaa Eddien Abdallah, and Badr Naciri Bennani

A Gathering Point Detection Scheme for Directed Diffusion in 
Wireless Sensor Networks 
	Jeongho Son, Jinsuk Pak and Kijun Han

Cluster-Based Framework in Vehicular Ad-Hoc Networks 
	Peng Fan, James Haran, Peter Nelson and John Dillenburg

Biology Inspired Distributed Consensus in Massively-Deployed Sensor Networks 
	K.H.Jones, K.N.Lodding, S.Olariu, L.W.Wilson and C.Xin

A Multiple Path Characterization of Ad-Hoc Network Capacity 
	Peter Giese and Ioanis Nikolaidis

Reed-Solomon and Hermitian Code-based Scheduling Protocols for 
Wireless Ad Hoc Networks 
	Carlos H. Rentel and Thomas Kunz

Efficient broadcasting in Self-Organizing Multi-hop Wireless Networks 
	Nathalie Mitton and Eric Fleury

An Intelligent Sensor Network for Oceanographic Data Acquisition. 
	Chris Roadknight, Antonio Gonzalez, Laura. Parrot, 
	Steve Boult and Ian Marshall

A service discovery protocol with maximally area disjoint paths in 
mobile ad hoc networks 
	Shihong Zou, Le Tian, Shiduan Cheng and Yu Lin

REGISTRATION
------------

You can proceed to: http://fismat.umich.mx/adhocnow/?f=registration

After you complete your registration to ADHOCNOW! 2005, you'll be able to download a postcript document which must be filled in with your credit card data and faxed to the number shown in order to secure your reservation to the Oasis Hotel.

The conference will be held at the Oasis Cancun Hotel. The hotel rate for this conference is within an All-inclusive program, which entitles you to all meals (buffet breakfast, lunch and dinner), unlimited drinks, recreational activities, non-motorized water sports, gym facilities, evening shows, disco, all taxes and tips. Rates are as follows:

    Single	US$86.00
    Double	US$140.00
    Triple	US$170.00

FOR ADDITIONAL INFORMATON
-------------------------
For questions regarding obtaining visas, accomodation, etc, please contact
Edgar Chavez (mailto:elchavez@fismat.umich.mx). 



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

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

--------------000506070801050402020707--




From mip6-bounces@ietf.org Sun Aug 21 23:53:29 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E73NJ-0000xc-UO; Sun, 21 Aug 2005 23:53:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E70pI-0000LB-01; Sun, 21 Aug 2005 21:10:12 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA29393;
	Sun, 21 Aug 2005 21:10:10 -0400 (EDT)
Received: from rodin.i2r.a-star.edu.sg ([192.122.139.27])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1E71Ph-00068t-JU; Sun, 21 Aug 2005 21:47:53 -0400
Received: from rodin.i2r.a-star.edu.sg (localhost [127.0.0.1])
	by rodin.i2r.a-star.edu.sg (8.13.1/8.13.1) with ESMTP id j7M19nED002467;
	Mon, 22 Aug 2005 09:09:49 +0800 (SGT)
Received: from newmailhost.i2r.a-star.edu.sg ([192.122.134.76])by rodin.i2r.
	a-star.edu.sg (8.13.1/8.13.1) with ESMTP id j7M19llf002423;
	Mon, 22 Aug 2005 09:09:48 +0800 (SGT)
Received: from bearty1 ([192.168.152.200])by mailhost.lit.org.sg (Sun Java S
	ystem Messaging Server 6.1 HotFix 0.06(built Nov 11 2004)) with SMTP id
	<0I LL00FDEN8DD620@mailhost.lit.org.sg>;
	Mon,22 Aug 2005 09:09:49 +0800 (SGT)
Date: Mon, 22 Aug 2005 09:09:53 +0800
From: Boon Sain Yeo <boonyeo@ieee.org>
To: <Undisclosed-Recipient:@ietf.org;>
Message-id: <104901c5a6b6$343c1a60$c898a8c0@bearty1>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-Priority: 3
X-MSMail-priority: Normal
X-imss-version: 2.29
X-imss-result: Passed
X-imss-scores: Clean:99.90000 C:2 M:3 S:5 R:5
X-imss-settings: Baseline:5 C:4 M:4 S:4 R:4 (1.5000 1.5000)
X-Spam-Score: 0.5 (/)
X-Scan-Signature: bacfc6c7290e34d410f9bc22b825ce96
X-Mailman-Approved-At: Sun, 21 Aug 2005 23:53:26 -0400
Cc: 
Subject: [Mip6] CFP SensorWare
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="===============0368494213=="
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0368494213==
Content-type: multipart/alternative;
	boundary="Boundary_(ID_2LetgtaYslsKWbFmxU0M3Q)"

This is a multi-part message in MIME format.

--Boundary_(ID_2LetgtaYslsKWbFmxU0M3Q)
Content-type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7BIT

(My apologies if you receive multiple copies of this message)

***********************************************************
1st International Workshop on Software for Sensor Networks (SensorWare) - CFP
***********************************************************
 

Welcome to the 1st International Workshop on Software for Sensor Networks (SensorWare) to be held on the 8 January 2006. The workshop is held in conjunction with COMSWARE 2006 in the beautiful and historical city of New Delhi.


Advances in technology have made deployment of miniature sensors a realistic proposition. These sensors are low-power, inexpensive, smart devices with multiple on-board sensors, and are connected through wireless links, so as to form a collaborative sensor network to perform a specific task. As a result, it opens up a new paradigm of ubiquitous computing and enables a range of applications that are previously unrealizable or too costly to be realized. However, given the limitation of on-board hardware, one of the key areas towards achieving superior performance is through the software implementation. The workshop is intended for the presentation and discussion of novel algorithms and software implementation for sensor networks. This workshop, intends to bring together engineering experts and academicians to discuss the current status, technical challenges, standards, fundamental issues, and future services and applications in the form of panels and technical presentation.



Topics of interest include but are not limited to the following:



Operating System 
Efficient algorithms 
Protocol design 
Performance analysis 
Performance related issues 
Sensor applications 
Deployment issues and scenarios 
Middleware 
Sensor security 
Sensor network design and modeling 
 

Workshop co-chairs:

Nirmala Shenoy (ns@rit.edu), RIT, USA
Boon Sain Yeo (boonyeo@ieee.org), Institute for Infocomm Research, Singapore 



TPC Members:

Holger Karl, University of Paderborn, Germany,
Ling-Jyh Chen, Academia Sinica, Taiwan
Kui Wu, University of Victoria, Canada,
Daeyoung Kim, ICU, Korea
Leonard Barolli, Fukuoka Institute of Technology, Japan,
Wei-Peng Chen, Fujitsu Labs of America, USA
Jason Redi, BBN Technologies, USA      
Biao Chen, Syracuse University, USA
Hairong  Qi, University of Tennessee, USA
Xiaojun Cao, Rochester Institute of Technology, USA
Xin Wang, University of Buffalo, USA
James Minseok Kwon, RIT, USA
Wenye Wang, North Carolina State University, USA
Fei Hu, RIT, USA
Robin Chellappa, Deakin Univeristy, Australia  

Technical Papers has to be submitted to the co-chairs at boonyeo@ieee.org. 

Papers should be written in English and should preferably follow the instructions in template.pdf. Preferred maximum paper length is 6 printed pages (10-point font) including figures.

Important Dates:

Paper Submission Deadline: 1 October 2005
Notification Acceptance/Rejection: 1 November 2005
Final Camera-Ready Paper Submission: 1 December 2005

Please visit the workshop website at http://www.sensorware.org for more info.

We look forward to seeing you at SensorWare.

Many thanks
Best regards,

Boon and Nirmala
Workshop co-chairs

--Boundary_(ID_2LetgtaYslsKWbFmxU0M3Q)
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.2900.2722" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2><FONT face=3DArial size=3D2>(My =
apologies if you=20
receive multiple copies of this message)</FONT></DIV>
<DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial=20
size=3D2>***********************************************************<BR>1=
st=20
International Workshop on Software for Sensor Networks (SensorWare) =96=20
CFP<BR>***********************************************************<BR>&nb=
sp;</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Welcome to the 1st International =
Workshop on=20
Software for Sensor Networks (SensorWare) to be held on the 8 January =
2006. The=20
workshop is held in conjunction with COMSWARE 2006 in the beautiful and=20
historical city of New Delhi.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Advances in technology have made =
deployment of=20
miniature sensors a realistic proposition. These sensors are low-power,=20
inexpensive, smart devices with multiple on-board sensors, and are =
connected=20
through wireless links, so as to form a collaborative sensor network to =
perform=20
a specific task. As a result, it opens up a new paradigm of ubiquitous =
computing=20
and enables a range of applications that are previously unrealizable or =
too=20
costly to be realized. However, given the limitation of on-board =
hardware, one=20
of the key areas towards achieving superior performance is through the =
software=20
implementation. The workshop is intended for the presentation and =
discussion of=20
novel algorithms and software implementation for sensor networks. This =
workshop,=20
intends to bring together engineering experts and academicians to =
discuss the=20
current status, technical challenges, standards, fundamental issues, and =
future=20
services and applications in the form of panels and technical=20
presentation.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Topics of interest include but are not =
limited to=20
the following:</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Operating System <BR>Efficient =
algorithms=20
<BR>Protocol design <BR>Performance analysis <BR>Performance related =
issues=20
<BR>Sensor applications <BR>Deployment issues and scenarios =
<BR>Middleware=20
<BR>Sensor security <BR>Sensor network design and=20
modeling&nbsp;<BR>&nbsp;</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Workshop co-chairs:</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Nirmala Shenoy (<A =
href=3D"">ns@rit.edu</A>), RIT,=20
USA<BR>Boon Sain Yeo (<A href=3D"">boonyeo@ieee.org</A>), Institute for =
Infocomm=20
Research, Singapore </FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>TPC Members:</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Holger Karl, University of Paderborn,=20
Germany,<BR>Ling-Jyh Chen, Academia Sinica, Taiwan<BR>Kui Wu, University =
of=20
Victoria, Canada,<BR>Daeyoung Kim, ICU, Korea<BR>Leonard Barolli, =
Fukuoka=20
Institute of Technology, Japan,<BR>Wei-Peng Chen, Fujitsu Labs of =
America,=20
USA<BR>Jason Redi, BBN Technologies, USA&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<BR>Biao=20
Chen, Syracuse University, USA<BR>Hairong&nbsp; Qi, University of =
Tennessee,=20
USA<BR>Xiaojun Cao, Rochester Institute of Technology, USA<BR>Xin Wang,=20
University of Buffalo, USA<BR>James Minseok Kwon, RIT, USA<BR>Wenye =
Wang, North=20
Carolina State University, USA<BR>Fei Hu, RIT, USA<BR>Robin Chellappa, =
Deakin=20
Univeristy, Australia&nbsp; </FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Technical Papers has to be submitted to =
the=20
co-chairs at <A href=3D"">boonyeo@ieee.org</A>. </FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Papers should be written in English and =
should=20
preferably follow the instructions in template.pdf. Preferred maximum =
paper=20
length is 6 printed pages (10-point font) including =
figures.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2><BR>Important Dates:</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Paper Submission Deadline: 1=20
October&nbsp;2005<BR>Notification Acceptance/Rejection: 1&nbsp;November=20
2005<BR>Final Camera-Ready Paper Submission: 1&nbsp;December =
2005</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Please visit the workshop website at <A =

href=3D"">http://www.sensorware.org</A> for more info.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>We look forward to seeing you at=20
SensorWare.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Many thanks<BR>Best =
regards,</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Boon and Nirmala<BR>Workshop=20
co-chairs</FONT></DIV></FONT></DIV></BODY></HTML>

--Boundary_(ID_2LetgtaYslsKWbFmxU0M3Q)--


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

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

--===============0368494213==--




From mip6-bounces@ietf.org Mon Aug 22 10:21:52 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E7DBQ-0002M0-Qu; Mon, 22 Aug 2005 10:21:52 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1E7DBP-0002Ls-DE
	for mip6@megatron.ietf.org; Mon, 22 Aug 2005 10:21:51 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18748
	for <mip6@ietf.org>; Mon, 22 Aug 2005 10:21:49 -0400 (EDT)
Received: from nav2.lgsoftindia.com ([203.200.13.13] helo=nav2.lgdomain.com)
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1E7Dlw-0002Lo-QE
	for mip6@ietf.org; Mon, 22 Aug 2005 10:59:39 -0400
Received: from appolo.lgdomain.com ([192.168.1.21])
	by nav2.lgdomain.com (SMSSMTP 4.1.2.20) with SMTP id
	M2005082219514408491
	for <mip6@ietf.org>; Mon, 22 Aug 2005 19:51:44 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 22 Aug 2005 19:53:04 +0530
Message-ID: <EC9E4C8E76FEF944B5C0711496A1072802940C9F@APPOLO.lgdomain.com>
Thread-Topic: Query on Neighbor cache and route cache
Thread-Index: AcWnJQJLak26tW3jTnSulwl62U6Y9w==
From: "Sameer T." <sameer.t@lgsoftindia.com>
To: <mip6@ietf.org>
X-Spam-Score: 2.5 (++)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Subject: [Mip6] Query on Neighbor cache and route cache
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="===============1713206859=="
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1713206859==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C5A725.01159F90"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C5A725.01159F90
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: base64

SGksDQpDYW4gc29tZW9uZSBwbGVhc2UgY2xhcmlmeSB0aGlzIHF1ZXJ5Lg0KV2hlbiBhIG1v
YmlsZSBub2RlIG1vdmVzIHRvIGEgZm9yZWlnbiBuZXR3b3JrIGZyb20gaGlzIGhvbWUgbmV0
d29yaywgYW5kIGNvbWVzIGJhY2sgdG8gaG9tZSBuZXR3b3JrIGFnYWluIGFmdGVyIHNvbWUg
dGltZSwgZG9lcyBoZSBuZWVkIHRvIHJlbWVtYmVyIGFsbCB0aGUgcm91dGUgY2FjaGUgZW50
cmllcyAgYW5kIG5laWdoYm9yIGNhY2hlIGVudHJpZXMsIHdoaWNoIHdlcmUgcHJlc2VudCBp
biBoaXMgaG9tZSBuZXR3b3JrPw0KRm9yIGV4YW1wbGUsIGluIGhpcyBob21lIG5ldHdvcmsg
aGUgaGFkIGEgbmVpZ2hib3IgY2FjaGUgZW50cnkgd2hpY2ggaXMgaW4gU1RBTEUgc3RhdGUs
IGFuZCBpdHMgbGlmZXRpbWUgd2lsbCBleHBpcmUgb25seSBhZnRlciAxMCBob3Vycy4gVGhl
biBoZSBnb2VzIHRvIGZvcmVpZ24gbmV0d29yaywgYWZ0ZXIgdHdvIGhvdXJzIGl0IGNvbWVz
IGJhY2sgdG8gaG9tZSBuZXR3b3JrLiBOb3cgc2hvdWxkIGhlIHJlbWVtYmVyIHRoaXMgb2xk
IGVudHJ5PyANCg0KYWxzbyB0aGUgZGVmYXVsdCByb3V0ZXIgbGlzdD8gY2FuIHdlIGZsdXNo
IGFsbCB0aGVzZSB0YWJsZXMgb25jZSB3ZSBtb3ZlIHRvIGEgbmV3IG5ldHdvcms/DQoNClRo
YW5rcywNClNhbWVlcnQNCg0KIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMj
IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjDQpUSElTIEVNQUlMIE1FU1NBR0Ug
SVMgRk9SIFRIRSBTT0xFIFVTRSBPRiBUSEUgSU5URU5ERUQgUkVDSVBJRU5UKFMpIEFORCBN
QVkgQ09OVEFJTiBDT05GSURFTlRJQUwgQU5EIFBSSVZJTEVHRUQgSU5GT1JNQVRJT04uIEFO
WSBVTkFVVEhPUklaRUQgUkVWSUVXLCBVU0UsIERJU0NMT1NVUkUgT1IgRElTVFJJQlVUSU9O
IElTIFBST0hJQklURUQuIEJFRk9SRSBPUEVOSU5HIEFOWSBBVFRBQ0hNRU5UUyBQTEVBU0Ug
Q0hFQ0sgRk9SIFZJUlVTRVMgQU5EIERFRkVDVFMuIElGIFlPVSBBUkUgTk9UIFRIRSBJTlRF
TkRFRCBSRUNJUElFTlQsIFBMRUFTRSBOT1RJRlkgVVMgSU1NRURJQVRFTFkgQlkgUkVQTFkg
RU1BSUwgQU5EIERFTEVURSBUSEUgT1JJR0lOQUwgTUVTU0FHRS4NCiMjIyMjIyMjIyMjIyMj
IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMj
Iw==

------_=_NextPart_001_01C5A725.01159F90
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDMuMi8vRU4iPg0KPEhU
TUw+DQo8SEVBRD4NCjxNRVRBIEhUVFAtRVFVSVY9IkNvbnRlbnQtVHlwZSIgQ09OVEVOVD0i
dGV4dC9odG1sOyBjaGFyc2V0PWlzby04ODU5LTEiPg0KPE1FVEEgTkFNRT0iR2VuZXJhdG9y
IiBDT05URU5UPSJNUyBFeGNoYW5nZSBTZXJ2ZXIgdmVyc2lvbiA2LjUuNzIyNi4wIj4NCjxU
SVRMRT5RdWVyeSBvbiBOZWlnaGJvciBjYWNoZSBhbmQgcm91dGUgY2FjaGU8L1RJVExFPg0K
PC9IRUFEPg0KPEJPRFk+DQo8IS0tIENvbnZlcnRlZCBmcm9tIHRleHQvcnRmIGZvcm1hdCAt
LT4NCg0KPFA+PEk+PEZPTlQgRkFDRT0iTW9ub3R5cGUgQ29yc2l2YSI+SGksPC9GT05UPjwv
ST4NCg0KPEJSPjxJPjxGT05UIEZBQ0U9Ik1vbm90eXBlIENvcnNpdmEiPkNhbiBzb21lb25l
IHBsZWFzZSBjbGFyaWZ5IHRoaXMgcXVlcnkuPC9GT05UPjwvST4NCg0KPEJSPjxJPjxGT05U
IEZBQ0U9Ik1vbm90eXBlIENvcnNpdmEiPldoZW4gYSBtb2JpbGUgbm9kZSBtb3ZlcyB0byBh
IGZvcmVpZ24gbmV0d29yayBmcm9tIGhpcyBob21lIG5ldHdvcmssIGFuZCBjb21lcyBiYWNr
IHRvIGhvbWUgbmV0d29yayBhZ2FpbiBhZnRlciBzb21lIHRpbWUsIGRvZXMgaGUgbmVlZCB0
byByZW1lbWJlciBhbGwgdGhlIHJvdXRlIGNhY2hlIGVudHJpZXMmbmJzcDsgYW5kIG5laWdo
Ym9yIGNhY2hlIGVudHJpZXMsIHdoaWNoIHdlcmUgcHJlc2VudCBpbiBoaXMgaG9tZSBuZXR3
b3JrPzwvRk9OVD48L0k+PC9QPg0KDQo8UD48ST48Rk9OVCBGQUNFPSJNb25vdHlwZSBDb3Jz
aXZhIj5Gb3IgZXhhbXBsZSwgaW4gaGlzIGhvbWUgbmV0d29yayBoZSBoYWQgYSBuZWlnaGJv
ciBjYWNoZSBlbnRyeSB3aGljaCBpcyBpbiBTVEFMRSBzdGF0ZSwgYW5kIGl0cyBsaWZldGlt
ZSB3aWxsIGV4cGlyZSBvbmx5IGFmdGVyIDEwIGhvdXJzLiBUaGVuIGhlIGdvZXMgdG8gZm9y
ZWlnbiBuZXR3b3JrLCBhZnRlciB0d28gaG91cnMgaXQgY29tZXMgYmFjayB0byBob21lIG5l
dHdvcmsuIE5vdyBzaG91bGQgaGUgcmVtZW1iZXIgdGhpcyBvbGQgZW50cnk/IDwvRk9OVD48
L0k+PC9QPg0KDQo8UD48ST48Rk9OVCBGQUNFPSJNb25vdHlwZSBDb3JzaXZhIj5hbHNvIHRo
ZSBkZWZhdWx0IHJvdXRlciBsaXN0PyBjYW4gd2UgZmx1c2ggYWxsIHRoZXNlIHRhYmxlcyBv
bmNlIHdlIG1vdmUgdG8gYSBuZXcgbmV0d29yaz88L0ZPTlQ+PC9JPg0KPC9QPg0KDQo8UD48
ST48Rk9OVCBGQUNFPSJNb25vdHlwZSBDb3JzaXZhIj5UaGFua3MsPC9GT05UPjwvST4NCg0K
PEJSPjxJPjxGT05UIEZBQ0U9Ik1vbm90eXBlIENvcnNpdmEiPlNhbWVlcnQ8L0ZPTlQ+PC9J
Pg0KPC9QPg0KDQo8L0JPRFk+DQo8L0hUTUw+PHByZT4jIyMjIyMjIyMjIyMjIyMjIyMjIyMj
IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMNClRISVMg
RU1BSUwgTUVTU0FHRSBJUyBGT1IgVEhFIFNPTEUgVVNFIE9GIFRIRSBJTlRFTkRFRCBSRUNJ
UElFTlQoUykgQU5EIE1BWSBDT05UQUlOIENPTkZJREVOVElBTCBBTkQgUFJJVklMRUdFRCBJ
TkZPUk1BVElPTi4gQU5ZIFVOQVVUSE9SSVpFRCBSRVZJRVcsIFVTRSwgRElTQ0xPU1VSRSBP
UiBESVNUUklCVVRJT04gSVMgUFJPSElCSVRFRC4gQkVGT1JFIE9QRU5JTkcgQU5ZIEFUVEFD
SE1FTlRTIFBMRUFTRSBDSEVDSyBGT1IgVklSVVNFUyBBTkQgREVGRUNUUy4gSUYgWU9VIEFS
RSBOT1QgVEhFIElOVEVOREVEIFJFQ0lQSUVOVCwgUExFQVNFIE5PVElGWSBVUyBJTU1FRElB
VEVMWSBCWSBSRVBMWSBFTUFJTCBBTkQgREVMRVRFIFRIRSBPUklHSU5BTCBNRVNTQUdFLg0K
IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMj
IyMjIyMjIyMjIyMjIyMjPC9wcmU+

------_=_NextPart_001_01C5A725.01159F90--


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

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

--===============1713206859==--




From mip6-bounces@ietf.org Tue Aug 23 09:02:59 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E7YQd-0007hy-7O; Tue, 23 Aug 2005 09:02:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1E7YQX-0007gl-DB
	for mip6@megatron.ietf.org; Tue, 23 Aug 2005 09:02:57 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02079
	for <mip6@ietf.org>; Tue, 23 Aug 2005 09:02:52 -0400 (EDT)
Received: from nav2.lgsoftindia.com ([203.200.13.13] helo=nav2.lgdomain.com)
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1E7YQd-0003mY-1S
	for mip6@ietf.org; Tue, 23 Aug 2005 09:03:01 -0400
Received: from appolo.lgdomain.com ([192.168.1.21])
	by nav2.lgdomain.com (SMSSMTP 4.1.2.20) with SMTP id
	M2005082318325016320 ; Tue, 23 Aug 2005 18:32:50 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 23 Aug 2005 18:34:05 +0530
Message-ID: <EC9E4C8E76FEF944B5C0711496A10728029417A7@APPOLO.lgdomain.com>
Thread-Topic: Mobile node communicating with Mobile node 
Thread-Index: AcWn4yP3FfPc+qWoRGCjXRPDCC2pNQ==
From: "Sameer T." <sameer.t@lgsoftindia.com>
To: <mip6@ietf.org>
X-Spam-Score: 2.5 (++)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2
Cc: Jari Arkko <jari.arkko@kolumbus.fi>
Subject: [Mip6] Mobile node communicating with Mobile node 
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="===============0153922020=="
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0153922020==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C5A7E3.27472DD5"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C5A7E3.27472DD5
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: base64

SGkgYWxsLA0KVGhpcyBpcyByZWdhcmRpbmcgTW9iaWxlIG5vZGUgY29tbXVuaWNhdGluZyB3
aXRoIGFub3RoZXIgbW9iaWxlIG5vZGUsIA0KV2hlbiB0aGVyZSBhcmUgdHdvIG1vYmlsZSBu
b2RlcywgTjEgJiBOMiAgKGJvdGggYXJlIE1JUHY2IGNhcGFibGUgYW5kIGluaXRpYWxseSBh
dCBob21lIG5ldHdvcmspLg0KIA0KMSkgd2hlbiBOMSBtb3ZlcyB0byBhIG5ldyBuL3csIC4u
Lml0IGZpbmlzaGVzIGhvbWUgcmVnaXN0cmF0aW9uLCAgaXQgIHRoZW4gdXBkYXRlcyBOMiAo
UmV0dXJuIHJvdXRhYmlsaXR5IGFuZCBCVSBtZXNzYWdlKS4gIA0KTm93IE4yIGhhcyBhIGJp
bmRpbmcgY2FjaGUgZm9yIE4xLg0KDQoyKSB0aGVuICBOMiBtb3ZlcyB0byBhIG5ldyBuL3cs
IGZpbmlzaGVzIGhvbWUgcmVnaXN0cmF0aW9uLCB0aGVuIE4yIHJlY2VpdmVzIGEgdHVubmVs
ZWQgcGFja2V0IGZyb20gTjEgd2l0aCBob21lIGFkZHJlc3Mgb3B0aW9uICh0dW5uZWxlZCB0
aHJ1IGl0cyBob21lIGFnZW50KSAuIE5vdyBpdCBzaG91bGQgdXBkYXRlIE4xIHdpdGggaXRz
ICBjYXJlIG9mIGFkZHJlc3MgKFJldHVybiByb3V0YWJpbGl0eSBhbmQgQlUgbWVzc2FnZSkg
cmlnaHQ/IA0KSW4gdGhpcyBjYXNlIA0KCWEpIGhvbWUgdGVzdCBpbml0IG1lc3NhZ2UgYW5k
IGNhcmUgb2YgdGVzdCBpbml0IG1lc3NhZ2Ugd2lsbCBiZSBzZW50IHRvIE4xJ3MgY2FyZSBv
ZiBhZGRyZXNzIG9yIE4xJ3MgaG9tZSBhZGRyZXNzLj8gDQoJYikgV2hhdCBhYm91dCBCdSBt
ZXNzYWdlLCBpdCBhbHNvIHdpbGwgYmUgc2VudCB0byBOMSdzIGMvbyBhZGRyZXNzIG9yIGhv
bWUgYWRkcmVzcz8NCklmIHRoZXkgYXJlIHNlbnQgdG8gTjEncyBob21lIGFkZHJlc3MsIE4x
J3MgaG9tZSBhZ2VudCBzaG91bGQgdHVubmVsIGFuZCBzZW5kIHRoaXMgcGFja2V0IHRvIE4x
J3MgY2FyZSBvZiBhZGRyZXNzIHJpZ2h0Pw0KRG9lcyByZmMgMzc3NSBtZW50aW9uIHRoaXMg
c2NlbmFyaW8/IG9yIGFtIEkgbWlzc2luZyBhbnkgY29uY2VwdCBoZXJlPyANCg0KDQpUaGFu
a3MsDQpTYW1lZXINCg0KICANCiMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMj
IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIw0KVEhJUyBFTUFJTCBNRVNTQUdF
IElTIEZPUiBUSEUgU09MRSBVU0UgT0YgVEhFIElOVEVOREVEIFJFQ0lQSUVOVChTKSBBTkQg
TUFZIENPTlRBSU4gQ09ORklERU5USUFMIEFORCBQUklWSUxFR0VEIElORk9STUFUSU9OLiBB
TlkgVU5BVVRIT1JJWkVEIFJFVklFVywgVVNFLCBESVNDTE9TVVJFIE9SIERJU1RSSUJVVElP
TiBJUyBQUk9ISUJJVEVELiBCRUZPUkUgT1BFTklORyBBTlkgQVRUQUNITUVOVFMgUExFQVNF
IENIRUNLIEZPUiBWSVJVU0VTIEFORCBERUZFQ1RTLiBJRiBZT1UgQVJFIE5PVCBUSEUgSU5U
RU5ERUQgUkVDSVBJRU5ULCBQTEVBU0UgTk9USUZZIFVTIElNTUVESUFURUxZIEJZIFJFUExZ
IEVNQUlMIEFORCBERUxFVEUgVEhFIE9SSUdJTkFMIE1FU1NBR0UuDQojIyMjIyMjIyMjIyMj
IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMj
IyM=

------_=_NextPart_001_01C5A7E3.27472DD5
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDMuMi8vRU4iPg0KPEhU
TUw+DQo8SEVBRD4NCjxNRVRBIEhUVFAtRVFVSVY9IkNvbnRlbnQtVHlwZSIgQ09OVEVOVD0i
dGV4dC9odG1sOyBjaGFyc2V0PWlzby04ODU5LTEiPg0KPE1FVEEgTkFNRT0iR2VuZXJhdG9y
IiBDT05URU5UPSJNUyBFeGNoYW5nZSBTZXJ2ZXIgdmVyc2lvbiA2LjUuNzIyNi4wIj4NCjxU
SVRMRT5Nb2JpbGUgbm9kZSBjb21tdW5pY2F0aW5nIHdpdGggTW9iaWxlIG5vZGUgPC9USVRM
RT4NCjwvSEVBRD4NCjxCT0RZPg0KPCEtLSBDb252ZXJ0ZWQgZnJvbSB0ZXh0L3J0ZiBmb3Jt
YXQgLS0+DQoNCjxQPjxJPjxGT05UIEZBQ0U9Ik1vbm90eXBlIENvcnNpdmEiPkhpIGFsbCw8
L0ZPTlQ+PC9JPg0KDQo8QlI+PEk+PEZPTlQgRkFDRT0iTW9ub3R5cGUgQ29yc2l2YSI+VGhp
cyBpcyByZWdhcmRpbmcgTW9iaWxlIG5vZGUgY29tbXVuaWNhdGluZyB3aXRoIGFub3RoZXIg
bW9iaWxlIG5vZGUsIDwvRk9OVD48L0k+DQoNCjxCUj48ST48Rk9OVCBGQUNFPSJNb25vdHlw
ZSBDb3JzaXZhIj5XaGVuIHRoZXJlIGFyZSB0d28gbW9iaWxlIG5vZGVzLCBOMSAmYW1wOyBO
MiZuYnNwOyAoYm90aCBhcmUgTUlQdjYgY2FwYWJsZSBhbmQgaW5pdGlhbGx5IGF0IGhvbWUg
bmV0d29yaykuPC9GT05UPjwvST4NCg0KPEJSPjxJPjxCPjxGT05UIEZBQ0U9Ik1vbm90eXBl
IENvcnNpdmEiPjwvRk9OVD48L0I+Jm5ic3A7PC9JPg0KDQo8QlI+PEk+PEZPTlQgRkFDRT0i
TW9ub3R5cGUgQ29yc2l2YSI+MSkgd2hlbiBOMSBtb3ZlcyB0byBhIG5ldyBuL3csIC4uLml0
IGZpbmlzaGVzIGhvbWUgcmVnaXN0cmF0aW9uLCZuYnNwOyBpdCZuYnNwOyB0aGVuIHVwZGF0
ZXMgTjIgKFJldHVybiByb3V0YWJpbGl0eSBhbmQgQlUgbWVzc2FnZSkuJm5ic3A7IDwvRk9O
VD48L0k+PC9QPg0KDQo8UD48ST48Rk9OVCBGQUNFPSJNb25vdHlwZSBDb3JzaXZhIj5Ob3cg
TjIgaGFzIGEgYmluZGluZyBjYWNoZSBmb3IgTjEuPC9GT05UPjwvST4NCjwvUD4NCg0KPFA+
PEk+PEZPTlQgRkFDRT0iTW9ub3R5cGUgQ29yc2l2YSI+MikgdGhlbiZuYnNwOyBOMiBtb3Zl
cyB0byBhIG5ldyBuL3csIGZpbmlzaGVzIGhvbWUgcmVnaXN0cmF0aW9uLCB0aGVuIE4yIHJl
Y2VpdmVzIGEgdHVubmVsZWQgcGFja2V0IGZyb20gTjEgd2l0aCBob21lIGFkZHJlc3Mgb3B0
aW9uICh0dW5uZWxlZCB0aHJ1IGl0cyBob21lIGFnZW50KSAuIE5vdyBpdCBzaG91bGQgdXBk
YXRlIE4xIHdpdGggaXRzJm5ic3A7IGNhcmUgb2YgYWRkcmVzcyAoUmV0dXJuIHJvdXRhYmls
aXR5IGFuZCBCVSBtZXNzYWdlKSByaWdodD8gPC9GT05UPjwvST48L1A+DQoNCjxQPjxJPjxG
T05UIEZBQ0U9Ik1vbm90eXBlIENvcnNpdmEiPkluIHRoaXMgY2FzZSA8L0ZPTlQ+PC9JPg0K
DQo8QlI+PEk+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IDxG
T05UIEZBQ0U9Ik1vbm90eXBlIENvcnNpdmEiPmEpIGhvbWUgdGVzdCBpbml0IG1lc3NhZ2Ug
YW5kIGNhcmUgb2YgdGVzdCBpbml0IG1lc3NhZ2Ugd2lsbCBiZSBzZW50IHRvIE4xJ3MgY2Fy
ZSBvZiBhZGRyZXNzIG9yIE4xJ3MgaG9tZSBhZGRyZXNzLj8gPC9GT05UPjwvST48L1A+DQoN
CjxQPjxJPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyA8Rk9O
VCBGQUNFPSJNb25vdHlwZSBDb3JzaXZhIj5iKSBXaGF0IGFib3V0IEJ1IG1lc3NhZ2UsIGl0
IGFsc28gd2lsbCBiZSBzZW50IHRvIE4xJ3MgYy9vIGFkZHJlc3Mgb3IgaG9tZSBhZGRyZXNz
PzwvRk9OVD48L0k+DQoNCjxCUj48ST48Rk9OVCBGQUNFPSJNb25vdHlwZSBDb3JzaXZhIj5J
ZiB0aGV5IGFyZSBzZW50IHRvIE4xJ3MgaG9tZSBhZGRyZXNzLCBOMSdzIGhvbWUgYWdlbnQg
c2hvdWxkIHR1bm5lbCBhbmQgc2VuZCB0aGlzIHBhY2tldCB0byBOMSdzIGNhcmUgb2YgYWRk
cmVzcyByaWdodD88L0ZPTlQ+PC9JPjwvUD4NCg0KPFA+PEk+PEZPTlQgRkFDRT0iTW9ub3R5
cGUgQ29yc2l2YSI+RG9lcyByZmMgMzc3NSBtZW50aW9uIHRoaXMgc2NlbmFyaW8/IG9yIGFt
IEkgbWlzc2luZyBhbnkgY29uY2VwdCBoZXJlPyA8L0ZPTlQ+PC9JPg0KPC9QPg0KPEJSPg0K
DQo8UD48ST48Rk9OVCBGQUNFPSJNb25vdHlwZSBDb3JzaXZhIj5UaGFua3MsPC9GT05UPjwv
ST4NCg0KPEJSPjxJPjxGT05UIEZBQ0U9Ik1vbm90eXBlIENvcnNpdmEiPlNhbWVlcjwvRk9O
VD48L0k+DQo8L1A+DQoNCjxQPjxJPjxGT05UIEZBQ0U9Ik1vbm90eXBlIENvcnNpdmEiPiZu
YnNwOyA8L0ZPTlQ+PC9JPg0KPC9QPg0KDQo8L0JPRFk+DQo8L0hUTUw+PHByZT4jIyMjIyMj
IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMj
IyMjIyMjIyMNClRISVMgRU1BSUwgTUVTU0FHRSBJUyBGT1IgVEhFIFNPTEUgVVNFIE9GIFRI
RSBJTlRFTkRFRCBSRUNJUElFTlQoUykgQU5EIE1BWSBDT05UQUlOIENPTkZJREVOVElBTCBB
TkQgUFJJVklMRUdFRCBJTkZPUk1BVElPTi4gQU5ZIFVOQVVUSE9SSVpFRCBSRVZJRVcsIFVT
RSwgRElTQ0xPU1VSRSBPUiBESVNUUklCVVRJT04gSVMgUFJPSElCSVRFRC4gQkVGT1JFIE9Q
RU5JTkcgQU5ZIEFUVEFDSE1FTlRTIFBMRUFTRSBDSEVDSyBGT1IgVklSVVNFUyBBTkQgREVG
RUNUUy4gSUYgWU9VIEFSRSBOT1QgVEhFIElOVEVOREVEIFJFQ0lQSUVOVCwgUExFQVNFIE5P
VElGWSBVUyBJTU1FRElBVEVMWSBCWSBSRVBMWSBFTUFJTCBBTkQgREVMRVRFIFRIRSBPUklH
SU5BTCBNRVNTQUdFLg0KIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMj
IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjPC9wcmU+

------_=_NextPart_001_01C5A7E3.27472DD5--


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

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

--===============0153922020==--




From mip6-bounces@ietf.org Thu Aug 25 07:36:22 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E8G1u-0000p6-4e; Thu, 25 Aug 2005 07:36:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1E8G1s-0000p1-FR
	for mip6@megatron.ietf.org; Thu, 25 Aug 2005 07:36:20 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13099
	for <mip6@ietf.org>; Thu, 25 Aug 2005 07:36:19 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E8G2N-0008SH-7h
	for mip6@ietf.org; Thu, 25 Aug 2005 07:36:52 -0400
Received: from il06exr02.mot.com (il06exr02.mot.com [129.188.137.132])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id j7PBkPtR022230;
	Thu, 25 Aug 2005 04:46:25 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by il06exr02.mot.com (8.13.1/8.13.0) with ESMTP id j7PBggmp002006;
	Thu, 25 Aug 2005 06:42:43 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 08EC48637E6; Thu, 25 Aug 2005 13:36:06 +0200 (CEST)
Message-ID: <430DAD25.70502@motorola.com>
Date: Thu, 25 Aug 2005 13:36:05 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Organization: Motorola Labs, Paris, France
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: "Sameer T." <sameer.t@lgsoftindia.com>
Subject: Re: [Mip6] Query on Neighbor cache and route cache
References: <EC9E4C8E76FEF944B5C0711496A1072802940C9F@APPOLO.lgdomain.com>
In-Reply-To: <EC9E4C8E76FEF944B5C0711496A1072802940C9F@APPOLO.lgdomain.com>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
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

Sameer T. wrote:
> /Hi,/
> /Can someone please clarify this query./
> /When a mobile node moves to a foreign network from his home network,
> and comes back to home network again after some time, does he need to
> remember all the route cache entries  and neighbor cache entries, which
> were present in his home network?/
> 
> /For example, in his home network he had a neighbor cache entry which is
> in STALE state, and its lifetime will expire only after 10 hours. Then
> he goes to foreign network, after two hours it comes back to home
> network. Now should he remember this old entry? /
> 
> /also the default router list? can we flush all these tables once we
> move to a new network?/

I wouldn't flush anything, just save them in some hidden tables when
moving away from home.  When coming back home copy these entries back to
the original tables if they've not expired.

Alex

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



From mip6-bounces@ietf.org Thu Aug 25 07:43:54 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E8G9C-0002ba-8w; Thu, 25 Aug 2005 07:43:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1E8G9A-0002bU-J5
	for mip6@megatron.ietf.org; Thu, 25 Aug 2005 07:43:52 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13305
	for <mip6@ietf.org>; Thu, 25 Aug 2005 07:43:51 -0400 (EDT)
Received: from motgate5.mot.com ([144.189.100.105])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E8G9f-0000Cb-Ix
	for mip6@ietf.org; Thu, 25 Aug 2005 07:44:24 -0400
Received: from az33exr02.mot.com (az33exr02.mot.com [10.64.251.232])
	by motgate5.mot.com (8.12.11/Motgate5) with ESMTP id j7PBom8s027671;
	Thu, 25 Aug 2005 04:50:48 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by az33exr02.mot.com (8.13.1/8.13.0) with ESMTP id j7PBnDdC009390;
	Thu, 25 Aug 2005 06:49:13 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 706A68637E6; Thu, 25 Aug 2005 13:43:45 +0200 (CEST)
Message-ID: <430DAEF1.6090904@motorola.com>
Date: Thu, 25 Aug 2005 13:43:45 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Organization: Motorola Labs, Paris, France
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: "Sameer T." <sameer.t@lgsoftindia.com>
Subject: Re: [Mip6] Mobile node communicating with Mobile node
References: <EC9E4C8E76FEF944B5C0711496A10728029417A7@APPOLO.lgdomain.com>
In-Reply-To: <EC9E4C8E76FEF944B5C0711496A10728029417A7@APPOLO.lgdomain.com>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org, Jari Arkko <jari.arkko@kolumbus.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

Sameer T. wrote:
> /Hi all,/
> /This is regarding Mobile node communicating with another mobile node, /
> /When there are two mobile nodes, N1 & N2  (both are MIPv6 capable and
> initially at home network)./
> /** /
> /1) when N1 moves to a new n/w, ...it finishes home registration,  it 
> then updates N2 (Return routability and BU message).  /
> 
> /Now N2 has a binding cache for N1./
> 
> /2) then  N2 moves to a new n/w, finishes home registration, then N2
> receives a tunneled packet from N1 with home address option (tunneled
> thru its home agent) . Now it should update N1 with its  care of address
> (Return routability and BU message) right? /

Right.

> 
> /In this case /
> /        a) home test init message and care of test init message will be
> sent to N1's care of address or N1's home address.? /
> 
> /        b) What about Bu message, it also will be sent to N1's c/o
> address or home address?/
> /If they are sent to N1's home address, N1's home agent should tunnel
> and send this packet to N1's care of address right?/
> 
> /Does rfc 3775 mention this scenario? or am I missing any concept here? /

I think rfc3775 describes behaviour of an MN talking to a correspondent.
 That "correspondent" could be either HA or a CN or another MN.  Which
means that the case MN talking RR to another MN has been looked at, at
least pencil on paper.

Please do not get confused by terminology.  Often it is useful for text
writers to have a simple terminology that is easy to grasp.  Questions
get quickly answered at implementation and test time.

Alex

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



From mip6-bounces@ietf.org Thu Aug 25 08:28:35 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E8GqR-0007py-Tc; Thu, 25 Aug 2005 08:28:35 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1E8GqQ-0007ps-HL
	for mip6@megatron.ietf.org; Thu, 25 Aug 2005 08:28:34 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15235
	for <mip6@ietf.org>; Thu, 25 Aug 2005 08:28:33 -0400 (EDT)
Received: from nav2.lgsoftindia.com ([203.200.13.13] helo=nav2.lgdomain.com)
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1E8Gqv-0001Z8-JO
	for mip6@ietf.org; Thu, 25 Aug 2005 08:29:07 -0400
Received: from appolo.lgdomain.com ([192.168.1.21])
	by nav2.lgdomain.com (SMSSMTP 4.1.2.20) with SMTP id
	M2005082517582924297 ; Thu, 25 Aug 2005 17:58:29 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [Mip6] Mobile node communicating with Mobile node
Date: Thu, 25 Aug 2005 17:59:53 +0530
Message-ID: <EC9E4C8E76FEF944B5C0711496A10728029A09F1@APPOLO.lgdomain.com>
Thread-Topic: [Mip6] Mobile node communicating with Mobile node
Thread-Index: AcWpaoJog8HoBUxsRwGLOjbcbxhqIgABKevg
From: "Sameer T." <sameer.t@lgsoftindia.com>
To: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>
X-Spam-Score: 2.2 (++)
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>
Content-Type: multipart/mixed; boundary="===============1740991101=="
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

--===============1740991101==
Content-class: urn:content-classes:message
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64

QWxleCwgVGhhbmtzIGZvciB5b3VyIHJlcGx5LCAgDQoNCkkgZG8gYWdyZWUgdGhhdCBpbiBy
ZmMgMzc3NSAiY29ycmVzcG9uZGVudCIgY291bGQgYmUgZWl0aGVyIEhBIG9yIGEgQ04gb3Ig
YW5vdGhlciBNTi4gQW5kICBteSBleGFjdCBxdWVyeSBpcyBpbiB0aGUgdGhpcmQgY2FzZSwg
d2hlbiB0aGUgY29ycmVzcG9uZGVudCBpcyBNTi4gDQoNCj4gPiAvICAgICAgICBhKSBob21l
IHRlc3QgaW5pdCBtZXNzYWdlIGFuZCBjYXJlIG9mIHRlc3QgaW5pdCANCj4gbWVzc2FnZSB3
aWxsIGJlDQo+ID4gc2VudCB0byBOMSdzIGNhcmUgb2YgYWRkcmVzcyBvciBOMSdzIGhvbWUg
YWRkcmVzcy4/IC8NCj4gPiANCj4gPiAvICAgICAgICBiKSBXaGF0IGFib3V0IEJ1IG1lc3Nh
Z2UsIGl0IGFsc28gd2lsbCBiZSBzZW50IHRvIE4xJ3MgYy9vDQo+ID4gYWRkcmVzcyBvciBo
b21lIGFkZHJlc3M/Lw0KPiA+IC9JZiB0aGV5IGFyZSBzZW50IHRvIE4xJ3MgaG9tZSBhZGRy
ZXNzLCBOMSdzIGhvbWUgYWdlbnQgDQo+IHNob3VsZCB0dW5uZWwNCj4gPiBhbmQgc2VuZCB0
aGlzIHBhY2tldCB0byBOMSdzIGNhcmUgb2YgYWRkcmVzcyByaWdodD8vDQo+ID4gDQoNCldo
YXQgSSByZWFsbHkgd2FudGVkIHRvIGtub3cgd2FzLCBpbiBteSBleGFtcGxlIGJvdGggTjEg
YW5kIE4yIGFyZSBhd2F5IGZyb20gaG9tZS4gU28gd2hlbiBOMiBzZW5kcyBIb21lIHRlc3Qg
aW5pdCBtZXNzYWdlLCBhcyBhIHBhcnQgb2YgUlIsIGl0IHNlbmRzIHRvIGhvbWUgYWRkcmVz
cyBvZiBOMS4gU28gSG9tZSB0ZXN0IGluaXQgbWVzc2FnZSBmaXJzdCBnb2VzIHRvIE4yJ3Mg
aG9tZSBhZ2VudCAoc2luY2UgaXQgaXMgYSBob21lIHRlc3QgaW5pdCBtZXNzYWdlKSwgdGhl
biBpdCBnb2VzIHRvIE4xJ3MgaG9tZSBhZ2VudCwgZmluYWxseSB0byBOMSAodGhydSBoaXMg
Y2FyZSBvZiBhZGRyZXNzKS4gSXMgbXkgdW5kZXJzdGFuZGluZyBjb3JyZWN0IGhlcmU/DQog
DQpTYW1lZXINCg0KDQoNCg0KDQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4g
RnJvbTogQWxleGFuZHJ1IFBldHJlc2N1IFttYWlsdG86YWxleGFuZHJ1LnBldHJlc2N1QG1v
dG9yb2xhLmNvbV0NCj4gU2VudDogVGh1cnNkYXksIEF1Z3VzdCAyNSwgMjAwNSA1OjE0IFBN
DQo+IFRvOiBTYW1lZXIgVC4NCj4gQ2M6IG1pcDZAaWV0Zi5vcmc7IEphcmkgQXJra28NCj4g
U3ViamVjdDogUmU6IFtNaXA2XSBNb2JpbGUgbm9kZSBjb21tdW5pY2F0aW5nIHdpdGggTW9i
aWxlIG5vZGUNCj4gDQo+IA0KPiBTYW1lZXIgVC4gd3JvdGU6DQo+ID4gL0hpIGFsbCwvDQo+
ID4gL1RoaXMgaXMgcmVnYXJkaW5nIE1vYmlsZSBub2RlIGNvbW11bmljYXRpbmcgd2l0aCBh
bm90aGVyIA0KPiBtb2JpbGUgbm9kZSwgLw0KPiA+IC9XaGVuIHRoZXJlIGFyZSB0d28gbW9i
aWxlIG5vZGVzLCBOMSAmIE4yICAoYm90aCBhcmUgTUlQdjYgDQo+IGNhcGFibGUgYW5kDQo+
ID4gaW5pdGlhbGx5IGF0IGhvbWUgbmV0d29yaykuLw0KPiA+IC8qKiAvDQo+ID4gLzEpIHdo
ZW4gTjEgbW92ZXMgdG8gYSBuZXcgbi93LCAuLi5pdCBmaW5pc2hlcyBob21lIA0KPiByZWdp
c3RyYXRpb24sICBpdCANCj4gPiB0aGVuIHVwZGF0ZXMgTjIgKFJldHVybiByb3V0YWJpbGl0
eSBhbmQgQlUgbWVzc2FnZSkuICAvDQo+ID4gDQo+ID4gL05vdyBOMiBoYXMgYSBiaW5kaW5n
IGNhY2hlIGZvciBOMS4vDQo+ID4gDQo+ID4gLzIpIHRoZW4gIE4yIG1vdmVzIHRvIGEgbmV3
IG4vdywgZmluaXNoZXMgaG9tZSByZWdpc3RyYXRpb24sIHRoZW4gTjINCj4gPiByZWNlaXZl
cyBhIHR1bm5lbGVkIHBhY2tldCBmcm9tIE4xIHdpdGggaG9tZSBhZGRyZXNzIG9wdGlvbiAN
Cj4gKHR1bm5lbGVkDQo+ID4gdGhydSBpdHMgaG9tZSBhZ2VudCkgLiBOb3cgaXQgc2hvdWxk
IHVwZGF0ZSBOMSB3aXRoIGl0cyAgDQo+IGNhcmUgb2YgYWRkcmVzcw0KPiA+IChSZXR1cm4g
cm91dGFiaWxpdHkgYW5kIEJVIG1lc3NhZ2UpIHJpZ2h0PyAvDQo+IA0KPiBSaWdodC4NCj4g
DQo+ID4gDQo+ID4gL0luIHRoaXMgY2FzZSAvDQo+ID4gLyAgICAgICAgYSkgaG9tZSB0ZXN0
IGluaXQgbWVzc2FnZSBhbmQgY2FyZSBvZiB0ZXN0IGluaXQgDQo+IG1lc3NhZ2Ugd2lsbCBi
ZQ0KPiA+IHNlbnQgdG8gTjEncyBjYXJlIG9mIGFkZHJlc3Mgb3IgTjEncyBob21lIGFkZHJl
c3MuPyAvDQo+ID4gDQo+ID4gLyAgICAgICAgYikgV2hhdCBhYm91dCBCdSBtZXNzYWdlLCBp
dCBhbHNvIHdpbGwgYmUgc2VudCB0byBOMSdzIGMvbw0KPiA+IGFkZHJlc3Mgb3IgaG9tZSBh
ZGRyZXNzPy8NCj4gPiAvSWYgdGhleSBhcmUgc2VudCB0byBOMSdzIGhvbWUgYWRkcmVzcywg
TjEncyBob21lIGFnZW50IA0KPiBzaG91bGQgdHVubmVsDQo+ID4gYW5kIHNlbmQgdGhpcyBw
YWNrZXQgdG8gTjEncyBjYXJlIG9mIGFkZHJlc3MgcmlnaHQ/Lw0KPiA+IA0KPiA+IC9Eb2Vz
IHJmYyAzNzc1IG1lbnRpb24gdGhpcyBzY2VuYXJpbz8gb3IgYW0gSSBtaXNzaW5nIGFueSAN
Cj4gY29uY2VwdCBoZXJlPyAvDQo+IA0KPiBJIHRoaW5rIHJmYzM3NzUgZGVzY3JpYmVzIGJl
aGF2aW91ciBvZiBhbiBNTiB0YWxraW5nIHRvIGEgDQo+IGNvcnJlc3BvbmRlbnQuDQo+ICBU
aGF0ICJjb3JyZXNwb25kZW50IiBjb3VsZCBiZSBlaXRoZXIgSEEgb3IgYSBDTiBvciBhbm90
aGVyIE1OLiAgV2hpY2gNCj4gbWVhbnMgdGhhdCB0aGUgY2FzZSBNTiB0YWxraW5nIFJSIHRv
IGFub3RoZXIgTU4gaGFzIGJlZW4gbG9va2VkIGF0LCBhdA0KPiBsZWFzdCBwZW5jaWwgb24g
cGFwZXIuDQo+IA0KPiBQbGVhc2UgZG8gbm90IGdldCBjb25mdXNlZCBieSB0ZXJtaW5vbG9n
eS4gIE9mdGVuIGl0IGlzIA0KPiB1c2VmdWwgZm9yIHRleHQNCj4gd3JpdGVycyB0byBoYXZl
IGEgc2ltcGxlIHRlcm1pbm9sb2d5IHRoYXQgaXMgZWFzeSB0byBncmFzcC4gIFF1ZXN0aW9u
cw0KPiBnZXQgcXVpY2tseSBhbnN3ZXJlZCBhdCBpbXBsZW1lbnRhdGlvbiBhbmQgdGVzdCB0
aW1lLg0KPiANCj4gQWxleA0KPiANCg0KDQojIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMj
IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMNClRISVMgRU1BSUwg
TUVTU0FHRSBJUyBGT1IgVEhFIFNPTEUgVVNFIE9GIFRIRSBJTlRFTkRFRCBSRUNJUElFTlQo
UykgQU5EIE1BWSBDT05UQUlOIENPTkZJREVOVElBTCBBTkQgUFJJVklMRUdFRCBJTkZPUk1B
VElPTi4gQU5ZIFVOQVVUSE9SSVpFRCBSRVZJRVcsIFVTRSwgRElTQ0xPU1VSRSBPUiBESVNU
UklCVVRJT04gSVMgUFJPSElCSVRFRC4gQkVGT1JFIE9QRU5JTkcgQU5ZIEFUVEFDSE1FTlRT
IFBMRUFTRSBDSEVDSyBGT1IgVklSVVNFUyBBTkQgREVGRUNUUy4gSUYgWU9VIEFSRSBOT1Qg
VEhFIElOVEVOREVEIFJFQ0lQSUVOVCwgUExFQVNFIE5PVElGWSBVUyBJTU1FRElBVEVMWSBC
WSBSRVBMWSBFTUFJTCBBTkQgREVMRVRFIFRIRSBPUklHSU5BTCBNRVNTQUdFLg0KIyMjIyMj
IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMj
IyMjIyMjIyMj


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

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

--===============1740991101==--



From mip6-bounces@ietf.org Thu Aug 25 09:12:03 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E8HWV-0003q5-M3; Thu, 25 Aug 2005 09:12:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1E8HWR-0003pb-2D
	for mip6@megatron.ietf.org; Thu, 25 Aug 2005 09:12:01 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16668
	for <mip6@ietf.org>; Thu, 25 Aug 2005 09:11:57 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E8HWw-0002hp-7e
	for mip6@ietf.org; Thu, 25 Aug 2005 09:12:31 -0400
Received: from il06exr04.mot.com (il06exr04.mot.com [129.188.137.134])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id j7PDMEVF010456;
	Thu, 25 Aug 2005 06:22:14 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by il06exr04.mot.com (8.13.1/8.13.0) with ESMTP id j7PDHwgq019140;
	Thu, 25 Aug 2005 08:17:59 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 7176F865980; Thu, 25 Aug 2005 14:50:21 +0200 (CEST)
Message-ID: <430DBE8D.4010106@motorola.com>
Date: Thu, 25 Aug 2005 14:50:21 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Organization: Motorola Labs, Paris, France
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: "Sameer T." <sameer.t@lgsoftindia.com>
Subject: Re: [Mip6] Mobile node communicating with Mobile node
References: <EC9E4C8E76FEF944B5C0711496A10728029A09F1@APPOLO.lgdomain.com>
In-Reply-To: <EC9E4C8E76FEF944B5C0711496A10728029A09F1@APPOLO.lgdomain.com>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org, 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

Sameer T. wrote:
> Alex, Thanks for your reply,
> 
> I do agree that in rfc 3775 "correspondent" could be either HA or a 
> CN or another MN. And  my exact query is in the third case, when the 
> correspondent is MN.
> 
> 
>>> /        a) home test init message and care of test init
>> 
>> message will be
>> 
>>> sent to N1's care of address or N1's home address.? /
>>> 
>>> /        b) What about Bu message, it also will be sent to N1's 
>>> c/o address or home address?/ /If they are sent to N1's home 
>>> address, N1's home agent
>> 
>> should tunnel
>> 
>>> and send this packet to N1's care of address right?/
>>> 
> 
> 
> What I really wanted to know was, in my example both N1 and N2 are 
> away from home. So when N2 sends Home test init message, as a part of
>  RR, it sends to home address of N1. So Home test init message first 
> goes to N2's home agent (since it is a home test init message),

Yes, first goes to N2's HA, but not because it is a HoTI, it's because
all packets out of an MN go through their HA before RR (the Ho in HoTI
stands for the Home Address of N1 not of N2).  The N2 acts as CN for N1
which acts as MN.

This is my understanding based on protocol description, not on
implementation.  Once implemented it should be easier to understand.

> then it goes to N1's home agent, finally to N1 (thru his care of
> address). Is my understanding correct here?

I guess so.

Alex

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



From mip6-bounces@ietf.org Thu Aug 25 20:28:26 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E8S54-00061J-4d; Thu, 25 Aug 2005 20:28:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1E8S52-00061B-Nl
	for mip6@megatron.ietf.org; Thu, 25 Aug 2005 20:28:24 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA03038
	for <mip6@ietf.org>; Thu, 25 Aug 2005 20:28:23 -0400 (EDT)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E8S5e-0000Vv-57
	for mip6@ietf.org; Thu, 25 Aug 2005 20:29:03 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j7PNtsn05393;
	Thu, 25 Aug 2005 16:55:54 -0700
X-mProtect: <200508252355> Nokia Silicon Valley Messaging Protection
Received: from mvdhcp14192.americas.nokia.com (172.18.141.92,
	claiming to be "[127.0.0.1]")
	by darkstar.iprg.nokia.com smtpd1o3cXK; Thu, 25 Aug 2005 16:55:53 PDT
Message-ID: <430E620E.6030407@iprg.nokia.com>
Date: Thu, 25 Aug 2005 17:27:58 -0700
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
Subject: Re: [Mip6] comments on draft-ietf-mip6-ikev2-ipsec-02.txt
References: <200508021032.j72AWogx011438@givry.rennes.enst-bretagne.fr>
In-Reply-To: <200508021032.j72AWogx011438@givry.rennes.enst-bretagne.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
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

Francis Dupont wrote:
> The last two requirements of section 4.2 are confusing because they
> are not required by this I-D but by RFC 3775. I propose to add
> the references.

actually they are mentioned in RFC 3776. initially they werent
in this draft at all. but people mentioned that it is better
to make the document self-contained wrt requirements. so I had
copied these requirements from RFC 3776. but you are right,
3775 is the right place to mandate this.

> I am still strongly against the first 4.3 requirements. In fact today
> many security gateways don't support protocol (so ports) in traffic selectors
> (because this solves the issue of fragment handling, cf the OPAQUE stuff
> in 2401bis). I.e., fine gain selectors are fine but should be made
> mandatory, so please downgrade to a SHOULD.

changed it to SHOULD

Vijay


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



From mip6-bounces@ietf.org Thu Aug 25 20:49:29 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E8SPR-000050-Qe; Thu, 25 Aug 2005 20:49:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1E8SPP-0008WG-Um
	for mip6@megatron.ietf.org; Thu, 25 Aug 2005 20:49:28 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05093
	for <mip6@ietf.org>; Thu, 25 Aug 2005 20:49:26 -0400 (EDT)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E8SPy-0001Wl-MW
	for mip6@ietf.org; Thu, 25 Aug 2005 20:50:07 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j7Q0Guu20304;
	Thu, 25 Aug 2005 17:16:56 -0700
X-mProtect: <200508260016> Nokia Silicon Valley Messaging Protection
Received: from manisht.iprg.nokia.com (205.226.2.40,
	claiming to be "[205.226.2.40]")
	by darkstar.iprg.nokia.com smtpd4zLLlp; Thu, 25 Aug 2005 17:16:55 PDT
Message-ID: <430E66FB.9090603@iprg.nokia.com>
Date: Thu, 25 Aug 2005 17:48:59 -0700
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
User-Agent: Mozilla Thunderbird 1.0.6-1.4.1 (X11/20050719)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
Subject: Re: [Mip6] comments on draft-ietf-mip6-ikev2-ipsec-02.txt
References: <200508021247.j72ClINf011771@givry.rennes.enst-bretagne.fr>
In-Reply-To: <200508021247.j72ClINf011771@givry.rennes.enst-bretagne.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
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

Francis Dupont wrote:
> 4.3 API already exists, cf draft-sugimoto-mip6-pfkey-migrate-00.txt

true. but I cant add a normative dependency to this draft.

> 6.2: I don't understand why IDi is mandatory: it is not optional at all
> in IKEv2 specs. Proposal: remove the MUST, i.e., change the requirement
> in a fact!

done.

>  BTW, when the home address is used the check against the peer address
> (which is the care-of address) has to be disabled. This is discussed
> in a pki4ipsec document, I propose to reference it in order to explain
> how to deal with the fact the peer address is not the commonly expected one.

can you please suggest some text here?

>  The text about the CREATE_CHILD_SA for RR protection is not clear enough:
> there is always one initiator. Usually it is the MN but it can be the HA
> when a CN which is mobile begins an RR. This must be explained in order
> to avoid "passive" configurations on HAs (note this should only break RR
> from outside, so this is not a critical misconfig).

fixed. the new text

    After the IKE_AUTH exchange completes, the mobile node initiates
    CREATE_CHILD_SA exchanges to negotiate additional security
    associations for protecting Return Routability signaling, Mobile
    Prefix Discovery messages and optionally payload traffic.  The
    CREATE_CHILD_SA exchanges are protected by the security association
    created during the IKE_AUTH exchange.  If a correspondent node that
    is also a mobile node, initiates the return routability exchange,
    then the Home Agent initiates the CREATE_CHILD_SA exchange to
    negotiate security associations for protecting Return Routabilty
    messages.

>  Last paragraph is ambiguous because it applies only when the whole stuff
> is restarted... As in IKEv2 SAs are managed, i.e., IPsec SAs are deleted
> when the IKE_SA goes down, I don't believe it is a real case. Perhaps
> it applies to previous context and in this case the paragraph should be moved?

which paragraph is this? the last paragraph in section 6.2 talks
PKI based authentication.

> 7: we should check but I believe the CERT from the responder/HA is not
> optional with EAP authentication, i.e., preshared secret is an alternative
> to the standard certificate-based mutual authentication, EAP is an option
> of the second. Further text in the I-D seems to say the same thing...
> Perhaps we have to choose between IKEv2 ([4]) and EAP/IKEv2 I-D ([8])?

well, [8] has no status currently and we may have to remove it.
currently I have it as an optional mechanism, with a informational
reference :). I am open to suggestions.

Vijay

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



From mip6-bounces@ietf.org Sat Aug 27 10:43:46 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E91uM-0006A6-CQ; Sat, 27 Aug 2005 10:43:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1E91uK-0006A1-TF
	for mip6@megatron.ietf.org; Sat, 27 Aug 2005 10:43:44 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16716
	for <mip6@ietf.org>; Sat, 27 Aug 2005 10:43:42 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E91vH-00028S-Iu
	for mip6@ietf.org; Sat, 27 Aug 2005 10:44:44 -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 j7REh5F22719; Sat, 27 Aug 2005 16:43:05 +0200
Received: from givry.rennes.enst-bretagne.fr
	(localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id
	j7REh5SH042870; Sat, 27 Aug 2005 16:43:05 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200508271443.j7REh5SH042870@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Vijay Devarapalli <vijayd@iprg.nokia.com>
Subject: Re: [Mip6] comments on draft-ietf-mip6-ikev2-ipsec-02.txt 
In-reply-to: Your message of Thu, 25 Aug 2005 17:48:59 PDT.
	<430E66FB.9090603@iprg.nokia.com> 
Date: Sat, 27 Aug 2005 16:43:05 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
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

 In your previous mail you wrote:

   Francis Dupont wrote:
   > 4.3 API already exists, cf draft-sugimoto-mip6-pfkey-migrate-00.txt
   
   true. but I cant add a normative dependency to this draft.
   
=> an API is always informational so I don't understand the issue
(PS: the 01 version of this I-D is nearly ready).
   
   >  BTW, when the home address is used the check against the peer address
   > (which is the care-of address) has to be disabled. This is discussed
   > in a pki4ipsec document, I propose to reference it in order to explain
   > how to deal with the fact the peer address is not the commonly expected
   > one.
   
   can you please suggest some text here?
   
=> First I quote the pki4ipsec I-D because the issue is a bit complex:

   In addition, implementations MUST be capable of verifying that the
   address contained in the ID is the same as the peer source address,
   contained in the outer most IP header.  If ID is one of the IP
   address types, then implementations MUST perform this verification by
   default.  If this default is enabled, then a mismatch MUST be treated
   as an error and security association setup MUST be aborted.  This
   event SHOULD be auditable.  Implementations MAY provide a
   configuration option to (i.e. local policy configuration can enable)
   skip that verification step, but that option MUST be off by default.
   We include the "option-to-skip-validation" in order to permit better
   interoperability, as today implementations vary greatly in how they
   behave on the topic of verification of source IP.

   If the default for both the verifications above are enabled, then, by
   transitive property, the implementation will also be verifying that
   the peer source IP address matches via a bitwise comparison the
   contents of the iPAddress field in the SubjectAltName extension in
   the certificate.  In addition, implementations MAY allow
   administrators to configure a local policy that explicitly requires
   that the peer source IP address match via a bitwise comparison the
   contents of the iPAddress field in the SubjectAltName extension in
   the certificate.  Implementations SHOULD allow administrators to
   configure a local policy that skips this validation check.

The first part of both is about the cert stuff. IMHO we should simply
reuse the last paragraph of (quoting again the pki4ipsec I-D):

   Implementations MAY use the IP address found in the header of packets
   received from the peer to lookup the policy, but such implementations
   MUST still perform verification of the ID payload.  Although packet
   IP addresses are inherently untrustworthy and must therefore be
   independently verified, it is often useful to use the apparent IP
   address of the peer to locate a general class of policies that will
   be used until the mandatory identity-based policy lookup can be
   performed.

   For instance, if the IP address of the peer is unrecognized, a VPN
   gateway device might load a general "road warrior" policy that
   specifies a particular CA that is trusted to issue certificates which
   contain a valid rfc822Name which can be used by that implementation
   to perform authorization based on access control lists (ACLs) after
   the peer's certificate has been validated.  The rfc822Name can then
   be used to determine the policy that provides specific authorization
   to access resources (such as IP addresses, ports, and so forth).

So if we specialize a bit the text for mobility clients...
The points are:
 - recognized the case as special (i.e., not default)
 - disable the check between the peer address and the ID/cert
 - base the policy on the ID

   >  Last paragraph is ambiguous because it applies only when the whole stuff
   > is restarted... As in IKEv2 SAs are managed, i.e., IPsec SAs are deleted
   > when the IKE_SA goes down, I don't believe it is a real case. Perhaps
   > it applies to previous context and in this case the paragraph
   > should be moved?
   
   which paragraph is this?

=> argh, I can't find it...

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 Aug 29 21:25:11 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E9usB-0001vg-Jm; Mon, 29 Aug 2005 21:25:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1E9us9-0001vT-7j
	for mip6@megatron.ietf.org; Mon, 29 Aug 2005 21:25:09 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28528
	for <mip6@ietf.org>; Mon, 29 Aug 2005 21:25:07 -0400 (EDT)
Received: from av12-2-sn2.hy.skanova.net ([81.228.8.186])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E9utZ-0007BL-OK
	for mip6@ietf.org; Mon, 29 Aug 2005 21:26:39 -0400
Received: by av12-2-sn2.hy.skanova.net (Postfix, from userid 502)
	id D8E1D38083; Tue, 30 Aug 2005 03:24:55 +0200 (CEST)
Received: from smtp4-1-sn2.hy.skanova.net (smtp4-1-sn2.hy.skanova.net
	[81.228.8.92])
	by av12-2-sn2.hy.skanova.net (Postfix) with ESMTP id C68BB38016
	for <mip6@ietf.org>; Tue, 30 Aug 2005 03:24:55 +0200 (CEST)
Received: from shiraz.levkowetz.com (81-224-201-50-no45.tbcn.telia.com
	[81.224.201.50])
	by smtp4-1-sn2.hy.skanova.net (Postfix) with ESMTP id B20C837E44
	for <mip6@ietf.org>; Tue, 30 Aug 2005 03:24:55 +0200 (CEST)
Received: from shiraz.local.levkowetz.com
	([192.168.3.14] helo=81-224-201-50-no45.tbcn.telia.com ident=www-data)
	by shiraz.levkowetz.com with esmtp (Exim 4.52) id 1E9uru-0004mu-Bl
	for mip6@ietf.org; Tue, 30 Aug 2005 03:24:55 +0200
Content-Type: text/plain; charset=utf-8
To: mip6@ietf.org
From: Vijay Devarapalli <tracker-mip6@mip4.org>
Date: Tue, 30 Aug 2005 01:24:52 +0000
MIME-Version: 1.0
Message-Id: <1125365092.91.0.442296024785.issue23@mip4.org>
X-Roundup-Name: Mip6 issue tracker
X-Roundup-Loop: hello
Content-Transfer-Encoding: quoted-printable
X-Helo-Check-Failed: Verification failed for HELO
	81-224-201-50-no45.tbcn.telia.com
X-SA-Exim-Connect-IP: 192.168.3.14
X-SA-Exim-Mail-From: roundup-admin@mip4.org
X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on 
	shiraz.levkowetz.com
X-Spam-Status: No, score=-103.4 required=2.5 tests=ALL_TRUSTED,AWL,BAYES_00,
	USER_IN_WHITELIST,X_HELO_CHECK_FAILED autolearn=ham version=3.0.4
X-SA-Exim-Version: 4.2 (built Thu, 03 Mar 2005 10:44:12 +0100)
X-SA-Exim-Scanned: Yes (on shiraz.levkowetz.com)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Content-Transfer-Encoding: quoted-printable
Subject: [Mip6] [issue23] SPD entries illustration
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Mip6 issue tracker <tracker-mip6@mip4.org>
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


New submission from Vijay Devarapalli <vijayd@iprg.nokia.com>:

This issue was raised by Francis Dupont. In his opinion, the SPD entries
should be depicted using ASN.1 as described in Appendix C. of=20
raft-ietf-ipsec-rfc2401bis-06.txt

for example the following SPD entry=20

            mobile node SPD-S:
              - IF source =3D home_address_1 & destination =3D home_agent_1=
 &
                   proto =3D MH & mh_type =3D BU
                Then use SA SA1

would appear as the following if ASN.1 is used.

SPDEntry =3D {
 iPsecEntry =3D {
  name =3D { passed =3D { rfc822 =3D user_1 }, ... },
  pFPs =3D 0,
  condition =3D {
   localAddr =3D { v6List =3D { ipv6Start =3D ipv6End =3D home_address_1 } =
},
   remoteAddr =3D { v6List =3D { ipv6Start =3D ipv6End =3D home_agent_1 } },
   protocol =3D { oneNext =3D { id =3D MH, nextLayer =3D { start =3D end =
=3D BU } } }
  },
  processing =3D {
    -- use SA1
    ...,
    algorithms =3D { esp =3D { both =3D ...} },
    tunnel =3D none
  }
 }
}

comments are welcome.

----------
category: Technical
draft: draft-ietf-mip6-ikev2-ipsec
messages: 86
nosy: vijay
priority: May fix
status: No discussion
title: SPD entries illustration

_________________________________________________
Mip6 issue tracker <tracker-mip6@mip4.org>
<http://www.mip4.org/issues/tracker/mip6/issue23>
_________________________________________________

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



From mip6-bounces@ietf.org Mon Aug 29 22:12:13 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1E9vbh-0003fq-9Y; Mon, 29 Aug 2005 22:12:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1E9vbe-0003en-Rs
	for mip6@megatron.ietf.org; Mon, 29 Aug 2005 22:12:11 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA00452
	for <mip6@ietf.org>; Mon, 29 Aug 2005 22:12:09 -0400 (EDT)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E9vd4-0008NA-VX
	for mip6@ietf.org; Mon, 29 Aug 2005 22:13:41 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j7U1dTg23399;
	Mon, 29 Aug 2005 18:39:29 -0700
X-mProtect: <200508300139> Nokia Silicon Valley Messaging Protection
Received: from manisht.iprg.nokia.com (205.226.2.40,
	claiming to be "[205.226.2.40]")
	by darkstar.iprg.nokia.com smtpdNZOHPD; Mon, 29 Aug 2005 18:39:28 PDT
Message-ID: <4313C05F.7080208@iprg.nokia.com>
Date: Mon, 29 Aug 2005 19:11:43 -0700
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
User-Agent: Mozilla Thunderbird 1.0.6-1.4.1 (X11/20050719)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
Subject: Re: [Mip6] comments on draft-ietf-mip6-ikev2-ipsec-02.txt
References: <200508271443.j7REh5SH042870@givry.rennes.enst-bretagne.fr>
In-Reply-To: <200508271443.j7REh5SH042870@givry.rennes.enst-bretagne.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
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

Francis Dupont wrote:
>  In your previous mail you wrote:
> 
>    Francis Dupont wrote:
>    > 4.3 API already exists, cf draft-sugimoto-mip6-pfkey-migrate-00.txt
>    
>    true. but I cant add a normative dependency to this draft.
>    
> => an API is always informational so I don't understand the issue
> (PS: the 01 version of this I-D is nearly ready).

you are right. added a reference to it.

>    
>    >  BTW, when the home address is used the check against the peer address
>    > (which is the care-of address) has to be disabled. This is discussed
>    > in a pki4ipsec document, I propose to reference it in order to explain
>    > how to deal with the fact the peer address is not the commonly expected
>    > one.
>    
>    can you please suggest some text here?
>    
> => First I quote the pki4ipsec I-D because the issue is a bit complex:
> 
>    In addition, implementations MUST be capable of verifying that the
>    address contained in the ID is the same as the peer source address,
>    contained in the outer most IP header.  If ID is one of the IP
>    address types, then implementations MUST perform this verification by
>    default.  If this default is enabled, then a mismatch MUST be treated
>    as an error and security association setup MUST be aborted.  This
>    event SHOULD be auditable.  Implementations MAY provide a
>    configuration option to (i.e. local policy configuration can enable)
>    skip that verification step, but that option MUST be off by default.
>    We include the "option-to-skip-validation" in order to permit better
>    interoperability, as today implementations vary greatly in how they
>    behave on the topic of verification of source IP.
> 
>    If the default for both the verifications above are enabled, then, by
>    transitive property, the implementation will also be verifying that
>    the peer source IP address matches via a bitwise comparison the
>    contents of the iPAddress field in the SubjectAltName extension in
>    the certificate.  In addition, implementations MAY allow
>    administrators to configure a local policy that explicitly requires
>    that the peer source IP address match via a bitwise comparison the
>    contents of the iPAddress field in the SubjectAltName extension in
>    the certificate.  Implementations SHOULD allow administrators to
>    configure a local policy that skips this validation check.
> 
> The first part of both is about the cert stuff. IMHO we should simply
> reuse the last paragraph of (quoting again the pki4ipsec I-D):
> 
>    Implementations MAY use the IP address found in the header of packets
>    received from the peer to lookup the policy, but such implementations
>    MUST still perform verification of the ID payload.  Although packet
>    IP addresses are inherently untrustworthy and must therefore be
>    independently verified, it is often useful to use the apparent IP
>    address of the peer to locate a general class of policies that will
>    be used until the mandatory identity-based policy lookup can be
>    performed.
> 
>    For instance, if the IP address of the peer is unrecognized, a VPN
>    gateway device might load a general "road warrior" policy that
>    specifies a particular CA that is trusted to issue certificates which
>    contain a valid rfc822Name which can be used by that implementation
>    to perform authorization based on access control lists (ACLs) after
>    the peer's certificate has been validated.  The rfc822Name can then
>    be used to determine the policy that provides specific authorization
>    to access resources (such as IP addresses, ports, and so forth).
> 
> So if we specialize a bit the text for mobility clients...
> The points are:
>  - recognized the case as special (i.e., not default)
>  - disable the check between the peer address and the ID/cert

how about the following text?

    If the mobile node had used its home address in the IDi field,
    implementations are required to match the source address in the outer
    most IP header with the IP address in the IDi field [9].  This
    verification step, however, should be configurable [9].  With Mobile
    IPv6, this verification step will always fail because the source
    address in the outer most IP header is the careof address and the IP
    address in the IDi field is the home address.  Therefore, this
    verification step should be skipped

>  - base the policy on the ID

we already have some text on this.

    When PKI based authentication is used between the mobile and the Home
    Agent, the identity presented by the mobile node in the IDi payload
    must correspond to the identity in the certificate obtained by the
    Home Agent.  The Home Agent uses the identity presented in the IDi
    payload to lookup the policy and the certificate that corresponds to
    the mobile node.

isn't that sufficient?

Vijay

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



From mip6-bounces@ietf.org Tue Aug 30 10:26:44 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EA74W-0004EP-Ou; Tue, 30 Aug 2005 10:26:44 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EA74U-0004EK-4C
	for mip6@megatron.ietf.org; Tue, 30 Aug 2005 10:26:42 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16093
	for <mip6@ietf.org>; Tue, 30 Aug 2005 10:26:39 -0400 (EDT)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EA75z-0002jA-Js
	for mip6@ietf.org; Tue, 30 Aug 2005 10:28:19 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j7UDrQR31789;
	Tue, 30 Aug 2005 06:53:26 -0700
X-mProtect: <200508301353> Nokia Silicon Valley Messaging Protection
Received: from esdhcp03594.research.nokia.com (172.21.35.94,
	claiming to be "[127.0.0.1]")
	by darkstar.iprg.nokia.com smtpdaZbcpw; Tue, 30 Aug 2005 06:53:24 PDT
Message-ID: <43146C61.3010101@iprg.nokia.com>
Date: Tue, 30 Aug 2005 17:25:37 +0300
From: "Charles E. Perkins" <charliep@iprg.nokia.com>
Organization: Nokia Research Center, Mtn. View
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Mip6 issue tracker <tracker-mip6@mip4.org>
Subject: Re: [Mip6] [issue23] SPD entries illustration
References: <1125365092.91.0.442296024785.issue23@mip4.org>
In-Reply-To: <1125365092.91.0.442296024785.issue23@mip4.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
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


Hello Vijay,

The example given is not a very persuasive argument.
I can easily figure out what the existing example text
is trying to say.  The ASN.1 causes one's eye to immediately
glaze over to avoid the pain.

Why is this a good idea?

Regards,
Charlie P.


Vijay Devarapalli wrote:

>New submission from Vijay Devarapalli <vijayd@iprg.nokia.com>:
>
>This issue was raised by Francis Dupont. In his opinion, the SPD entries
>should be depicted using ASN.1 as described in Appendix C. of 
>raft-ietf-ipsec-rfc2401bis-06.txt
>
>for example the following SPD entry 
>
>            mobile node SPD-S:
>              - IF source = home_address_1 & destination = home_agent_1 &
>                   proto = MH & mh_type = BU
>                Then use SA SA1
>
>would appear as the following if ASN.1 is used.
>
>SPDEntry = {
> iPsecEntry = {
>  name = { passed = { rfc822 = user_1 }, ... },
>  pFPs = 0,
>  condition = {
>   localAddr = { v6List = { ipv6Start = ipv6End = home_address_1 } },
>   remoteAddr = { v6List = { ipv6Start = ipv6End = home_agent_1 } },
>   protocol = { oneNext = { id = MH, nextLayer = { start = end = BU } } }
>  },
>  processing = {
>    -- use SA1
>    ...,
>    algorithms = { esp = { both = ...} },
>    tunnel = none
>  }
> }
>}
>
>comments are welcome.
>
>----------
>category: Technical
>draft: draft-ietf-mip6-ikev2-ipsec
>messages: 86
>nosy: vijay
>priority: May fix
>status: No discussion
>title: SPD entries illustration
>
>_________________________________________________
>Mip6 issue tracker <tracker-mip6@mip4.org>
><http://www.mip4.org/issues/tracker/mip6/issue23>
>_________________________________________________
>
>_______________________________________________
>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 Tue Aug 30 14:29:08 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EAAr6-0005Dc-7g; Tue, 30 Aug 2005 14:29:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EAAr3-0005DU-Ev
	for mip6@megatron.ietf.org; Tue, 30 Aug 2005 14:29:06 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29208
	for <mip6@ietf.org>; Tue, 30 Aug 2005 14:29:03 -0400 (EDT)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EAAsc-00014b-7P
	for mip6@ietf.org; Tue, 30 Aug 2005 14:30:44 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j7UHtp712972;
	Tue, 30 Aug 2005 10:55:51 -0700
X-mProtect: <200508301755> Nokia Silicon Valley Messaging Protection
Received: from manisht.iprg.nokia.com (205.226.2.40,
	claiming to be "[205.226.2.40]")
	by darkstar.iprg.nokia.com smtpdLa5kqG; Tue, 30 Aug 2005 10:55:50 PDT
Message-ID: <4314A537.5030700@iprg.nokia.com>
Date: Tue, 30 Aug 2005 11:28:07 -0700
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
User-Agent: Mozilla Thunderbird 1.0.6-1.4.1 (X11/20050719)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Charles E. Perkins" <charliep@iprg.nokia.com>
Subject: Re: [Mip6] [issue23] SPD entries illustration
References: <1125365092.91.0.442296024785.issue23@mip4.org>
	<43146C61.3010101@iprg.nokia.com>
In-Reply-To: <43146C61.3010101@iprg.nokia.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
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

hi Charlie,

I too prefer the current format. the current format is also
more familiar to MIPv6 implementors.

Francis raised this issue. Francis?

Vijay

Charles E. Perkins wrote:
> 
> Hello Vijay,
> 
> The example given is not a very persuasive argument.
> I can easily figure out what the existing example text
> is trying to say.  The ASN.1 causes one's eye to immediately
> glaze over to avoid the pain.
> 
> Why is this a good idea?
> 
> Regards,
> Charlie P.
> 
> 
> Vijay Devarapalli wrote:
> 
>> New submission from Vijay Devarapalli <vijayd@iprg.nokia.com>:
>>
>> This issue was raised by Francis Dupont. In his opinion, the SPD entries
>> should be depicted using ASN.1 as described in Appendix C. of 
>> raft-ietf-ipsec-rfc2401bis-06.txt
>>
>> for example the following SPD entry
>>            mobile node SPD-S:
>>              - IF source = home_address_1 & destination = home_agent_1 &
>>                   proto = MH & mh_type = BU
>>                Then use SA SA1
>>
>> would appear as the following if ASN.1 is used.
>>
>> SPDEntry = {
>> iPsecEntry = {
>>  name = { passed = { rfc822 = user_1 }, ... },
>>  pFPs = 0,
>>  condition = {
>>   localAddr = { v6List = { ipv6Start = ipv6End = home_address_1 } },
>>   remoteAddr = { v6List = { ipv6Start = ipv6End = home_agent_1 } },
>>   protocol = { oneNext = { id = MH, nextLayer = { start = end = BU } } }
>>  },
>>  processing = {
>>    -- use SA1
>>    ...,
>>    algorithms = { esp = { both = ...} },
>>    tunnel = none
>>  }
>> }
>> }
>>
>> comments are welcome.
>>
>> ----------
>> category: Technical
>> draft: draft-ietf-mip6-ikev2-ipsec
>> messages: 86
>> nosy: vijay
>> priority: May fix
>> status: No discussion
>> title: SPD entries illustration
>>
>> _________________________________________________
>> Mip6 issue tracker <tracker-mip6@mip4.org>
>> <http://www.mip4.org/issues/tracker/mip6/issue23>
>> _________________________________________________
>>
>> _______________________________________________
>> 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 Wed Aug 31 03:31:31 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EAN4F-00033N-5b; Wed, 31 Aug 2005 03:31:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EAN4D-00032B-HQ
	for mip6@megatron.ietf.org; Wed, 31 Aug 2005 03:31:29 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA05707
	for <mip6@ietf.org>; Wed, 31 Aug 2005 03:31:27 -0400 (EDT)
Received: from mail.sfc.wide.ad.jp ([203.178.142.146])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EAN5n-0004el-UM
	for mip6@ietf.org; Wed, 31 Aug 2005 03:33:15 -0400
Received: from [192.168.0.2] (unknown [61.196.102.211])
	by mail.sfc.wide.ad.jp (Postfix) with ESMTP id 40FD14C182
	for <mip6@ietf.org>; Wed, 31 Aug 2005 16:30:44 +0900 (JST)
Date: Wed, 31 Aug 2005 16:30:39 +0900
From: Shinta Sugimoto <shinta@sfc.wide.ad.jp>
To: mip6@ietf.org
Message-Id: <20050831112601.5070.SHINTA@sfc.wide.ad.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.21.03 [ja]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Content-Transfer-Encoding: 7bit
Subject: [Mip6] comments/questions on draft-ieft-mip6-ikev2-ipsec-02.txt
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

Hello,

I read draft-ieft-mip6-ikev2-ipsec-02.txt and had following
comments/questions.  I support this draft and think it's useful.

Technical Comments:

- Basically I agree that removal of dependency on per-interface SPD
  entry is a good thing which can be achieved by having MH type in
  the traffic selector.  But I see concern about interoperability
  issue which may come up when the security policy settings of the
  mobile node and home agent are slightly different.  For instance,
  suppose if the home agent does not support RFC2401bis and sets
  only MH(135) in the protocol field while the mobile node supports
  RFC2401bis and specifies MH type in its selector of the SP entry.
  Obviously such operation will fail.  The mobile node will fail to
  receive IPsec tunneled mobility signals (e.g. BA or CoTI) from its
  peer who is also a mobile node.  This problem was seen in the past
  interop event.  So, I would suggest to add some texts in Section
  4.3 to avoid having interoperability problem.

  o  The home agent and mobile node MUST have equivalent settings of
     security policy in terms of granularity of upper layer protocol
     specified in the traffic selector.

- Section 6.1.2, I found that some of the selector information does
  not contain src addr, dst addr (or both).  Is there any specific
  reason for this ? In addition, I found description of inner src/dst
  addr information as a part of SPD entry but is it needed ?
- Section 6.1.3, similar to above, some of the src/dst address is
  missing in the selector info.
- First paragraph of Section 8 (Dynamic Home Address Configuration):

   The mobile node can dynamically configure a home address by including
   a Configuration Payload in the IKE_AUTH exchange, with a request for
   an address from the home link.  The mobile node should include an
   INTERNAL_IP6_ADDRESS attribute in the CFG_REQUEST Payload.  The
   mobile node MAY also include the INTERNAL_IP6_SUBNET attribute if it
   wants to obtain information about the IPv6 prefixes on the home link.

  IMHO, s/should/SHOULD/ in the second sentence seems reasonable.

- Section 8 (Dynamic Home Address Configuration), this may be outside of
  scope of this draft but I wonder how could the initiator (mobile node)
  starts initial IKE exchanges in dynamic configuration scenario.  In
  normal case (where HoA and HA address is configured beforehand), BU
  would be the triggering packet of the IKE negotiation.  But how about
  in this (dynamic HoA config) case ?  And what would be the content
  of TSi in the IKE_AUTH exchange ?
- Section 9 (Security Considerations), the last sentence says "The Home
  Agent MAY store the assigned home address in the SPD entries created
  for the mobile node." To me, this sounds a bit weird.  I assume that
  the home agent basically manages SPD entries per mobile node.

Editorial Comments:

- I think all the "SPD-I" that appear in the document should be
  replaced with "SPD-S", if I understand the RFC2401bis terminology
  correctly.  No matter which direction is, all the SPD entries that
  we are dealing with in MIPv6 are of secure traffic.
- Use of term "Home Agent" or "home agent" (same applies to mobile node)
  should be consistent throughout the document.


Regards,
Shinta


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



From mip6-bounces@ietf.org Wed Aug 31 03:47:17 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EANJV-0006wj-7M; Wed, 31 Aug 2005 03:47:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EANJT-0006sk-QU
	for mip6@megatron.ietf.org; Wed, 31 Aug 2005 03:47:15 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA06174
	for <mip6@ietf.org>; Wed, 31 Aug 2005 03:47:13 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EANLA-00051z-FV
	for mip6@ietf.org; Wed, 31 Aug 2005 03:49:01 -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 j7V7kQZ13916; Wed, 31 Aug 2005 09:46:27 +0200
Received: from givry.rennes.enst-bretagne.fr
	(localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id
	j7V7kQ1Y059556; Wed, 31 Aug 2005 09:46:26 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200508310746.j7V7kQ1Y059556@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Vijay Devarapalli <vijayd@iprg.nokia.com>
Subject: Re: [Mip6] [issue23] SPD entries illustration 
In-reply-to: Your message of Tue, 30 Aug 2005 11:28:07 PDT.
	<4314A537.5030700@iprg.nokia.com> 
Date: Wed, 31 Aug 2005 09:46:26 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: mip6@ietf.org, "Charles E. Perkins" <charliep@iprg.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

 In your previous mail you wrote:

   I too prefer the current format. the current format is also
   more familiar to MIPv6 implementors.
   
=> the issue is it has to be familiar to IPsec implementors...

   Francis raised this issue. Francis?
   
=> here is an answer I sent:

 In his previous mail Vijay wrote:

   but this is ASN.1 representation of the SPD entry. we dont have to
   illustrate the SPD entries in this format. even rfc2401bis says
   
=> yes, this is not required but as it was done in order to provide
an uniform and clean way to describe concrete SPD entries I can't see
a good reason to not use it.

Thanks

Francis.Dupont@enst-bretagne.fr

PS: BTW I believe that some implementations will really use it, for
instance in order to save pages of documentations.

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



From mip6-bounces@ietf.org Wed Aug 31 03:58:28 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EANUK-0000vn-18; Wed, 31 Aug 2005 03:58:28 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EA4zy-0005ih-RK
	for mip6@megatron.ietf.org; Tue, 30 Aug 2005 08:13:55 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08984
	for <mip6@ietf.org>; Tue, 30 Aug 2005 08:13:53 -0400 (EDT)
Received: from hkueee2.eee.hku.hk ([147.8.180.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EA51V-0007lG-Ug
	for mip6@ietf.org; Tue, 30 Aug 2005 08:15:30 -0400
Received: from se6000 (se6000.eee.hku.hk [147.8.180.36])
	by hkueee2.eee.hku.hk (8.13.4/8.13.4) with ESMTP id j7UCDDrq019523;
	Tue, 30 Aug 2005 20:13:13 +0800 (HKT)
Date: Tue, 30 Aug 2005 20:13:12 +0800 (HKT)
From: Ka-Cheong Leung <kcleung@eee.hku.hk>
X-X-Sender: kcleung@se6000
To: mip6@ietf.org
Subject: [mip6] [CFP]  NASM 2005  (Deadline EXTENDED:  Sep. 14, 2005)
In-Reply-To: <Pine.SOL.4.63.0508262216580.11504@se6000>
Message-ID: <Pine.SOL.4.63.0508302012480.4516@se6000>
References: <Pine.SOL.4.63.0508262216580.11504@se6000>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-HKUEEE-MailScanner-Information: www.eee.hku.hk/intranet/computer/faq/mailscanner.htm
X-HKUEEE-MailScanner: Found to be clean
X-HKUEEE-MailScanner-SpamCheck: not spam, SpamAssassin (score=-2.133,
	required 5, autolearn=not spam, AWL 0.47, BAYES_00 -2.60)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: dbb8771284c7a36189745aa720dc20ab
X-Mailman-Approved-At: Wed, 31 Aug 2005 03:58:26 -0400
Cc: Leung Ka Cheong <kcleung@eee.hku.hk>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: kcleung@ieee.org
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

(We apologize if you receive multiple copies of this CFP.)

Dear colleagues,

Due to numerous requests, the paper submission deadline is now
EXTENDED to:

 			September 14, 2005
 			==================


CALL FOR PAPERS
The First International Workshop on Network Architecture and Service Models
NASM 2005
November 21-23, 2005
Fudan University, Shanghai, China

http://www.elec.qmul.ac.uk/wharf/NASM-2005.htm

Technically Co-Sponsored by:
British Computer Society (BCS)
Institution of Electrical Engineers (IEE)
Queen Mary / Fudan Joint Laboratory in Mobile Networks and Ubiquitous Computing


SCOPE

Network architecture and service model are two key topics of network research
and applications.  With the rapid development of optical and wireless
communications, chips and software, network architectures are changing and new
service models are needed.  Many research and technical challenges are being
addressed by researchers from both industries and academia.  It is viewed that
through international collaboration among several experts in different parts of
the globe, greater research excellence and achievements can be made.


OBJECTIVE

The objective of this workshop is to discuss new approaches and technologies
in the field of next generation networks (NGN), ad hoc mobile networks,
wireless sensor networks, and P2P networks.


TOPICS OF INTERESTS

The main topics of interests include, but not limited to:

*  Network architectures and services
*  Optical and wireless networks
*  Routing and scheduling
*  Application model and QoS
*  Mobile network architecture
*  MAC and QoS MAC in MANET
*  Mobile addressing
*  Mobile routing
*  Mobile applications


PAPER SUBMISSIONS

-  Format:  Submissions should include an abstract of 100 words, 5-7 keywords,
 	    the e-mail address of the corresponding author, and must not
 	    exceed 8 pages (in 2-column format), including tables and figures,
 	    with PDF, Postscript, or MS Word format.

-  Submission:  Please submit your paper directly to the workshop chair or
 		co-chair.
 		E-mail:	xinw@fudan.edu.cn

-  Review:  Contributions will be reviewed by at least three reviewers from
 	    both program committee and external reviewers for relevance and
 	    technical contents on basis of papers.

-  Publication:  Selected accepted papers will be published as special issues
 		 of International Journal of Ad Hoc and Ubiquitous Computing
 		 (IJHAUC).
 		 http://www.inderscience.com/browse/index.php?journalID=145


IMPORTANT DATES

Paper Submission Due:	   September 14, 2005  *** Extended ***
Acceptance Notification:   October 15, 2005
Final Camera-Ready Paper:  October 22, 2005
Author Registration:	   October 22, 2005
Workshop Date:		   November 22, 2005


ORGANIZERS AND COMMITTEE

Honorary Chair

      Prof. Jiangxing Wu, NDSC, China

General Chair

      Prof. CK Toh, Queen Mary University of London, UK

Technical Program Chair

      Prof. Xiangyang Xue, Fudan University, China

TPC Members

      Prof. Victor Li, University of Hong Kong, China
      Prof. Laurie Cuthbert, University of London, UK
      Prof. Hong Shen, Japan Advanced Institute of Science and Technology, Japan
      Prof. Yoshiaki Kakuda, Hiroshima University, Japan
      Prof. Tadanori Mizuno, Shizuoka University, Japan
      Prof. Shuigeng Zhou, Fudan University, China
      Prof. Ke Xu, Tsinghua University, China
      Prof. Hai Jin, Wuhan University, China
      Prof. Jiandong Li, Xidian University, China
      Prof. Zhengbin Li, Peking University, China
      Prof. Y.-H. Choi, Seoul National University, Korea
      Prof. H.-K. Kahng, Korea University, Korea
      Prof. D.-K. Kim, Kyungpook National University, Korea
      Dr. Jiang Du, Queensland University, Australia
      Prof. Lai Xu, Vrije University, Netherlands
      Prof. Jun Zhang, National Chiao Tung University, China
      Prof. Qing'an Zeng, Southeast University, China
      Prof. H-C. Chao, National Dong Hwa University, Taiwan, China
      Prof. J.-C. Chen, National Hsing Hwa University, Taiwan, China
      Prof. Y. S. Chen, National Chung Cheng University, Taiwan, China
      Dr. Russell Hsing, Telcordia Technologies Inc., USA
      Prof. Wei K. Tsai, University of California Irvine, USA
      Prof. Joe Hui, Arizona State University, USA

Local Arrangements Chair

      Prof. Wang Xin, Fudan University, China

Publicity Chair

      Dr. K.-C. Leung, University of Hong Kong, China

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



From mip6-bounces@ietf.org Wed Aug 31 10:02:14 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EATAM-00061x-5p; Wed, 31 Aug 2005 10:02:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EATAL-00061s-1d
	for mip6@megatron.ietf.org; Wed, 31 Aug 2005 10:02:13 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21829
	for <mip6@ietf.org>; Wed, 31 Aug 2005 10:02:10 -0400 (EDT)
From: Basavaraj.Patil@nokia.com
Received: from mgw-ext04.nokia.com ([131.228.20.96])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EATC2-0006lK-QJ
	for mip6@ietf.org; Wed, 31 Aug 2005 10:04:02 -0400
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-ext04.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id
	j7VE0wWu016840 for <mip6@ietf.org>; Wed, 31 Aug 2005 17:01:01 +0300
Received: from daebh101.NOE.Nokia.com ([10.241.35.111]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 31 Aug 2005 17:02:04 +0300
Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by
	daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 31 Aug 2005 09:02:02 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 31 Aug 2005 09:02:04 -0500
Message-ID: <456943D540CFC14A8D7138E64843F8530191EAC7@daebe101.NOE.Nokia.com>
Thread-Topic: I-D announcement: draft-patil-mip6-whyauthdataoption-01.txt
Thread-Index: AcWuNJDx6sTrejHfTlaVaoha/zHkfQ==
To: <mip6@ietf.org>
X-OriginalArrivalTime: 31 Aug 2005 14:02:02.0241 (UTC)
	FILETIME=[8FB42F10:01C5AE34]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Content-Transfer-Encoding: quoted-printable
Subject: [Mip6] I-D announcement: draft-patil-mip6-whyauthdataoption-01.txt
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

I-D ACTION:draft-patil-mip6-whyauthdataoption-01.txt


A New Internet-Draft is available from the on-line Internet-Drafts
directories.


	Title		: Why Authentication Data suboption is needed
for MIP6
	Author(s)	: G. Dommety, B. Patil
	Filename	: draft-patil-mip6-whyauthdataoption-01.txt
	Pages		: 16
	Date		: 2005-9-30
=09
Mobile IPv6 defines a set of messages that enable the mobile node
   (MN) to authenticate and perform registration with its home agent
   (HA).  These authentication signaling messages between the mobile
   node and home agent are secured by an IPsec SA that is established
   between the MN and HA.  The MIP6 Working group ID
   draft-ietf-mip6-auth- protocol-04.txt specifies a mechanism to secure
   the binding update and binding acknowledgement messages using an
   authentication option, similar to authentication option in Mobile
   IPv4, carried within the messages that are exchanged between the MN
   and HA to establish a binding.  This document provides the
   justifications as to why the authentication option mechanism is
   needed for Mobile IPv6 deployment in certain deployment environments.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-patil-mip6-whyauthdataoption-0
1.txt

To remove yourself from the I-D Announcement list, send a message to=20
i-d-announce-request at ietf.org with the word unsubscribe in the body
of the message. =20
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce=20
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the
username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-patil-mip6-whyauthdataoption-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html=20
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


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



From mip6-bounces@ietf.org Wed Aug 31 10:50:29 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EATv3-0003rb-7Y; Wed, 31 Aug 2005 10:50:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EATv1-0003p3-FB
	for mip6@megatron.ietf.org; Wed, 31 Aug 2005 10:50:27 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25268
	for <mip6@ietf.org>; Wed, 31 Aug 2005 10:50:24 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EATwk-0007zR-Tt
	for mip6@ietf.org; Wed, 31 Aug 2005 10:52:17 -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 j7VEnhe16457; Wed, 31 Aug 2005 16:49:43 +0200
Received: from givry.rennes.enst-bretagne.fr
	(localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id
	j7VEnhxb061164; Wed, 31 Aug 2005 16:49:43 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200508311449.j7VEnhxb061164@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Shinta Sugimoto <shinta@sfc.wide.ad.jp>
Subject: Re: [Mip6] comments/questions on draft-ieft-mip6-ikev2-ipsec-02.txt 
In-reply-to: Your message of Wed, 31 Aug 2005 16:30:39 +0900.
	<20050831112601.5070.SHINTA@sfc.wide.ad.jp> 
Date: Wed, 31 Aug 2005 16:49:43 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
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

 In your previous mail you wrote:

     o  The home agent and mobile node MUST have equivalent settings of
        security policy in terms of granularity of upper layer protocol
        specified in the traffic selector.
   
=> there was a long discussion about SPD mismatch between IKE peers
in the IPsec mailing list. It seems the TS exchange helps to detect
this kind of problems but IMHO even it should be common sense we can
repeat the policies at each side must match.
(PS: TSs are not enough, for instance they don't always show if a
SA pair can be shared... IMHO their indications are mainly negative,
and of course they never repair misconfigs).

   - Section 6.1.2, I found that some of the selector information does
     not contain src addr, dst addr (or both).  Is there any specific
     reason for this ? In addition, I found description of inner src/dst
     addr information as a part of SPD entry but is it needed ?

=> the inner addresses are part of the selectors (if the abstract
syntax for SPD entries was used, this kind of questions would be
avoided).

   - Section 8 (Dynamic Home Address Configuration), this may be outside of
     scope of this draft but I wonder how could the initiator (mobile node)
     starts initial IKE exchanges in dynamic configuration scenario.  In
     normal case (where HoA and HA address is configured beforehand), BU
     would be the triggering packet of the IKE negotiation.  But how about
     in this (dynamic HoA config) case ?  And what would be the content
     of TSi in the IKE_AUTH exchange ?

=> I believe the answer is in the IKEv2 specs (at least I am sure for
the TSi!) so the HoA before the assignment is ::? Of course the BU
should not be cached...
If someone using internal address config with IKE has more details?

   - Section 9 (Security Considerations), the last sentence says "The Home
     Agent MAY store the assigned home address in the SPD entries created
     for the mobile node." To me, this sounds a bit weird.  I assume that
     the home agent basically manages SPD entries per mobile node.
   
=> I am afraid this is just a consequence of dynamic home address
assignments and in fact the issue is more complex because authorization
(not only policies) must be updated according to assignments.

BTW when a mobile node returns to home, the home agent (i.e., its
MIPv6 code) has to delete/disable some corresponding SPD entries,
and (worse) it has to readd/enable them when the mobile node is
detected as in visit. How to manage this when the MIPv6 code crashes,
the home agent reboots, etc, is still an open question in SHISA
(the KAME MIPv6 code)...

   Editorial Comments:
   
   - Use of term "Home Agent" or "home agent" (same applies to mobile node)
     should be consistent throughout the document.
   
=> I've already signaled this point (:-).

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 Aug 31 11:08:55 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EAUCt-0000BI-IJ; Wed, 31 Aug 2005 11:08:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EAUCr-0000BD-Jy
	for mip6@megatron.ietf.org; Wed, 31 Aug 2005 11:08:53 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25807
	for <mip6@ietf.org>; Wed, 31 Aug 2005 11:08:50 -0400 (EDT)
From: jouni.korhonen@teliasonera.com
Received: from floor.dave.sonera.fi ([131.177.130.22])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EAUEa-0008Mn-HF
	for mip6@ietf.org; Wed, 31 Aug 2005 11:10:43 -0400
Received: from floor.dave.sonera.fi (localhost [127.0.0.1]) by
	floor.dave.sonera.fi (Sendmail) with ESMTP id j7VF8Vb9001222
	for <mip6@ietf.org>; Wed, 31 Aug 2005 18:08:31 +0300 (EEST)
Received: from FITMS201MB.tcad.telia.se (fitms201cb.tcad.telia.se
	[131.177.121.204]) by floor.dave.sonera.fi (Sendmail) with
	ESMTP id j7VF8TBm001206 for <mip6@ietf.org>;
	Wed, 31 Aug 2005 18:08:31 +0300 (EEST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6617.27
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 31 Aug 2005 18:08:15 +0300
Message-ID: <07B14A720C46C344AC96AAA64F5D6A31014918AE@FITMS201MB.tcad.telia.se>
Thread-Topic: A question regarding
	draft-devarapalli-mip4-mobike-connectivity-00.txt
Thread-Index: AcWpanS/lBEfYJspT4qmhd0WCzPcSgEzVKmw
To: <mip6@ietf.org>, <vijayd@iprg.nokia.com>
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Content-Transfer-Encoding: quoted-printable
Cc: 
Subject: [Mip6] A question regarding
	draft-devarapalli-mip4-mobike-connectivity-00.txt
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

Hi,

There was this MIP4 draft
(draft-devarapalli-mip4-mobike-connectivity-00)
proposing combining MOBIKE and MIP4 in a pretty nice way. Common
understanding is so far  seems to be that there shouldn't be anything
strictly MIP4 specific in this solution. Wouldn't it be worth thinking
of a MIP6 version of this proposed solution as well? Also, IMHO, it
could
be worth thinking how to make use of general IKEv2 capabilities that=20
could come along with (possibly) tightly couple or colocated HA and
IKEv2
capable VPN GW.
=20
>From a telco (3GPP-WLAN interworking.. and maybe 3GPP2-WLAN interworking
as well) perspective MOBIKE with MIP6 could actually provide one
solution
for migration in heterogeneous access network. I was thinking of the
case,
where the cellular using MIP6 would be considered as the trusted network
and the other accesses (e.g. WLANs) as untrusted. There MOBIKE could be
used to provide access also in untrusted IPv4 access networks.

Any comments?

Cheers,
	Jouni

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



From mip6-bounces@ietf.org Wed Aug 31 12:34:27 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EAVXf-00087g-CG; Wed, 31 Aug 2005 12:34:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EAVXd-000870-Nx
	for mip6@megatron.ietf.org; Wed, 31 Aug 2005 12:34:25 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29509
	for <mip6@ietf.org>; Wed, 31 Aug 2005 12:34:20 -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.43) id 1EAVZM-0002F4-Ny
	for mip6@ietf.org; Wed, 31 Aug 2005 12:36:14 -0400
Message-ID: <074601c5ae49$ccc2eee0$196115ac@dcml.docomolabsusa.com>
From: "James Kempf" <Kempf@docomolabs-usa.com>
To: "Shinta Sugimoto" <shinta@sfc.wide.ad.jp>, <mip6@ietf.org>
References: <20050831112601.5070.SHINTA@sfc.wide.ad.jp>
Subject: Re: [Mip6] comments/questions on draft-ieft-mip6-ikev2-ipsec-02.txt
Date: Wed, 31 Aug 2005 09:34:04 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Content-Transfer-Encoding: 7bit
Cc: 
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


-----> - Section 8 (Dynamic Home Address Configuration), this may be outside 
of
>  scope of this draft but I wonder how could the initiator (mobile node)
>  starts initial IKE exchanges in dynamic configuration scenario.  In
>  normal case (where HoA and HA address is configured beforehand), BU
>  would be the triggering packet of the IKE negotiation.  But how about
>  in this (dynamic HoA config) case ?  And what would be the content
>  of TSi in the IKE_AUTH exchange ?

draft-ietf-mip6-bootstrapping-split-00.txt discusses this somewhat. Perhaps 
more detail is necessary.

            jak



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



From mip6-bounces@ietf.org Wed Aug 31 18:45:37 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EAbKr-0005Da-30; Wed, 31 Aug 2005 18:45:37 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EAbKq-0005DV-42
	for mip6@megatron.ietf.org; Wed, 31 Aug 2005 18:45:36 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA22651
	for <mip6@ietf.org>; Wed, 31 Aug 2005 18:45:32 -0400 (EDT)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EAbMf-0005Fl-Dw
	for mip6@ietf.org; Wed, 31 Aug 2005 18:47:29 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j7VMCpN09962;
	Wed, 31 Aug 2005 15:12:51 -0700
X-mProtect: <200508312212> Nokia Silicon Valley Messaging Protection
Received: from mvdhcp14192.americas.nokia.com (172.18.141.92,
	claiming to be "[127.0.0.1]")
	by darkstar.iprg.nokia.com smtpdtr0TXh; Wed, 31 Aug 2005 15:12:49 PDT
Message-ID: <431632F5.2030601@iprg.nokia.com>
Date: Wed, 31 Aug 2005 15:45:09 -0700
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Shinta Sugimoto <shinta@sfc.wide.ad.jp>
Subject: Re: [Mip6] comments/questions on draft-ieft-mip6-ikev2-ipsec-02.txt
References: <20050831112601.5070.SHINTA@sfc.wide.ad.jp>
In-Reply-To: <20050831112601.5070.SHINTA@sfc.wide.ad.jp>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2086112c730e13d5955355df27e3074b
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

Shinta Sugimoto wrote:
> Hello,
> 
> I read draft-ieft-mip6-ikev2-ipsec-02.txt and had following
> comments/questions.  I support this draft and think it's useful.
> 
> Technical Comments:
> 
> - Basically I agree that removal of dependency on per-interface SPD
>   entry is a good thing which can be achieved by having MH type in
>   the traffic selector.  But I see concern about interoperability
>   issue which may come up when the security policy settings of the
>   mobile node and home agent are slightly different.  For instance,
>   suppose if the home agent does not support RFC2401bis and sets
>   only MH(135) in the protocol field while the mobile node supports
>   RFC2401bis and specifies MH type in its selector of the SP entry.
>   Obviously such operation will fail.  The mobile node will fail to
>   receive IPsec tunneled mobility signals (e.g. BA or CoTI) from its
>   peer who is also a mobile node.  This problem was seen in the past
>   interop event.  So, I would suggest to add some texts in Section
>   4.3 to avoid having interoperability problem.

I dont have anything to add to what Francis said. we can't do
anything about this.

>   o  The home agent and mobile node MUST have equivalent settings of
>      security policy in terms of granularity of upper layer protocol
>      specified in the traffic selector.

this sounds obvious, right?

> - Section 6.1.2, I found that some of the selector information does
>   not contain src addr, dst addr (or both).  Is there any specific
>   reason for this ? 

if they are exlcuded, it means "any".

In addition, I found description of inner src/dst
>   addr information as a part of SPD entry but is it needed ?

I think so. the SPD entries say create tunnel mode SAs. but we
need to specify which address to use for the inner src, outer src,
inner dst, and outer dst. right?

> - First paragraph of Section 8 (Dynamic Home Address Configuration):
> 
>    The mobile node can dynamically configure a home address by including
>    a Configuration Payload in the IKE_AUTH exchange, with a request for
>    an address from the home link.  The mobile node should include an
>    INTERNAL_IP6_ADDRESS attribute in the CFG_REQUEST Payload.  The
>    mobile node MAY also include the INTERNAL_IP6_SUBNET attribute if it
>    wants to obtain information about the IPv6 prefixes on the home link.
> 
>   IMHO, s/should/SHOULD/ in the second sentence seems reasonable.

why? the whole section is optional. one of the requirements in
Section 4.1 says

    o  The Home Agent and the mobile node MAY support remote
       configuration of home address as described in Section 8.

if the MN wants to use this mechanism to configure a HoA, then its
got to include the INTERNAL_IP6_ADDRESS attribute in the CFG_REQUEST 
payload. thats why the lower case 'should'.

> - Section 8 (Dynamic Home Address Configuration), this may be outside of
>   scope of this draft but I wonder how could the initiator (mobile node)
>   starts initial IKE exchanges in dynamic configuration scenario.  In
>   normal case (where HoA and HA address is configured beforehand), BU
>   would be the triggering packet of the IKE negotiation.  But how about
>   in this (dynamic HoA config) case ?

good question. I dont have a good answer. starting up the mip6
daeomn? the lack of a HoA? could be anything.

   And what would be the content
>   of TSi in the IKE_AUTH exchange ?

the same as TSi in a regular IKEv2 exchange used with a
configuration payload. nothing MIP6 specific.

> - Section 9 (Security Considerations), the last sentence says "The Home
>   Agent MAY store the assigned home address in the SPD entries created
>   for the mobile node." To me, this sounds a bit weird.  I assume that
>   the home agent basically manages SPD entries per mobile node.

you are right. you may not necessarily have an SPD entry per
mobile node. the idea is that the MN requests and gets a HoA
assigned. later on it tries to re-use the same HoA and creates
new security associations. the HA must check if the MN
(identified by some kind of identity, NAI, FQDN, etc) is
allowed to use the HoA. you could store the state somewhere
else instead of the SPD entries to achieve the same.


> Editorial Comments:
> 
> - I think all the "SPD-I" that appear in the document should be
>   replaced with "SPD-S", if I understand the RFC2401bis terminology
>   correctly.  No matter which direction is, all the SPD entries that
>   we are dealing with in MIPv6 are of secure traffic.

I am not sure about this. lets say a MN sends an unprotected
BU. the Home Agent receives this. since there is no IPsec
protection on this, it will hit the SPD-I. what should the
HA do with this packet. silently drop it or trigger IKEv2
negotiation? if silently drop, then what you say is true.
if trigger IKEv2 negotiation then don't you need something
like the following?

         home agent SPD-I:
           - IF destination = home_agent_1 & proto = MH & mh_type = BU
             Then use SA ESP transport mode
                             IDr = user_1, IDi = home_agent_1,
                             TSr = home_address_1

> - Use of term "Home Agent" or "home agent" (same applies to mobile node)
>   should be consistent throughout the document.

I have tried to use "Home Agent" and "mobile node" throughout.
will fix wherever needed.

Vijay


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



From mip6-bounces@ietf.org Wed Aug 31 22:26:10 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EAemI-0003D8-Pz; Wed, 31 Aug 2005 22:26:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EAemG-0003CZ-U4
	for mip6@megatron.ietf.org; Wed, 31 Aug 2005 22:26:09 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA03189
	for <mip6@ietf.org>; Wed, 31 Aug 2005 22:26:06 -0400 (EDT)
Received: from mail.sfc.wide.ad.jp ([203.178.142.146])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EAeo6-0003GF-2z
	for mip6@ietf.org; Wed, 31 Aug 2005 22:28:04 -0400
Received: from [192.168.0.2] (unknown [61.196.102.211])
	by mail.sfc.wide.ad.jp (Postfix) with ESMTP id 4F2274C828;
	Thu,  1 Sep 2005 11:25:36 +0900 (JST)
Date: Thu, 01 Sep 2005 11:25:31 +0900
From: Shinta Sugimoto <shinta@sfc.wide.ad.jp>
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
Subject: Re: [Mip6] comments/questions on draft-ieft-mip6-ikev2-ipsec-02.txt 
In-Reply-To: <200508311449.j7VEnhxb061164@givry.rennes.enst-bretagne.fr>
References: <20050831112601.5070.SHINTA@sfc.wide.ad.jp>
	<200508311449.j7VEnhxb061164@givry.rennes.enst-bretagne.fr>
Message-Id: <20050901100731.5079.SHINTA@sfc.wide.ad.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.21.03 [ja]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86
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

Hello Francis,

On Wed, 31 Aug 2005 16:49:43 +0200
Francis Dupont <Francis.Dupont@enst-bretagne.fr> wrote:

>  In your previous mail you wrote:
> 
>      o  The home agent and mobile node MUST have equivalent settings of
>         security policy in terms of granularity of upper layer protocol
>         specified in the traffic selector.
>    
> => there was a long discussion about SPD mismatch between IKE peers
> in the IPsec mailing list. It seems the TS exchange helps to detect
> this kind of problems but IMHO even it should be common sense we can
> repeat the policies at each side must match.
> (PS: TSs are not enough, for instance they don't always show if a
> SA pair can be shared... IMHO their indications are mainly negative,
> and of course they never repair misconfigs).

OK. TS negotiation seems to be (to some extent) helpful to detect the
mismatch of security policy between the peers.

>    - Section 6.1.2, I found that some of the selector information does
>      not contain src addr, dst addr (or both).  Is there any specific
>      reason for this ? In addition, I found description of inner src/dst
>      addr information as a part of SPD entry but is it needed ?
> 
> => the inner addresses are part of the selectors (if the abstract
> syntax for SPD entries was used, this kind of questions would be
> avoided).

Ahh, yes, inner address is certainly part of traffic selector. So
why not illustrate the SPD entry like:

        mobile node SPD-S:
          - IF source = home_address_1 & proto = MH & mh_type = HoTi
            Then use SA ESP tunnel mode
                            IDi = user_1,
                            outer src addr = coa,
                            outer dst addr = home_agent_1

rather than

        mobile node SPD-S:
          - IF proto = MH & mh_type = HoTi
            Then use SA ESP tunnel mode
                            IDi = user_1,
                            outer src addr = coa,
                            outer dst addr = home_agent_1,
                            inner src addr = home_address_1

?

>    - Section 8 (Dynamic Home Address Configuration), this may be outside of
>      scope of this draft but I wonder how could the initiator (mobile node)
>      starts initial IKE exchanges in dynamic configuration scenario.  In
>      normal case (where HoA and HA address is configured beforehand), BU
>      would be the triggering packet of the IKE negotiation.  But how about
>      in this (dynamic HoA config) case ?  And what would be the content
>      of TSi in the IKE_AUTH exchange ?
> 
> => I believe the answer is in the IKEv2 specs (at least I am sure for
> the TSi!) so the HoA before the assignment is ::? Of course the BU
> should not be cached...
> If someone using internal address config with IKE has more details?

(pls correct me if I am wrong) I checked the Section 2.19 of IKEv2 spec
and I believe the procedure described in the section applies to MIPv6
dynamic config scenario.  IRAC (MN in this case) consults IRAS (HA)
for the inner address (HoA).  According to the examples given in Section
2.19, it seems that you are right.  TSi included in the message from
initiator to responder just contains :: in MIPv6 case.

>    - Section 9 (Security Considerations), the last sentence says "The Home
>      Agent MAY store the assigned home address in the SPD entries created
>      for the mobile node." To me, this sounds a bit weird.  I assume that
>      the home agent basically manages SPD entries per mobile node.
>    
> => I am afraid this is just a consequence of dynamic home address
> assignments and in fact the issue is more complex because authorization
> (not only policies) must be updated according to assignments.

Right. If dynamic home address assignment is performed, I believe SPD
entries should also be updated dynamically.

> 
> BTW when a mobile node returns to home, the home agent (i.e., its
> MIPv6 code) has to delete/disable some corresponding SPD entries,
> and (worse) it has to readd/enable them when the mobile node is
> detected as in visit. How to manage this when the MIPv6 code crashes,
> the home agent reboots, etc, is still an open question in SHISA
> (the KAME MIPv6 code)...

Yes, as mentioned in the draft, the tunnel SPD entries should be
torn down (or deleted).  How to do this is an implementation issue.


Regards,
Shinta


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



From mip6-bounces@ietf.org Wed Aug 31 23:15:29 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EAfY1-0007ag-1K; Wed, 31 Aug 2005 23:15:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EAfXz-0007Zj-OK
	for mip6@megatron.ietf.org; Wed, 31 Aug 2005 23:15:27 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA04853
	for <mip6@ietf.org>; Wed, 31 Aug 2005 23:15:24 -0400 (EDT)
Received: from mail.sfc.wide.ad.jp ([203.178.142.146])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EAfZo-0004dV-OE
	for mip6@ietf.org; Wed, 31 Aug 2005 23:17:23 -0400
Received: from [192.168.0.2] (unknown [61.196.102.211])
	by mail.sfc.wide.ad.jp (Postfix) with ESMTP id 772F64CBC9;
	Thu,  1 Sep 2005 12:15:09 +0900 (JST)
Date: Thu, 01 Sep 2005 12:15:04 +0900
From: Shinta Sugimoto <shinta@sfc.wide.ad.jp>
To: Vijay Devarapalli <vijayd@iprg.nokia.com>
Subject: Re: [Mip6] comments/questions on draft-ieft-mip6-ikev2-ipsec-02.txt
In-Reply-To: <431632F5.2030601@iprg.nokia.com>
References: <20050831112601.5070.SHINTA@sfc.wide.ad.jp>
	<431632F5.2030601@iprg.nokia.com>
Message-Id: <20050901112538.507C.SHINTA@sfc.wide.ad.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.21.03 [ja]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0770535483960d190d4a0d020e7060bd
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

Hello Vijay,

On Wed, 31 Aug 2005 15:45:09 -0700
Vijay Devarapalli <vijayd@iprg.nokia.com> wrote:

> Shinta Sugimoto wrote:
> > Hello,
> > 
> > I read draft-ieft-mip6-ikev2-ipsec-02.txt and had following
> > comments/questions.  I support this draft and think it's useful.
> > 
> > Technical Comments:
> > 
> > - Basically I agree that removal of dependency on per-interface SPD
> >   entry is a good thing which can be achieved by having MH type in
> >   the traffic selector.  But I see concern about interoperability
> >   issue which may come up when the security policy settings of the
> >   mobile node and home agent are slightly different.  For instance,
> >   suppose if the home agent does not support RFC2401bis and sets
> >   only MH(135) in the protocol field while the mobile node supports
> >   RFC2401bis and specifies MH type in its selector of the SP entry.
> >   Obviously such operation will fail.  The mobile node will fail to
> >   receive IPsec tunneled mobility signals (e.g. BA or CoTI) from its
> >   peer who is also a mobile node.  This problem was seen in the past
> >   interop event.  So, I would suggest to add some texts in Section
> >   4.3 to avoid having interoperability problem.
> 
> I dont have anything to add to what Francis said. we can't do
> anything about this.
> 
> >   o  The home agent and mobile node MUST have equivalent settings of
> >      security policy in terms of granularity of upper layer protocol
> >      specified in the traffic selector.
> 
> this sounds obvious, right?

Yes, but I am sure there will be an interoperability issue comes up.
IMHO, any effort which may help to avoid having miscofig should be made. 

> > - Section 6.1.2, I found that some of the selector information does
> >   not contain src addr, dst addr (or both).  Is there any specific
> >   reason for this ? 
> 
> if they are exlcuded, it means "any".

why any? home_address_1 is already specified as an inner address.
I believe home_address_1 should be given in the source/destination of
the selector information.

> In addition, I found description of inner src/dst
> >   addr information as a part of SPD entry but is it needed ?
> 
> I think so. the SPD entries say create tunnel mode SAs. but we
> need to specify which address to use for the inner src, outer src,
> inner dst, and outer dst. right?

Yes.

Sorry, my question may have been unclear. IMHO, inner src/dst is needed
as a part of SPD entry as a selector.  To me, the illustration was
a bit confusing because the inner src/dst was given as if they were
part of SA entry.

> > - First paragraph of Section 8 (Dynamic Home Address Configuration):
> > 
> >    The mobile node can dynamically configure a home address by including
> >    a Configuration Payload in the IKE_AUTH exchange, with a request for
> >    an address from the home link.  The mobile node should include an
> >    INTERNAL_IP6_ADDRESS attribute in the CFG_REQUEST Payload.  The
> >    mobile node MAY also include the INTERNAL_IP6_SUBNET attribute if it
> >    wants to obtain information about the IPv6 prefixes on the home link.
> > 
> >   IMHO, s/should/SHOULD/ in the second sentence seems reasonable.
> 
> why? the whole section is optional. one of the requirements in
> Section 4.1 says
> 
>     o  The Home Agent and the mobile node MAY support remote
>        configuration of home address as described in Section 8.
> 
> if the MN wants to use this mechanism to configure a HoA, then its
> got to include the INTERNAL_IP6_ADDRESS attribute in the CFG_REQUEST 
> payload. thats why the lower case 'should'.

OK, I see.

> > - Section 8 (Dynamic Home Address Configuration), this may be outside of
> >   scope of this draft but I wonder how could the initiator (mobile node)
> >   starts initial IKE exchanges in dynamic configuration scenario.  In
> >   normal case (where HoA and HA address is configured beforehand), BU
> >   would be the triggering packet of the IKE negotiation.  But how about
> >   in this (dynamic HoA config) case ?
> 
> good question. I dont have a good answer. starting up the mip6
> daeomn? the lack of a HoA? could be anything.
> 
>    And what would be the content
> >   of TSi in the IKE_AUTH exchange ?
> 
> the same as TSi in a regular IKEv2 exchange used with a
> configuration payload. nothing MIP6 specific.

I see.  It seems that this is exactly the case which is presented
in IKEv2 spec where IRAS procures inner address for IRAC.
IRAS=HA, IRAC=MN, inner address=HoA, in MIPv6 case.

> > - Section 9 (Security Considerations), the last sentence says "The Home
> >   Agent MAY store the assigned home address in the SPD entries created
> >   for the mobile node." To me, this sounds a bit weird.  I assume that
> >   the home agent basically manages SPD entries per mobile node.
> 
> you are right. you may not necessarily have an SPD entry per
> mobile node. the idea is that the MN requests and gets a HoA
> assigned. later on it tries to re-use the same HoA and creates
> new security associations. the HA must check if the MN
> (identified by some kind of identity, NAI, FQDN, etc) is
> allowed to use the HoA. you could store the state somewhere
> else instead of the SPD entries to achieve the same.

OK, understood.

> > Editorial Comments:
> > 
> > - I think all the "SPD-I" that appear in the document should be
> >   replaced with "SPD-S", if I understand the RFC2401bis terminology
> >   correctly.  No matter which direction is, all the SPD entries that
> >   we are dealing with in MIPv6 are of secure traffic.
> 
> I am not sure about this. lets say a MN sends an unprotected
> BU. the Home Agent receives this. since there is no IPsec
> protection on this, it will hit the SPD-I. what should the
> HA do with this packet. silently drop it or trigger IKEv2
> negotiation? if silently drop, then what you say is true.
> if trigger IKEv2 negotiation then don't you need something
> like the following?
> 
>          home agent SPD-I:
>            - IF destination = home_agent_1 & proto = MH & mh_type = BU
>              Then use SA ESP transport mode
>                              IDr = user_1, IDi = home_agent_1,
>                              TSr = home_address_1

Mmm, it seems that we have different understanding on SPD-I,O,S.
If I understand 2401bis correctly, the distinctions of SPD-I,O,S
entries are dependent on processing info of the security policy
(DISCARD, BYPASS, PROTECT) entry.  SPD-S entry is applied to the traffic
which is expected to be protected by IPsec.  SPD-I,O entry is
applied to the traffic which is expected to be bypassed/discarded.
"I" for inbound, "O" for outbound traffic.

In your example above, "Then use SA ESP transport mode" means PROTECT,
so, I believe the SPD entry is categorized as SPD-S.

Regards,
Shinta


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



