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

Jan Zorz - Go6 <jan@go6.si> Tue, 19 February 2019 11:46 UTC

Return-Path: <jan@go6.si>
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 06A29130EA3 for <ipv6@ietfa.amsl.com>; Tue, 19 Feb 2019 03:46:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=go6.si
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 TYtm0tbk3bMy for <ipv6@ietfa.amsl.com>; Tue, 19 Feb 2019 03:46:11 -0800 (PST)
Received: from mx.go6lab.si (mx.go6lab.si [IPv6:2001:67c:27e4::23]) (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 84FE71286E7 for <ipv6@ietf.org>; Tue, 19 Feb 2019 03:46:11 -0800 (PST)
Received: from localhost (localhost [IPv6:::1]) by mx.go6lab.si (Postfix) with ESMTP id 0B5926608B for <ipv6@ietf.org>; Tue, 19 Feb 2019 12:46:07 +0100 (CET)
X-Virus-Scanned: amavisd-new at go6.si
Received: from mx.go6lab.si ([IPv6:::1]) by localhost (mx.go6lab.si [IPv6:::1]) (amavisd-new, port 10024) with LMTP id Dqtsgu3zem_4 for <ipv6@ietf.org>; Tue, 19 Feb 2019 12:46:06 +0100 (CET)
Received: from mail.go6.si (mail.go6.si [IPv6:2001:67c:27e4::61]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.go6.si", Issuer "Let's Encrypt Authority X3" (not verified)) by mx.go6lab.si (Postfix) with ESMTPS id 023D665A2D for <ipv6@ietf.org>; Tue, 19 Feb 2019 12:46:06 +0100 (CET)
Received: from haktar.local (unknown [IPv6:2001:67c:27e4:5::2c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "Jan Zorz", Issuer "COMODO RSA Client Authentication and Secure Email CA" (not verified)) (Authenticated sender: jan) by mail.go6.si (Postfix) with ESMTPSA id 5E75D80642 for <ipv6@ietf.org>; Tue, 19 Feb 2019 12:46:05 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=go6.si; s=mail; t=1550576765; bh=bkVgyIK5xGnjw7vKe013Wbsk13e3zeluPRXdaaSZryE=; h=Subject:To:References:From:Date:In-Reply-To:From; b=Jt4WMhxIGKEnYfaBVgDU1OKpmSXbdGNJJq8Q5fpCyr1FGUe3AZzGC1XfQq5ETyQzO vW+wC9QdoYDkxlHR/K9kXvMb6T4KwyVOtph8cAlxysrB9zd4gGLvcwnG4tGUnvHk8S xisht6DTpSZDymr1IzuGGE44bF3KahmL+1nArZLA=
Subject: Re: Revision of the SLAAC/renum I-D (Fwd: New Version Notification for draft-gont-6man-slaac-renum-01.txt)
To: ipv6@ietf.org
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> <alpine.DEB.2.20.1902191102200.24327@uplift.swm.pp.se> <20190219102427.GK33237@ernw.de>
From: Jan Zorz - Go6 <jan@go6.si>
Message-ID: <fd19943c-1601-5e0e-b402-bd5164c50f07@go6.si>
Date: Tue, 19 Feb 2019 12:46:05 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.5.1
MIME-Version: 1.0
In-Reply-To: <20190219102427.GK33237@ernw.de>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/lqT50ZuHnXFHCIx9q1YPbZe9CZM>
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 11:46:14 -0000

On 19/02/2019 11:24, Enno Rey wrote:
> Hi,
> 
> On Tue, Feb 19, 2019 at 11:08:20AM +0100, Mikael Abrahamsson wrote:
>> 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?
> 
> yes, I can confirm this (lack of legal authority or mandate). 
> Assuming the above reference to another list could point to a thing I
> sent I could copy+paste that if needed (avoiding cross-posting for
> the moment).

Thank you, Enno, appreciated.

> I think I can provide a statement on this (not being a lawyer though,
> but somewhat familiar with the space). From a legal perspective that
> document doesn't have a binding character. Reasons include: - the
> "Datenschutzbeauftragte" (data protection officers) don't have (much)
> legal authority by themselves, but mostly a consulting (e.g. to the
> parliament) role and some "supervisory" tasks. - the committee which
> issued the document ("Konferenz der Datenschutzbeauftragten") by
> itself isn't a legal or even (afaik) an institutional body. - the
> title explicitly says "Hinweise" => here to be best translated (I'd
> say) as "advise".
> 
> tl;dr: that document doesn't have legally binding character.

If that's the case, then a reference should be removed from the I-D.

<joke>
Or even better - we could say that despite all the rumors and FUD - even 
in Germany that's not legally binding and therefore operators can do 
whatever they want with their architecture :)
</joke>

Cheers, Jan