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

Bob Hinden <bob.hinden@gmail.com> Thu, 18 October 2018 20:00 UTC

Return-Path: <bob.hinden@gmail.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 4AFB2130DC7 for <mtgvenue@ietfa.amsl.com>; Thu, 18 Oct 2018 13:00:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 PdZ2uQwx1E6N for <mtgvenue@ietfa.amsl.com>; Thu, 18 Oct 2018 13:00:56 -0700 (PDT)
Received: from mail-pg1-x530.google.com (mail-pg1-x530.google.com [IPv6:2607:f8b0:4864:20::530]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 032DE1286E3 for <mtgvenue@ietf.org>; Thu, 18 Oct 2018 13:00:56 -0700 (PDT)
Received: by mail-pg1-x530.google.com with SMTP id n31-v6so14683958pgm.7 for <mtgvenue@ietf.org>; Thu, 18 Oct 2018 13:00:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=IiLPZkiQUmIp2frRNNMdtKKIq5oJfvTOgnU9TjfnTeY=; b=eIOrjnCPbXgM+3qWjDHDHsF1eH9C1Wn1Az7iQydADwW1u235E55uuD59duKpMSlOlu L9SkFfWwOkzpV4dkdSPC9LsO5jQMJW+J+0UcJpphYAnnA/zYQdv40ju+JgpdnRuws5bO oP3Gma8KK0/2tKq1SuB1WnIldAcIQ/IazEmoMWbmJTBnNSYtyCfx7uqo60He8QKknFTq AOo4iE6cFbPqO2izbwtAU4HVsouOEY3Ua/V0p61wOUMPqL74qGsUUA1UNg+TMMCDgMNv EE8eEEfTtgY9Umepu/a9vFACf/ZtVZKDH1tiamQ74xujGcEHn+q5YZcbKHg9z/0cgSQg EoFw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=IiLPZkiQUmIp2frRNNMdtKKIq5oJfvTOgnU9TjfnTeY=; b=Ex+g1aptp8Z4DKffCboFflCeZUSf1EfdMc5osL8M1+QsjwHgdn3rEFES7+Ph4IhyD5 rH+AC6Qo9Ew0e2ZyNALMjc1zs73XuvK+3BhR2cdvTFMGECIMBqKPqBbcZmdq93vdllUT eP1veCv77aabeC/LzrFJc7MfzgJSnUcyqM8QoPq9QOB0PE5HCn9AiTjcSL/pLROuVCEM LOK6MK4ONTV1ooy3RlxChlnRv74Px8khfdFTtGUsG8nAAwIiqUMoP78FbDfB/1rbNW9B i//LzQhTzF+vb9DODkyZMm26X9w9AqTJGLgGLkaxHz1lTD8M0W6DCcER/7f8XKuIxvOl sjDg==
X-Gm-Message-State: ABuFfogik/se6ar9RgQlNVmlHYrxwxmHgwvEFSZzMyvL4t6jVZqw4mEp bAGMUvS7ZkZFvk4BNFs7MX8=
X-Google-Smtp-Source: ACcGV61ahbRlKZCzBbcS78N+tRc1u3lEfh8Djj5uaUQWV+mDCt3nPCTjRYc3r5Il2ATZSDrTJa/FtQ==
X-Received: by 2002:a63:4384:: with SMTP id q126-v6mr29849517pga.142.1539892855606; Thu, 18 Oct 2018 13:00:55 -0700 (PDT)
Received: from [172.16.224.219] ([209.97.127.34]) by smtp.gmail.com with ESMTPSA id r81-v6sm37284262pfa.110.2018.10.18.13.00.54 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 18 Oct 2018 13:00:54 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <63CC2CD2-08D9-4FAA-9E1F-C04849E99ACE@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_44A78CD0-610E-430D-9D8A-49F6D4915B20"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Thu, 18 Oct 2018 13:00:53 -0700
In-Reply-To: <f2147935-e5d2-11a5-f522-bc404af685b6@gmail.com>
Cc: Bob Hinden <bob.hinden@gmail.com>, Alissa Cooper <alissa@cooperw.in>, Andrew Sullivan <ajs@anvilwalrusden.com>, mtgvenue@ietf.org, Lou Berger <lberger@labn.net>, Eliot Lear <lear@cisco.com>
To: Brian Carpenter <brian.e.carpenter@gmail.com>
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>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/SuW_mqZtQtJeakze9yZ5h7ie-Po>
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: Thu, 18 Oct 2018 20:00:59 -0000

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?

Bob