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

Russ Housley <housley@vigilsec.com> Tue, 12 June 2018 21:30 UTC

Return-Path: <housley@vigilsec.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 7CDB4130ECD for <mtgvenue@ietfa.amsl.com>; Tue, 12 Jun 2018 14:30:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 mXhOAav3hKWN for <mtgvenue@ietfa.amsl.com>; Tue, 12 Jun 2018 14:30:54 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 69CAC130EBC for <mtgvenue@ietf.org>; Tue, 12 Jun 2018 14:30:54 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id A9CF0300A3D for <mtgvenue@ietf.org>; Tue, 12 Jun 2018 17:22:34 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id y4du0GKrAxbE for <mtgvenue@ietf.org>; Tue, 12 Jun 2018 17:22:32 -0400 (EDT)
Received: from a860b60074bd.home (pool-71-127-50-4.washdc.fios.verizon.net [71.127.50.4]) by mail.smeinc.net (Postfix) with ESMTPSA id 091AF300558; Tue, 12 Jun 2018 17:22:31 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Message-Id: <0E48423E-71CC-4B27-B9BC-255F63862020@vigilsec.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_324C4D9D-C133-4B12-8B42-8C41C546AC81"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Tue, 12 Jun 2018 17:22:33 -0400
In-Reply-To: <47011565-8d42-fe86-3591-94d86c6df2cd@cisco.com>
Cc: IESG <iesg@ietf.org>, "mtgvenue@ietf.org" <mtgvenue@ietf.org>, IETF <IETF@ietf.org>
To: Eliot Lear <lear@cisco.com>
References: <e9f6f6f5-f2af-6a89-09df-d423386c4af7@cisco.com> <987EFB85-2050-4229-B912-1F7229075246@vigilsec.com> <47011565-8d42-fe86-3591-94d86c6df2cd@cisco.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/CMnneLtuEW4Mq087M5smCHIK1ck>
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:30:56 -0000

> On Jun 12, 2018, at 1:20 PM, Eliot Lear <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.  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 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.

Russ