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

Andrew Sullivan <ajs@anvilwalrusden.com> Thu, 18 October 2018 06:51 UTC

Return-Path: <ajs@anvilwalrusden.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 6BE221292F1 for <mtgvenue@ietfa.amsl.com>; Wed, 17 Oct 2018 23:51:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=yitter.info header.b=Mj/LNJrL; dkim=pass (1024-bit key) header.d=yitter.info header.b=hO1eG7xh
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 5kzLTgftT-I6 for <mtgvenue@ietfa.amsl.com>; Wed, 17 Oct 2018 23:51:14 -0700 (PDT)
Received: from mx4.yitter.info (mx4.yitter.info [159.203.56.111]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 955F5128766 for <mtgvenue@ietf.org>; Wed, 17 Oct 2018 23:51:14 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx4.yitter.info (Postfix) with ESMTP id B0660BD3E8 for <mtgvenue@ietf.org>; Thu, 18 Oct 2018 06:50:43 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1539845443; bh=LPGoR4sh36gjdVfyzdT3oV+sulN90BGhusTYw4K+pQg=; h=Date:From:To:Subject:References:In-Reply-To:From; b=Mj/LNJrL6OvA1cwjD2kuTGexTZLRNVs7LzbvZJ1CSg3iRZBmzU/2D6CaaQYXQT5uy ou2pEEcUqdkzwNHY6fEECurnIOhE9zhUu4mGx9ujpLjB01zcJauytJ7wfPNiGtmxtR xK+2YTlewEyYRuh934jXjM8MZGXEOj12j/zYVQN0=
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx4.yitter.info ([127.0.0.1]) by localhost (mx4.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rBqKlz6R0HID for <mtgvenue@ietf.org>; Thu, 18 Oct 2018 06:50:42 +0000 (UTC)
Date: Thu, 18 Oct 2018 02:50:42 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1539845442; bh=LPGoR4sh36gjdVfyzdT3oV+sulN90BGhusTYw4K+pQg=; h=Date:From:To:Subject:References:In-Reply-To:From; b=hO1eG7xhZf9luMjvvTR6S9l8jQ/fhFHXXSveDbFJ73y0Hn1UPTH/ev3GNqrljaAj5 acxuexFCUPUQWeZpX9H9ey0FLwXpJ4ridp3TzotPkzeXmBBgR38zkrEXXSk71jO1Og ydJm3teNButqYWD7bV9+XpPyrGcREBqal5jVH7zg=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: mtgvenue@ietf.org
Message-ID: <20181018065041.43gcja2afcbsoylm@mx4.yitter.info>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <e462c84b-62ba-8be9-a783-522cec948115@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/MPfNVYvvqD29JTKUdy-Reizv8q0>
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 06:51:17 -0000

Hi,

On Thu, Oct 18, 2018 at 08:48:26AM +1300, Brian E Carpenter wrote:
> 2) I suspect that when the IETF Trust was created, we viewed it as
> part of IASA.

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.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com