Re: [Mtgvenue] comments on draft-ietf-mtgvenue-iaoc-venue-selection-process-04

Stephen Farrell <stephen.farrell@cs.tcd.ie> Mon, 30 January 2017 12:45 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
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 8895E129458 for <mtgvenue@ietfa.amsl.com>; Mon, 30 Jan 2017 04:45:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.5
X-Spam-Level:
X-Spam-Status: No, score=-7.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-3.199, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 EmaJo_OOb17i for <mtgvenue@ietfa.amsl.com>; Mon, 30 Jan 2017 04:45:34 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5BAEF129450 for <mtgvenue@ietf.org>; Mon, 30 Jan 2017 04:45:34 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 98CDFBE2E; Mon, 30 Jan 2017 12:45:32 +0000 (GMT)
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u6s8wz3Rtgw3; Mon, 30 Jan 2017 12:45:32 +0000 (GMT)
Received: from [134.226.36.93] (bilbo.dsg.cs.tcd.ie [134.226.36.93]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 0B64DBE3E; Mon, 30 Jan 2017 12:45:32 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1485780332; bh=O7VvksqqWNLEInsyK6A72Lh7rI2zWZrx0S5DXYn6d8U=; h=Subject:To:References:From:Date:In-Reply-To:From; b=gjFIdt3j5ADT6hqJspauKok467/cAXoFD0Hpoa4IsTLrQlNI/A1+WAsug+XHSb1no WVK6wdtnYEh6MGByKKfptOAst85odoTOCxnZb3P8VoTCuNJh+r7c5q6ZnGUqvswrb7 DDXk8SuFZaEEQUUvk8Cn6iWFI7BtT3gTwGfuicg4=
To: Lou Berger <lberger@labn.net>, mtgvenue@ietf.org
References: <9139334c-9c5e-814d-4299-c6f5950039b8@cs.tcd.ie> <f9b2a33d-db49-54a0-a657-be58a08ff021@labn.net>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <a1a08b89-9088-07e0-d878-2c171c04602b@cs.tcd.ie>
Date: Mon, 30 Jan 2017 12:45:31 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <f9b2a33d-db49-54a0-a657-be58a08ff021@labn.net>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="------------ms000809040405050606050606"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/UIyWlxnMjkRT-CfponCtHWuaAtQ>
Subject: Re: [Mtgvenue] comments on draft-ietf-mtgvenue-iaoc-venue-selection-process-04
X-BeenThere: mtgvenue@ietf.org
X-Mailman-Version: 2.1.17
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: Mon, 30 Jan 2017 12:45:36 -0000

Hiya,

On 30/01/17 12:32, Lou Berger wrote:
> Stephen,
> 
>     Just focusing in on comments to section 5 (as I suspect the other
> comments will receive sufficient attention by others):
> 
> 
> On 1/29/2017 11:10 PM, Stephen Farrell wrote:
>> - section 5: this overall seems too prescriptive to me.  Do
>> we really think we'll need to follow this process *exactly*
>> in say 2027? I'd say making this all less prescriptive
>> would be better.
> 
> I disagree -- Given the importance, visibility, impact, divisiveness,
> etc of venue selection I think exactly this level of detail needs to be
> agreed to by the community.  I do see your point that this section is
> likely to need to be revisited more frequently than the rest of the
> document and would support publishing it in its own document.  In fact
> this section has been pretty stable and is probably ready for LC so such
> a document could be rapidly split out and published.

So how about emphasising more that this section is a guideline
that's expected to evolve, that what's listed here is the
current practice (assuming it is) and that the IAOC may change
this but must publish their changes and follow community
consensus on such changes (as evaluated by the IESG)? To be
clear, I mean adding such text to the start of section 5,
before 5.1.

> 
>> - 5.3 & 5.5: the links aren't a good idea (and are access
>> controlled which is unacceptable if not fixed).
> 
> Agreed this material can either be incorporated as an appendix.  Given
> the current evolving situation the flow chart on contingency planning is
> good info to have available to the community...

So I still get a 401 when I click those links - has the material
been published somewhere else that the WG could see? If not, I
think that has to happen before one could think about WGLC.

Cheer,
S.


> 
> Lou
> 
>