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

"Charles Eckel (eckelcu)" <eckelcu@cisco.com> Wed, 19 April 2017 20:49 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 4D40412E3AE for <mtgvenue@ietfa.amsl.com>; Wed, 19 Apr 2017 13:49:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.022
X-Spam-Level:
X-Spam-Status: No, score=-14.022 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_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 bp4xeeWfCprP for <mtgvenue@ietfa.amsl.com>; Wed, 19 Apr 2017 13:49:01 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 124E212D0C3 for <mtgvenue@ietf.org>; Wed, 19 Apr 2017 13:49:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9374; q=dns/txt; s=iport; t=1492634941; x=1493844541; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=REnAXWT0TCF2FoN8tmJ/B387zZ8T5cvq5KZhTyNjzTA=; b=a802FcLJNsoM77pabq3LB9O1+Vtc1gRmheU3ZITXhPLtOGUuutqtUGnJ pFVGjoJ+lKuRXkLVDigl1EkCl42NhJ9wWw5x+fNVzBuNqsxoBfjpdZjzl jO+2GxRA6noKBaJhFSHnSDIj5vvEkzTndFU17xHTrx1Ve+Q42jp1IK+Zd E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AeAQABzfdY/4cNJK1cGQEBAQEBAQEBAQEBBwEBAQEBg1RhgQsHg2CKFZFjcIcujUSCDyENhSxKAhqDaz8YAQIBAQEBAQEBayiFFQEBAQEDAQEhEToXBAIBCBEDAQIBAgImAgICHwYLFQgIAgQBEooBAxUOqkOCJoc4DYNfAQEBAQEBAQEBAQEBAQEBAQEBAQEBHYELhyUrgjo0glFHgRAvF4JvLoIxBYcAlXQ7AYcQhllKhEiCAFWEXIobiGyCIYkDAR84gQVjFRoqEQGFCYFKdQGHXYENAQEB
X-IronPort-AV: E=Sophos;i="5.37,222,1488844800"; d="scan'208";a="17022728"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by rcdn-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 19 Apr 2017 20:48:46 +0000
Received: from XCH-ALN-019.cisco.com (xch-aln-019.cisco.com [173.36.7.29]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id v3JKmkUQ027357 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 19 Apr 2017 20:48:46 GMT
Received: from xch-aln-018.cisco.com (173.36.7.28) by XCH-ALN-019.cisco.com (173.36.7.29) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 19 Apr 2017 15:48:45 -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; Wed, 19 Apr 2017 15:48:45 -0500
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, 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: AQHSuBeZkn3zSf39ZUq9XAsiMkyxAaHLE3CAgADcAwD//6YkgIAA13wAgACd4oA=
Date: Wed, 19 Apr 2017 20:48:45 +0000
Message-ID: <B333A072-07BE-4B51-97E9-0267FB1A264C@cisco.com>
References: <149250145994.17799.797785115553248255@ietfa.amsl.com> <187e2e43-3559-6566-015c-d45dce5b6e89@cisco.com> <aa9b41ec-11ed-71bf-4a21-f0490dd5f97f@gmail.com> <D7DCED45-4B27-4E68-ABD3-B21E2F9AB5D1@cisco.com> <a7ad7f85-0344-8446-6842-c4008cdfed91@gmail.com>
In-Reply-To: <a7ad7f85-0344-8446-6842-c4008cdfed91@gmail.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.154.176.150]
Content-Type: text/plain; charset="utf-8"
Content-ID: <E3AA6CB3802FD545959C2F6F7D9815B1@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/Nwg0rfWbAAqFHHJPl46Mz2h6Jrs>
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: Wed, 19 Apr 2017 20:49:03 -0000

I agree. Any suggestions for how to make it easier for folks to find the link?

Thanks,
Charles

-----Original Message-----
From: "brian.e.carpenter@gmail.com" <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Date: Tuesday, April 18, 2017 at 9:23 PM
To: Charles Eckel <eckelcu@cisco.com>, "lear@cisco.com" <lear@cisco.com>, "mtgvenue@ietf.org" <mtgvenue@ietf.org>
Subject: Re: [Mtgvenue] I-D Action: draft-ietf-mtgvenue-iaoc-venue-selection-process-06.txt

    Thanks! That seems a bit hard to find from the tracker.
    
       Brian
    
    
    On 19/04/2017 10:32, Charles Eckel (eckelcu) wrote:
    > https://github.com/elear/mtgvenue/issues
    > 
    > Cheers,
    > Charles
    > 
    > -----Original Message-----
    > From: Mtgvenue <mtgvenue-bounces@ietf.org> on behalf of "brian.e.carpenter@gmail.com" <brian.e.carpenter@gmail.com>
    > Organization: University of Auckland
    > Date: Tuesday, April 18, 2017 at 1:54 PM
    > To: "lear@cisco.com" <lear@cisco.com>, "mtgvenue@ietf.org" <mtgvenue@ietf.org>
    > Subject: Re: [Mtgvenue] I-D Action: draft-ietf-mtgvenue-iaoc-venue-selection-process-06.txt
    > 
    >     Hi Eliot,
    >     
    >     Could you kindly remind us where the issue tracker is?
    >     
    >     Regards
    >        Brian
    >     
    >     On 18/04/2017 19:46, Eliot Lear wrote:
    >     > 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
    >     >>
    >     > 
    >     > 
    >     > 
    >     > 
    >     > _______________________________________________
    >     > 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
    >     
    >