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

Behcet Sarikaya <sarikaya2012@gmail.com> Thu, 04 October 2018 15:02 UTC

Return-Path: <sarikaya2012@gmail.com>
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 3E254130E3C for <pidloc@ietfa.amsl.com>; Thu, 4 Oct 2018 08:02:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 OmSa_XhIxQAn for <pidloc@ietfa.amsl.com>; Thu, 4 Oct 2018 08:02:25 -0700 (PDT)
Received: from mail-wm1-x32b.google.com (mail-wm1-x32b.google.com [IPv6:2a00:1450:4864:20::32b]) (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 54EC8130DFB for <pidloc@ietf.org>; Thu, 4 Oct 2018 08:02:25 -0700 (PDT)
Received: by mail-wm1-x32b.google.com with SMTP id e187-v6so1891115wmf.0 for <pidloc@ietf.org>; Thu, 04 Oct 2018 08:02:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:reply-to:from:date:message-id:subject:to; bh=VYO4BPUkpmuZodd7V3b7zvArs4Sgp+FfL1kmvdCjScM=; b=uMXH7aU03GhFKbqEw9V4+KGtP2tZY0LvGUhoyoExdfRRlVv9WN7O9SkJGGiqUQBfhd y+zSpmvSozVGOgtTUeqCNQhEHF5XNMQh8R6wDxKFj+tT2b+o42DTEXfYRsNuflJ/vObo RsxZT6Qol+nKcTeUSTTDQ2ebigHrAgLufkdRdO30cixmNCiZKDcDc+fFNIrVH7gzvfTB l21eoANjqUXQxChphY9PXytgI/3l5jFA5xFeo6hS6ZxecrIkSlOs4dWocBHhqwoLVwwN aWgActRdSc4IwyQQ/ukkUsTNycsqbcXhaUNz72S2rLrkw393ByQCf3IkdSKebvMXLLCc yz4w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:from:date:message-id :subject:to; bh=VYO4BPUkpmuZodd7V3b7zvArs4Sgp+FfL1kmvdCjScM=; b=aK8StZ7q5gQxtsDkCmHJ+j4Ae5ScadQE00d14r0++NXKImpY9KPLZjMYoH/YPQNaFo 9kYCDwccLszyKb2E6lK+47sgbvagxtclJKLNzThoBGUxfvi359nyj0rR9JhhF39ddaJy TWt6lzmhwyvFWIYsWGAeaFyAXzslrczwy5S6UGIDwCC5eGA0NWtNwo0B2kPYctmB28gc x5Kw2X/kZKJVNSpXWIqb9R507T2eDv6TC5nodjyO7b7ZTWQNa3o+QoiuJHxPhFvB4DP6 Y38s9E7p4PxtZXt9JgRpVIebH0ojxB5sFBoRrZ1SH2uipDrKJXfBxUkmyiJQodR1V5dj 9qHg==
X-Gm-Message-State: ABuFfogrfG403HqxS4CZSHCMJZ8OKj3CQK7lrXah/dtsukjYFaIKXzfu vl/HsHVylU39vN/+RXnYh6TLPikIKTwSJ/DevInedT/N
X-Google-Smtp-Source: ACcGV60Eez7TVCJf4HY4+sP+XUAa+dHeDb9mT3PrdRhirf0xZSMfPV4G4UvPerTL1OA7c3aq4TCHz1YtKHPkTdWYYAU=
X-Received: by 2002:a1c:8a94:: with SMTP id m142-v6mr4951416wmd.80.1538665343611; Thu, 04 Oct 2018 08:02:23 -0700 (PDT)
MIME-Version: 1.0
Reply-To: sarikaya@ieee.org
From: Behcet Sarikaya <sarikaya2012@gmail.com>
Date: Thu, 04 Oct 2018 10:02:12 -0500
Message-ID: <CAC8QAcf-w6QhFXAf9c2y69-aWjwoLWJvuPP0Wgp4iT=Qz9+6tQ@mail.gmail.com>
To: pidloc@ietf.org
Content-Type: multipart/alternative; boundary="0000000000003bf7e405776871a0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pidloc/o2yuXDJN63PU_KyVy0Bwl_XDitQ>
Subject: [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, 04 Oct 2018 15:02:27 -0000

Hi Luigi, Dirk, all,

So far we have a number of reviews on Erik's draft indicating some
editorial issues and asking for clarification of some parts. All that is
good.

What I suggest is that we should also look into what he is saying in that
draft, what is he suggesting as the future work to do?

Here I am going to summary what I could find out:

- We should concentrate on long-lived identifiers;

- Worry not much on designing a privacy based unified mapping mapping
system which we had concentrated in our previous activity. This is because only
trusted devices can access the mappings  in an operator network

- Instead worry about minimizing the privacy implication one can explore
limiting to which peers and when the ID/ locator binding are exposed.

The cases where ID/locator bindings are exposed (especially any mobile
devices)
- Family and friends for example where are parents sharing young children
location
- In industrial IoT case, the devices belonging to the same company
share ID/locator
bindings but not share the ID/locator binding with third parties

In Section 6, the draft points to some possibilities on how this limiting
can be achieved:

1. pointing a locator for some fixed anchor point, like PGW or UPF

2. injecting routing prefixes for the ID prefixes into the normal routing
system

3. not providing any stable locators across this boundary; only allow
ephemeral IP addresses per session or otherwise limited exposure.

In short, the draft is coming up with a lot work to do.
We suggest that the group takes a close look into all these points and see
what we can do :-)
Regards,
Behcet & Dirk