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

Dave CROCKER <dhc@dcrocker.net> Tue, 26 August 2008 18:42 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 B2C1B3A685D; Tue, 26 Aug 2008 11:42:42 -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 F1D853A69D5 for <72attendees@core3.amsl.com>; Tue, 26 Aug 2008 11:42:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.996
X-Spam-Level:
X-Spam-Status: No, score=-1.996 tagged_above=-999 required=5 tests=[AWL=0.604, BAYES_00=-2.599]
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 jLhpvrQM0bgp for <72attendees@core3.amsl.com>; Tue, 26 Aug 2008 11:42:41 -0700 (PDT)
Received: from sbh17.songbird.com (mail.mipassoc.org [IPv6:2001:470:1:76:0:ffff:4834:7146]) by core3.amsl.com (Postfix) with ESMTP id 9C4AC3A685D for <72attendees@ietf.org>; Tue, 26 Aug 2008 11:42:40 -0700 (PDT)
Received: from [192.168.0.3] (adsl-68-122-33-201.dsl.pltn13.pacbell.net [68.122.33.201]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id m7QIgdfF006804 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 26 Aug 2008 11:42:39 -0700
Message-ID: <48B44E9E.2090003@dcrocker.net>
Date: Tue, 26 Aug 2008 11:42:38 -0700
From: Dave CROCKER <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Thunderbird 2.0.0.16 (Windows/20080708)
MIME-Version: 1.0
To: Mary Barnes <mary.barnes@nortel.com>
References: <F66D7286825402429571678A16C2F5EE04FE7247@zrc2hxm1.corp.nortel.com> <48B44333.4060905@dcrocker.net> <F66D7286825402429571678A16C2F5EE0508B21F@zrc2hxm1.corp.nortel.com>
In-Reply-To: <F66D7286825402429571678A16C2F5EE0508B21F@zrc2hxm1.corp.nortel.com>
X-Virus-Scanned: ClamAV 0.92/8093/Tue Aug 26 09:01:30 2008 on sbh17.songbird.com
X-Virus-Status: Clean
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Tue, 26 Aug 2008 11:42:40 -0700 (PDT)
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
Reply-To: dcrocker@bbiw.net
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

Mary,

Given the diversity of IETF participation, we can be assured that there are 
representatives for almost any point of view.  So, yes, I'm sure that some folks 
have no empathy or sympathy for the plight of others with culinary constraints. 
  But I think it is clear that that is not a dominant, or even significant, 
constituency within the IETF.

Rather, I believe the issue is merely one of practicality.  Some needs are 
easily accommodated.  Some are not.

Where more information is needed, the kind of discussion you are planning could 
be quite helpful.

But there are practical limits.  Limited resources and priorities to juggle.

That's why I ended by noting the considerable strategic benefit that accrues 
from placing the IETF somewhere with rich local resources:  It can offload the 
IETF machinery from some considerable burdens.

No matter how accommodating a hotel's staff might wish to be it, too, has 
resource constraints.

d/

Mary Barnes wrote:
> 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
...
> 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
...
> -----Original Message-----
> From: Dave CROCKER [mailto:dhc@dcrocker.net] 
...
 > 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