[Mtgvenue] Review of draft-ietf-mtgvenue-iaoc-venue-selection-process-04
"John Dickinson" <jad@sinodun.com> Mon, 30 January 2017 18:58 UTC
Return-Path: <jad@sinodun.com>
X-Original-To: mtgvenue@ietfa.amsl.com
Delivered-To: mtgvenue@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C6778129AAD for <mtgvenue@ietfa.amsl.com>; Mon, 30 Jan 2017 10:58:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 XZDthl6rR3NH for <mtgvenue@ietfa.amsl.com>; Mon, 30 Jan 2017 10:58:22 -0800 (PST)
Received: from balrog.mythic-beasts.com (balrog.mythic-beasts.com [IPv6:2a00:1098:0:82:1000:0:2:1]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 20A0A12957C for <mtgvenue@ietf.org>; Mon, 30 Jan 2017 10:58:22 -0800 (PST)
Received: from [92.23.35.133] (port=50988 helo=[192.168.1.101]) by balrog.mythic-beasts.com with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from <jad@sinodun.com>) id 1cYH9g-00036q-64 for mtgvenue@ietf.org; Mon, 30 Jan 2017 18:58:20 +0000
From: John Dickinson <jad@sinodun.com>
To: mtgvenue@ietf.org
Date: Mon, 30 Jan 2017 18:58:25 +0000
Message-ID: <DFD97C10-83BB-4BDB-A4BB-11420089C56F@sinodun.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.6r5319)
X-BlackCat-Spam-Score: -28
X-Mythic-Debug: State = no_sa; Score =
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/AwbVzZD0KUtY9iLh34RKwG7QaQE>
Subject: [Mtgvenue] Review of draft-ietf-mtgvenue-iaoc-venue-selection-process-04
X-BeenThere: mtgvenue@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "List for email discussion of the IAOC meeting venue selection process." <mtgvenue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mtgvenue>, <mailto:mtgvenue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mtgvenue/>
List-Post: <mailto:mtgvenue@ietf.org>
List-Help: <mailto:mtgvenue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mtgvenue>, <mailto:mtgvenue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Jan 2017 18:58:24 -0000
Thanks to all who have put so much work into this draft and to the past meeting organisers who have organised many fantastic meetings. As a wheelchair user I have a few comments… §3.1. There is no mention of accessible transport between airport and hotel. At every meeting I have to remotely pre-book a wheelchair accessible taxi for the airport transfer, some of which (even though arranged via the venue hotel) turned out to be unsuitable/unsafe. At the last Hawaii IETF we were told that there was only one wheelchair capable taxi on the entire island that had to be booked days in advance for any trip! §3.2. Could someone explain the reasoning behind the different requirements levels for “The Facility permits easy wheelchair access.” and “The Facility is accessible by people with disabilities.”? I have just seen the discussion between Dave and Stephen. Dave, could your comments defending the difference be added to the draft to justify the distinction. §3.4 Same question again. Also, I would like to see some mention of a pool of accessible rooms being available in the IETF reservation and that those rooms be reserved for people who require them. I don’t know how large this pool needs to be. In Yokohama due to maintenance at the hotel there were no fully wheelchair accessible rooms in the hotel. §3.5 “as well as areas within a reasonable walking distance or conveniently accessible by a short taxi, bus, or subway ride, have convenient and inexpensive choices for meals that can accommodate a wide range of dietary requirements.” A reasonable number of the areas and restaurants also need to be accessible. In Toronto, and Berlin we ended up using a bike lock to secure my chair in the street. IIRC the state of the sidewalks in Toronto were almost inaccessible for people without disabilities! The pavements in Bueno Aires were also heavily damaged in places. Venue and Lodging: In several recent meetings there have been areas of the hotel or venue that were off limits due to wheelchair lifts that could only be operated by a member of staff with a key. I am lucky enough that I can still walk short distances but for others it would (in Toronto I think) have prevented access to the bar! Heavy doors: It is often the case that meeting room doors are so heavy they could not be opened by an unaccompanied wheelchair user. I have been to several meetings (not just ietf) where coaches to social events could not accommodate a non-collapsible chair. I either walk on the coach and hope that the other end does not involve too much walking or I have to make my own way there. In general, the document is very light on accessibility issues and perhaps, given the wide range of potential disabilities, the authors could consider getting some professional advice. Maybe it is something the ADA could help with?? I know we don’t live in a perfect world and I don’t expect everything I described to be perfect in every location but at least these things (among may others) should be considered. John Dickinson http://sinodun.com Sinodun Internet Technologies Ltd. Magdalen Centre Oxford Science Park Robert Robinson Avenue Oxford OX4 4GA U.K.
- [Mtgvenue] Review of draft-ietf-mtgvenue-iaoc-ven… John Dickinson
- Re: [Mtgvenue] Review of draft-ietf-mtgvenue-iaoc… Brian E Carpenter
- Re: [Mtgvenue] Review of draft-ietf-mtgvenue-iaoc… Spencer Dawkins at IETF
- Re: [Mtgvenue] Review of draft-ietf-mtgvenue-iaoc… John Dickinson