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

[Brian E Carpenter <[e-mail]>]

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 <[e-mail]> on behalf of "[e-mail]" <[e-mail]>
> Organization: University of Auckland
> Date: Tuesday, April 18, 2017 at 1:54 PM
> To: "[e-mail]" <[e-mail]>, "[e-mail]" <[e-mail]>
> 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, [e-mail] 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
>     >> [e-mail]
>     >> https://www.ietf.org/mailman/listinfo/mtgvenue
>     >>
>     > 
>     > 
>     > 
>     > 
>     > _______________________________________________
>     > Mtgvenue mailing list
>     > [e-mail]
>     > https://www.ietf.org/mailman/listinfo/mtgvenue
>     > 
>     
>     _______________________________________________
>     Mtgvenue mailing list
>     [e-mail]
>     https://www.ietf.org/mailman/listinfo/mtgvenue
>     
>