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

Stephen Farrell <stephen.farrell@cs.tcd.ie> Mon, 30 January 2017 16:20 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 2DEF112951D for <mtgvenue@ietfa.amsl.com>; Mon, 30 Jan 2017 08:20:31 -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 T0WeGgKlo9Xd for <mtgvenue@ietfa.amsl.com>; Mon, 30 Jan 2017 08:20:29 -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 9DC7512953A for <mtgvenue@ietf.org>; Mon, 30 Jan 2017 08:20:28 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 058E0BE2E; Mon, 30 Jan 2017 16:20:27 +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 dby72MqE--Gw; Mon, 30 Jan 2017 16:20:26 +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 6CCA9BDCC; Mon, 30 Jan 2017 16:20:26 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1485793226; bh=JbgMorUupJ23Tmajkr0vIf7n8nKj9ChzGWGxlKF7qUY=; h=Subject:To:References:From:Date:In-Reply-To:From; b=KnLtIH+jjjnSXvgDwkTyrodOpwbT9f8hFRfQahMc6MA+tfaTScoDjdlal5yfdHit8 yvsY/rHKtsE6ZiCE5qa0W7K5arMJf3J8jzHYWs/YDrSp265pwIXwdFLQgOo8vPw6MQ D4HN/R5PzmOwMSNAuJ1haAdd2QatI4JUnIyseNCs=
To: dcrocker@bbiw.net, mtgvenue@ietf.org
References: <9139334c-9c5e-814d-4299-c6f5950039b8@cs.tcd.ie> <f9b2a33d-db49-54a0-a657-be58a08ff021@labn.net> <a1a08b89-9088-07e0-d878-2c171c04602b@cs.tcd.ie> <d5d75e80-1285-f510-709e-9f1e24240ec5@dcrocker.net> <518a705f-096d-cc4d-6402-5ae605c71f36@cs.tcd.ie> <1babea2c-10ad-113d-0537-4d4c49628350@dcrocker.net>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <bd1e3bce-7bfd-cb65-4017-a763f415d7cd@cs.tcd.ie>
Date: Mon, 30 Jan 2017 16:20:25 +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: <1babea2c-10ad-113d-0537-4d4c49628350@dcrocker.net>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="------------ms070109090503010002010900"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/cfZjJMrBrc31cjl8GEEeS8MGamU>
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 16:20:31 -0000

Hiya,

On 30/01/17 16:14, Dave Crocker wrote:
> On 1/30/2017 7:57 AM, Stephen Farrell wrote:
>> On 30/01/17 15:34, Dave Crocker wrote:
>>> On 1/30/2017 4:45 AM, Stephen Farrell wrote:
>>>> So how about emphasising more that this section is a guideline
>>>> that's expected to evolve,
> ...
>>> Stephen,
>>>
>>> A number of your suggestions show this kind of basis:  Things might
>>> change and we should say something about that.
>>>
>>> In specification-writing terms, this has no utility.
> ...
>> In any case, I disagree about section 5 - my suggestion has
>> the substantive statement that the IAOC would publish the
>> ways in which they're diverging from the text there and that
>> the community get to say what they/we think of that. You
>> may consider that solely a form of entertainment, I do not.
> 
> 
> Having the IAOC document how a particular venue selection has diverged
> from the existing specification 

I think that'd be useful. But I was suggesting that the IAOC
document how their algorithm/processes (as outlined in section 5)
change over time.

> is quite different from a suggestion
> that the specification contain language noting that things might change
> (at some unknown point in the future and in some unknown ways.)
> 
> My comment was about the several points in your original note that were
> of the latter type.

I'm not sure how you got that from the text you quoted.
But that's ok, if we agree that section 5 needs some work
along the above lines (or to otherwise solve the issue)

S.

> 
> d/
> 
> 
> 
>