Re: [HT-rt] HR-RT Review of draft-ietf-mtgvenue-iaoc-venue-selection-process
Beatrice Martini <mail@beatricemartini.it> Fri, 20 April 2018 13:14 UTC
Return-Path: <mail@beatricemartini.it>
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 0195B12D77B for <hr-rt@ietfa.amsl.com>; Fri, 20 Apr 2018 06:14:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.185
X-Spam-Level:
X-Spam-Status: No, score=-1.185 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, GB_AFFORDABLE=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, T_DKIMWL_WL_MED=-0.01, URIBL_GREY=0.424] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=beatricemartini-it.20150623.gappssmtp.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 e3WUe4EtF6gO for <hr-rt@ietfa.amsl.com>; Fri, 20 Apr 2018 06:14:38 -0700 (PDT)
Received: from mail-io0-x235.google.com (mail-io0-x235.google.com [IPv6:2607:f8b0:4001:c06::235]) (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 207A812D7E4 for <hr-rt@irtf.org>; Fri, 20 Apr 2018 06:14:35 -0700 (PDT)
Received: by mail-io0-x235.google.com with SMTP id l2-v6so9025144iog.9 for <hr-rt@irtf.org>; Fri, 20 Apr 2018 06:14:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=beatricemartini-it.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=qJ4ypEj+Wiu2KLcX8rSGUW1clTv6eRcvQtZOmvwpkUk=; b=DVEkmPNi1pJla03R89X4rSTLoj2gVN/U449zdXdEWdX/UBhFPvOa8BO2y2FwuS2/eE QMQgAN0CE+/ApJQAW7hC5uvTqTHtRUKYg3xF26gY2O+/1LTxmbmiPBaLP7WJxa7dqUF/ OnIfMrhyE1SAS9uv9otZ7m7LqmLOkJmAnx7QxlIAoOqdEAaS/MzbErZxV37O5yrDwDaA YKiTvRsgp3yv3TpQnNjOwOwLWWP/fG1Qh2qNCakr4Z/yM2fTwoFodvn3waYBBBIBmxoJ quZYQH/O7eNSS3R7Z0WJfQZhGrftpWsFQlfvSDPcOeIkBijKgFNaBwTFSjtSWIRCJW7u eKjQ==
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=qJ4ypEj+Wiu2KLcX8rSGUW1clTv6eRcvQtZOmvwpkUk=; b=iS+G/+1IaNBgQb94fYwgqtgPvbbYddS4r0qUBjA/x4hCW2ZfxbiXEH1Wb8V3UcnldX c4DkR2G1yPxYroy4PUvhUYucNW3YJ5FtUCf+mgNc2VTXIg66+pILa+tdbFo5CoG4F7L/ BKTSxK+4vb1aH1y2N/GS8tMRNrM2+lF3BDK8/CuERqwLeTv3Cq2KDbLvDha2O/UTzsw5 UEddshkfkc9IkhzGodCI+VaM/6CgxN/2xqSI3nPx3lCXUuOXoF/XhlU4DwF787QG50Fi vPHjixgNySW3fxScJt132iKR8XfnDMKq55dCpaDu54PDUDzy3OlkPNwnakKMdxLxbZYN EpWw==
X-Gm-Message-State: ALQs6tDyFSfJnEClgUJGtoHEbvtB7/0n2mJ4wxuMYKtAaasNNPZKVuTZ auWRj5LKQeqQc5NngkSAALIyrMtbPGSTET1frEIbfg==
X-Google-Smtp-Source: AIpwx48gh2CkukvsItaPbZYVCeuvffCwIAm9MPEg1GhC+odNkGd5nbszQ8pZdjI1c+LvNzxq0MTtDzEtqj+OPgQMGAU=
X-Received: by 2002:a6b:2583:: with SMTP id l125-v6mr10757907iol.151.1524230075149; Fri, 20 Apr 2018 06:14:35 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a02:840e:0:0:0:0:0 with HTTP; Fri, 20 Apr 2018 06:14:34 -0700 (PDT)
In-Reply-To: <7f7fced1-489b-94a8-170b-0038e330484f@digitaldissidents.org>
References: <d0739bb2-626e-8aa3-f22f-d51b07dfdacf@digitaldissidents.org> <21952.1524157167@obiwan.sandelman.ca> <7B17FF2E-4393-4644-998B-16462F71A00F@qti.qualcomm.com> <7f7fced1-489b-94a8-170b-0038e330484f@digitaldissidents.org>
From: Beatrice Martini <mail@beatricemartini.it>
Date: Fri, 20 Apr 2018 15:14:34 +0200
Message-ID: <CA+0Hr7tNwgLAauPQ28fEaz2LVer9XYHxoaU88fV=aqqruMfE+A@mail.gmail.com>
To: Niels ten Oever <lists@digitaldissidents.org>
Cc: Pete Resnick <presnick@qti.qualcomm.com>, hr-rt@irtf.org, draft-ietf-mtgvenue-iaoc-venue-selection-process@ietf.org, ietf@ietf.org
Content-Type: multipart/alternative; boundary="0000000000002f8fac056a4778fd"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hr-rt/Wwpgx-xp6pJj4yx7R4xgtbTPk0A>
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 13:14:41 -0000
Hi Michael, hi Pete, Thank you for your prompt responses. Best, Beatrice On 20 April 2018 at 13:08, Niels ten Oever <lists@digitaldissidents.org> wrote: > Hi all, > > Thanks for the great responses! > > On 04/19/2018 11:08 PM, Pete Resnick 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? > > > > Yes! > > >>> 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. > > > > 3.2.2 would be nice, also because asking hotels/venues for this also > would prompt them to include it in their renovation plans. > > >> 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. :-) > > One does not exclude the other imho. > > > > > 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. > > > > I would be surprised if this would not be the case. > > >>> 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. > > > >>> 3.4) > > > > There is no section 3.4 in the document. Did you mean for this to go in > > 3.3? > > > > Yes, sry. > > >>> 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. > > > > Thanks > > >>> 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 > > Our pleasure! > > Best, > > Niels > > -- > Niels ten Oever > Head of Digital > > Article 19 > www.article19.org > > PGP fingerprint 8D9F C567 BEE4 A431 56C4 > 678B 08B5 A0F2 636D 68E9 > > _______________________________________________ > HR-rt mailing list > HR-rt@irtf.org > https://www.irtf.org/mailman/listinfo/hr-rt > -- Beatrice Martini Twitter <https://twitter.com/beatricemartini> / Blog <http://beatricemartini.it/blog/> / Newsletter <http://eepurl.com/bbDuEn>
- [HT-rt] HR-RT Review of draft-ietf-mtgvenue-iaoc-… Niels ten Oever
- Re: [HT-rt] HR-RT Review of draft-ietf-mtgvenue-i… Michael Richardson
- Re: [HT-rt] HR-RT Review of draft-ietf-mtgvenue-i… Pete Resnick
- Re: [HT-rt] HR-RT Review of draft-ietf-mtgvenue-i… Niels ten Oever
- Re: [HT-rt] HR-RT Review of draft-ietf-mtgvenue-i… Beatrice Martini
- Re: [HT-rt] HR-RT Review of draft-ietf-mtgvenue-i… Mary B
- Re: [HT-rt] HR-RT Review of draft-ietf-mtgvenue-i… Eliot Lear
- Re: [HT-rt] [EXTERNAL] Re: HR-RT Review of draft-… Deen, Glenn (NBCUniversal)
- Re: [HT-rt] [EXTERNAL] Re: HR-RT Review of draft-… Brian E Carpenter
- Re: [HT-rt] [EXTERNAL] Re: HR-RT Review of draft-… Mark Perkins
- Re: [HT-rt] [EXTERNAL] Re: HR-RT Review of draft-… Eliot Lear
- Re: [HT-rt] [EXTERNAL] Re: HR-RT Review of draft-… Deen, Glenn (NBCUniversal)
- Re: [HT-rt] [EXTERNAL] Re: HR-RT Review of draft-… Deen, Glenn (NBCUniversal)
- Re: [HT-rt] [EXTERNAL] Re: HR-RT Review of draft-… Eliot Lear
- Re: [HT-rt] HR-RT Review of draft-ietf-mtgvenue-i… Beatrice Martini
- Re: [HT-rt] HR-RT Review of draft-ietf-mtgvenue-i… Beatrice Martini
- Re: [HT-rt] [EXTERNAL] Re: HR-RT Review of draft-… Eliot Lear