Russ,
Thanks for the review. On your overall comment:
On 17 Apr 2018, at 12:29, Russ Housley wrote:
Thanks for putting this document together. I have one overall comment and a couple of nits.
I think that an overall goal is missing. We try to share the load among IETF participants. That is the reason we rotate between North America, Europe, and Asia-Pacific. Without this goal, the IETF might select the one perfect location and hold every meeting there.
Do you not think that the paragraph in 2.1 addresses this?
We meet in different locations globally, in order to spread the
difficulty and cost of travel among active participants, balancing
travel time and expense across the regions in which IETF
participants are based.
Or did you mean that you wanted it stated up front more clearly?
For the editorial bits, I will leave Eliot to address those.
pr
The document uses "Venue" and "venue" in many, many places. I cannot figure out what the presence or absence of the capital letter is trying to convey.
Section 4 says:
The IETF Community works best when it is best informed.
It might be better to say:
The IETF Community works best when it is well informed.
In Section 1, please update the last paragraph to reference RFC 8174 in addition to RFC 2119, as follows:
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in
BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in
all capitals, as shown here.Russ
On Apr 5, 2018, at 4:12 PM, The IESG iesg-secretary@xxxxxxxx wrote:
The IESG has received a request from the Meeting Venue WG (mtgvenue) to
consider the following document: - 'IETF Plenary Meeting Venue Selection
Process'
<draft-ietf-mtgvenue-iaoc-venue-selection-process-13.txt> as Best Current
PracticeThe IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
ietf@xxxxxxxx mailing lists by 2018-04-19. Exceptionally, comments may be
sent to iesg@xxxxxxxx instead. In either case, please retain the beginning of
the Subject line to allow automated sorting.Abstract
The IASA has responsibility for arranging IETF plenary meeting Venue
selection and operation. This memo specifies IETF community
requirements for meeting venues, including hotels and meeting room
space. It directs the IASA to make available additional process
documents around that describe the current meeting selection process.The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-mtgvenue-iaoc-venue-selection-process/IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-mtgvenue-iaoc-venue-selection-process/ballot/No IPR declarations have been submitted directly on this I-D.
