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

"Deen, Glenn (NBCUniversal)" <> Tue, 16 October 2018 18:42 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 401C3130DFF for <>; Tue, 16 Oct 2018 11:42:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 0.098
X-Spam-Status: No, score=0.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_DYNAMIC=1.999, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id uNNWcLcJn3xu for <>; Tue, 16 Oct 2018 11:42:33 -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 6BD10130D7A for <>; Tue, 16 Oct 2018 11:42:33 -0700 (PDT)
Received: from pps.filterd ( []) by ( with SMTP id w9GIcSTS033108 for <>; Tue, 16 Oct 2018 14:42:31 -0400
Received: from ([]) by with ESMTP id 2n3bydx4er-1 (version=TLSv1.2 cipher=RC4-SHA bits=128 verify=NOT) for <>; Tue, 16 Oct 2018 14:42:29 -0400
Received: from unknown (HELO ([]) by with ESMTP; 16 Oct 2018 11:42:28 -0700
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.669.32; Tue, 16 Oct 2018 12:42:27 -0600
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.669.32; Tue, 16 Oct 2018 12:42:26 -0600
Received: from ([]) by ([]) with mapi id 15.01.0669.032; Tue, 16 Oct 2018 12:42:26 -0600
From: "Deen, Glenn (NBCUniversal)" <>
To: Lou Berger <>, Eliot Lear <>, "" <>
CC: Alissa Cooper <>, "Deen, Glenn (NBCUniversal)" <>
Thread-Topic: [EXTERNAL] Re: [Mtgvenue] About draft-ietf-mtgvenue-iaoc-venue-selection-process
Thread-Index: AQHUZU44T6wbYUjMU0qLjfbN4OWRxqUiOc+AgAAoHgCAAAoKAIAABuaAgAA31gA=
Date: Tue, 16 Oct 2018 18:42:26 +0000
Message-ID: <>
References: <> <> <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: []
x-exclaimer-md-config: 47edc00f-f2d6-45ef-be83-8a353bd47e45
Content-Type: text/plain; charset="utf-8"
Content-ID: <E8548607EC0F5C4A90283F2EFCB5B854@NBCUNI.COM>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Forward
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-10-16_13:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1810160154
Archived-At: <>
Subject: Re: [Mtgvenue] [EXTERNAL] Re: 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 18:42:36 -0000

I think it is clearer for the reader of MTGVENUE if it's referenced as the LLC and not IASA as it is the LCC that is responsible for doing the function.  

While IASA is the name we've given to the structure of how the IETF Administrative Support Activity is organized, to the actual reader of the MTGVENUE document I think it's much clearer to reference the LLC since it is the LLC that is responsible for the work.

And before someone askes does that mean the LLC Board or the IETF Executive Director it does not matter here. For the purposes of MTGVENUE document that is not a relevant question. All that matters here in who owns the responsibilities, it is up to the LLC to decide how the execution of the responsibilities are assigned..    


On 10/16/18, 9:22 AM, "Mtgvenue on behalf of Lou Berger" < on behalf of> wrote:

    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
    > 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 mailing list
    > _______________________________________________
    > Mtgvenue mailing list
    Mtgvenue mailing list