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

Mary B <> Wed, 09 May 2018 16:47 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D405912DDD2; Wed, 9 May 2018 09:47:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -0.099
X-Spam-Status: No, score=-0.099 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id z-iWYMRq_3d4; Wed, 9 May 2018 09:47:44 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4003:c0f::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 66BEF12D95F; Wed, 9 May 2018 09:47:44 -0700 (PDT)
Received: by with SMTP id n1-v6so40910342otf.7; Wed, 09 May 2018 09:47:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=C9tEqnpHUTMwkjC6/7BppmdyWkoU8B0rv2w9MOvPMK8=; b=gPQeLJ9Hsd3dYP+3shtFhA8IFGMiUw/5xx10NJR3izBFz+Nu6Uk+aisHfy8CdwqJdi 2e3WzgouXPCnH6PKQUSovODVFMwdsZakbJtiGiXvk8LPmGKpvDnjaD68KGUaHffqqeN0 PLg2OZVcO9MLAArs7ReAoFayl5+BNYcGa5Z3JNe4B2j0wsemKB8CABIOiDHXDei37n87 quAXnVwKwb3evK8Z6e8kXtplD7SI9rClcXEaiEwah+bMi0AtUrvmemg+JmW5yKL9UFzS HSavRWXthgfErKlmst5xPeKJ8OxddcqsSCoIuev1gKtn3xCky8jdrN26qjwXPCSvbwcR 4Yfg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=C9tEqnpHUTMwkjC6/7BppmdyWkoU8B0rv2w9MOvPMK8=; b=bGQOlGOyRiN4nRjbvYPXrWC0j2VyQm9m5y7FYcCvxdjZ2UM6UrYTHsK9jB3ZSn9ipa 956s169hFnMrNGUtVYSdL5KVxjVv+7BuK8LLJyfhwWUkW0KSKpEyVnvZgj/tJTtK2T2Y vKl9oXtc/qBZFsxSvOfYUiMVVtIhYaRuhdjpCBtbIrBZQQnasgvSsT40WqLrHdLgLVU3 VcQoUvKsB6HPF+wobdPr+81MNsiUrLcgWqYQtqQqqLN9XfWZ/M9+ZS/me55CG2ou77AE mhh3c8RNfhXY83MVFV4BDbOxtfZhrTwl6BRy67JFhYgtMdxtBa1OwLRptQS6DRgQM1Bk 1Vpg==
X-Gm-Message-State: ALQs6tAH4zPVpnI3X8La+1lYMGrlfDt5mN+a3aUZOKqizvr6DmQJSP/A 5AsG1HCybfxoXQDImwzk2y/6QdG8cxNa8K4Ju4c=
X-Google-Smtp-Source: AB8JxZqQx5FLoXit0euAs9aDamC5guo4G3g8YBWYQ9T5I5/eF+NDjmP7j/q0sePa8hH2ES3vxzAPQzvvFf4LexHBfMY=
X-Received: by 2002:a9d:2171:: with SMTP id l46-v6mr31062398otd.50.1525884463432; Wed, 09 May 2018 09:47:43 -0700 (PDT)
MIME-Version: 1.0
Received: by with HTTP; Wed, 9 May 2018 09:47:42 -0700 (PDT)
In-Reply-To: <>
References: <> <>
From: Mary B <>
Date: Wed, 09 May 2018 11:47:42 -0500
Message-ID: <>
To: Eliot Lear <>
Cc: ietf <>,
Content-Type: multipart/alternative; boundary="000000000000694729056bc8a9ad"
Archived-At: <>
Subject: Re: [Mtgvenue] I-D Action: draft-ietf-mtgvenue-iaoc-venue-selection-process-14.txt
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "List for email discussion of the IAOC meeting venue selection process." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 09 May 2018 16:47:48 -0000

I personally do not find it acceptable that the bullet was added for
Non-smoking, yet mold is totally being ignored.  Mold has the potential to
have far more severe health impacts than secondhand smoke.  I can point to
tons of published medical research on this topic.  Just because some feel
it is a harder thing to accommodate doesn't mean it should be of lower
priority than smoking.   And, no it's not just me that's impacted - I just
have a more overt reaction, but 25% of our participants are being impacted
- it's an additive impact.  And, the impact on a fetus should one of our
participants be pregnant can be significant (again, I'm happy to provide

Symptoms of mold illness start as very non-specific and many just think
their allergies are getting worse (which is one aspect but the inhaled
mycotoxins are not recognized and removed due to an innate immune system
defect.   And, the fact that we had a meeting in a venue that had such
overt, obviously long term, water damage just isn't acceptable and clearly
means that unlike the smoking issue it isn't a "current (implied)
practice"  to avoid such, as Alissa noted in her email with regards to
smoking.  I've offered to educate folks on some basic things to look for
and how to do a very, very simple test.  And, no this would not
significantly limit venues since this has been the only venue where we have
met for the 20 years I've attended IETF that had the issue.   That's a
bogus argument for not addressing this concern.

And, while some folks might think that I just shouldn't attend meetings in
places that have a higher risk,  I will continue to do so as long as my job
requires.  And, any building can have toxic mold no matter where it's
located.  I go to many places that have water damage and some mold, but
don't have an overt reaction because it's not the toxic levels that we
encountered in Singapore.   And, if I go to Bangkok, I will be prepared -
Tyvek suit, mold mask and most importantly a test kit so I can get a sample
if I encounter issues.    I do find it quite ironic that we have a RG to
look into human rights related to protocols, etc. but the basic human right
to breath air that isn't full of mycotoxins, while attending meetings to
develop such protocols, seems to be easily ignored.


On Wed, May 9, 2018 at 3:48 AM, Eliot Lear <> wrote:

> This draft addresses feedback from LC.  It includes the resolutions
> Alissa previously mentioned, in addition to a small number of agreed
> edits (update normative language, correct grammar, add some
> informational text around inclusivity, no smoking).
> Eliot
> On 09.05.18 08:13, wrote:
> > A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> > This draft is a work item of the Meeting Venue WG of the IETF.
> >
> >         Title           : IETF Plenary Meeting Venue Selection Process
> >         Author          : Eliot Lear
> >       Filename        : draft-ietf-mtgvenue-iaoc-
> venue-selection-process-14.txt
> >       Pages           : 14
> >       Date            : 2018-05-08
> >
> > 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 IETF datatracker status page for this draft is:
> >
> venue-selection-process/
> >
> > There are also htmlized versions available at:
> >
> venue-selection-process-14
> >
> iaoc-venue-selection-process-14
> >
> > A diff from the previous version is available at:
> >
> venue-selection-process-14
> >
> >
> > Please note that it may take a couple of minutes from the time of
> submission
> > until the htmlized version and diff are available at
> >
> > Internet-Drafts are also available by anonymous FTP at:
> >
> >
> > _______________________________________________
> > Mtgvenue mailing list
> >
> >
> >