Re: [HT-rt] HR-RT Review of draft-ietf-mtgvenue-iaoc-venue-selection-process

Mary B <mary.h.barnes@gmail.com> Fri, 20 April 2018 15:08 UTC

Return-Path: <mary.h.barnes@gmail.com>
X-Original-To: hr-rt@ietfa.amsl.com
Delivered-To: hr-rt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF9C412D7E8 for <hr-rt@ietfa.amsl.com>; Fri, 20 Apr 2018 08:08:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level:
X-Spam-Status: No, score=-1.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, GB_AFFORDABLE=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=no 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 l556LrXkXrSe for <hr-rt@ietfa.amsl.com>; Fri, 20 Apr 2018 08:08:36 -0700 (PDT)
Received: from mail-oi0-x232.google.com (mail-oi0-x232.google.com [IPv6:2607:f8b0:4003: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 057B61275F4 for <hr-rt@irtf.org>; Fri, 20 Apr 2018 08:08:36 -0700 (PDT)
Received: by mail-oi0-x232.google.com with SMTP id 126-v6so8318047oig.0 for <hr-rt@irtf.org>; Fri, 20 Apr 2018 08:08:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=vz9XtZrW+pxSd9y7Y0hxz3fDNZF0B592cTplPBMXoYA=; b=UUPXDdOVmQH2U22e5lDCEiA9bAwNNk97iE5z4xyxik2f/6LBo+U6Pij2gXXQGfvIg1 P59pITnqp+/8kLNu2XaqJnz6rzfniMPhOszorMO7bz1knsZWgOkTTRstFurstyO/I5fW IirnYwUpewMJMUl/FWv12o11SGJsKSRfAWgzZpMojLuNiSNk0Ep7PKF+7LNLEpmTBTE7 CVSx7Uywn53pNqThu7RN0VKNDiaM/UktnCk6oV07wJUYvac0XgEL7WrjytkAssITRVFA io6wxpXqpWsKskMMMAj5YDqA5ItU11K14XGtxnF9JD2Ax2IbTK98Argwnxjbk0pFSmyM 3pWw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=vz9XtZrW+pxSd9y7Y0hxz3fDNZF0B592cTplPBMXoYA=; b=mrfpN0Ba62wOL9UYJ3/u9NsbpZjufokxSp1EvIOUj9rsCo64WBN5c6NIJ1bK7KXPCr A+demleGG/Ri3USvJ3MB+s6/WcimeXkBu7JTrI8zjpv5yRVqylOePKAA83eFPi2jnF2c IZQnMV+7l8RcOHgRc3Ia75rsfkK+yx2oGCLshViB6XDyV0vQlgwnz5zANk9wF6r9NUui cFU+9KqALaajS9ZD13PDLKZI2kLgvIX4Zh/Y5aaiS+y8fSDY3NgtVDtOqjZ6mJuyWbc6 srDgk3Zy1/xR648c/VkGUXsGBvlVI3cWVsrH0/Qm7KwXL7Qs50qCvS5YZ+dQKYX92jod ytMw==
X-Gm-Message-State: ALQs6tAPcaEtTmeHNMokAjbo1pWG3gxXrzNk2yHLxiHqNOduk/txsOjk WpN5YR2QcTM5JqD9jLfFEU+WxtO1yVdzyymDJ4Q=
X-Google-Smtp-Source: AIpwx49ksiSGsXolAAPoUJ2ug+kG4vMrKpJy9fof3/CswvdeGDk4xaQLEwqKJhiVeo+8N/pUFZgf0C/Lv6Yw1WukfaQ=
X-Received: by 2002:aca:5d46:: with SMTP id r67-v6mr6177508oib.257.1524236915272; Fri, 20 Apr 2018 08:08:35 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.201.45.161 with HTTP; Fri, 20 Apr 2018 08:08:34 -0700 (PDT)
In-Reply-To: <7B17FF2E-4393-4644-998B-16462F71A00F@qti.qualcomm.com>
References: <d0739bb2-626e-8aa3-f22f-d51b07dfdacf@digitaldissidents.org> <21952.1524157167@obiwan.sandelman.ca> <7B17FF2E-4393-4644-998B-16462F71A00F@qti.qualcomm.com>
From: Mary B <mary.h.barnes@gmail.com>
Date: Fri, 20 Apr 2018 10:08:34 -0500
Message-ID: <CABmDk8m69CN-A3d+LW8H20mbcBVvroakcVaVBNbKeQ9mwvoWhw@mail.gmail.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
Cc: Niels ten Oever <lists@digitaldissidents.org>, hr-rt@irtf.org, draft-ietf-mtgvenue-iaoc-venue-selection-process@ietf.org, "<ietf@ietf.org>" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000e3949f056a490f5f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hr-rt/HcE1S_P5RALQggy09tHJjVoogAA>
Subject: Re: [HT-rt] HR-RT Review of draft-ietf-mtgvenue-iaoc-venue-selection-process
X-BeenThere: hr-rt@irtf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Human Rights Protocol Considerations Review Team <hr-rt.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/hr-rt>, <mailto:hr-rt-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hr-rt/>
List-Post: <mailto:hr-rt@irtf.org>
List-Help: <mailto:hr-rt-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/hr-rt>, <mailto:hr-rt-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Apr 2018 15:08:39 -0000

I'm glad this discussion has come up.  I have one comment below [MB].

Regards,
Mary.

On Thu, Apr 19, 2018 at 4:08 PM, Pete Resnick <presnick@qti.qualcomm.com>
wrote:

> Hi Niels,
>
> Thanks for the extensive review. Much appreciated. Many of Michael's
> comments are spot on; I'll add my replies below (and trim a bit of the
> explanatory text to save space):
>
> On 19 Apr 2018, at 11:59, Michael Richardson wrote:
>
> Niels ten Oever <lists@digitaldissidents.org> wrote:
>>
>>> This is a review done within the framework of the Human Rights Review
>>> Team, is was done by Beatrice Martini and Niels ten Oever. The Human
>>>
>>
>> Thank you.
>>
>> 1)
>>> Section: 2. Venue Selection Objectives/ 2.1. Core Values
>>>
>>
>> Text from draft:
>>> "Inclusiveness: We would like to facilitate the onsite or remote
>>> participation of anyone who wants to be involved."
>>>
>>
>> We suggest an edit along these lines:
>>> "We would like to facilitate the onsite or remote participation of
>>> anyone who wants to be involved and who may contribute to the diversity
>>> of perspectives represented in the working sessions"
>>>
>>
>> I suggest you reword your suggestion to:
>>    "We would like to facilitate the onsite or remote participation of
>>    anyone who wants to be involved.  Widespread participation
>>    contributes to the diversity of perspectives represented in the
>> working sessions"
>>
>> the problem with the "and" in the sentence is that the sentence can
>> otherwise be parsed
>> to say that we only want to facilitate partition from those who
>> contribute to
>> increased diversity.
>>
>
> I have to agree with Michael's suggestion. In addition to the possible
> ambiguity, there was pretty explicit consensus in the WG that the objective
> was to facilitate people who participants that want to participate, and
> explicitly not to use venue selection for purposes of outreach. Michael's
> reformulation makes that a bit clearer. Does that satisfy your concern?
>
>
> 2)
>>> We find that the current draft is not totally consistent in regards to
>>> the affordability of participation.
>>>
>>
>> This is my intepretation.
>>
>> Initially, it acknowledges that many participants are self-funded, and
>>> that budget solutions should be available. That's great.
>>>
>>
>> From Section 2.  Venue Selection Objectives/ 2.1. Core Values:
>>> "Economics:
>>> Meeting attendees participate as individuals. While many are
>>> underwritten by employers or sponsors, many are self-funded.  In order
>>> to reduce participation costs and travel effort, we therefore seek
>>> locations that provide convenient budget alternatives for food and
>>> lodging, and which minimize travel segments from major airports to the
>>> Venue.  Within reason, budget should not be a barrier to accommodation."
>>>
>>
>> But then, in Section 3.2.2, things sounds less affordable.
>>>
>>
>> From Section 3.2.2 Basic Venue Criteria:
>>> "The cost of guest rooms, meeting space, meeting food and beverage is
>>> affordable, within the norms of business travel."
>>>
>>
>> "Business travel" has commonly a higher cost than "self-funded budget
>>> travel".
>>>
>>
>> The intention is that the *venue* (primary hotel) should not be so
>> expensive as to be prohibitively expensive to even those on "business
>> travel".  There are locations (resorts in really exotic locations) where
>> the nightly price of room is like $500/night.  The intention is to rule
>> those out.
>> As a self-funded individual, I accept that I can't often afford to stay at
>> the primary hotel, but I will find something acceptable within a few
>> blocks.  So that's how section 2 and 3.2.2 are reconciled.
>>
>
> Michael's explanation is correct, but I take your point that "guest rooms"
> in the second bullet of 3.2.2 sounds like the combination of rooms in the
> IETF Hotels, Overflow Hotels, and other nearby local accommodations.
> Perhaps we can clarify. Let's see if Eliot has any thoughts.
>
> 3)
>>> We invite to consider the addition of a few items to Section 3.2.2.
>>> Basic Venue Criteria.
>>>
>>
>> 3.1)
>>> "All Meeting Venues should have at least one gender neutral restroom
>>> with stalls on each floor."
>>>
>>
>> I'd like to support adding this as aspirational, but it's gonna be two
>> hotel renovation cycles before it can be found often enough to be a
>> reasonable criteria.
>>
>
> Given that the 3.1 criteria are those for which IASA MUST NOT enter into a
> contract if they are missing, I don't see how we can make this mandatory at
> this point, unless IASA can tell us that a sufficient number of Facilities
> meet this criterion already. Perhaps something along these lines could be
> added to 3.2.2, but even there I think we'd want input that there are such
> Facilities available, lest the criteria simply be ignored.
>
> On the topic of being family friendly,  the major thing we can do to
>> support families is to outside of the mtgvenue, and is with the nomcom
>> eligibility criteria.
>>
>
> Agreed Michael. :-)
>
> On to the rest of your comments, Niels:
>
> 3.2)
>>> "The Meeting Venue should have at least one dedicated infant feeding
>>> room and one family restroom."
>>>
>>
> I presume you mean "Facility" here and not "Meeting Venue", correct? Like
> the gender neutral restrooms, I think we probably want to hear from IASA
> that this is going to be satisfiable by a reasonable number of Facilities.
>
> 3.3)
>>> "The event should be accessible to non-smokers and those with
>>> respiratory conditions. Therefore all meeting spaces during daytime and
>>> nighttime should make it possible to fully participate in the scheduled
>>> activities without being exposed to second-hand smoke."
>>>
>>
> I have no particular concerns about adding this in section 3.3, barring
> objections.
>
[MB] I think this is a good thing as we had problems with this at the
Prague venue at one time due to the casino.  And, if we're concerned about
air quality and respiratory issues, can we please add to the last
sentence:  "..exposed to second-hand smoke and mold."   The venue in
Singapore had *a lot* of visible water damage, in particular on the
acoustic ceiling tiles that are well known to be a wonderful breeding
ground for mold.  While I might have been the only one that was literally
on the floor due to the extent of mold and the mycotoxins the molds
produce, others did experience respiratory issues and 25% of the population
has the genetic predisposition to get sick from mold exposure - the body
does not recognize and remove the toxins which then remain in the body and
contribute to chronic inflammation.  And, yes, the world is full of mold
and I spend a lot of time in the world and if a place impacts me to the
point it did in Singapore it is a *very* sick building.  [/MB]

