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

S Moonesamy <sm+ietf@elandsys.com> Sun, 08 January 2017 23:38 UTC

Return-Path: <sm@elandsys.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 48BFE1299BF for <mtgvenue@ietfa.amsl.com>; Sun, 8 Jan 2017 15:38:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.989
X-Spam-Level:
X-Spam-Status: No, score=-4.989 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-3.199, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=opendkim.org header.b=hv6muVVa; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=xNO7+4yN
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 6PWlsdR4kBPA for <mtgvenue@ietfa.amsl.com>; Sun, 8 Jan 2017 15:38:23 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 586E61299B4 for <mtgvenue@ietf.org>; Sun, 8 Jan 2017 15:38:23 -0800 (PST)
Received: from SUBMAN.elandsys.com (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id v08Nc4Ug027704 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 8 Jan 2017 15:38:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1483918692; x=1484005092; bh=TvfzqM65oSIlm1IF2aMzg5cs59VBP7vGcdqQNgS4cFA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=hv6muVVamSv3S43kimfKU8p7gwA1PwDuUqgQdVcwROOhe5ddQg3EFVNBvi1dhWf6a myjJ0Aa6sqtyXCHtgTdGStvPUka44vfUZ3T7FuFoIryUCOxqqe8+DBuuKtAPM5uA6S AH69hbEjFHCo3tqsB7w4KulfYmYxTzWCZPacV/Bk=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1483918692; x=1484005092; i=@elandsys.com; bh=TvfzqM65oSIlm1IF2aMzg5cs59VBP7vGcdqQNgS4cFA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=xNO7+4yNaQrHLOK5JQHg8Jy7axwOnoxTdiwK4mS8q/hTlMQAYhvwBWZrz5mruYt0A 4BudSU1BqhRWGSdpyFO0BgIgSfeQikdbJCcijYZRnC1ZeM7qxm72PqeBUTCpNRReOJ pS4PIfQZkFzfJ2CWHM5BC0q0k5xeGm26Y9PlzIms=
Message-Id: <6.2.5.6.2.20170108120533.0bdb3408@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 08 Jan 2017 13:59:52 -0800
To: dcrocker@bbiw.net, S Moonesamy <sm+ietf@elandsys.com>, mtgvenue@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <8cda2592-cf82-e379-6678-2ced0a0098bc@dcrocker.net>
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> <ac68caa4-a6da-9eb0-d7cb-41ccab444e81@cisco.com> <6.2.5.6.2.20170108090723.0badd8d0@elandnews.com> <8cda2592-cf82-e379-6678-2ced0a0098bc@dcrocker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/ePMx6RGTFcnMOD2T5Z412MARQos>
Cc: Eliot Lear <lear@cisco.com>
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: Sun, 08 Jan 2017 23:38:24 -0000

Hi Dave,
At 10:44 08-01-2017, Dave Crocker wrote:
>However prior to the announcement of Singapore, what record was 
>there on "the IETF discussion list and the triannual attendees 
>mailing lists" that informed the IAOC/Meetings committee about the 
>concerns that were finally raised about Singapore?

There isn't any record of the concerns.

>Any model that presumes that the IAOC/Meetings committee is going to 
>know all of the relevant concerns of the IETF community, about each 
>possible meeting city, is certain to fail eventually.  There are too 
>many possible issues and their importance to the community varies over time.

I'll put this differently; it is not possible to identify all the 
future concerns at the time when the decision about the venue is taken.

>No formalized text is going to be sufficiently accurate or complete 
>over the long term.  Stating broad principles can be helpful for 
>shared reference during discussion, but assuming that any such text 
>will provide sufficient synchrony between the committee and the 
>community will eventually fail.

Yes.

>The only way to ensure that community concerns are recognized 
>adequately is for the open, early-stage community comment process 
>that has recently been added.  And it effectively marginalizes the 
>importance of any detailed document text we might create, about 
>political/legal/social concerns.

My guess is that the open early-stage comment period can be a good 
way to capture some of the concerns.  The discussions about meetings 
and the detailed document highlighted that the IAOC may have 
overlooked basic stuff over the years, e.g. travel advisories.  If I 
am not mistaken, there has only been two occurrences of 
political/legal concerns over the years.

There are some good things in the draft, i.e. issues which should not 
be revisited on a triannual basis.  There are also some IETF policy 
questions, e.g. is the venue selection about endorsing or condemning 
the political choices of a country which is selected as a venue.

Regards,
S. Moonesamy