Re: [72attendees] New mailing list to discuss IETF Food requirements

"Mary Barnes" <mary.barnes@nortel.com> Tue, 26 August 2008 18:13 UTC

Return-Path: <72attendees-bounces@ietf.org>
X-Original-To: 72attendees-archive@ietf.org
Delivered-To: ietfarch-72attendees-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D1B613A69E7; Tue, 26 Aug 2008 11:13:21 -0700 (PDT)
X-Original-To: 72attendees@core3.amsl.com
Delivered-To: 72attendees@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AF9A83A685B for <72attendees@core3.amsl.com>; Tue, 26 Aug 2008 11:13:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.11
X-Spam-Level:
X-Spam-Status: No, score=-5.11 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hbZ1mYmxb7wJ for <72attendees@core3.amsl.com>; Tue, 26 Aug 2008 11:13:19 -0700 (PDT)
Received: from zcars04e.nortel.com (zcars04e.nortel.com [47.129.242.56]) by core3.amsl.com (Postfix) with ESMTP id 5B5DE3A6962 for <72attendees@ietf.org>; Tue, 26 Aug 2008 11:13:19 -0700 (PDT)
Received: from zrc2hxm1.corp.nortel.com (zrc2hxm1.corp.nortel.com [47.103.123.72]) by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id m7QIAsc00376; Tue, 26 Aug 2008 18:10:54 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 26 Aug 2008 13:10:33 -0500
Message-ID: <F66D7286825402429571678A16C2F5EE0508B21F@zrc2hxm1.corp.nortel.com>
In-Reply-To: <48B44333.4060905@dcrocker.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [72attendees] New mailing list to discuss IETF Food requirements
thread-index: AckHpLxhbftgI+heSeePuvsVOeOkIwAAEY/Q
References: <F66D7286825402429571678A16C2F5EE04FE7247@zrc2hxm1.corp.nortel.com> <48B44333.4060905@dcrocker.net>
From: "Mary Barnes" <mary.barnes@nortel.com>
To: <dcrocker@bbiw.net>
Cc: 72attendees@ietf.org
Subject: Re: [72attendees] New mailing list to discuss IETF Food requirements
X-BeenThere: 72attendees@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Discussion list for the attendees of IETF 72 meeting." <72attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/72attendees>, <mailto:72attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/72attendees>
List-Post: <mailto:72attendees@ietf.org>
List-Help: <mailto:72attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/72attendees>, <mailto:72attendees-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: 72attendees-bounces@ietf.org
Errors-To: 72attendees-bounces@ietf.org

Sure...the idea is for the information flow to go both ways.  But in my
experience, the burden of accomodating folks like us is really quite
minimal if things are properly planned in advance. I also know of other
SDOs that manage this quite well (e.g., providing kosher lunches
separately and there are already accomodations for vegetarians when IETF
provides lunch.  It really is as simple as making the staff aware of the
needs since the venues at which IETF holds meetings are typically the
largest and most experienced available. Even in Dublin, once the staff
was aware, accomodations were made - it just made Monday lunchtime
particularly miserable and hectic for everyone (due to no advance
planning - I had successfully eaten at the hotel, so didn't realize how
constrained our lunch options would be) and for some of us, unless foods
are labeled or servers are trained, we still can't eat it.   

I have no doubt that if everyone was impacted in such a way (i.e., no
suitable meal for over 12 hours during the day) that folks would expect
something to be done. And, as I've said before if IETF were to have a
meeting at a location with no cookies or beer, there would certainly be
far more complaints and concerns. And, the no nuts in the cookies folks
were accomodated in the past.  

I do realize that for folks that don't have these limitations, the whole
idea that this requires ANY discussion seems quite trite and whiny, but
again my experience is that the difference in folks' attitudes about
this changes TREMENDOUSLY when it impacts them personally or they have a
family member that's impacted.  

I have already started looking into food options for Minneapolis and
that's one of the things I will post on that list. 

Thanks,
Mary Barnes.


-----Original Message-----
From: Dave CROCKER [mailto:dhc@dcrocker.net] 
Sent: Tuesday, August 26, 2008 12:54 PM
To: Barnes, Mary (RICH2:AR00)
Cc: 72attendees@ietf.org
Subject: Re: [72attendees] New mailing list to discuss IETF Food
requirements



Mary Barnes wrote:
>    The list is intended to provide a forum for discussion so that we 
> can understand one another's requirements and plan ahead for IETF 
> meetings by both preparing ourselves and the meeting planners."


I hope the discussion distinguishes between defining the burden that is
to be assumed by IETF meeting planners, versus private efforts by IETF
meeting attendees.

 From a pragmatic standpoint, meeting planners cannot accommodate 100%
of attendees' needs.

So, striking a reasonable balance between the two is the interesting
challenge.

d/

ps. Having meetings placed in resource-rich venues, within walking
distance of those resources, is an important way to accommodate diverse
requirements...

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net
_______________________________________________
72attendees mailing list
72attendees@ietf.org
https://www.ietf.org/mailman/listinfo/72attendees