IETF Logo Mail Archive

Re: [Pidloc] draft-nordmark-id-loc-privacy

Luigi Iannone <ggx@gigix.net> Thu, 11 October 2018 09:27 UTC

Return-Path: <ggx@gigix.net>
X-Original-To: pidloc@ietfa.amsl.com
Delivered-To: pidloc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E769130DCB for <pidloc@ietfa.amsl.com>; Thu, 11 Oct 2018 02:27:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gigix-net.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Yiv0GATeuIku for <pidloc@ietfa.amsl.com>; Thu, 11 Oct 2018 02:27:32 -0700 (PDT)
Received: from mail-wr1-x435.google.com (mail-wr1-x435.google.com [IPv6:2a00:1450:4864:20::435]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1AE7B129BBF for <pidloc@ietf.org>; Thu, 11 Oct 2018 02:27:32 -0700 (PDT)
Received: by mail-wr1-x435.google.com with SMTP id n11-v6so8751019wru.13 for <pidloc@ietf.org>; Thu, 11 Oct 2018 02:27:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gigix-net.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=wPTu7PpAzvdziq3/jV7emF20z05MfpmFU4LV+7UF7oE=; b=A2EuBu/SQ6ajJHZ9V3JNG8Br5MMHFZg8FhEI4L3ilVS8UUvu8CTRtjFnzjc7QEImEW ivNI2ZfIGSCg5EZlC9zNT0x8xhwiqzHaPp+VGlLx2PI/1IcZ8sjVOns9Zt8ClxKppgUD 8NgCad1cJmj3j00XfI76XNNm32YZlGhqu9QR4JiKazEGLsQ+4kD7boOHOAbLNpWtR8RW kIsLz/AmaYxjsNsve+1fNAQTiMHqR2vyeF0OTZg0kM2X7GEiOGvu+5QpfVQFysFtnhjo 1jN8JoGteLB9rY9kcXFk3w6Mj4XNeJhvj4FcP6juexNQwcvhZcFAgkHv5uGmEvjiINLY 0QAA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=wPTu7PpAzvdziq3/jV7emF20z05MfpmFU4LV+7UF7oE=; b=F9WAgPyAn5p1p9SSSHltAMFxlYqj/25DK/bEAa1K9dQS4/yAZ5dlJ7F7fWnU9dUwtb Vai55CmHOUUKTYaOorsJzoA4dNNCXBl14P6Uk5j9g2G+c8FDK7VmOpGT8y/f6X6YktBJ KrJ2wGcAhz886aKMZMwy4qJkOS8Z1HHT1UgBEoZ/laCmIjP3BWMmYK3uGY0aEZliTY8N Z91TwZGt62Et0/1gn2zsS79uu6L2uX8VLdLeJ3AAvjNz0s+YrX7nrkCkclI0UZASpkyp bfpSIGtdij01onh3/ycw0UR2Jvuzf16p1pHgsdyiIeuGS7UiYPocoX5IJDUihnD8sbk1 tsjQ==
X-Gm-Message-State: ABuFfogzDrofwChS0/HY1UiF23eAOYKfNJMLGGBnf0YWMrgeP9rsjjSh nVd0srwsxTCgzgE1/1aWxUoGJQ==
X-Google-Smtp-Source: ACcGV63phi+8pNKdaqxXwMnSySzAIiiPa1PMOZucXXzmPQCGbRVJK589yd/S9kvpoVhnybNkQcT8SA==
X-Received: by 2002:adf:c3cd:: with SMTP id d13-v6mr866500wrg.68.1539250050525; Thu, 11 Oct 2018 02:27:30 -0700 (PDT)
Received: from ?IPv6:2001:660:330f:a4:7489:ccd2:f7c:1d15? ([2001:660:330f:a4:7489:ccd2:f7c:1d15]) by smtp.gmail.com with ESMTPSA id g15-v6sm19740735wrp.56.2018.10.11.02.27.28 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 11 Oct 2018 02:27:29 -0700 (PDT)
From: Luigi Iannone <ggx@gigix.net>
Message-Id: <4C08DC39-6987-4D13-B52E-59CD8A612363@gigix.net>
Content-Type: multipart/alternative; boundary="Apple-Mail=_5CDE9D80-6CE9-4B65-8273-5B35891D55ED"
Mime-Version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\))
Date: Thu, 11 Oct 2018 11:27:33 +0200
In-Reply-To: <CAC8QAcdLqj1zMuitq-88dmHEZ5YXyYwR7ytwJftdcPwBn1wnDg@mail.gmail.com>
Cc: Tom Herbert <tom@quantonium.net>, pidloc@ietf.org
To: sarikaya@ieee.org
References: <CAC8QAcf-w6QhFXAf9c2y69-aWjwoLWJvuPP0Wgp4iT=Qz9+6tQ@mail.gmail.com> <CAPDqMeos1-=xTAdnOw893C3RkiM9wrt7_njg+jDEasHa-kz1zg@mail.gmail.com> <CAC8QAcct_h7Ti+U0U0McF2GSii+ynJZQg4ZO_2058XhPm6dy4w@mail.gmail.com> <CAPDqMepFhwFwU_G6Wnj+wdtKXT7BX1mPMwQpVkJEEY688FoXVQ@mail.gmail.com> <CAC8QAcdLqj1zMuitq-88dmHEZ5YXyYwR7ytwJftdcPwBn1wnDg@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.100.39)
Archived-At: <https://mailarchive.ietf.org/arch/msg/pidloc/A2-P-kKCR7W09x58bhX82zlgfaI>
Subject: Re: [Pidloc] draft-nordmark-id-loc-privacy
X-BeenThere: pidloc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <pidloc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pidloc>, <mailto:pidloc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pidloc/>
List-Post: <mailto:pidloc@ietf.org>
List-Help: <mailto:pidloc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pidloc>, <mailto:pidloc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Oct 2018 09:27:34 -0000


> On 5 Oct 2018, at 17:09, Behcet Sarikaya <sarikaya2012@gmail.com> wrote:
> 
> 
> Sure, it could be considered, but the benefits of exposing a third
> party to identifier/locator mappings would have to be weighed against
> the cost. The potential cost is weakened user privacy and security.
> Locators will convey geo location in a mobile network, so if someone
> knows identifier to locator mapping, then they know location of node
> with that identifier. But more than that, knowledge of
> identifier/locator mappings allow correlations to be made between
> identifiers. For instance, if a device is using some number of
> untrackable and uncorrelatable identifiers for privacy, knowledge of
> identifier to locator mappings allows correlations to be made and the
> identifiers that belong to the device can be deduced and the users can
> be tracked.
> 
> 
> Absolutely.
> 
> One reason why I posted this mail was to encourage the discussion of solution approaches in different 
> IdLoc protocols.
> How could we treat each of cases of Family and Friends, Industrial IoT, etc. in ILA, ILNP, and LISP?

Not sure I follow the question here. 

You mean how these protocol can behave in the listed scenarios or how these protocol can avoid tracking ID?

Ciao

L.


> What about the three points in Section 6?
> 
> Behcet
> 
> -- 
> Pidloc mailing list
> Pidloc@ietf.org
> https://www.ietf.org/mailman/listinfo/pidloc

v2.23.0 | Report a Bug | By Email