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

Bob Hinden <bob.hinden@gmail.com> Tue, 16 October 2018 16:08 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 CA506130DF5 for <mtgvenue@ietfa.amsl.com>; Tue, 16 Oct 2018 09:08:24 -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 gP4bYm957oTc for <mtgvenue@ietfa.amsl.com>; Tue, 16 Oct 2018 09:08:22 -0700 (PDT)
Received: from mail-ed1-x535.google.com (mail-ed1-x535.google.com [IPv6:2a00:1450:4864:20::535]) (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 DA375130DF1 for <mtgvenue@ietf.org>; Tue, 16 Oct 2018 09:08:21 -0700 (PDT)
Received: by mail-ed1-x535.google.com with SMTP id l14-v6so12912378edq.0 for <mtgvenue@ietf.org>; Tue, 16 Oct 2018 09:08:21 -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=gSvKmC9GzYz3NpUd+LL/01HQ3L2VkUHOLa2A76GC6f4=; b=HCCpXfD0RIar2JbZXT9+GZXIUcOWkYZcHqNh5dIdMP7tOSKk39JYNmdqXzmNhyE1ve +TsqhG5seuSh6eAAMwJphKwGEGwh9D2jEfE46fZmnKzArvNKcaPzncU9XsZpHRx0XPyp rc6pcNpDOCnMlXEtCLNEtkvmO60wcylTXiv4WMXjktAwnTSXeKA0FAA+FrlW5OtuP+7a j+gtLojSDn3dCtxXUuRoD4F96pSz2jytiTl8uydOMepdAqoAub/PjsQfPx6TuqWDOOU4 aHfW6HUgOukuZ8D2txDe+CWWIOhBKe+1G6Q1UKR0YugmBaiLyIclVFZOJEGj0a8BCvJU 9E/w==
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=gSvKmC9GzYz3NpUd+LL/01HQ3L2VkUHOLa2A76GC6f4=; b=Ecx2kOHFr3P287EZhQEPV62bIYpSen+d1TdycCRryCvXMXyAHMFq0UJcqVpx1kUq7u hGvochHRq7lwZjdeB7FrehZJ9ImvwPwqerr0x+j+JBx0tmukFQA6mBBmTOH53yOByDhv UrwIhwhyTfJd8c3BVf+dFJ4Oka9L/bnp3k/ZtG33+5FjPtKc0xVLlR0X0VfOuqVzFed1 1bj2pkv50wUNRZpg1ejRH2E0pmCVznbLZNMcROx80PgiS97JAW/AKpJLArqJ0vUY6UUK 3vbVEmTbHPP3M35g3/mOpOrqWBfspSPSsVKpzQfSbT6PiKpEBg7Z7Q19EpqQD3w4FV+6 J5Xw==
X-Gm-Message-State: ABuFfoiEQGZZuhs4y2iPIENyYb0LnnfqySeQsFM+i+EoqEhGr0gXr5Xg 4YA0UsQM9v++E61rLJ3KhAI=
X-Google-Smtp-Source: ACcGV613m5WecUWPzUK1+BS62dIxxcRmpc7DmVCZbCiDufZQgRI9pFq2TkC6TtDL3qHEg76S/FRkwA==
X-Received: by 2002:a50:8fa4:: with SMTP id y33-v6mr31979801edy.131.1539706100366; Tue, 16 Oct 2018 09:08:20 -0700 (PDT)
Received: from [10.0.0.50] (c-76-21-112-100.hsd1.ca.comcast.net. [76.21.112.100]) by smtp.gmail.com with ESMTPSA id a16-v6sm5138823eda.20.2018.10.16.09.08.18 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 16 Oct 2018 09:08:19 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <B103EE1A-086F-4D3C-B22F-8C51FAF3B2E1@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_EB4AE451-1A05-4CB6-9C01-B125CD1FFD14"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Tue, 16 Oct 2018 09:08:15 -0700
In-Reply-To: <58f9ebdd-355e-129f-a987-dab72bc5da6f@labn.net>
Cc: Bob Hinden <bob.hinden@gmail.com>, Lou Berger <lberger@labn.net>, mtgvenue <mtgvenue@ietf.org>, Alissa Cooper <alissa@cooperw.in>
To: Eliot Lear <lear@cisco.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>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/SvZadIwI7oPTSlJHjmQu84E1L3s>
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:08:25 -0000

Eliot,

> On Oct 16, 2018, at 8:21 AM, Lou Berger <lberger@labn.net> 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 is correct.   From my read the changes proposed are not correct.

Please reread <draft-ietf-iasa2-struct-06>.  It’s current title is:

   Record of Proposed Structure of the IETF Administrative Support Activity
                          (IASA), Version 2.0

The Abstract is:

   The IETF Administrative Support Activity (IASA) was originally
   established in 2005.  In the 13 years from 2005 to 2018, the needs of
   the IETF have evolved in ways that require changes to its
   administrative structure.  The purpose of this document is to outline
   a proposed new "IASA 2.0" structure and to document the decisions
   made by the IASA2 Working Group over the past 20 months in developing
   the proposed structure.  The proposal is for the work of the IETF's
   administrative and fundraising tasks to be conducted by a new
   administrative organization, the IETF Administration Limited
   Liability Company ("LLC").  Under the proposal, the Internet
   Administrative Oversight Committee (IAOC) will be eliminated, and its
   oversight and advising functions transferred to the new LLC Board.

The IASA will still exist, we are changing it’s implementation.  If the meeting venue document needs to change, the changes should be like s/IAOC/IETF LLC/.

Bob









> 
> 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