Re: privacy at layer 7 and above (was: A common problem with SLAAC in "renumbering" scenarios)

Alexandre Petrescu <alexandre.petrescu@gmail.com> Fri, 15 February 2019 09:53 UTC

Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10C09130F97 for <ipv6@ietfa.amsl.com>; Fri, 15 Feb 2019 01:53:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.632
X-Spam-Level:
X-Spam-Status: No, score=-2.632 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 5VoxvUiQFcYQ for <ipv6@ietfa.amsl.com>; Fri, 15 Feb 2019 01:53:23 -0800 (PST)
Received: from cirse-smtp-out.extra.cea.fr (cirse-smtp-out.extra.cea.fr [132.167.192.148]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2ABCA130F5F for <ipv6@ietf.org>; Fri, 15 Feb 2019 01:53:22 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x1F9rL42009660 for <ipv6@ietf.org>; Fri, 15 Feb 2019 10:53:21 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 10C402062AC for <ipv6@ietf.org>; Fri, 15 Feb 2019 10:53:21 +0100 (CET)
Received: from muguet1-smtp-out.intra.cea.fr (muguet1-smtp-out.intra.cea.fr [132.166.192.12]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 06C44205E71 for <ipv6@ietf.org>; Fri, 15 Feb 2019 10:53:21 +0100 (CET)
Received: from [10.8.35.150] (is154594.intra.cea.fr [10.8.35.150]) by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x1F9rKuR020973 for <ipv6@ietf.org>; Fri, 15 Feb 2019 10:53:21 +0100
Subject: Re: privacy at layer 7 and above (was: A common problem with SLAAC in "renumbering" scenarios)
To: ipv6@ietf.org
References: <60fabe4b-fd76-4b35-08d3-09adce43dd71@si6networks.com> <c16e0e1f-1ed2-ad88-80f1-070bdd8bccca@go6.si> <1F2C2AEE-1C7D-481C-BBA7-7E507312C53A@employees.org> <e56a6e5b-648d-200e-c35d-97f15a31fb2a@asgard.org> <CAO42Z2zh7fKAgQJq9aLCTiFoSSsTeGM=pK3gXitg+gcxH=9fhQ@mail.gmail.com> <d38857c2-6e92-91d6-bb5d-d3eeeb61276a@gmail.com> <CAO42Z2yb47OyXk__Sz-kO00pfcBJgLAhff5DF=mpAddR0iCnAA@mail.gmail.com> <2612280f-195a-ae7a-b3b1-9022d9282fa7@foobar.org> <56F813F4-C512-40A9-8A68-1090C76A80F6@consulintel.es> <CAHL_VyCN8kU7qnLOphfGR25-xGBe_p6WeGTkKVXwU5uy5aJ8Dg@mail.gmail.com> <65DB4854-97D2-4C31-A691-2CD93812EF93@consulintel.es> <CAHL_VyCMpCcGkEQu+RV1GRf2QLB-HD0+AOOBV0YhfQ5sbydVzQ@mail.gmail.com> <8CE7A0CD-97D9-46A0-814D-CAF8788F9964@consulintel.es> <e3e0bf2273e04f15b792665d0f66dfe5@boeing.com> <4c5fab33-2bff-e5b5-fc1d-8f60a01a146d@go6.si> <b4525832-9151-20bf-7136-31d87ba6c88d@huitema.net> <463f15cf-2754-e2e8-609d-dc0f33448c6c@go6.si>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <5519271a-fce7-ed75-d7b1-a360e34bb47a@gmail.com>
Date: Fri, 15 Feb 2019 10:53:20 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.0
MIME-Version: 1.0
In-Reply-To: <463f15cf-2754-e2e8-609d-dc0f33448c6c@go6.si>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/2Xp-VSDoSH5BorwODxgIHnGbz9Q>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Feb 2019 09:53:27 -0000

Le 15/02/2019 à 10:30, Jan Zorz - Go6 a écrit :
[...]

> /64 for each device is fine. What I'm questioning is if we really need 
> to make underlying to be something that was never meant to be if L7 and 
> above is broken? I think L7 and above needs to be fixed first and then 
> changing of addresses in transport layer can have any effect. Until then 
> - let's transport packets in a way that doesn't break often and make 
> user grumpy.
> 
> To put "lipstick on a pig" is a rhetorical expression, but quite useful 
> in our case :) :) :)

I do not know what putting lipstick on a pig means, although I do 
remember this expression being used by or in relationship with a politician.

Signed contractual allocation of permanent IPv6 address, and of an IPv6 
prefix, to a (group of) mobile device, is an excellent thing for session 
continuity.

The privacy concerns are matters of L7 and above, specifically politics, 
computer-assisted human interactions, graphical user interfaces.  GDPR 
is one a politics answer for privacy.

GDPR itself has some issues when it comes to implementation: websites 
now invite the user to accept or not cookies, but the manner in which 
this is performed - a technical implementation - leads to accept more, 
or less.  Some times end users feel confident their privacy is 
respected, other times they feel they loose control of it, and worse - 
outright cheated.

In time, an example of this GDPR-enforced dialogue is the following 
related to cookie acceptance:
- first, there was 2 answers possible: yes, or no.  Exclusively.  You
   had to press something.
- then came the little cross on the window corner, to avoid answering
   altogether - do not leave any trace.  YEt the end user did not
   know whether the answer was yes or no when pressing that cross.
- recent dialogues involve a cross with only one default answer
  'Accept'.  How dare they to take my cross pressing as Accept.  I did
   not say 'Accept'.  I pressed a cross, or Escape button, to avoid
   answering the question.
- what I want in the future is cross closing the dialogue box and tell
   the website to shut up, dont trace me, dont use cookies.  Dont even
   record the fact that I pressed that cross.

Is that 3rd option part of GDPR?

This reminds of the cartoon showing the options possible for vote, 
during a particular campaign, in which only one option was actually 
possible: whatever button one pressed, the end result was the same.

This is the kind of privacy issues that need to be addressed.  It is 
level 7 and above.

This looks far from being a matter of using or not using stable IP 
addresses when querying a website.

Alex

> 
> Cheers, Jan
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>