Re: [Mtgvenue] [Iasa20] Terminology issue in mtgvenue

Alissa Cooper <alissa@cooperw.in> Fri, 26 October 2018 12:22 UTC

Return-Path: <alissa@cooperw.in>
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 A36E8130DC2; Fri, 26 Oct 2018 05:22:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 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_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=CdDSbWfX; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=ADJRyekr
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 LDr7v6Cd296K; Fri, 26 Oct 2018 05:21:59 -0700 (PDT)
Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BB527127333; Fri, 26 Oct 2018 05:21:59 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.west.internal (Postfix) with ESMTP id 7C795D97; Fri, 26 Oct 2018 08:21:58 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Fri, 26 Oct 2018 08:21:58 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm1; bh=k hVYFAJ1d5PXl3hXrRbQ8OOsLmPRTUQ+A7xsfvxXIPw=; b=CdDSbWfX5sO4Sp+md VwLuysdioXWrhO53ImL7Y5jOO4jFtblM4bIFtG2KcEn+/cL1f16lOae7KaiksOS8 sCsHpLom50HMCjL62UwQA25D8ctP9mP4uz14Ya0P4BSBrsFmKxWTQSakvV6QtyZk Owwi1J/K5rrTYs4O2/8CG9j9ZD+BFWZEjTIrP4qUzgZ8kGENTN97aiuAx4klmJWA AcwCNFcNWdxos5AbAqPLCyhTLZJUJ3mR2EVcnL4biInYY01AyY/Pb1fJc6XlFTUf Wzve+OiZh6BrBwtEpgbTGrcHc0ki+Bfs1qPYpLDyBuATEwRMF1CvhDmc0N6DZT5K 9dIfA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=khVYFAJ1d5PXl3hXrRbQ8OOsLmPRTUQ+A7xsfvxXI Pw=; b=ADJRyekrsHL6wRa+S+Lavaq6WuJwXn/HWBLZ3b4bQTUOO4I0NZ6K8POOx 19jV9X61NTxFxL4/pjJMAHtJrZfs/AcKTPBA3iU8ZUsOEYFa8XsyAzYqBTFOBCVw 8oZFj3qA250i+82AEYm+oC/B5YsYlFFh/9b7fsM8Wga0i3prMmv7bCGnyhRxEfJC q50wjyWNZk91GS9PRemDACy5EeLk5UBx36royZo4i+sd38XM8buhy6XhQJhzh1ji Bnck36dEoMP8DytDpU37x2lWe8pOeFQDrdlLqvpgjrRSWzsLsIoZE9JA+7+Sqbd5 4xZtcunWvr4p/bJF+Lk2MlE3kOFwQ==
X-ME-Sender: <xms:5QbTW-HrSTRjE60vQz6sTmzVskAUJr3sh0SEYDyrKCb9KYjoGxMfbQ>
X-ME-Proxy: <xmx:5QbTWzUP9zk9lvfkTdyODkwcexNmmsTsPo5tj632VAyXVEqNrRSgbQ> <xmx:5QbTWxm3SnlKVyncec_2uuCVdYTQsdI2fYuxH9b7j3Z0UMmFRUk2Zg> <xmx:5QbTW9BhpXK5i5uNelgmOpTcLbTLNDyhyGGn--03rsp0r81NvhnSuQ> <xmx:5QbTW5fO5RnBobz6TR-LTuNBgl9kDuCpYcKt26H91qRUraJLfnFnTA> <xmx:5QbTWwIeb82arIE4tiqoEG0GDkryXYnz_tplzsW35xzfKlLhXFv8Ng> <xmx:5gbTWzBSteQT-TJZBq8zty4imws3CCsMWeQJYLSeHIWm24ybzelF7Q>
Received: from rtp-vpn4-684.cisco.com (unknown [173.38.117.79]) by mail.messagingengine.com (Postfix) with ESMTPA id 437F8E4894; Fri, 26 Oct 2018 08:21:56 -0400 (EDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <5D35E1D4-220A-41F7-B552-61D0C5586A2B@cable.comcast.com>
Date: Fri, 26 Oct 2018 14:21:53 +0200
Cc: Pete Resnick <resnick@episteme.net>, "iasa20@ietf.org" <iasa20@ietf.org>, "mtgvenue@ietf.org" <mtgvenue@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <399BB3CA-4EAD-422F-B8A0-2A9758FDA3F8@cooperw.in>
References: <8F025819-6D43-4D09-858E-0866532FEBDC@episteme.net> <5D35E1D4-220A-41F7-B552-61D0C5586A2B@cable.comcast.com>
To: "Livingood, Jason" <Jason_Livingood@comcast.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/a0OElVpWtYSFNYLg4asPl2kDIPo>
Subject: Re: [Mtgvenue] [Iasa20] Terminology issue in mtgvenue
X-BeenThere: mtgvenue@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 26 Oct 2018 12:22:03 -0000

Is there any update on this? 

Thanks,
Alissa

> On Oct 19, 2018, at 11:51 PM, Livingood, Jason <Jason_Livingood@comcast.com> wrote:
> 
> Thanks for this heads-up, Pete! We in the IASA2 WG will put this in our work queue. I will take a look as co-chair early next week and try to actively start up list discussion on the details.
> 
> Jason
> 
> On 10/19/18, 5:38 PM, "iasa20 on behalf of Pete Resnick" <iasa20-bounces@ietf.org on behalf of resnick@episteme.net> wrote:
> 
>    IASA 2.0 folks:
> 
>    With my mtgvenue chair hat on: An issue has come up over in mtgvenue 
>    that I think really needs to be resolved by iasa20, and in particular 
>    not by the mtgvenue folks alone.
> 
>    The Venue Selection document, 
>    <https://datatracker.ietf.org/doc/draft-ietf-mtgvenue-iaoc-venue-selection-process/>, 
>    refers to "IASA" throughout. When written, the document presumed that we 
>    were working under IASA 1.0, and had references to RFC 4071. When our 
>    documents got to AUTH48, we realized that it was going to come out right 
>    on the heels of the IASA 2.0 docs and that it would be silly to publish 
>    only to have to turn around and fix things. The initial suggestion in 
>    mtgvenue was to pretty much do a global replace of "IASA" with "IETF 
>    LLC" (with some other editorial changes). The document editor's version 
>    with those edits is here: 
>    <https://www.rfc-editor.org/authors/rfc8491-auth48diff.html>. However, a 
>    few folks (and in particular, folks who are active in iasa20) noted that 
>    in fact "IASA" was correct, because under IASA 2.0, the LLC is under 
>    IASA, and that using "LLC" might be incorrect in some instances. 
>    Conversely, some folks thought that "LLC" was a clearer reference. As 
>    that discussion has evolved, your faithful mtgvenue chair is no longer 
>    sure that we've gotten this exactly right. On top of that, Alissa has 
>    indicated that it's probably better to have iasa20 figure out what 
>    terminology is appropriate to refer to the assorted entities, for the 
>    sake of all documents, not just mtgvenue's.
> 
>    So, I would ask that the iasa20 WG review the above two documents and 
>    let us know whether we've got it right or wrong, and generally let us 
>    know which terminology should be used in which circumstances. I'm sure 
>    mtgvenue folks will pipe up with their concerns, but guidance should 
>    really be coming from a discussion in iasa20.
> 
>    BTW: Don't worry about the fact that the document is in AUTH48 or 
>    whether it will need a new Last Call or whatever. Let's get the document 
>    correct first, and then we'll figure out what process knobs, lights, and 
>    buttons need to be operated.
> 
>    Cheers,
> 
>    pr
>    -- 
>    Pete Resnick http://www.episteme.net/
>    All connections to the world are tenuous at best
> 
>    _______________________________________________
>    iasa20 mailing list
>    iasa20@ietf.org
>    https://www.ietf.org/mailman/listinfo/iasa20
> 
> 
> _______________________________________________
> iasa20 mailing list
> iasa20@ietf.org
> https://www.ietf.org/mailman/listinfo/iasa20