Re: [IETF LLC] Venue Review Committee

"Livingood, Jason" <Jason_Livingood@comcast.com> Fri, 17 May 2019 19:37 UTC

Return-Path: <Jason_Livingood@comcast.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C82571200FE for <ietf@ietfa.amsl.com>; Fri, 17 May 2019 12:37:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.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 DDs0VQHw6pq7 for <ietf@ietfa.amsl.com>; Fri, 17 May 2019 12:37:57 -0700 (PDT)
Received: from copdcmhout02.cable.comcast.com (copdcmhout02.cable.comcast.com [96.114.158.212]) (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 6B736120033 for <ietf@ietf.org>; Fri, 17 May 2019 12:37:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=comcast.com; s=20190412; c=relaxed/simple; q=dns/txt; i=@comcast.com; t=1558121874; x=2422035474; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=Tz6IM0pyfesRaCFSy9wODEO2mrqzYWYuboUyTgFDg+g=; b=no0WZn19hxht7vuXgUt7a3UFHJ7Sh2w4Sd21SZq+yHQ9edqsTcYqxjxBOBYdJJih BjRajLd6NSfbAxohkvV0GuZfnCFzHy6Csuc1H3c+9sQ5t2SZ8MhkQ3ZHPPoFzrXs rO6HaupIn42PMqV7DZmu3/AjNHvtwV4njUdULo2bHwGKgN7Vo/7Ud0eT0bgrsXY5 4fzWExrizqcAXiBwKa6W1tQpSiEww36T8Xdkm6QbQHA5+22ObrSXFjdH1fD8KWhV BZRRWJIu/2A2BKH6E/+PEq3QjXOGh1052wm+Nmto7VYn8iwMSVG32f9nO8OZaWAz TlW+Gv5pA2L8z7LXsRM0SQ==;
X-AuditID: 60729ed4-f05ff7000000add3-fd-5cdf0d92e440
Received: from COPDCEXC40.cable.comcast.com (copdcmhoutvip.cable.comcast.com [96.114.156.147]) (using TLS with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client did not present a certificate) by copdcmhout02.cable.comcast.com (SMTP Gateway) with SMTP id E8.99.44499.29D0FDC5; Fri, 17 May 2019 13:37:54 -0600 (MDT)
Received: from COPDCEXC37.cable.comcast.com (147.191.125.136) by COPDCEXC40.cable.comcast.com (147.191.125.139) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Fri, 17 May 2019 15:37:53 -0400
Received: from COPDCEXC37.cable.comcast.com ([fe80::3aea:a7ff:fe36:8a94]) by COPDCEXC37.cable.comcast.com ([fe80::3aea:a7ff:fe36:8a94%15]) with mapi id 15.01.1713.004; Fri, 17 May 2019 15:37:54 -0400
From: "Livingood, Jason" <Jason_Livingood@comcast.com>
To: John C Klensin <john-ietf@jck.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [IETF LLC] Venue Review Committee
Thread-Topic: [IETF LLC] Venue Review Committee
Thread-Index: AQHVDDcqggaQZ7NQRES6hcrg42nzb6ZvoeIAgAAVuYA=
Date: Fri, 17 May 2019 19:37:53 +0000
Message-ID: <440D630E-6030-4174-8A5C-30C005E93DA0@cable.comcast.com>
References: <155804588507.19810.11194675256615619971.idtracker@ietfa.amsl.com> <5FB3C570B19FE808708190A7@PSB>
In-Reply-To: <5FB3C570B19FE808708190A7@PSB>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.19.0.190512
x-originating-ip: [96.115.73.254]
Content-Type: text/plain; charset="utf-8"
Content-ID: <EBE1FD6D95E7624F8DB58D62B1A5CDEA@comcast.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Forward
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprDKsWRmVeSWpSXmKPExsWSUDRnsu4k3vsxBh9vmls82zifxaL10h82 ByaPJUt+MnlcXvmaOYApqoHRpiSjKDWxxCU1LTWvONWOSwED2CSlpuUXpbomFuVUBqXmpCZi VwZSmZKak1mWWqSP1Rh9rOYkdDFldD1pZi44pV8x7+1HtgbGNXpdjJwcEgImEu9PnWTrYuTi EBI4wiTx/uUSVginhUni0ed5zBDOaUaJznVX2EFa2ATMJO4uvMIMYosIuEss3bMAzBYW0JP4 eXoxC0RcX6Jr6mWgOAeQbSWx7lwRSJhFQFXi3btWsBJeAReJpXMPsoLYQgL5Ej+fPQGzOQW0 JfrXvwQbySggJvH91BomEJtZQFzi1pP5TBBXC0gs2XOeGcIWlXj5+B9YryjQ2h/bb7JBxBUl fs27wgZyArOApsT6XfoQY6wknmw6DjVSUWJK90N2iHMEJU7OfMIC0SoucfjIDtYJjBKzkGye hTBpFpJJs5BMmoVk0gJG1lWMfJZmeoaGJnqGphZ6RoZGmxjBaWbelR2Ml6d7HGIU4GBU4uG1 5bgfI8SaWFZcmXuIUYKDWUmEd8P72zFCvCmJlVWpRfnxRaU5qcWHGKU5WJTEeX01gVIC6Ykl qdmpqQWpRTBZJg5OqQbGxl+pp29ME5vKXDVXcNcUtX2ajw4GqWquCuKUFGmfJLFmGdtd28Lo l6+u3zsgneY0f53K6voDIg+yXxz/3yDcf2Sx6dEPD0vXFfdqPlZoneV7QTtpedSpzTGOtQwP 5vhtrJb5L9R96uqRw2f9U7emBJzNe/l3NouVRITf/9MZ187NY5mZ52H6SomlOCPRUIu5qDgR AOAdtDcvAwAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/SM6ojjfVwJ3S4TV3MhCWTcujz5M>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 May 2019 19:38:00 -0000

Hi John - In my recollection, the VRC was created in an era that may have pre-dated the meeting venue working group (https://datatracker.ietf.org/wg/mtgvenue/about/) and their drafts that will likely soon be RFCs based on the datatracker notes (https://tools.ietf.org/html/draft-ietf-mtgvenue-meeting-policy-07 and https://tools.ietf.org/html/draft-ietf-mtgvenue-iaoc-venue-selection-process-16). So my perception is that the community came together to document its requirements that would then serve to guide the IASA (in this case the LLC) in selecting venues. That means the people in question don't necessarily need that expertise because it's all documented in requirements and other guidance by the community. And they can always ask the board or the community for input/guidance/feedback - and the community certainly never shies away from sharing feedback as well. 

We'll continue to discuss meeting plans on regular board calls - and feel free to raise questions in open session - and our ED and Secretariat will continue to seek community feedback as we go (such as post-meeting surveys, surveys on venue preferences, etc.). 

The board certainly knows that meetings are key to the IETF - we have no intention of letting things go off the rails. :-)

Jason

On 5/17/19, 10:34 AM, "ietf on behalf of John C Klensin" <ietf-bounces@ietf.org on behalf of john-ietf@jck.com> wrote:

    Jason,
    
    While I understand that the IETF LLC arrangements make this the
    Board's decision to make, I wonder if replacing an IETF
    community-based group with a diversity of opinions and
    perspectives with two staff members (neither of whom have any
    history in the IETF's technical work) is a step in the right
    direction?  
    
    Please forgive me if I've forgotten important details of the new
    model but haven't we already put most of the meeting venue
    selection process into the hands of the LLC Exec Director and
    the Secretariat?  If so, does this change not essentially ask
    the same people to review their own decisions?   And, if that is
    the case, does the Board except to perform the review function
    and supply the perspectives of the IETF participant community
    itself and has it allocated the time and resources to do that?
    
    Just asking...
        john
    
    
    --On Thursday, May 16, 2019 15:31 -0700 IETF Administration LLC
    Board of Directors Chair <llc-board-chair@ietf.org> wrote:
    
    > Last year the IAOC created the Venue Review Committee (VRC) to
    > assist with the review of potential meeting venues [1]. While
    > the other IAOC committees were previously disbanded or
    > re-purposed, the VRC continued to function beyond the IAOC's
    > conclusion to help maintain continuity as the IETF LLC has
    > been ramping up. The LLC operation is now stable enough that
    > the LLC Board has asked the Interim IETF Executive Director,
    > Portia Wenze-Danley, to assume the responsibilities previously
    > handled by the VRC. Portia will enjoy significant assistance
    > from   Laura Nugent from the Secretariat. Final meeting venue
    > contracting decisions will continue to require LLC Board
    > approval.
    > 
    > The IETF LLC Board very much appreciates the service of the
    > current and prior IAOC Venue Review Committee members for
    > their contributions to the community, including Lou Berger,
    > Glenn Deen (Chair), Avri Doria, Bob Hinden, Eliot Lear, Jim
    > Martin, Andrew Sullivan, and Sam Weiler. 
    > 
    > Regards, 
    > Jason Livingood
    > Chair, IETF LLC Board
    > LLC-Board-Chair@ietf.org 
    > 
    > [1]
    > https://mailarchive.ietf.org/arch/msg/ietf-announce/xNqXAQmCvz
    > O338hoixMJPyKj0eQ
    > 
    > ++++++++++ How to Contact the IETF LLC ++++++++++
    > Executive Director: Exec-Director@ietf.org  
    > Sponsorship: sponsorship@ietf.org 
    > Board: LLC-Board@ietf.org 
    > 
    > ++++++++++ General IETF LLC Board Background ++++++++++
    > About the IETF LLC: https://www.ietf.org/about/administration/
    > Meeting minutes:
    > https://www.ietf.org/about/groups/llc-board/minutes/ Future
    > meetings:
    > https://www.ietf.org/about/groups/llc-board/meeting-info/ 
    > Financial statements:
    > https://www.ietf.org/about/administration/financial-statements/
    >