Re: Revision of the SLAAC/renum I-D (Fwd: New Version Notification for draft-gont-6man-slaac-renum-01.txt)

Mikael Abrahamsson <swmike@swm.pp.se> Tue, 19 February 2019 10:08 UTC

Return-Path: <swmike@swm.pp.se>
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 09E50130E9B for <ipv6@ietfa.amsl.com>; Tue, 19 Feb 2019 02:08:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level:
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
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 mIEBozJOC1nq for <ipv6@ietfa.amsl.com>; Tue, 19 Feb 2019 02:08:23 -0800 (PST)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (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 0B4DF130E9A for <ipv6@ietf.org>; Tue, 19 Feb 2019 02:08:23 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id AA678BB; Tue, 19 Feb 2019 11:08:20 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1550570900; bh=nlIGzCd+MRvprsuxK4/s+j2aMSyJfZ84ZWIZ7ZhOldY=; h=Date:From:To:Subject:In-Reply-To:References:From; b=lMB9mDvNLcu2CBJ15YspO2QnnvOV30PyqtPUgFuOOhJlF5GCBfhq1iNxRZjyPzo9j fcSREAnaPlk+qeKIjAD1xbOUquq8t7/UE1zf0bKzWcgmnyCndVvl7xhQP28GOSB3+2 AtwF6EYvUB0tLxuJ5sWfTmC+G1jG/8MLEys6DbaA=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id A83A3BA for <ipv6@ietf.org>; Tue, 19 Feb 2019 11:08:20 +0100 (CET)
Date: Tue, 19 Feb 2019 11:08:20 +0100
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: ipv6@ietf.org
Subject: Re: Revision of the SLAAC/renum I-D (Fwd: New Version Notification for draft-gont-6man-slaac-renum-01.txt)
In-Reply-To: <7f0bd1d3-2bc2-69d1-1ff9-91e4da104e3e@gmail.com>
Message-ID: <alpine.DEB.2.20.1902191102200.24327@uplift.swm.pp.se>
References: <155053352190.25856.12031845488827430669.idtracker@ietfa.amsl.com> <fe9eecc0-b41a-53c5-5e17-7f8d732cb7cf@si6networks.com> <105E9F49-A9E7-4C77-963D-0B37997FF7AE@consulintel.es> <61d3daff-927f-b289-197a-01ff504aeba9@go6.si> <7f0bd1d3-2bc2-69d1-1ff9-91e4da104e3e@gmail.com>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: multipart/mixed; BOUNDARY="-137064504-671648784-1550570900=:24327"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/iW-DLvJA3OjT6daSWvYP4n5F-2E>
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: Tue, 19 Feb 2019 10:08:26 -0000

On Tue, 19 Feb 2019, Alexandre Petrescu wrote:

>
>
> Le 19/02/2019 à 10:40, Jan Zorz - Go6 a écrit :
>> On 19/02/2019 02:18, JORDI PALET MARTINEZ wrote:
>>> As just said in another list in Spanish, the reference to GERMAN-DP
>>> is wrong, in the sense that is not a law or anything similar. German
>>> folks can confirm. At least that has been said a few weeks ago by
>>> Germans in another list ...
>> 
>> Hi,
>> 
>> Interesting. Can any German speaking person on this list confirm?
>> 
>> I also heard something like this, but can't confirm.
>
> I was wondering what does this reference in the draft mean:
>
> "Einfuhrung von IPv6 Hinweise fur Provider im Privatkundengeschaft und 
> Herstellere"

http://www.bfdi.bund.de/SharedDocs/Publikationen/Entschliessungssammlung/DSBundLaender/84DSK_EinfuehrungIPv6.pdf?__blob=publicationFile

"Um das zielgerichtete Verfolgen von Nutzeraktivitäten (Tracking) zu 
vermeiden, müssen Adresspräfixe grundsätzlich dynamisch an Endkunden 
vergeben werden. Auch eine Vergabe mehrerer statischer und dynamischer 
Adresspräfixe kann datenschutzfreundlich sein, wenn Betriebssystem und 
Anwendungen den Nutzer dabei unterstützen, Adressen gezielt nach der 
erforderlichen Lebensdauer auszuwählen."

This seems to say that default should be dynamically changing prefix.

"Entscheidet sich ein Provider für die Vergabe statischer Präfixe an 
Endkunden, müssen diese Präfixe auf Wunsch des Kunden gewechselt werden 
können. Hierzu müssen dem Kunden einfache Bedienmöglichkeiten am Router
oder am Endgerät zur Verfügung gestellt werden."

This says provider must have functionality so to change prefixes at 
customer request if they provide static prefixes.

I don't know the legal standing of this document. Anyone else know?

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se