Re: [Mtgvenue] resolution of IESG comments for draft-ietf-mtgvenue-iaoc-venue-selection-process-15

Eliot Lear <lear@cisco.com> Tue, 12 June 2018 21:40 UTC

Return-Path: <lear@cisco.com>
X-Original-To: mtgvenue@ietfa.amsl.com
Delivered-To: mtgvenue@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64926130EAA; Tue, 12 Jun 2018 14:40:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.509
X-Spam-Level:
X-Spam-Status: No, score=-14.509 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 RSf6YaYqpvZz; Tue, 12 Jun 2018 14:39:59 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 44537124BE5; Tue, 12 Jun 2018 14:39:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10550; q=dns/txt; s=iport; t=1528839599; x=1530049199; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to; bh=2y0V/oEzUH/SKTx0d0cdg8oWYMm9WOQDbxzBOET2V8E=; b=m4Q/vuXKj19IBvt3tWukFRRfQHinF5I3WT+JbpP2aak50Q7SF00eO+pN MdqWw5T87mtRv2qZJRH6uolgkGUEmhn/O+KCM60CxyMEqXEGVIz0YsQZ6 CxCdJ9rMe+E00Oq+qGUrbPyXVJLd7GO6TJHlUR7OU31QAuEi7/9PLJe5k 0=;
X-Files: signature.asc : 488
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DfAQD2PCBb/5BdJa1cGQEBAQEBAQEBAQEBAQcBAQEBAYJOdYFhKIN4lGyBVil1jmuFD4FkCAOEbAKCMiE3FQECAQEBAQEBAm0ohSgBAQEDASNWBQsLGCcDAgJGEQYNBgIBARCDDgKBdwisGYIcH4gqgVkPiEiCE4EPJIIzNYRAAQsHAQeDGYJVApE2h1AJg0qBVoFDiBAGgT+GQoUxkTiBVyJhcTMaCBsVgn6CIRcRjiIjMI1JDxeCIgEB
X-IronPort-AV: E=Sophos;i="5.51,216,1526342400"; d="asc'?scan'208,217";a="406252339"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by rcdn-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 Jun 2018 21:39:58 +0000
Received: from [10.82.217.15] (rtp-vpn3-269.cisco.com [10.82.217.15]) by rcdn-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id w5CLdv2L032573; Tue, 12 Jun 2018 21:39:57 GMT
To: Russ Housley <housley@vigilsec.com>
Cc: IESG <iesg@ietf.org>, "mtgvenue@ietf.org" <mtgvenue@ietf.org>, IETF <IETF@ietf.org>
References: <e9f6f6f5-f2af-6a89-09df-d423386c4af7@cisco.com> <987EFB85-2050-4229-B912-1F7229075246@vigilsec.com> <47011565-8d42-fe86-3591-94d86c6df2cd@cisco.com> <0E48423E-71CC-4B27-B9BC-255F63862020@vigilsec.com>
From: Eliot Lear <lear@cisco.com>
Openpgp: preference=signencrypt
Autocrypt: addr=lear@cisco.com; prefer-encrypt=mutual; keydata= xsBNBFMe1UQBCADdYOS5APDpIpF2ohAxB+nxg1GpAYr8iKwGIb86Wp9NkK5+QwbW9H035clT lpVLciExtN8E3MCTPOIm7aITPlruixAVwlBY3g7U9eRppSw9O2H/7bie2GOnYxqmsw4v1yNZ 9NcMLlD8raY0UcQ5r698c8JD4xUTLqybZXaK2sPeJkxzT+IwupRSQ+vXEvFFGhERQ88zo5Ca Sa1Gw/Rv54oH0Dq2XYkO41rhxQ60BKZLZuQK1d9+1y3I+An3AJeD3AA31fJZD3H8YRKOBgqe ILPILbw1mM7gCtCjfvFCt6AFCwEsjITGx55ceoQ+t5B5XGYJEppMWsIFrwZsfbL+gP31ABEB AAHNJUVsaW90IExlYXIgPGxlYXJAb2Zjb3Vyc2VpbXJpZ2h0LmNvbT7CwJEEEwECADsCGwMC HgECF4ACGQEWIQSY0L2QRh2wkqeyYR2HtmtG2dJ6MwUCWxJwMwULCQgHAgYVCAkKCwIEFgID AQAKCRCHtmtG2dJ6MyMyCACXvtFjAYGMtOkD9MD4nI3ifFpkrj8xTMbXjrv5hdqmzRmQ0wqA 1U/OlZux+P/NaVMiZNZc8zw0nsx/INAqDOVd4/tLWF+ywTkeRFR0VnaUxLwCReZAZOaRS+md +52u/6ddoFja2RnjZ43qbbuvVUARQVIyMJz+GbR6mEZQHR0psD7dDYZDyrpivCxm8zHQwmB6 AZUlO7OJgljDvVPVDCabg/ZnJw1qS0OzSiNb0MySk1D5A7FdwDgeKxuMYUOOoVVTTMWNWcME UkRX9LxElswEt0PQWiz/j3FYXTxiFfl/1vKcHx4pM+E5C5mhTbrdFUFLJC3Y5fLID7stK/Ch aEaBzsBNBFMe1UQBCAC0WV7Ydbv95xYGPhthTdChBIpPtl7JPCV/c6/3iEmvjpfGuFNaK4Ma cj9le20EA5A1BH7PgLGoHOiPM65NysRpZ96RRVX3TNfLmhGMFr5hPOGNdq+xcGHVutmwPV9U 7bKeUNRiPFx3YdEkExddqV2E8FltT0x2FSKe2xszPPHB6gVtMckX5buI9p1K3fbVhXdvEkcY Y/jB0JEJGyhS5aEbct5cHUvDAkT81/YFK5Jfg8RRwu1q1t1YuIJSOWAZQ9J9oUsg6D9RpClU +tIFBoe3iTp1AUfJcypucGKgLYKtpu/aygcpQONHYkYW5003mPsrajFhReVF5veycMbHs4u5 ABEBAAHCwF8EGAECAAkFAlMe1UQCGwwACgkQh7ZrRtnSejOSuQgA27p2rYB7Kh20dym6V8c6 2pWpBHHTgxr/32zevxHSiXl6xvUCg5T8WUwfUk8OvgDcBErK/blDAMXQzSg3sp450JhR8RnX HXF5Zz2T04X7HnlIVJGwf2CjnwyEAJCqMzaCmI+g3Imvg/8L4nyBFvhlFHDv+kIvMiujyycj PAu7xxKplBs1/IEwmDoAMjneFmawvfeQnwdMhSKK8PjKSuzGU5uUmxj3GBfRqvTM0qpmhMPF OmDhJSmH55HLAky2MlmqJYXJPt/9EfSEhFiua1M6gLiuNEuPkp+8jcnHQqKr0IeHt8UqcwLt 2mGfIyl0FVdF9hvWPjNRzGbgqoT1Di03RQ==
Message-ID: <1ab44f41-fc7b-e55d-b409-6b22de796ee5@cisco.com>
Date: Tue, 12 Jun 2018 17:40:02 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <0E48423E-71CC-4B27-B9BC-255F63862020@vigilsec.com>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="uIIcVqeWZ5LZCZHQ3Lcd8toaxviSIeG9B"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/bwVvEsiXH4ZV2G6b-zQ5Ms5ihXA>
Subject: Re: [Mtgvenue] resolution of IESG comments for draft-ietf-mtgvenue-iaoc-venue-selection-process-15
X-BeenThere: mtgvenue@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: "List for email discussion of the IAOC meeting venue selection process." <mtgvenue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mtgvenue>, <mailto:mtgvenue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mtgvenue/>
List-Post: <mailto:mtgvenue@ietf.org>
List-Help: <mailto:mtgvenue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mtgvenue>, <mailto:mtgvenue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jun 2018 21:40:03 -0000


