Re: [RTG-DIR] Rtgdir telechat review of draft-ietf-mtgvenue-iaoc-venue-selection-process-12
Stewart Bryant <stewart.bryant@gmail.com> Tue, 06 February 2018 09:41 UTC
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: rtg-dir@ietfa.amsl.com
Delivered-To: rtg-dir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CC2012D811; Tue, 6 Feb 2018 01:41:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham 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 JYYmDtbVRfLW; Tue, 6 Feb 2018 01:40:58 -0800 (PST)
Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::232]) (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 84A49126CE8; Tue, 6 Feb 2018 01:40:58 -0800 (PST)
Received: by mail-wm0-x232.google.com with SMTP id j21-v6so17023602wmh.1; Tue, 06 Feb 2018 01:40:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=8qjkm9wfo6Haafpv4XLl0Z4z+dkMkJD9ANfE/8imye0=; b=pX/hq3AB0tYfgof6VA8VeqF3bmD/7e8a7v8hoaijJ/65bZpnZN7xlALj8vUSH4LKXe kG8sV5/16ZVULKg6XJp/XU/rfccATu5M5zehso7vN8GEzgjfykOG034M2pL2nMBSzYxW 3lEjtnUWEvndCBS7LwE0C8l9KbDh6FILO9kSmSOSWLtVa6vTIX4U9R4F1X6ZESTTmA01 FPemL3Dg5k2cK1QDfdxjTV7M12QQajnA6BPBGYdKvcbX8/oz4ZgZ7eeQUqvo08otcf6P 9B9XFJfggyjGosZiIGQ6GzAgz1LGyL/seVtYToUTIbV/iFps8pYZ1I8Q6xML+p/WNSyp EhJg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=8qjkm9wfo6Haafpv4XLl0Z4z+dkMkJD9ANfE/8imye0=; b=OUeJA4BjUtgDXSUQl8i8q4gvumUbtF5f8H+4Q52s2viFVbjE4LXk9QasMZypaFDD/W GL2QTmc69q8MOp4YXkUKoHs/tFTNigNXtyfvuWLAVMRKUP0NbY+JjzUFiVtC+QxpDmXc iDDL/tJ3Pjlu4juxG5Ihn42H6o153yFChkuxZaI3cN+gKFReh7FBPU3+cF8mpCo6GOuo g8yonaiuSR0QKiy2loB1/gtHY79BpzfE5pIZSEiVkKzHQtWpORpq+r6LmzSbMZ4fMXZk syxdeNBtCUnSphrMSNGBudFY36WnXTGiUF5wDenAc/UtHEd8q/TP6wbwHPHntlspZnlz hLOg==
X-Gm-Message-State: APf1xPALWedBbxeA98FCFuW2CdwMcoGxHuzTqHw4ultZ9bgjOfCSQJlQ RE7Kk3Gkv1RmwuumA2wGlB9hAtDO
X-Google-Smtp-Source: AH8x226WOWheGNU2EEas3Tf/Cjrb8X7QF1pBr8QTSNPDB0q818oDJAnMm/5RVM3uc/KoAHTQ+GFk1A==
X-Received: by 10.80.179.6 with SMTP id q6mr2882933edd.87.1517910056800; Tue, 06 Feb 2018 01:40:56 -0800 (PST)
Received: from [192.168.2.126] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id y3sm9007604edb.1.2018.02.06.01.40.55 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 06 Feb 2018 01:40:56 -0800 (PST)
To: adrian@olddog.co.uk, 'Alissa Cooper' <alissa@cooperw.in>, 'Stewart Bryant' <stewart@g3ysx.org.uk>
Cc: mtgvenue@ietf.org, rtg-dir@ietf.org, 'IETF' <ietf@ietf.org>, draft-ietf-mtgvenue-iaoc-venue-selection-process.all@ietf.org
References: <151782868264.5731.15496399706573021777@ietfa.amsl.com> <F3AE809A-C4A2-4FCE-91BF-3C64D80E6ACF@cooperw.in> <02b801d39f2d$ee76e3b0$cb64ab10$@olddog.co.uk>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <ea1a7deb-ddf2-061c-0a73-000b663852cf@gmail.com>
Date: Tue, 06 Feb 2018 09:40:55 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <02b801d39f2d$ee76e3b0$cb64ab10$@olddog.co.uk>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-dir/46R1LB-4-UlmdXeM2jCQbSQuOys>
Subject: Re: [RTG-DIR] Rtgdir telechat review of draft-ietf-mtgvenue-iaoc-venue-selection-process-12
X-BeenThere: rtg-dir@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Routing Area Directorate <rtg-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-dir/>
List-Post: <mailto:rtg-dir@ietf.org>
List-Help: <mailto:rtg-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Feb 2018 09:41:00 -0000
On 06/02/2018 09:36, Adrian Farrel wrote: > Hi all, > >>> 8. Privacy Considerations >>> >>> This note reveals no personally identifying information apart from >>> its authorship. >>> >>> SB> This is true, but does spawn the question of whether privacy should >>> be a meeting location selection criteria? >> Any actionable criterion that I can conceive of to address this would likely > render >> our already tiny set of acceptable locations to roughly zero. If you have a > proposal >> that would do otherwise, feel free to suggest it. > In the spirit of Privacy Considerations for protocol specs we should not > necessarily be looking to resolve all privacy concerns, but we should be looking > to expose them so that participants can be aware of the risks and can mitigate > them or choose to not participate. > > I would certainly agree that we are unlikely to find a nation stat that > perfectly respects personal and online privacy, but that need not be the > objective. Nor need it be a requirement that the IAOC report on the privacy of a > venue when announcing it. On the other hand, I bet we would all agree that a > venue that assigned a government official to accompany us at all times listening > to our conversations and noting our sleeping habits would rule itself out. So > there are lines :-) > > But what this section should say is something like... > > == > Physical and remote participants at IETF meetings should be aware that privacy > norms vary considerably from country to country. Participants with a concern for > their personal or work-related privacy are advised to familiarise themselves > with the privacy risks associated with a venue before attending. Concerns may > include privacy of Internet communications, record of having travelled, and > freedom of association. Some people may have particular concern for the privacy > of information stored on electronic devices when they cross specific national > borders. > > Participants are responsible for taking their own measures in mitigation. > > In general, the meeting selection process will not take privacy concerns into > consideration and will not seek to report on them to the community for any > chosen venue. However, it is expected that the selection process will exclude > venues where privacy of attendees is known to be particularly at risk. Such > exclusions might include (although not be limited to) venues where attendees > cannot use VPNs or other security mechanisms to access their home networks and > the Internet in general. > == > > ...I'm not wedded to that - I only had 4 hours sleep :-) > > Adrian > That looks like good text. - Stewart
- [RTG-DIR] Rtgdir telechat review of draft-ietf-mt… Stewart Bryant
- Re: [RTG-DIR] Rtgdir telechat review of draft-iet… Eliot Lear
- Re: [RTG-DIR] Rtgdir telechat review of draft-iet… Stewart Bryant
- Re: [RTG-DIR] Rtgdir telechat review of draft-iet… Eliot Lear
- Re: [RTG-DIR] Rtgdir telechat review of draft-iet… Stewart Bryant
- Re: [RTG-DIR] [Mtgvenue] Rtgdir telechat review o… Pete Resnick
- Re: [RTG-DIR] [Mtgvenue] Rtgdir telechat review o… Stewart Bryant
- Re: [RTG-DIR] [Mtgvenue] Rtgdir telechat review o… Brian E Carpenter
- Re: [RTG-DIR] [Mtgvenue] Rtgdir telechat review o… Eggert, Lars
- Re: [RTG-DIR] [Mtgvenue] Rtgdir telechat review o… John C Klensin
- Re: [RTG-DIR] [Mtgvenue] Rtgdir telechat review o… Stephen Farrell
- Re: [RTG-DIR] Rtgdir telechat review of draft-iet… Alissa Cooper
- Re: [RTG-DIR] [Mtgvenue] Rtgdir telechat review o… Pete Resnick
- Re: [RTG-DIR] [Mtgvenue] Rtgdir telechat review o… Alissa Cooper
- Re: [RTG-DIR] [Mtgvenue] Rtgdir telechat review o… Pete Resnick
- Re: [RTG-DIR] [Mtgvenue] Rtgdir telechat review o… Stewart Bryant
- Re: [RTG-DIR] Rtgdir telechat review of draft-iet… Adrian Farrel
- Re: [RTG-DIR] Rtgdir telechat review of draft-iet… Stewart Bryant
- Re: [RTG-DIR] [Mtgvenue] Rtgdir telechat review o… Eliot Lear
- Re: [RTG-DIR] [Mtgvenue] Rtgdir telechat review o… Matthew Ford
- Re: [RTG-DIR] Rtgdir telechat review of draft-iet… Eliot Lear
- Re: [RTG-DIR] [Mtgvenue] Rtgdir telechat review o… Alissa Cooper
- Re: [RTG-DIR] [Mtgvenue] Rtgdir telechat review o… John C Klensin