IETF Logo Mail Archive

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

Russ Housley <housley@vigilsec.com> Tue, 12 June 2018 13:56 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 9DDC7130E35 for <mtgvenue@ietfa.amsl.com>; Tue, 12 Jun 2018 06:56:17 -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 6fveiMFsWAnS for <mtgvenue@ietfa.amsl.com>; Tue, 12 Jun 2018 06:56:14 -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 A63E3130E27 for <mtgvenue@ietf.org>; Tue, 12 Jun 2018 06:56:14 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 6DF98300A1E for <mtgvenue@ietf.org>; Tue, 12 Jun 2018 09:56:12 -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 SDKsyMnk-Eny for <mtgvenue@ietf.org>; Tue, 12 Jun 2018 09:56:10 -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 B18EF300538; Tue, 12 Jun 2018 09:56:10 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Message-Id: <987EFB85-2050-4229-B912-1F7229075246@vigilsec.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_702F52BC-5C5E-45D4-BD00-95718D8ED63C"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Tue, 12 Jun 2018 09:56:15 -0400
In-Reply-To: <e9f6f6f5-f2af-6a89-09df-d423386c4af7@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>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/TMTAfL4RmlSSjSmfdfmbi-INeZc>
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 13:56:18 -0000

> On Jun 12, 2018, at 8:42 AM, Eliot Lear <lear=40cisco.com@dmarc.ietf.org> wrote:
>> Section 7
>> 
>>    The requirements in this memo are intended to provide for some
>>    limited protections that attendees can apply.
>> 
>> This reads oddly to me -- we provide for limited
>> privacy protections that attendees can choose to apply but are not
>> universally applied without explicit action?  What are they?
>> The text would read more naturally to me as "to provide for some
>> limited protections that apply to attendees", though that does of
>> course have a different meaning.
> I propose the following:
> 
>> 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.

Russ

v2.23.0 | Report a Bug | By Email