Re: [Mtgvenue] I-D Action: draft-ietf-mtgvenue-iaoc-venue-selection-process-06.txt

Eliot Lear <lear@cisco.com> Tue, 18 April 2017 07:47 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 00A981317E6 for <mtgvenue@ietfa.amsl.com>; Tue, 18 Apr 2017 00:47:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level:
X-Spam-Status: No, score=-14.522 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, 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 EBjRnrqC0FBG for <mtgvenue@ietfa.amsl.com>; Tue, 18 Apr 2017 00:47:03 -0700 (PDT)
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 8BDE1126DEE for <mtgvenue@ietf.org>; Tue, 18 Apr 2017 00:47:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11405; q=dns/txt; s=iport; t=1492501622; x=1493711222; h=subject:to:references:from:message-id:date:mime-version: in-reply-to; bh=5lE8B2+EFJRRPzzRAGFI9F6z3swMy71u09iWIr5TWI4=; b=A+ilAqjWZKIA/kx14XGFLbvtZGnKllSN5PyaLlrMdJyp2u/lGwTTuUBp M3QmrxgmyekEmiKI1kTVgJRxOhDm2Wm1h9yJGPe+kra8D94LGTsuSYarQ QKkRGf8FOtY5rG/NdNIIkq39EuIxw84469CBIBfNSN0aXph9qx5Fw5iLc A=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CcAgA/xPVY/xbLJq1cGQEBAQEBAQEBAQEBBwEBAQEBgyiBDIELg2aKFXOQSyFvjzyFNIIPBxoBDIUsSgKESBgBAgEBAQEBAQFrKIUWAQEBAwEBIUsbCxgqAgInMBMGAgEBihMOqjuCJiuKdwEBAQEBBQEBAQEBAQESD4gvKwqCLzSDGIEQgzWCXwWGd5Ykg36CEHaGVIUOgX9VhFuDOoZdiGmLIR84gQUmHQgYFRoqhRuBTD41iRsBAQE
X-IronPort-AV: E=Sophos;i="5.37,218,1488844800"; d="asc'?scan'208,217";a="693784089"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 Apr 2017 07:46:36 +0000
Received: from [10.61.65.157] (ams3-vpn-dhcp413.cisco.com [10.61.65.157]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id v3I7kZEh015233 for <mtgvenue@ietf.org>; Tue, 18 Apr 2017 07:46:35 GMT
To: mtgvenue@ietf.org
References: <149250145994.17799.797785115553248255@ietfa.amsl.com>
From: Eliot Lear <lear@cisco.com>
Message-ID: <187e2e43-3559-6566-015c-d45dce5b6e89@cisco.com>
Date: Tue, 18 Apr 2017 09:46:35 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <149250145994.17799.797785115553248255@ietfa.amsl.com>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="RXkv1pLKDIUhOfigR2kWs6I5ufc2VKNii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/A7tzp_CwFI284pNGn6JK5BdOcN8>
Subject: Re: [Mtgvenue] I-D Action: draft-ietf-mtgvenue-iaoc-venue-selection-process-06.txt
X-BeenThere: mtgvenue@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 18 Apr 2017 07:47:05 -0000

Hi everyone,

This draft intends to address the following issues:

  * #1: What means "mandatory/important/..."
  * #3: Too much mandatory
  * #4: Process innovation
  * #5: Clarity on definitions re hotel rooms and the facility in Section 3
  * #6: Terminology hard to follow
  * #7: Clarity of responsibility
  * #8: What if Target list of cities is not known?
  * #9: Concurrent objection?
  * #10: What happens if there is a change of policies in the interim?
  * #11: Text seems strange
  * #12: Sponsor required as mandatory?
  * #13: Handling repeats
  * #16: What is consensus on? venue selection or process?
  * #17: Timing of 3 month final check

Each of these issues has been tagged with the -06 milestone.

Probably we will not need to do anything with issue 18 (Align
mandatories with values).

I would expect there to be additional issues opened at this point, as I
might have got something wrong.  This draft is yours, not mine, so
please feel free to offer proposed edits or backouts (I'll have a few
myself with my editor hat off).  Speaking of which, let me draw your
attention to Section 5.  In my opinion we have not yet settled on
chapeau text, and have left an editorial comment in there indicating as
such.  In addition, In addressing issues 10 and 17, as well as Alissa's
comments, I've attempted to provide some guidance as to what should
happen AFTER the contract is signed, but it is relatively minimal.  My
suggestion is that if we cannot agree on some text along those lines
relatively quickly we simply excise the section.

There are a number of newer issues that need to be addressed and are
not.  There are also some issues that are holding, pending resolution of
the above.  As such, you might reasonably expect an update in May based
on this working group's progress.

Eliot

On 4/18/17 9:44 AM, internet-drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Meeting Venue of the IETF.
>
>         Title           : IETF Plenary Meeting Venue Selection Process
>         Authors         : Ray Pelletier
>                           Laura Nugent
>                           Dave Crocker
>                           Lou Berger
>                           Ole Jacobsen
>                           Jim Martin
>                           Fred Baker
>                           Eliot Lear
> 	Filename        : draft-ietf-mtgvenue-iaoc-venue-selection-process-06.txt
> 	Pages           : 28
> 	Date            : 2017-04-18
>
> Abstract:
>    The IAOC has responsibility for arranging IETF plenary meeting Venue
>    selection and operation.  This document details the IETF's Meeting
>    Venue Selection Process from the perspective of its goals, criteria
>    and thought processes.  It points to additional process documents on
>    the IAOC Web Site that go into further detail and are subject to
>    change with experience.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-mtgvenue-iaoc-venue-selection-process/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-mtgvenue-iaoc-venue-selection-process-06
> https://datatracker.ietf.org/doc/html/draft-ietf-mtgvenue-iaoc-venue-selection-process-06
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-mtgvenue-iaoc-venue-selection-process-06
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> Mtgvenue mailing list
> Mtgvenue@ietf.org
> https://www.ietf.org/mailman/listinfo/mtgvenue
>