3.4)
>>>
>>
> There is no section 3.4 in the document. Did you mean for this to go in
> 3.3?
>
> We believe that supporting parents with small children attending events
>>> is a great step forward towards inclusivity.
>>>
>>> We would like the document to address this aspect in regards to venue
>>> requirements.
>>>
>>> In particular, it would be helpful for the document to provide
>>> information about the following:
>>>
>>> * Can participants feel comfortable and welcome to have their kid(s)
>>> with them at the event? If so, are kids under a certain age not allowed
>>> to be in session rooms?
>>>
>>> * Would the venue provide a childcare space and service, like a
>>> play/activity room managed by a licensed childcare professional? See
>>> further information about childcare at events at:
>>> http://geekfeminism.wikia.com/wiki/Childcare
>>>
>>> If the organization determines that children should not be allowed to
>>> access meetings, and/or no childcare space and service can be provided,
>>> it would anyway be important for the document to acknowledge that the
>>> organization is aware of the limitation that this would constitute and
>>> that this might hinder the participation of some attendees.
>>>
>>
> Whether children can be present in meeting rooms sounds like a policy
> issue beyond the question of venue selection, so I believe is out of scope
> for the document.
>
> As for whether having childcare services available at the Facility or
> Hotels should go in 3.3, I have no particular concerns about adding it,
> again, barring objections.
>
> 4)
>>> We invite to consider the addition of one item to Section 3.3 Other
>>> Considerations.
>>>
>>> Section 3.2.2 Basic Venue Criteria says:
>>> "The Facility is accessible or reasonable accommodations can be made to
>>> allow access by people with disabilities."
>>>
>>> This is great!
>>> At the same time, sometimes one person's required accommodation might
>>> create a barrier for someone else. For example, the same session could
>>> be attended by one participant with a guide dog, and another participant
>>> with a severe allergy to dogs.
>>>
>>> It would be ideal if the document could mention a consideration on this
>>> type of conflicting requirements that might occur. For example, it could
>>> say that, in the full respect of everyone's needs, the organizing team
>>> will aim to find the most suitable solution on a case by case basis.
>>>
>>> This statement should also include information about who / what team can
>>> be contacted to ask for information in case of need.
>>>
>>
> I think adding a short informational note to that bullet in 3.2.2 makes
> sense. I'll again leave it to Eliot to see if he can come up with something.
>
> 5)
>>> Correct typo in the title: "3.3. Other Consideraitons"
>>>
>>> Edit: "3.3. Other Considerations"
>>>
>>
> Of course.
>
> Thanks again for the great comments.
>
> pr
>
>