[Mtgvenue] Where we are, post #1

Melinda Shore <melinda.shore@nomountain.net> Mon, 30 January 2017 21:00 UTC

Return-Path: <melinda.shore@nomountain.net>
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 4B6B0129600 for <mtgvenue@ietfa.amsl.com>; Mon, 30 Jan 2017 13:00:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=nomountain-net.20150623.gappssmtp.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 hutT9YXnGp9H for <mtgvenue@ietfa.amsl.com>; Mon, 30 Jan 2017 13:00:39 -0800 (PST)
Received: from mail-pf0-x229.google.com (mail-pf0-x229.google.com [IPv6:2607:f8b0:400e:c00::229]) (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 1A0B81295F2 for <mtgvenue@ietf.org>; Mon, 30 Jan 2017 13:00:39 -0800 (PST)
Received: by mail-pf0-x229.google.com with SMTP id e4so92934029pfg.1 for <mtgvenue@ietf.org>; Mon, 30 Jan 2017 13:00:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nomountain-net.20150623.gappssmtp.com; s=20150623; h=to:from:subject:message-id:date:user-agent:mime-version; bh=GMDSjEIczYlJPVIcsYn9wBXxOFaC6eeHEGLYXSS85cY=; b=BIFRXBPtyg9gyOf2rETVvu895TGCCLKFqsX9FoRiNCuGJ3964EtUQGXSizFIZi1VNw wfo26+EQOYRjniU+5vUmLRC7P9WWqrTVBOQgoVqEQLPDhA1ayiLRigGi1NLCIr7uC/pc lyCBEQPYuQpwvE3g8QoRkM/5YWLRWJpx/anmgaZy/QMs7pQ0iRZtsiYtH5EEu3SjwKIW vHPQjW4VkCRKFbVCk1q2bpTp4z+t2oZo+INv2ZOON9KY4rp0ygLSrFFrTmPcDgQh/rO6 /TlXqeiC3Yt0g77IHM+WCtZPtTGSG64nK9raepkxFsB4k9Ylkr9xcixGMU4AmvewxyCD n34A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version; bh=GMDSjEIczYlJPVIcsYn9wBXxOFaC6eeHEGLYXSS85cY=; b=NQs6O0hxhtMOaYm1jpzW1LJ3gqiG0/EUr+Eo4Ie2TaZOKD8o+IOLjpdCzr3bFqC3qW Hns53bmKFD2ulEasCalXddK5evqVkYMoZAa6wbZ6Qq1Tqd3BiqNeNXfJw1ojWkxi2Jty m09JOXRQjksiNbLUf+R5WKoVoIhGs5Z4PgX0+6ce2ZUesy0AlNLqRzQ6C3ATPg65fDtc SIL+ZJBoFB6u9wKUO/CwoMBkO1v9wy5KAwfu4dUZE47EaLMD6ap079H0TUBplwiPar2c fR7obrvZtQozFqxz9ZUkgygb5dQud7hwIAB7N8flyEym/YhDRxt+rwyBU4cCQRwfxwch 8NKg==
X-Gm-Message-State: AIkVDXIJSllxt0fCnERytRftO3R8EYdNjkE+VfseBUidcF7TFNat57wdidm7RgoPvoLXqQ==
X-Received: by 10.99.166.17 with SMTP id t17mr5337894pge.196.1485810038480; Mon, 30 Jan 2017 13:00:38 -0800 (PST)
Received: from Melindas-MacBook-Pro.local (216-67-10-189-radius.dynamic.acsalaska.net. [216.67.10.189]) by smtp.gmail.com with ESMTPSA id k76sm34861052pfg.42.2017.01.30.13.00.37 for <mtgvenue@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 30 Jan 2017 13:00:37 -0800 (PST)
To: mtgvenue@ietf.org
From: Melinda Shore <melinda.shore@nomountain.net>
Message-ID: <b3731b2e-1526-beef-2bee-33d014fb88e3@nomountain.net>
Date: Mon, 30 Jan 2017 12:00:35 -0900
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
Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="tkslLkKcrnonopXV1Hdd3gCdcTP4DioR7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/PG6iUFPebHD1sIiS46aWq9ZR0ok>
Subject: [Mtgvenue] Where we are, post #1
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: Mon, 30 Jan 2017 21:00:41 -0000

Hi, all:

There's been a ton of mail today and it's fantastic seeing the
process document under active review and discussion.  I thought
it might be helpful to try to pull together some of the discussion
and close it out, where possible.  There will be additional posts
summarizing where we don't have agreement or where we need
further discussion.

Also, many, many thanks to those who've proposed text.

So, stuff where we appear to have agreement:

In the matter of a statement about the meeting selection process
being as open as possible, Eliot's proposed text,
	The IETF's meeting venue selection process, as with all IETF 	
	processes, should be as open as practicable.
seems acceptable to everybody.

Stephen was concerned about the definition of "unfiltered" in section
1.2.  Eliot also thinks this needs elaboration so that potential hosts
will understand what's expected.  His proposed text:
	 Note that "unfiltered" in this context is meant to allow for
	all manner of forms of communications, as the
	IETF often makes first use of its own technologies at our
	meetings.  In addition, to facilitate
	the business of the IETF it is also necessary for participants
	to hold confidential discussions with their businesses,
	customers, and partners.
appears acceptable.  However, his proposed text
	At the same time, IETF participants are expected
	to make use of the network in a manner consistent
	with local laws and customs.
received some pushback and needs further discussion

Stephen was also concerned that section 5 is too prescriptive and
suggests emphasizing that this section is a guideline that's expect
to evolve, that what's listed is current practice, and while the
IAOC may change what they do they will need to publish their changes
and follow community consensus on those changes.  There appears to be
agreement to that, but text is needed.

There was also the question of the links in 5.3 and 5.5.  Lou suggested
that that material could be moved to an appendix, and there hasn't
been any disagreement.

Brian proposed the following text to address the international nature
of the IETF and its work:
	The IETF operates internationally and adjusts to local
	requirements.
and there appears to be agreement

Thanks,

Melinda