IETF Logo Mail Archive

Re: [Mtgvenue] Issue resolution (Was: New Version Notification for draft-ietf-mtgvenue-iaoc-venue-selection-process-07.txt)

Stephen Farrell <stephen.farrell@cs.tcd.ie> Wed, 07 June 2017 06:54 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 7C618127337 for <mtgvenue@ietfa.amsl.com>; Tue, 6 Jun 2017 23:54:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.302
X-Spam-Level:
X-Spam-Status: No, score=-4.302 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=-0.001, 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 0ksGSP1kARWY for <mtgvenue@ietfa.amsl.com>; Tue, 6 Jun 2017 23:54:22 -0700 (PDT)
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 150CA1201FA for <mtgvenue@ietf.org>; Tue, 6 Jun 2017 23:54:22 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 41BE3BE50; Wed, 7 Jun 2017 07:54:20 +0100 (IST)
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 g8bQIooMfj6v; Wed, 7 Jun 2017 07:54:19 +0100 (IST)
Received: from [10.244.2.100] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id C7E44BE38; Wed, 7 Jun 2017 07:54:18 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1496818459; bh=6+JudlfnSk0WdnhriQq76/w/Z83/jGVn9ALzKZdeGtA=; h=Subject:To:References:From:Date:In-Reply-To:From; b=khgFX3dtJcZhEPrZSg6RBgPmm7/tt6FwGjQ0LtNlUpPja9W+YUp08R14EzOrmfm6Y 2JyhisSZe2huQAiUyvfyUfVaxUwtWA73Sw7mKBlqkxlhzQJgWvFJG3L2NgH3Lxbfl7 dVtjoVLpnwxpDwpPT4dWRjR0/rBpRzTJOKDEvRpI=
To: Pete Resnick <presnick@qti.qualcomm.com>, "mtgvenue@ietf.org" <mtgvenue@ietf.org>
References: <149476468729.2939.13565256113481725918.idtracker@ietfa.amsl.com> <2faf7a9d-7e0a-1eaa-9d0b-cd7e81559e2b@cisco.com> <D9CF49A9-4AC6-4CBC-96F9-7AC89B47A3C0@qti.qualcomm.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <7deab350-3af9-559a-d3b0-ea2816e15fa7@cs.tcd.ie>
Date: Wed, 07 Jun 2017 07:54:18 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1
MIME-Version: 1.0
In-Reply-To: <D9CF49A9-4AC6-4CBC-96F9-7AC89B47A3C0@qti.qualcomm.com>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="5F2scVoXwuFqa6amSMrJuM50uOukIq20k"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/QGr8jMNw9j0BI7HKw-605id84zs>
Subject: Re: [Mtgvenue] Issue resolution (Was: New Version Notification for draft-ietf-mtgvenue-iaoc-venue-selection-process-07.txt)
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: Wed, 07 Jun 2017 06:54:24 -0000


On 07/06/17 03:17, Pete Resnick wrote:
> 
> - Issue 20, "s/IASA/IAOC?" (which is actually titled backwards, since
> the suggestion was to change IAOC to IASA pretty much throughout): Not
> enough to go on.

I think Brian has a good point there - the draft is describing
stuff intended to be overseen by the IAOC but that is perceived
to be done by the IAOC. It's not clear to me which of those the
members of the IAOC and it's committees consider to be the case
in practice.

So I reckon yes it'd be correct to make the substitution.

That will however make the draft harder to understand for all of
us who've forgotten the IASA acronym, but who (like me;-) have
and recall others having whined at the IAOC periodically, so I'd
also be fine with just adding text that explains that when we say
IAOC in this draft, we maybe mean IASA, and that that contradiction
is being considered elsewhere.

S.

v2.23.0 | Report a Bug | By Email