[Mip6] [issue79] Review by Lisa Dusseault <lisa@osafoundation.org>

admin <tracker-mip6@mip4.org> Wed, 15 November 2006 20:16 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GkRBZ-0007Bj-Fp; Wed, 15 Nov 2006 15:16:41 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GkRBY-0007BV-7S for mip6@ietf.org; Wed, 15 Nov 2006 15:16:40 -0500
Received: from av12-1-sn2.hy.skanova.net ([81.228.8.185]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GkRBU-0004y5-P7 for mip6@ietf.org; Wed, 15 Nov 2006 15:16:38 -0500
Received: by av12-1-sn2.hy.skanova.net (Postfix, from userid 502) id D381E38170; Wed, 15 Nov 2006 21:16:28 +0100 (CET)
Received: from smtp4-2-sn2.hy.skanova.net (smtp4-2-sn2.hy.skanova.net [81.228.8.93]) by av12-1-sn2.hy.skanova.net (Postfix) with ESMTP id BC8BE37E48 for <mip6@ietf.org>; Wed, 15 Nov 2006 21:16:28 +0100 (CET)
Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com [81.232.110.214]) by smtp4-2-sn2.hy.skanova.net (Postfix) with ESMTP id A7C9837E81 for <mip6@ietf.org>; Wed, 15 Nov 2006 21:16:28 +0100 (CET)
Received: from shiraz.local.levkowetz.com ([192.168.3.14] helo=shiraz.levkowetz.com) by shiraz.levkowetz.com with esmtp (Exim 4.63) (envelope-from <roundup-admin@mip4.org>) id 1GkRBK-0002Ul-JN for mip6@ietf.org; Wed, 15 Nov 2006 21:16:27 +0100
Content-Type: text/plain; charset="utf-8"
To: mip6@ietf.org
From: admin <tracker-mip6@mip4.org>
Date: Wed, 15 Nov 2006 20:16:26 +0000
MIME-Version: 1.0
Message-Id: <1163621786.44.0.274376954002.issue79@mip4.org>
X-Roundup-Name: Mip6 issue tracker
X-Roundup-Loop: hello
Content-Transfer-Encoding: quoted-printable
X-SA-Exim-Connect-IP: 192.168.3.14
X-SA-Exim-Mail-From: roundup-admin@mip4.org
X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on shiraz.levkowetz.com
X-Spam-Level:
X-Spam-Status: No, score=-110.4 required=2.5 tests=ALL_TRUSTED,BAYES_00, USER_IN_WHITELIST,USER_IN_WHITELIST_TO autolearn=ham version=3.1.7
X-SA-Exim-Version: 4.2.1 (built Mon, 27 Mar 2006 13:42:28 +0200)
X-SA-Exim-Scanned: Yes (on shiraz.levkowetz.com)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Subject: [Mip6] [issue79] Review by Lisa Dusseault <lisa@osafoundation.org>
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>
Errors-To: mip6-bounces@ietf.org

New submission from admin <roundup-admin@mip4.org>:

Comment:

This document lacks many important references and definitions for an outsider to be able to figure out 
what's going on.  
 - No reference for understanding where "Care of address" comes from -- this is most devastating as 
there is no reference or explanation to understand who gets the Care of address in the course of MIP6 
operation
 - In poking around, I found that draft-haddad-alien-privacy-terminology-01.txt has a much better 
definition for "location privacy"
 - MN is not expanded on first use or defined, I have to assume MN=Mobile Node
 - HoA never defined -- is this same as HA which I assume is Home Address
 - CN never defined -- hunting through the informative reference to draft-haddad-momipriv-problem-
statement-03.txt (also not helpfully named) I guess this is Correspondent Node?
 - ESP never defined
 - SIP never defined or referenced
 - Neither reference explains bidirectional tunneling, or reverse tunneling (are these the same???)
 - All these terms and acronyms seem to be very inconsistently used

Most fundamentally, the Conclusion -- that disclosing Care of address to a correspondent and 
disclosing Home address to an onlooker can compromise location privacy -- is not supported by this 
document or its references.  It's probably a reasonable statement if the WG has reviewed the document, 
but even if so, it's poorly explained and based on much material that's not here even in reference form.

----------
category: Editorial
draft: draft-ietf-mip6-location-privacy-ps
messages: 267
nosy: admin
priority: Should fix
status: Pending
title: Review by Lisa Dusseault <lisa@osafoundation.org>

_________________________________________________
Mip6 issue tracker <tracker-mip6@mip4.org>
<http://www.mip4.org/issues/tracker/mip6/issue79>
_________________________________________________

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