Leslie, I'm confused and I assume others will be when they read
the announcement below as well.
Are there to be separate Venue Review and Venue Selection
committees? Your first paragraph and the charter appear to
refer to the former, but your second paragraph indicates that a
Venue Selection committee is being (or has been) created. If
there are actually two committees, I suggest that the charter
for the Review committee is incomplete without some discussion
about how they are expected to interact, whether membership with
overlap, etc.
thanks,
john
--On Monday, February 26, 2018 13:32 -0800 IAOC Chair
<iaoc-chair@xxxxxxxx> wrote:
> In reviewing its requirements and operations, especially in
> the light of the imminent conclusion of the MTGVENUE work, the
> IAOC has decided to create a new subcommittee, the Venue
> Review committee (charter copied below), effective as of IETF
> 101. Its composition is as noted below, plus IAOC members that
> the new IAOC will select in London, and any community
> volunteers that the new IAOC chooses to appoint. (A call for
> community volunteers for all IAOC committees went out earlier
> today -- see
> https://mailarchive.ietf.org/arch/msg/ietf-announce/kQy7Ob-GeQ
> -w0uB_WTO1PXfkpyc ).
>
> With the creation of the Venue Selection committee, the IAOC
> has also chosen to conclude the work of the Meetings
> Committee, effective March 23, 2018 (i.e., Friday of the IETF
> 101 meeting).
>
> I'll take this opportunity to thank Ole Jacobsen for his
> many years of service in chairing the Meetings Committee, as
> well as all the Meetings Committee members for their hard work
> over the years, helping the IETF broaden its scope of meeting
> locations and getting us well set up for the future.
>
> Information about all current IAOC committees is available
> here: https://iaoc.ietf.org/committees.html .
>
> Leslie Daigle,
> IAOC Chair.
>
> Venue Review Committee
>
> Approved 22 February 2018 to be effective as of IETF 101
>
> Background
>
> The Venue Review Committee provides support to the
> professional meeting staff to ensure that venues selected for
> IETF meetings are tuned to IETF community requirements. This
> includes:
>
> reviewing and providing input to the IETF meeting calendar
> (based on the planned IETF meeting schedule and general
> geography)
>
> ensuring there is an up to date public resource with
> structured information about potential cities and venues
> (e.g., which cities have been reviewed and seem reasonable,
> which are off the table because of lack of appropriate meeting
> venue, etc) and accepting community input in maintaining the
> information
>
> reviewing possible meeting cities and venues with the
> Secretariat staff and NOC lead; providing the IAOC with any
> appropriate feedback where its attention may be needed as
> regards the meeting requirements laid out in
> draft-ietf-mtgvenue-iaoc-venue-selection-process-12.
>
> reviewing community feedback on proposed venues and
> contributing to the meeting proposal package that is prepared
> for approval.
>
> The number and general geographic layout of IETF meetings is
> decided elsewhere. The overall meeting requirements are laid
> out in draft-ietf-mtgvenue-iaoc-venue-selection-process-12.
>
> The Venue Review Committee shall report to the IAOC monthly
> unless circumstances dictate that the IAOC be informed sooner.
>
> Mailing list: venue-review@xxxxxxxx
>
> Members
>
> <tbd>
> Jim Martin
>
> Staff
>
> Kirsten Machi
> Stephanie McCammon
> Alexa Morris
> Laura Nugent
> Portia Wenze-Danley
>
