Re: [v6ops] New Version Notification for draft-hilliard-v6ops-host-addr-update-00.txt - Privacy Properties

Nick Hilliard <nick@foobar.org> Thu, 20 July 2017 16:45 UTC

Return-Path: <nick@foobar.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9E1513192B for <v6ops@ietfa.amsl.com>; Thu, 20 Jul 2017 09:45:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 y8smlo74MElc for <v6ops@ietfa.amsl.com>; Thu, 20 Jul 2017 09:45:08 -0700 (PDT)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AC3C9131714 for <v6ops@ietf.org>; Thu, 20 Jul 2017 09:45:07 -0700 (PDT)
X-Envelope-To: v6ops@ietf.org
Received: from cupcake.local (089-101-195156.ntlworld.ie [89.101.195.156] (may be forged)) (authenticated bits=0) by mail.netability.ie (8.15.2/8.15.2) with ESMTPSA id v6KGj5L6098111 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 20 Jul 2017 17:45:05 +0100 (IST) (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host 089-101-195156.ntlworld.ie [89.101.195.156] (may be forged) claimed to be cupcake.local
Message-ID: <5970DE11.5070001@foobar.org>
Date: Thu, 20 Jul 2017 17:45:05 +0100
From: Nick Hilliard <nick@foobar.org>
User-Agent: Postbox 5.0.16 (Macintosh/20170718)
MIME-Version: 1.0
To: Tim Chown <Tim.Chown@jisc.ac.uk>
CC: IPv6 Ops WG <v6ops@ietf.org>
References: <596CF817.8040900@foobar.org> <BC0BBAF5-B016-44B5-8D73-BC9382CB79A9@google.com> <20170719090835.GC45648@Space.Net> <CAKD1Yr29MmGJuX+uhXaroB6UMRBBWBscCZPaMjaVscL0q7a7pg@mail.gmail.com> <98208c2e-7524-7afa-b0c8-865f251cd66e@gmail.com> <20170720062751.GL45648@Space.Net> <CAKD1Yr1ihnqHAzjhPcA8HB7sBBRwht2t5epJqQA-B_YGnfoTQA@mail.gmail.com> <52ed5fcd-8af5-5b6b-4328-002a431977b6@gmail.com> <CAPt1N1mzRmX6ZccDS8O642N-Lkq5=FZuUHUEFotwo9CFuMNsAQ@mail.gmail.com> <D45180D3-D889-4B9C-B059-F6D1A59909A8@jisc.ac.uk> <5970D1FF.2090707@foobar.org> <6C5C7F6F-0503-47CA-9C28-D0F405340EC2@jisc.ac.uk>
In-Reply-To: <6C5C7F6F-0503-47CA-9C28-D0F405340EC2@jisc.ac.uk>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/lyRnJBArmped9rsNltpuNhkFNnc>
Subject: Re: [v6ops] New Version Notification for draft-hilliard-v6ops-host-addr-update-00.txt - Privacy Properties
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jul 2017 16:45:10 -0000

Tim Chown wrote:
> For campus network wifi, you get accountability through eduroam.

s/campus network/eduroam campus network/

There are lots of different types of campus, and campus type networks.

> Many hotspots have zero authentication.

Sadly, there is an increasing number of situations which refuse hotspot
connectivity without authentication, depending on a variety of situations.

>> Note that in cases like hotspots and campus wifi, you would be
>> well advised not to have any expectations of privacy to start with,
>> so in the general case, it would be questionable as to whether
>> these networks would be bcp204 compliant to start with.  This isn't
>> a blanket statement or a position of intent, btw - just an
>> observation that if you use someone else's network resources, you
>> are subject to their policies. </ymmv>
> 
> Yeah things like GDPR would come into play. But let’s not go down
> this rathole; the point is that different scenarios will have
> different expectations and requirements.

indeed, and the ietf needs to acknowledge this explicitly.

Nick