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

Lou Berger <> Tue, 16 October 2018 15:25 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id EFA30130DE6 for <>; Tue, 16 Oct 2018 08:25:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (768-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id io5JUyIvzjYy for <>; Tue, 16 Oct 2018 08:25:31 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id DEC9612D4E6 for <>; Tue, 16 Oct 2018 08:25:31 -0700 (PDT)
Received: from (unknown []) by (Postfix) with ESMTP id 3169C1405B3 for <>; Tue, 16 Oct 2018 09:22:00 -0600 (MDT)
Received: from ([]) by cmsmtp with ESMTP id CRAVgd4Iaj0soCRAWgFBfK; Tue, 16 Oct 2018 09:22:00 -0600
X-Authority-Reason: nr=8
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version :Date:Message-ID:From:References:Cc:To:Subject:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=7T5jo4LvRtkjAH9Y7Ey7YCczv4PDz06I1BcHoFfO8Eo=; b=z0rZDjnP/siw6rj4A2IB2PSS8L jnlmYEqfRd1/ojM2TdX9sWsnfPRU6fseqW8LoMQyPh6FmdGkKpI1D9HDuVnWkHOAZCk0DFFsLIn0p qaILxFzr55Lc0xDiulDs+Ucio;
Received: from ([]:40140 helo=[IPv6:::1]) by with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.91) (envelope-from <>) id 1gCRAV-004Btr-QD; Tue, 16 Oct 2018 09:21:59 -0600
To: Eliot Lear <>,
Cc: Alissa Cooper <>
References: <> <> <>
From: Lou Berger <>
Message-ID: <>
Date: Tue, 16 Oct 2018 11:21:58 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname -
X-AntiAbuse: Original Domain -
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain -
X-BWhitelist: no
X-Source-L: No
X-Exim-ID: 1gCRAV-004Btr-QD
X-Source-Sender: ([IPv6:::1]) []:40140
X-Email-Count: 8
X-Source-Cap: bGFibm1vYmk7bGFibm1vYmk7Ym94MzEzLmJsdWVob3N0LmNvbQ==
X-Local-Domain: yes
Archived-At: <>
Subject: Re: [Mtgvenue] About draft-ietf-mtgvenue-iaoc-venue-selection-process
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for email discussion of the IAOC meeting venue selection process." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 16 Oct 2018 15:25:34 -0000


I think you are conflating IASA with IAOC.  IASA is being updated to 
replace the IAOC with the LLC.  By leaving the document as is, the 
document won't have to be update if we change how IASA is implemented in 
the future.  I think the other RFC updates that need to be done to 
remove references to IAOC highlight how keeping IASA in this document is 
really the right answer.


PS I think the following change is particularly unneeded:
     the ISOC Board of  Trustees, from which the LLC Board is constructed.

On 10/16/2018 8:58 AM, Eliot Lear wrote:
> On 16.10.18 14:13, Lou Berger wrote:
>> Hi Eliot,
>> Given the LLC is more specific than, i.e., part of, IASA why is this
>> change needed or even a good idea?
> I'm not an IASA 2.0 expert, and of course I could be wrong, but from my
> vantage point, what you might think of as the IASA is really just the
> LLC.  So far as I can tell, All functions from the old IASA are
> transferring either into the LLC or beyond the bounds of what was the
> IASA. Given that the distinction is lost, there is value in losing the
> IASA monogram so as to avoid confusion with the old structure.
> Eliot
> _______________________________________________
> Mtgvenue mailing list