Re: [Mtgvenue] document status, the role of the iaoc, and enforceability

Eliot Lear <lear@cisco.com> Fri, 06 January 2017 18:13 UTC

Return-Path: <lear@cisco.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 15BF6129D4A for <mtgvenue@ietfa.amsl.com>; Fri, 6 Jan 2017 10:13:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.622
X-Spam-Level:
X-Spam-Status: No, score=-17.622 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 zKd4NCoruFsP for <mtgvenue@ietfa.amsl.com>; Fri, 6 Jan 2017 10:13:44 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F1E87129D3F for <mtgvenue@ietf.org>; Fri, 6 Jan 2017 10:13:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4591; q=dns/txt; s=iport; t=1483726424; x=1484936024; h=subject:to:references:from:message-id:date:mime-version: in-reply-to; bh=nFKxCve27Pl+D6reOJ6JFtIUsBG0hkuvy/JzyNVKnh8=; b=B8mjQ0QYS3NFzoXYzXI3aK5CqCizn7bgnsWgZ+T6/TsriSUGlHDT4Izr ZIMiuXNN4WojgIhwcm1cpw/Jqas0hsDtiZpS9nYrUBGWB9B/6w4K9YXUe aRaIPayPPl1UYSVq3njTIRJEDP28XS0HIJggACfnqA7RoP1LCORfcmVo0 g=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0D+AABH3W9Y/xbLJq1eGQEBAQEBAQEBAQEBBwEBAQEBgzkBAQEBAX6BDI1XcpEvlSaCCR8LhS5KAoIUFAECAQEBAQEBAWMohGkBAQQBASFLGwsOCioCAicwBgEMBgIBARCIXA6wTYIlih8BAQEBAQEBAwEBAQEBARMKBYhHgVmBBodOgj8fBZsVg2aBfotjiiaGNY5AhBEfOIEPEgcUFTWEKRyBYD01iGYBAQE
X-IronPort-AV: E=Sophos;i="5.33,326,1477958400"; d="asc'?scan'208";a="691120337"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 06 Jan 2017 18:13:40 +0000
Received: from [10.61.77.32] (ams3-vpn-dhcp3360.cisco.com [10.61.77.32]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id v06IDdBB022323; Fri, 6 Jan 2017 18:13:39 GMT
To: Lou Berger <lberger@labn.net>, dcrocker@bbiw.net, mtgvenue@ietf.org
References: <148302624729.30218.3797301462532090032.idtracker@ietfa.amsl.com> <e2da432a-1ed8-fd51-be59-70213cd932f6@dcrocker.net> <be74a492-a414-1947-91cc-f8eafabd57f8@cisco.com> <31e61662-a92e-dbdc-f918-d91c5694420b@labn.net>
From: Eliot Lear <lear@cisco.com>
Message-ID: <ac68caa4-a6da-9eb0-d7cb-41ccab444e81@cisco.com>
Date: Fri, 06 Jan 2017 19:13:38 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <31e61662-a92e-dbdc-f918-d91c5694420b@labn.net>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="q0w3B1eKkr9u7OgS8t8WDna4aElN3LJPI"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/5JC1ZqS0e8CGX5qAhBgHK2IBId0>
Subject: Re: [Mtgvenue] document status, the role of the iaoc, and enforceability
X-BeenThere: mtgvenue@ietf.org
X-Mailman-Version: 2.1.17
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: Fri, 06 Jan 2017 18:13:46 -0000

Hi Lou,

Yes, there is this indirection with NOMCOM.  Having a voice is
important.  I don't really know the composition of the meetings
committee, but it seems to me that perhaps that is a place for a certain
amount of diversity so that concerns can be identified early.  Maybe
it's just me, but when I consider a question like, “should the IETF meet
in a certain location?” my first question is, would I be comfortable
with my wife or daughter present?  In other words, I personalize it.  I
would expect others do something similar, if only subconsciously.  Had
Ted been a member of that committee, I'm sure we never would have been
standing there in BA in that uncomfortable situation, even if the
decision were STILL to go to Singapore (Ted's better at this than me- he
can put himself in many people's shoes).

Eliot

On 1/6/17 6:19 PM, Lou Berger wrote:
> Eliot,
>
> On 1/6/2017 11:40 AM, Eliot Lear wrote:
>> Hi,
>>
>> IETF leadership tends to use BCPs as a means of enforcement.  That can't
>> be the case with this document.  It simply is impracticable to rework
>> contracts based on some sort of appeal, for instance.  At best,
>> therefore, this is the IETF community's advice to the IAOC about how it
>> would like venues selected.  At the end of the day, if members of the
>> community are unhappy with the IAOC's venue selections, the appropriate
>> recourse is the NOMCOM and not some sort of appeal.  I would like this
>> further clarified in the document.
> I'm not sure how viable this is for a specific meeting, but that's not
> to say that there can't be some longer term/process impact via the
> nomcom path.
>
> I have a little experience with trying this path.  The announcement of
> the 2016 venues was the straw that made me volunteer for the IAOC and I
> got appointed ~2 years ago.  Even then it was too late for me to have
> any impact on changing Singapore as a venue (my objections were based on
> expense and IETF 100 relevance, not the objection which I was unaware of
> that was raised by the community) .
>
> That said, I do believe I've been able to have some impact on meeting
> selection as an IAOC member -- specifically promoting the idea of repeat
> locations for cost benefits, (somewhat) improving transparency, and
> initiating the draft with the personal objective of ensuring that the
> venue selection process follows a community driven/consensus process.
>
> Also, keep in mind that the IAOC is made up of mostly non-nomcom
> appointed members.
>
> Lou
>
>> 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
>