Re: [Mobopts] Fw: New Version Notification for draft-irtf-mobopts-location-privacy-solutions-07

"Rajeev Koodli" <rajeev.koodli@gmail.com> Thu, 06 March 2008 02:24 UTC

Return-Path: <mobopts-bounces@ietf.org>
X-Original-To: ietfarch-mobopts-archive@core3.amsl.com
Delivered-To: ietfarch-mobopts-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0D6C228C344; Wed, 5 Mar 2008 18:24:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.037
X-Spam-Level:
X-Spam-Status: No, score=-99.037 tagged_above=-999 required=5 tests=[AWL=-0.399, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, HTML_MESSAGE=1, RDNS_NONE=0.1, SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RIvPra1WcKb8; Wed, 5 Mar 2008 18:24:34 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 03F213A6C3C; Wed, 5 Mar 2008 18:24:34 -0800 (PST)
X-Original-To: mobopts@core3.amsl.com
Delivered-To: mobopts@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D45473A6C0F for <mobopts@core3.amsl.com>; Wed, 5 Mar 2008 18:24:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fnwWw4PT864h for <mobopts@core3.amsl.com>; Wed, 5 Mar 2008 18:24:31 -0800 (PST)
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.174]) by core3.amsl.com (Postfix) with ESMTP id DF58F28C693 for <mobopts@irtf.org>; Wed, 5 Mar 2008 18:24:26 -0800 (PST)
Received: by wf-out-1314.google.com with SMTP id 25so2039478wfa.7 for <mobopts@irtf.org>; Wed, 05 Mar 2008 18:24:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=gOl1A4rfu5UlkTOTRUG6tOR/CFA8R57TZ41a5t9titw=; b=SqwsrVRZxsYtsDDRsCpdEMfKsELpKbphjpYLcZys25wDYYHGvJjIejH6BTNS1okavrxRztBYPoS+tK5qbWZo63VbawPJHg8BAVTJ4SxVsTdYUzQHfGyhxgv/U4g9ExabNNrPy8VeqdS50wLQSE3ovU2gZAutAq9wO28XNGmFniA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=VdZaHrkIjsztXb38yeDO7T1QcNJ/QsX+ft4otSiQXL33FMoMX1qZBlN1UkKR704SGqxT18QCAVWvnPG+IAcCenKwvK5DbIEBgzDn/A7HtLYDCRL4P5w3h4XC3QRCpMf8Vi4RE8v5hgYDk3bJemrDhC1FM1IbMzH4/l3id01Z9g4=
Received: by 10.143.163.10 with SMTP id q10mr1063532wfo.141.1204770256902; Wed, 05 Mar 2008 18:24:16 -0800 (PST)
Received: by 10.142.47.18 with HTTP; Wed, 5 Mar 2008 18:24:16 -0800 (PST)
Message-ID: <3d57679a0803051824u1d2a357eof98036112e77f279@mail.gmail.com>
Date: Wed, 5 Mar 2008 18:24:16 -0800
From: "Rajeev Koodli" <rajeev.koodli@gmail.com>
To: mobopts@irtf.org
In-Reply-To: <00e701c877c6$43f886d0$3589a8c0@precision5570>
MIME-Version: 1.0
References: <00e701c877c6$43f886d0$3589a8c0@precision5570>
Subject: Re: [Mobopts] Fw: New Version Notification for draft-irtf-mobopts-location-privacy-solutions-07
X-BeenThere: mobopts@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobility Optimizations <mobopts.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mobopts>, <mailto:mobopts-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mobopts@ietf.org>
List-Help: <mailto:mobopts-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mobopts>, <mailto:mobopts-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1240939793=="
Sender: mobopts-bounces@ietf.org
Errors-To: mobopts-bounces@ietf.org

Hello folks,
this ID has been revised based on the LC input (see below). An additional
point to note: the ID clarifies that approaches in Section 4 and Section 5
can be implemented on their own. So, folks have choice; those interested in
claimed benefits of the approach in Section 5 can choose to do so. Others
can go with the approach in Section 4.

I would like to ask folks (including reviewers Heejin and Vijay) to take a
look so that we can move this forward.

Thanks,

-Rajeev


On Mon, Feb 25, 2008 at 7:51 AM, QIU Ying <qiuying@i2r.a-star.edu.sg> wrote:

> Dear all,
>
> The draft of "Mobile IPv6 Location Privacy Solutions" is updated.
>
> The major changes are:
>
> 1) revise according to Heejin and Vijay comments
> 2) add traffic formats
> 3) IANA requirement
> 4) other editorial errors
>
> Thanks again for your attention. Any comments are very appreciated.
>
> Regards
> Qiu Ying
>
>
> ----- Original Message -----
> From: "IETF I-D Submission Tool" <idsubmission@ietf.org>
> To: <qiuying@i2r.a-star.edu.sg>
> Cc: <fanzhao@marvell.com>; <Rajeev.Koodli@gmail.com>
> Sent: Monday, February 25, 2008 11:40 PM
> Subject: New Version Notification for
> draft-irtf-mobopts-location-privacy-solutions-07
>
>
> >
> > A new version of I-D,
> draft-irtf-mobopts-location-privacy-solutions-07.txt
> > has been successfuly submitted by QIU Ying and posted to the IETF
> > repository.
> >
> > Filename: draft-irtf-mobopts-location-privacy-solutions
> > Revision: 07
> > Title: Mobile IPv6 Location Privacy Solutions
> > Creation_date: 2008-02-25
> > WG ID: Independent Submission
> > Number_of_pages: 42
> >
> > Abstract:
> > Mobile IPv6 [10] enables mobile nodes to remain reachable while
> > roaming on the Internet.  With its current specification, the
> > location of a mobile node can be revealed and its movement can be
> > tracked by simply monitoring its IP packets.  In this document, we
> > consider the MIP6 location privacy problem described in [14] and
> > propose efficient and secure techniques to protect the location
> > privacy of a mobile node.
> >
> >
> >
> > The IETF Secretariat.
> >
> >
>
>
> ------------ Institute For Infocomm Research - Disclaimer
> -------------This email is confidential and may be privileged.  If you are
> not the intended recipient, please delete it and notify us immediately.
> Please do not copy or use it for any purpose, or disclose its contents to
> any other person. Thank
> you.--------------------------------------------------------
> _______________________________________________
> Mobopts mailing list
> Mobopts@ietf.org
> http://www.ietf.org/mailman/listinfo/mobopts
>
_______________________________________________
Mobopts mailing list
Mobopts@ietf.org
https://www.ietf.org/mailman/listinfo/mobopts