Re: [Mobopts] Re: [Mip6] [Fwd: FW:resubmit draft-irtf-mobopts-locat ion-privacy-ps-00.txtwith revised boilerplate]
Wassim Haddad <whaddad@tcs.hut.fi> Wed, 03 August 2005 09:18 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E0FOT-0001gG-GQ; Wed, 03 Aug 2005 05:18:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E0FOQ-0001bY-Py for mobopts@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 FAA27388 for <mobopts@irtf.org>; Wed, 3 Aug 2005 05:18:28 -0400 (EDT)
Received: from neon.tcs.hut.fi ([130.233.215.20]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E0Fv4-0005W8-GZ for mobopts@irtf.org; Wed, 03 Aug 2005 05:52:16 -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, 03 Aug 2005 12:18:20 +0300
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, Rajeev Koodli <rajeev@iprg.nokia.com>, mobopts@irtf.org
X-BeenThere: mobopts@irtf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IP Mobility Optimizations <mobopts.irtf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mobopts>, <mailto:mobopts-request@irtf.org?subject=unsubscribe>
List-Post: <mailto:mobopts@irtf.org>
List-Help: <mailto:mobopts-request@irtf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mobopts>, <mailto:mobopts-request@irtf.org?subject=subscribe>
Sender: mobopts-bounces@irtf.org
Errors-To: mobopts-bounces@irtf.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. > >>>>> > >>>>> > >>>>> > >>>>> > > > > _______________________________________________ Mobopts mailing list Mobopts@irtf.org https://www1.ietf.org/mailman/listinfo/mobopts