Re: [97attendees] Food poisoning

John C Klensin <john-ietf@jck.com> Mon, 21 November 2016 02:05 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: 97attendees@ietfa.amsl.com
Delivered-To: 97attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C933D129490 for <97attendees@ietfa.amsl.com>; Sun, 20 Nov 2016 18:05:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.397
X-Spam-Level:
X-Spam-Status: No, score=-3.397 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.497] 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 1BU2WLtN_T4g for <97attendees@ietfa.amsl.com>; Sun, 20 Nov 2016 18:05:53 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A86CC129418 for <97attendees@ietf.org>; Sun, 20 Nov 2016 18:05:53 -0800 (PST)
Received: from [198.252.137.10] (helo=JcK-HP8200) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1c8dzQ-000FUU-Tw; Sun, 20 Nov 2016 21:05:48 -0500
Date: Sun, 20 Nov 2016 21:05:43 -0500
From: John C Klensin <john-ietf@jck.com>
To: Shane Kerr <shane@biigroup.cn>, Aaron Falk <aaron.falk@gmail.com>, 97attendees@ietf.org
Message-ID: <F8A15ECAE54C96BA3B0FF108@JcK-HP8200>
In-Reply-To: <tencent_46D8E03E634BBE997D2525BF@qq.com>
References: <CAD62q9W-VncWdvM4r=p8kGHanmMvTKpsFFtNmv_sbowOr3R2Kw@mail.gmail.com> <tencent_46D8E03E634BBE997D2525BF@qq.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/97attendees/4JkxJj8NflDZ5V5IW2f8VvyASyE>
Subject: Re: [97attendees] Food poisoning
X-BeenThere: 97attendees@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Mailing list of IETF 97 attendees that have opted in on this list." <97attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/97attendees>, <mailto:97attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/97attendees/>
List-Post: <mailto:97attendees@ietf.org>
List-Help: <mailto:97attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/97attendees>, <mailto:97attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Nov 2016 02:05:54 -0000

Aaron,

FWIW, having spend some time talking and working with experts in
food protection (both from public health and what is broadly
called architecture), I tend to agree with Shane and father.

In addition, unless there are fundamental problems with the food
and/or water supply that no one is dealing with, most actual
cases of food poisoning are very local to particular
establishments or food preparers. Probably not a good idea to
condemn an entire city on that basis, at least unless there are
a lot of cases, good data, and/or evidence that local health
authorities just don't care (which is, of course, different from
lack of proof that they do).  To future complicate the
statistics, it is common for the population in some areas to
develop resistance to local varieties of irritating but not
particularly dangerous "bugs" (and chemicals) while visitors to
the area have problems -- it is not an accident that popular
slang terms for badly upset digestive systems by visitors to
many areas are variations on the local term for "tourist".
Issues like that go on Shane's list of "confounding factors"
--safe for locals may not be safe for some visitors.

Incidentally, while the vegetarian advice is probably good, one
gets full protection that way only if one peels and/or washes
one's own vegetables in water whose safety is known and/or
observes other precautions.  :-)

best,
   john


--On Monday, November 21, 2016 09:41 +0800 Shane Kerr
<shane@biigroup.cn> wrote:

> Aaron,
> 
> I would caution against the IETF embarking down the road of
> trying to do ad-hoc public health screening. We have no
> expertise in this area, and our sample size is small, the time
> frame of an IETF meeting is smaller than the potential
> lifetime of food poisoning, and there are so many confounding
> factors that we are unlikely to get any valid results.
> 
> My father worked in public health for 30 years or so - he was
> a food inspector for the US Army. I remember once he told me
> that about half of cases of food poisoning were actually from
> food poisoning, and the other half were non-food-related.
> Contrariwise a lot of food poisoning goes unreported because
> it is mild or contains symptoms similar to other ailments.
> Humans are even harder to diagnose than computer networks, it
> turns out. ;)
> 
> Certainly the IETF can and possibly should consider reviewing
> records and recommendations about all health in potential
> destinations - not just food safety but also other potential
> health problems. (I don't follow the meeting selection process
> so it is possible this is already on a checklist.)
> 
> As a final note, you can avoid all problems with seafood,
> poorly cooked meat and the like by eating vegetarian. ;)
> 
> Cheers,
> 
> --
> Shane