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

Lou Berger <lberger@labn.net> Tue, 16 October 2018 16:22 UTC

Return-Path: <lberger@labn.net>
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 AA0F5130DF1 for <mtgvenue@ietfa.amsl.com>; Tue, 16 Oct 2018 09:22:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
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: ietfa.amsl.com (amavisd-new); dkim=pass (768-bit key) header.d=labn.net
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 mi7zv5omoERn for <mtgvenue@ietfa.amsl.com>; Tue, 16 Oct 2018 09:22:37 -0700 (PDT)
Received: from gproxy2-pub.mail.unifiedlayer.com (gproxy2-pub.mail.unifiedlayer.com [69.89.18.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A15A3130DEE for <mtgvenue@ietf.org>; Tue, 16 Oct 2018 09:22:37 -0700 (PDT)
Received: from cmgw12.unifiedlayer.com (unknown [10.9.0.12]) by gproxy2.mail.unifiedlayer.com (Postfix) with ESMTP id 489381E0E39 for <mtgvenue@ietf.org>; Tue, 16 Oct 2018 10:22:37 -0600 (MDT)
Received: from box313.bluehost.com ([69.89.31.113]) by cmsmtp with ESMTP id CS7AgwZKJE0jMCS7BgNFk1; Tue, 16 Oct 2018 10:22:37 -0600
X-Authority-Reason: nr=8
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; 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=43RLJaehpuzS8RQbzkLNhr+NAwSZYUXY7K1dviqYoVs=; b=ZE22JnM0zCxmPJp5977sFsLpm7 rqu6bhFWkLWOXaUQPjv4pGjQgenF9Jgc4mv3VGz0TCmCRhTQp7honMV+ilBrAmlIGzhFedOR9rHlO B+mYHHabJiidmLj/wb522BHVM;
Received: from pool-100-15-106-211.washdc.fios.verizon.net ([100.15.106.211]:40272 helo=[IPv6:::1]) by box313.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.91) (envelope-from <lberger@labn.net>) id 1gCS7A-000857-QC; Tue, 16 Oct 2018 10:22:36 -0600
To: Eliot Lear <lear@cisco.com>, mtgvenue@ietf.org
Cc: Alissa Cooper <alissa@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>
From: Lou Berger <lberger@labn.net>
Message-ID: <38ad1b3b-309c-4bdb-fe14-0bbd584bb808@labn.net>
Date: Tue, 16 Oct 2018 12:22:35 -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: <9472f4e7-86bc-121c-ae43-13fcdde451d4@cisco.com>
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 - box313.bluehost.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - labn.net
X-BWhitelist: no
X-Source-IP: 100.15.106.211
X-Source-L: No
X-Exim-ID: 1gCS7A-000857-QC
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: pool-100-15-106-211.washdc.fios.verizon.net ([IPv6:::1]) [100.15.106.211]:40272
X-Source-Auth: lberger@labn.net
X-Email-Count: 4
X-Source-Cap: bGFibm1vYmk7bGFibm1vYmk7Ym94MzEzLmJsdWVob3N0LmNvbQ==
X-Local-Domain: yes
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/1woBkXx9Fse9zkCS7zW9W8CrZPI>
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: Tue, 16 Oct 2018 16:22:40 -0000

Hi Eliot,


On 10/16/2018 11:57 AM, Eliot Lear wrote:
> Lou,
>
> I'll let Alissa answer this further, but I'd ask you to answer my
> question.
I must have missed it, what question, the one that follows or a 
different one?

>   The IASA previously was an actual group and not just a
> function.
no IASA was an activity.  IAOC was the group.

>    Now what is left that is not covered by the LLC?
The LLC replaces the IAOC and is part of the revised (2.0) IASA 
structure - see https://tools.ietf.org/html/draft-ietf-iasa2-struct

Lou

> Eliot
>
>
> On 16.10.18 17:21, Lou Berger wrote:
>> Eliot,
>>
>> 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.
>>
>> Lou
>>
>> 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
>>> Mtgvenue@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mtgvenue
>> _______________________________________________
>> Mtgvenue mailing list
>> Mtgvenue@ietf.org
>> https://www.ietf.org/mailman/listinfo/mtgvenue
> _______________________________________________
> Mtgvenue mailing list
> Mtgvenue@ietf.org
> https://www.ietf.org/mailman/listinfo/mtgvenue