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

Stephen Farrell <stephen.farrell@cs.tcd.ie> Mon, 30 January 2017 18:58 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 3D84C129AB7 for <mtgvenue@ietfa.amsl.com>; Mon, 30 Jan 2017 10:58:26 -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 C6GGOJjJHuek for <mtgvenue@ietfa.amsl.com>; Mon, 30 Jan 2017 10:58:24 -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 1FD0312957C for <mtgvenue@ietf.org>; Mon, 30 Jan 2017 10:58:24 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 3116FBE4C; Mon, 30 Jan 2017 18:58:22 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
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 Oz3vlQRq1Mxv; Mon, 30 Jan 2017 18:58:21 +0000 (GMT)
Received: from [10.87.48.75] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 8907CBE3E; Mon, 30 Jan 2017 18:58:20 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1485802700; bh=LvbGvIVf0F8fRl1CkyUTw1kJMLms6OOTIHfXLJqQIf8=; h=Subject:To:References:From:Date:In-Reply-To:From; b=C8HU2GPI+Uta3Bi7Y8NDttzy4/UqDqU2tE2RC+oLqgqAC3smzhvHQzH3pWdO1GHsz XxcoVug8OdPF7ra5AT0o1QPff/eCbKbOlpvBYMsZ7DXDLW7xJaF8NSmFaSMJIaHETw j+dD/DH6MpZz//A9lBinJ/Yc1/S98mHBVBq1RxOo=
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> <bd1e3bce-7bfd-cb65-4017-a763f415d7cd@cs.tcd.ie> <3adf8871-cec3-1555-099d-3c32bcf37315@dcrocker.net>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <364b3495-4142-c92b-1489-0939026f44c8@cs.tcd.ie>
Date: Mon, 30 Jan 2017 18:58:20 +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: <3adf8871-cec3-1555-099d-3c32bcf37315@dcrocker.net>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="------------ms060508020100040103000009"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/TT7nqmjdhOPDpfYvn3BxIbXMAEc>
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 18:58:26 -0000


On 30/01/17 17:37, Dave Crocker wrote:
> On 1/30/2017 8:20 AM, Stephen Farrell wrote:
>>  But I was suggesting that the IAOC
>> document how their algorithm/processes (as outlined in section 5)
>> change over time.
> 
> That's the task of revising this document.  The document covers
> procedures.  As noted by a separate exchange this morning, that might
> make it appropriate to factor some of the current text into a separate
> document, to localize the change effort.
> 
> Is there some reason the basic question of documenting changed
> procedures should be handled differently than we do for other
> specifications?

Yes. IMO the procedures/processes set out in the RFC we'll
end up with will change significantly more often than the
RFC will be revised. In the interests of improved IAOC
transparency, (which I think we've agreed is a goal here)
it'd be good if variations from that are documented somehow
(however IAOC like is fine by me) in a way that's visible
to the community and subject to community consensus. That
mostly applies to section 5, but also perhaps to other
sections. (I'd have no problem if that was a general thing
nor if it were specific to section 5.)

S.

> 
> 
> 
> d/
>