Re: [Mtgvenue] Last Call: <draft-ietf-mtgvenue-meeting-policy-04.txt> (High level guidance for the meeting policy of the IETF) to Best Current Practice

Russ Housley <housley@vigilsec.com> Thu, 26 April 2018 21:52 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 CD00E12D7EC for <mtgvenue@ietfa.amsl.com>; Thu, 26 Apr 2018 14:52:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=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 04SMDeTaoRbS for <mtgvenue@ietfa.amsl.com>; Thu, 26 Apr 2018 14:52:47 -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 3193E12D7EA for <mtgvenue@ietf.org>; Thu, 26 Apr 2018 14:52:47 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 17A2E300A0E for <mtgvenue@ietf.org>; Thu, 26 Apr 2018 17:52:45 -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 uYx3qEHy506C for <mtgvenue@ietf.org>; Thu, 26 Apr 2018 17:52:43 -0400 (EDT)
Received: from a860b60074bd.home (pool-108-45-101-150.washdc.fios.verizon.net [108.45.101.150]) by mail.smeinc.net (Postfix) with ESMTPSA id CAD103002C7; Thu, 26 Apr 2018 17:52:43 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <DB05B47C-4B05-4ABD-9C29-0AB2212DECE3@gmail.com>
Date: Thu, 26 Apr 2018 17:52:44 -0400
Cc: IETF <ietf@ietf.org>, mtgvenue@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <64013D65-9E4E-4A71-AF61-F99FF7234030@vigilsec.com>
References: <152295916074.25912.932711807710247299.idtracker@ietfa.amsl.com> <B86A9648-9C63-481D-B4B8-9E981AB0FE73@vigilsec.com> <DB05B47C-4B05-4ABD-9C29-0AB2212DECE3@gmail.com>
To: Suresh Krishnan <suresh.krishnan@gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/qRBEwO6RevhPf0CPSVu5G-SqUWA>
Subject: Re: [Mtgvenue] Last Call: <draft-ietf-mtgvenue-meeting-policy-04.txt> (High level guidance for the meeting policy of the IETF) to Best Current Practice
X-BeenThere: mtgvenue@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 26 Apr 2018 21:52:49 -0000

Suresh:
> 
>  Thanks for your comments. Please find responses inline.
> 
>> On Apr 17, 2018, at 7:47 PM, Russ Housley <housley@vigilsec.com> wrote:
>> 
>> Thanks for putting this document together.  I have two minor comments.
>> 
>> First, in Section 2 the document says:
>> 
>>  Please note that the boundaries between those regions has been
>>  purposefully left undefined per WG consensus.
>> 
>> As a BCP, I think it would be more valuable to simply say:
>> 
>>  The boundaries between regions is purposefully left ambiguous.
> 
> Sounds good. Will make this change.
> 
>> 
>> 
>> Second, at the end of Section 2, the document says:
>> 
>>  How often we intend to do such meetings in the future should also be
>>  an open topic for discussion within the community.
>> 
>> I think the document should nail down who makes this decision.  I suggest:
>> 
>>  The timing and frequency of such exploratory meetings in the future
>>  is left to the IETF Chair, after discussion with the IESG and the
>>  community.
> 
> Sounds good. Does this text work?
> 
> "The timing and frequency of such exploratory meetings in the future will be based on IETF consensus as determined by the IETF chair”

Works for me.

Russ