Re: [Mtgvenue] I-D Action: draft-ietf-mtgvenue-iaoc-venue-selection-process-14.txt

Mary B <mary.h.barnes@gmail.com> Thu, 10 May 2018 15:03 UTC

Return-Path: <mary.h.barnes@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2C55124B18; Thu, 10 May 2018 08:03:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 BrnJYCM8HwOM; Thu, 10 May 2018 08:03:48 -0700 (PDT)
Received: from mail-oi0-x22b.google.com (mail-oi0-x22b.google.com [IPv6:2607:f8b0:4003:c06::22b]) (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 17EB41243FE; Thu, 10 May 2018 08:03:48 -0700 (PDT)
Received: by mail-oi0-x22b.google.com with SMTP id y15-v6so2011597oia.13; Thu, 10 May 2018 08:03:48 -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=9Izs9wb7sRejS+DaQDjIOeVP4p8/8lhMQFULjnH11j0=; b=WeR4W3/XQPedx1ySnHxaqbuZU6zKkLoxIOl+VOhiMZrdXcznEowUgaKQ7dWomm59rV J/qIxm6DOnfYoaJlr5jil8XOZMRszL9CFDK5CoW06awnCmi2JXzDCGdR5I3y90X40Bwo hilQ4Kr13oqALWF5u6MPwfVhfhriSdfFOXEK5UyQl80335SEjS/XvR2YLQriu/BfanKX xQY5Q8Mdn2n3dEi7C4Ltn116eP6uEyzGUr+1k8PzfClkdxDKvahHT63SC16HLlS97viU cAjgPB0WtxMZ3xsQlVI3Zo8fpk92S6+omaZKG/IPoTzJ8vQux7g6lEF7wagXIY8aZFFJ FktA==
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=9Izs9wb7sRejS+DaQDjIOeVP4p8/8lhMQFULjnH11j0=; b=KrhtHjKIk11zczInL0/A5fGTWgT/FISkO5jBuoE24+X89cgGKcFX9+owymkXJk6REO FOqIASvwcfKc4keXpvne9gQdkWIYrr8XeFMaVgDeaMficYmnZ240rjhhKxgHS2hImwFU 4F5Pguu5tipSrLbpxsKmwqjf8SoL4S0cnd9Axak24uMKxBl3wG2CC/Vs+bQDDPqwYwXB xTS1oS/CDp45LXIBLfve1VR2wQVzUoXV2HNPSrf95qWroQxizCzKicEJaY5uE+1Obc1q JLRSkBm+G3tU6QixG5PJLgEzrt+O1WoTr5U446mjnslKpr0pUyFgfHzLhmzzP8kSLmAP m/ww==
X-Gm-Message-State: ALKqPwfJXZ+ITKwSDI/mt8qXQZ8Bmlwt7pLUorkOXuQNdJDPDd+WME3r qPKcErQJSNc4cIeTq/ToiFiLfYCHeTru96XfyTo=
X-Google-Smtp-Source: AB8JxZoVue53F6xvn7igVNdmlwNnGxoaSK9zTsTfno8WwXxU9XXHPVE5rxdo04awNcrPZVnk87ivsroHuOwhUFa4EV0=
X-Received: by 2002:aca:db44:: with SMTP id s65-v6mr1064958oig.157.1525964627331; Thu, 10 May 2018 08:03:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.201.20.34 with HTTP; Thu, 10 May 2018 08:03:46 -0700 (PDT)
In-Reply-To: <20180510021428.GG9500@mx4.yitter.info>
References: <152584638193.2839.7801870228413280951@ietfa.amsl.com> <c30fd21a-85ee-734c-771c-00ff65490acb@cisco.com> <CABmDk8=HKLR89dvDTuO4eguPE5LCV-YPmcbBr1WdUuFNi+NsBw@mail.gmail.com> <20180510021428.GG9500@mx4.yitter.info>
From: Mary B <mary.h.barnes@gmail.com>
Date: Thu, 10 May 2018 10:03:46 -0500
Message-ID: <CABmDk8=jyJ_AD+gH10-=Bp2f8Ed-kyxC+8j+gjpq-4N7CsXdzQ@mail.gmail.com>
Subject: Re: [Mtgvenue] I-D Action: draft-ietf-mtgvenue-iaoc-venue-selection-process-14.txt
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Cc: "mtgvenue@ietf.org" <mtgvenue@ietf.org>, ietf <IETF@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000008d4fbc056bdb53bb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Q4yUBoKHw0VXvvRuBDq7q_3cuJE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 May 2018 15:03:50 -0000

Andrew’s suggestion of removing he non-smoking bullet and adding the
general one is fine with me.  My big issue was that if we were explicitly
including mandatory requirements for non-smoking then the mold should be
given equal consideration.

Thanks,
Mary

On Wednesday, May 9, 2018, Andrew Sullivan <ajs@anvilwalrusden.com> wrote:

> Dear colleagues,
>
> Mary's, Ted's, and Ole's discussion of particulars of environmental
> contaminents (in this case, smoking and mo[u]ld) makes me again wish
> to suggest the position I held before the specific change was made to
> draft-ietf-mtgvenue-iaoc-venue-selection-process-14.  My position at
> the time was that the Important criterion
>
>    o  Economic, safety, and health risks associated with this Venue are
>       acceptable.
>
> was what we needed.  It was pretty unlikely to be traded off with any
> kind of regularity, since "risk" and "acceptable" were sufficiently
> flexible that we'd need to call out things that were in stark contrast
> to what we normally dealt with.  In any case, I thought, further
> specification would be a problem.  Therefore, I claimed, the above
> criterion was as good as anyone could reasonably expect and it seemed
> that the details needed to be left to meeting planners.  (I didn't
> support it becoming Mandatory because the "are acceptable" language
> means that there's no test, so no way to know whether the Venue
> necessarily fails.)
>
> We are now in the situation where we have a Mandatory criterion about
> smoking in various parts of the Venue, and at least one person who
> claims that such a Mandatory criterion requires site-visiting staff to
> do some kinds of spot checks.  It's totally unclear to me what that
> would mean or what we would do if, 2 or more years later when we
> actually show up, the spot checks turn out to have been wrong.
>
> We are now also faced with the suggestion that the same staff are
> supposed to do mo[u]ld tests without having the requisite training or
> hazardous materials equipment.  If in fact we are demanding staff do
> such things, it seems to me at least plausible that staff would have a
> future complaint if we did not provide them with appropriate equipment
> to undertake the tests.  This is, I think, an important reason why we
> cannot realistically mandate such tests.
>
> Moreover, once we begin requiring such tests by staff, there are other
> pollutants that (1) could be required to be tested and (2) are not yet
> mentioned in the document, either because we haven't yet thought of
> (or discovered) them or because someone who is affected wasn't
> involved in all this.
>
> Therefore, I would like again to propose that we go back to the
> previous text -- which had the nice advantage too of having had
> consensus in the WG -- and drop the new Mandatory criterion in section
> 3.1, relying on staff to do their level best (as they ever have done)
> to address health issues that are likely to affect IETF participants
> at meetings.
>
> None of this, please note, is in any way intended to minimise or
> denigrate the health issues (or even discomforts, for all that) people
> have talked about.  But we need a document that establishes
> principles, not rules.  If one's particular concern cannot be covered
> under the principles laid out, then I think it would be most important
> to raise that.  But this particular change seems to me to be the
> addition of a specific rule where an exising principle in the document
> was already adequate to the purpose.
>
> Best regards,
>
> A
>
> --
> Andrew Sullivan
> ajs@anvilwalrusden.com
>
>

-- 
Sent from Gmail Mobile