IETF Logo Mail Archive

Re: [Mtgvenue] About draft-ietf-mtgvenue-iaoc-venue-selection-process

Alissa Cooper <alissa@cooperw.in> Fri, 19 October 2018 12:14 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 ABE4E130DD7 for <mtgvenue@ietfa.amsl.com>; Fri, 19 Oct 2018 05:14:09 -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=Qi9N3ZEe; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=CGamjdbZ
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 HswWPbQOymhO for <mtgvenue@ietfa.amsl.com>; Fri, 19 Oct 2018 05:14:07 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 698C4128B14 for <mtgvenue@ietf.org>; Fri, 19 Oct 2018 05:14:07 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 425D4222C2; Fri, 19 Oct 2018 08:14:06 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Fri, 19 Oct 2018 08:14:06 -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=z aPbPfY9YuymFXrst0a+ulvoRl1YblkfHtUr3YYIdRE=; b=Qi9N3ZEedHzYsMqPd Ew/MBlBW5L3+QGmcUxCnfz5D+RceGHyfp9TuOEZvF7xSTHTwVXT8ps6VUZk4G4wl xfCfBAWoqpOcYZ6VCgnhG0LHjjpeolOxiZcAKCmwaGSNnRAAW9fHdX0XpxH5h5d+ 4XBuVohyHRvrvqFiVAmsv2MWL41jLAE+6ARO9aFL7/upw37tMdhVgwEQA1zJ4UNg rAcwqJy1TV8nra7eqgaJou5EbWXOzG58rmW0wRqJM/KQn7k5ch3sVE5ftBNVt2dV t9d1x9cz0cvbMnhH7o3ZG392wDXFS6rNL/YCtzLliVZrf7iuygONXd/LrzHwgZwP E6S6Q==
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=zaPbPfY9YuymFXrst0a+ulvoRl1YblkfHtUr3YYId RE=; b=CGamjdbZX0QopnkOBmydfvvaruhwrb17VHc0E5fgOxyuXYBnTU7+VVm4R fdlT0b+DZ3NS7nUSppRglkO9jyVykyQiEwy8ErFjhRnrO+c6RPm1ljvjHNZX1Txu IpIvL+cMNj6yTguWaHl2IEe9UZrNTIDWafR7uB1t1hBprxQirhD0Lzf1u15p5kTs NSS7KHMampwCPCsXkn8Yhamgj4GFwzO0bvVtIHsI3Ninwc42vOsECdxtwXNjlQMB yGXAKal7xHUdd3FgoRuig+b2v73CrzgGSHRCP4vVf3LIbZNK9Q6HZ3F5zt2reuR9 OBUkMGyVtw4edvoGehL4tuLYiVEzg==
X-ME-Sender: <xms:jcrJW0Nq5WpuUgNpTS7CEc82gTyIo3cUQbQVk-80aVs_xE_Y-d1Lbw>
X-ME-Proxy: <xmx:jcrJWwPXJfgRxoLx7_BGuEQRHFtrXH1RyDqvdu3iiP8DN-F7_7QB0w> <xmx:jcrJW7_bMr4qQ_BgY5pIYL0WUajTyfGMwwnLO_7dV_yb7y4NNoKjhw> <xmx:jcrJW4Lxlf4j1bHpvp7WNW-OJUdEdaSHq3AL2GCjPjFFHSqNdPbVAQ> <xmx:jcrJW-fjaFEf23EZzj44SIP4hwIF5eJkT3ltZbAJcQ6_xQUqDgG4uA> <xmx:jcrJW1bqlmfwdTzUngVxv0BGTjRMtml1cVxxikdzcy0GhCq1Hgg14A> <xmx:jsrJW_kyzEvfjDSFWlRQaDQbvFtH64tmpsPay5LIlpo5-TQu6Z4cLg>
Received: from rtp-vpn5-436.cisco.com (unknown [173.38.117.76]) by mail.messagingengine.com (Postfix) with ESMTPA id A8482E455C; Fri, 19 Oct 2018 08:13:57 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <63CC2CD2-08D9-4FAA-9E1F-C04849E99ACE@gmail.com>
Date: Fri, 19 Oct 2018 14:13:50 +0200
Cc: Brian Carpenter <brian.e.carpenter@gmail.com>, Andrew Sullivan <ajs@anvilwalrusden.com>, mtgvenue@ietf.org, Lou Berger <lberger@labn.net>, Eliot Lear <lear@cisco.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <213A6B3D-D104-4248-86DB-AADC35F0506A@cooperw.in>
References: <328e9dfe-8e30-6388-68be-95b55af0a5b0@cisco.com> <1667ccb8a70.27ce.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <471f7ba9-0b9e-256c-513d-78559ff200a1@cisco.com> <58f9ebdd-355e-129f-a987-dab72bc5da6f@labn.net> <9472f4e7-86bc-121c-ae43-13fcdde451d4@cisco.com> <38ad1b3b-309c-4bdb-fe14-0bbd584bb808@labn.net> <adc56f21-0f57-0be0-799e-126072c62fe0@cisco.com> <1667f3a9670.27ce.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <6b18f4f3-1e5a-24ac-36e1-54c509139d25@cisco.com> <e462c84b-62ba-8be9-a783-522cec948115@gmail.com> <9B3F3D67-CB95-414D-BCDF-525FDE7E9722@cooperw.in> <f2147935-e5d2-11a5-f522-bc404af685b6@gmail.com> <63CC2CD2-08D9-4FAA-9E1F-C04849E99ACE@gmail.com>
To: Bob Hinden <bob.hinden@gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/l1zZzaVltJl5kT-lFOEQWVlFtRY>
Subject: Re: [Mtgvenue] About draft-ietf-mtgvenue-iaoc-venue-selection-process
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, 19 Oct 2018 12:14:10 -0000


> On Oct 18, 2018, at 10:00 PM, Bob Hinden <bob.hinden@gmail.com> wrote:
> 
> Brian,
> 
>> On Oct 18, 2018, at 12:37 PM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>> 
>> On 2018-10-18 19:47, Alissa Cooper wrote:
>> ....
>>>> 2) I suspect that when the IETF Trust was created, we viewed it as
>>>> part of IASA.
>>> 
>>> This seems even more confusing because the Trust is definitely not involved in venue selection.
>> 
>> Indeed not, but I was addressing the question of whether the term "IASA" is still useful.
>> 
>> On 2018-10-18 19:50, Andrew Sullivan wrote:
>> ....
>>> Whatever people thought at the time, IMO it was not actually part of
>>> IASA as set up, because the IAD did not have the authority within the
>>> Trust that s/he had as IAD for IASA activities.
>> 
>> But s/he was a voting member of the Trust, and we did haul the Trust into BCP101.
>> I agree that the situation was a bit ambiguous (not that it was ever a problem).
>> It's fine by me to think of the Trust as a stand-alone entity now.
>> 
> 
> I tend to agree, except that the Trust needs some money to operate.  I would have assumed that would come from the LLC.  Remind me how that happens?

The plan is for the LLC to contribute funds to the Trust, together with contributions from corporate sponsors.

Alissa

> 
> Bob
> 
> 
>

v2.23.0 | Report a Bug | By Email