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

"Charles Eckel (eckelcu)" <eckelcu@cisco.com> Mon, 08 May 2017 13:58 UTC

Return-Path: <eckelcu@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 4221A129471 for <mtgvenue@ietfa.amsl.com>; Mon, 8 May 2017 06:58:22 -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 FWC2xZ_0e_S2 for <mtgvenue@ietfa.amsl.com>; Mon, 8 May 2017 06:58:19 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B383D1293FF for <mtgvenue@ietf.org>; Mon, 8 May 2017 06:58:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=27406; q=dns/txt; s=iport; t=1494251899; x=1495461499; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=Lqmonv8cuEUVUAPa4+howCo1HcuV8oj3oQceHnmn4BM=; b=Ob758H1vIBHX/MOalB0HpopZ7VEzQAKEnsIE5z0OteDO0Zxv/PdbDONd STFiHaqySkyI9R9umtrtWadzfk08DnoTLwIzWIvPijH3mjagSV8a0TVD0 kMnZzdPIUBUHcCCRtJwAGUcHGKBjX3FOy8b5FbXCzXP3GdgFL9M75QaH1 k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0B1AQBkeBBZ/5ldJa1cGQEBAQEBAQEBAQEBBwEBAQEBgm5nYoEMB4NhihiRNSFylQCCDyEBDIUsSgIahEU/GAECAQEBAQEBAWsohRUBAQEBAwEBIUsbAgEIEQMBAigDAgICJQsUCQgCBAESiiAOshuCJiuKOAEBAQEBAQEBAQEBAQEBAQEBAQEBAR2IPSsLgjE0gyGBElAWglQugjEFhw2PWYcTAYcbhl+FHYIEVYRniiyIfItBAR84gQpwFRwqEgGFFoFKdodegQ0BAQE
X-IronPort-AV: E=Sophos;i="5.38,309,1491264000"; d="scan'208,217";a="242585365"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 08 May 2017 13:58:18 +0000
Received: from XCH-ALN-020.cisco.com (xch-aln-020.cisco.com [173.36.7.30]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id v48DwIH0005927 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <mtgvenue@ietf.org>; Mon, 8 May 2017 13:58:18 GMT
Received: from xch-aln-018.cisco.com (173.36.7.28) by XCH-ALN-020.cisco.com (173.36.7.30) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 8 May 2017 08:58:17 -0500
Received: from xch-aln-018.cisco.com ([173.36.7.28]) by XCH-ALN-018.cisco.com ([173.36.7.28]) with mapi id 15.00.1210.000; Mon, 8 May 2017 08:58:17 -0500
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: Eliot Lear <lear@cisco.com>, "mtgvenue@ietf.org" <mtgvenue@ietf.org>
Thread-Topic: [Mtgvenue] I-D Action: draft-ietf-mtgvenue-iaoc-venue-selection-process-06.txt
Thread-Index: AQHSuBeZkn3zSf39ZUq9XAsiMkyxAaHLE3CAgB+TbYA=
Date: Mon, 08 May 2017 13:58:17 +0000
Message-ID: <8F0D5F1F-C472-4193-98A6-1EDE3E298D46@cisco.com>
References: <149250145994.17799.797785115553248255@ietfa.amsl.com> <187e2e43-3559-6566-015c-d45dce5b6e89@cisco.com>
In-Reply-To: <187e2e43-3559-6566-015c-d45dce5b6e89@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.20.0.170309
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.86.252.18]
Content-Type: multipart/alternative; boundary="_000_8F0D5F1FC472419398A61EDE3E298D46ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/xDwJBdG6P-S3Y54o42OWexiHhSg>
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: Mon, 08 May 2017 13:58:22 -0000

Thanks and congrats to everyone for the all the great work on version -06 of the draft, aka. milestone1 in github https://github.com/elear/mtgvenue/milestone/1

I marked the issues addressed by it as closed. In some cases, comments resulted in the creation of new issues. If you feel any issue was closed inappropriately or something was missed, please call attention to it.

Issue #6 was not marked as having been addressed by version -06, but I think it was. Eliot, please confirm and we can update the issue list accordingly.
https://github.com/elear/mtgvenue/issues/6

Cheers,
Charles

From: Mtgvenue <mtgvenue-bounces@ietf.org> on behalf of "lear@cisco.com" <lear@cisco.com>
Date: Tuesday, April 18, 2017 at 3:46 AM
To: "mtgvenue@ietf.org" <mtgvenue@ietf.org>
Subject: Re: [Mtgvenue] I-D Action: draft-ietf-mtgvenue-iaoc-venue-selection-process-06.txt


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<mailto: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<mailto:Mtgvenue@ietf.org>

https://www.ietf.org/mailman/listinfo/mtgvenue