On 12.06.18 17:22, Russ Housley wrote:
>
>> On Jun 12, 2018, at 1:20 PM, Eliot Lear <lear@cisco.com
>> <mailto:lear@cisco.com>> wrote:
>>
>> Hi Russ,
>>
>>    
>>>>> 7.  Privacy Considerations
>>>>>
>>>>>    Different places have different constraints on individual privacy.
>>>>>    The requirements in this memo are intended to provide for some
>>>>>    limited protections. 
>>>
>>> I do not think that the memo itself provides any privacy
>>> protections.  Rather, the IAOC process described in the memo takes
>>> individual privacy as one factor in venue selection.
>>>
>>
>> Perhaps this goes to the AD's comment a bit more, but the only real
>> privacy protections involve how the network is managed, and that is a
>> requirement, not a process.
>
>
> Here is the whole section, which is a single paragraph:
>
>     7.  Privacy Considerations
>
>    Different places have different constraints on individual privacy.
>    The requirements in this memo are intended to provide for some
>    limited protections that attendees can apply.  As meetings are
>    announced, IASA SHALL inform the IETF of any limitations to privacy
>    they have become aware of in their investigations.  For example,
>    participants would be informed of any regulatory authentication or
>    logging requirements.  This note reveals no personally identifying
>    information apart from its authorship.
>
> I do not understand the use of "attendees can apply" in the second
> sentence. 

Right.  Nobody did.  It's trimmed.

> I think the requirements in this memo set some expectations, and then
> the next few sentence say that the IAOC shall tell the community about
> anything that is out of the norm.  But it does not really say that.

I think the point of the text is that if there are privacy limitations,
the community should be informed.



>
> I do not understand the last sentence.  This note reveals email
> addresses of the authors.  I think the last sentence should be removed
> or it should become an additional paragraph with more explanation.
>

Needs a new paragraph.