Re: [Mtgvenue] Issue 20: s/IAOC/IASA?

Pete Resnick <presnick@qti.qualcomm.com> Wed, 07 June 2017 14:01 UTC

Return-Path: <presnick@qti.qualcomm.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 6AB30127909 for <mtgvenue@ietfa.amsl.com>; Wed, 7 Jun 2017 07:01:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7
X-Spam-Level:
X-Spam-Status: No, score=-7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=qti.qualcomm.com
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 zR4c-gQmt3d3 for <mtgvenue@ietfa.amsl.com>; Wed, 7 Jun 2017 07:01:13 -0700 (PDT)
Received: from sabertooth01.qualcomm.com (sabertooth01.qualcomm.com [65.197.215.72]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8BA68126D74 for <mtgvenue@ietf.org>; Wed, 7 Jun 2017 07:01:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1496844073; x=1528380073; h=from:to:cc:subject:date:message-id:mime-version; bh=KBl+oFqG3Ba0D9Vcgtg2Qw2iTuUNwtv+z7AWzHWJAHk=; b=K/qHnCI3pCSmczJibDkkbgiZD3SfIou6I8Lawz1Z2Nou8yJF8/K7JtND hWKJ2xn/fbczW6GrNT0lE0Ad9iPUaAER+Na1mT++Vcmsl93gNzGlrvh1d tvcgoRgfvHX+/47p96ln1XAvSgI6y8Bq4mklfq3qdwGo70w2kIO5wncJT Q=;
X-IronPort-AV: E=Sophos;i="5.39,311,1493708400"; d="scan'208,217";a="107980153"
Received: from unknown (HELO Ironmsg03-R.qualcomm.com) ([10.53.140.107]) by sabertooth01.qualcomm.com with ESMTP; 07 Jun 2017 07:01:12 -0700
X-IronPort-AV: E=McAfee;i="5800,7501,8553"; a="1382902476"
X-MGA-submission: MDHPcI32EUHzkq/STssu0vFRRh6Bm0bRgsUYUb3zApPXV4Pm/9a+/OUh5g2JwV0dh4HHsNOZ2uVyW1cyNmYLL2xjGuwlSQu0bklLdhq3dXqXEFXLEyphuLGMKqIrYjssVIG0auhwZpfvJvRIl9GBqV6H
Received: from nasanexm01f.na.qualcomm.com ([10.85.0.32]) by Ironmsg03-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 07 Jun 2017 07:01:11 -0700
Received: from [10.64.124.45] (10.80.80.8) by NASANEXM01F.na.qualcomm.com (10.85.0.32) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Wed, 7 Jun 2017 07:01:10 -0700
From: Pete Resnick <presnick@qti.qualcomm.com>
To: Eliot Lear <lear@cisco.com>
CC: Stephen Farrell <stephen.farrell@cs.tcd.ie>, "mtgvenue@ietf.org" <mtgvenue@ietf.org>
Date: Wed, 07 Jun 2017 09:01:09 -0500
Message-ID: <E5919FD5-F5AB-4FF7-8407-4545E06CA528@qti.qualcomm.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_FD1A2F43-9605-48BE-8579-8E29BC6C5AC4_="
X-Mailer: MailMate (1.9.6r5347)
X-Originating-IP: [10.80.80.8]
X-ClientProxiedBy: NASANEXM01E.na.qualcomm.com (10.85.0.31) To NASANEXM01F.na.qualcomm.com (10.85.0.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/vKx-sKVQ0dUn-vmHDjwZ4Ye2bN4>
Subject: Re: [Mtgvenue] Issue 20: s/IAOC/IASA?
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 14:01:15 -0000

Just splitting this out into it's own thread. Please continue discussing.

On 7 Jun 2017, at 4:09, Eliot Lear wrote:

> Hi Stephen,
>
> I agree with both you and Brian that the current text is quite loose
> with the terms, but it's probably worth a bit more than a substitution.
> People blew up all over the IAOC for one particular decision, because
> most people beyond those who play Inside Baseball actually understand
> the difference between the IASA, IAD, and the IAOC.  And so some
> explanation is needed, and I'm a little concerned about getting too much
> into the IAOC's business in this draft, lest they reorganize themselves
> (say, with IASA 2.0) and then have to update this draft again (which I
> will bet NO ONE will want to do).  And so, as best we can I wonder if
> the right thing to do is to use some words like "the IAOC MUST see
> that..." {$X} (happens/doesn't happen).
>
> Eliot
>
> On 6/7/17 8:54 AM, Stephen Farrell wrote:
>>
>> 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.
>>
>>
>>
>> _______________________________________________
>> Mtgvenue mailing list
>> Mtgvenue@ietf.org
>> https://www.ietf.org/mailman/listinfo/mtgvenue