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

Brian E Carpenter <brian.e.carpenter@gmail.com> Wed, 19 April 2017 22:28 UTC

Return-Path: <brian.e.carpenter@gmail.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 42DB6129C04 for <mtgvenue@ietfa.amsl.com>; Wed, 19 Apr 2017 15:28:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 UL1WfZ-YCEqF for <mtgvenue@ietfa.amsl.com>; Wed, 19 Apr 2017 15:28:41 -0700 (PDT)
Received: from mail-io0-x232.google.com (mail-io0-x232.google.com [IPv6:2607:f8b0:4001:c06::232]) (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 F2FF2129BBF for <mtgvenue@ietf.org>; Wed, 19 Apr 2017 15:28:40 -0700 (PDT)
Received: by mail-io0-x232.google.com with SMTP id k87so40581573ioi.0 for <mtgvenue@ietf.org>; Wed, 19 Apr 2017 15:28:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=sVz6S95XJhUVtdedI4AsL47Ww42KgRM4tvLtbHr3z7c=; b=W4T+WfceonQ8uX/JjVIVK/LdtZ6Sbvt3M3D5nKr16juv6j7z7BzcQ2fOCQVLEe6CCV yhNg45f+miIjYCR6P2CRa6CQZ9Wdu7YbBkeRDhzG2oi2PBF9c4V4NadimZi55lKcx0a6 Wik05GOzmDrkFDQf5b9pAt0EgZ+4MCBO47cwwTjdWf/QXwYJNp+zGGlMs1KVnI7e4de6 iLUdARLnoYl6tr5zJazB805N/X+GMmqJywYTnnv0FwJVtXKgVT0m3P6IZbbwkUGVtqRv Gj65N5l9c5WiD3J8bwg92B8Smqv6b4509VLJBOqWehQgUqRjmMnTg6EkuTOWoYj4gU7v aiXw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=sVz6S95XJhUVtdedI4AsL47Ww42KgRM4tvLtbHr3z7c=; b=P07VB3Tct2vLNzIjkZCQtIiC7rAdZtZuR8T1oP1xNzGwaP9GyE3EM1M5D6YOUw7udS 0jI1NSEE9c35pCz1d/ZRw77q9G75ZTB3gT/PSqpcei//IpUXRAPILrPwFHmTuD1Lcwzv Jd3lBhjRzymnNjAcodOvA6tJo/TRphGXnhbkUndZza7b98VkcVLpKWOgdm6QOky31BRb gNgaVHG/iJ1+Oub3iqHZGI5IVq2QPWBDPfjLUwU8tDdSJ1kAoueK0e0ys0M2wlO5Nc03 RxfM43KbKyJ6IDFwzjovClhv5G1+KopFHlTy8l46i3bR3g9eU73V/ZJBfn+wi2YWB0+V cpSw==
X-Gm-Message-State: AN3rC/5rxc0JWmwvaiWKChMxmLl0+ZKbUfHjIHaCv+DYt5pFSpZYYQvh tkP+AmC0t/+OroFG
X-Received: by 10.99.240.83 with SMTP id s19mr5085749pgj.45.1492640920026; Wed, 19 Apr 2017 15:28:40 -0700 (PDT)
Received: from [130.216.38.132] (sc-cs-567-laptop.uoa.auckland.ac.nz. [130.216.38.132]) by smtp.gmail.com with ESMTPSA id 12sm6344286pgb.35.2017.04.19.15.28.37 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 19 Apr 2017 15:28:39 -0700 (PDT)
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, Eliot Lear <lear@cisco.com>, "mtgvenue@ietf.org" <mtgvenue@ietf.org>
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> <B333A072-07BE-4B51-97E9-0267FB1A264C@cisco.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <dbd147b9-799c-cfd9-66ce-11744ce5080b@gmail.com>
Date: Thu, 20 Apr 2017 10:28:41 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <B333A072-07BE-4B51-97E9-0267FB1A264C@cisco.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/wKbRZmS12ybuMnCzEK67LsRVFWY>
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 22:28:43 -0000

I don't know whether the Chairs have the ability to add a link to the tracker page for the draft. If not, that could be a feature request for the tools team.

Also, I don't know whether the Chairs have the ability to modify the "Additional URLs" at https://datatracker.ietf.org/wg/mtgvenue/about/

Meanwhile, maybe just add a note in the draft itself?

Regards
    Brian
On 20/04/2017 08:48, Charles Eckel (eckelcu) wrote:
> 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
>     >     
>     > 
>     
>