Re: IETF65 hotel location

Jeffrey Hutzelman <jhutz@cmu.edu> Fri, 27 January 2006 21:53 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F2bWv-0002bk-Hp; Fri, 27 Jan 2006 16:53:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F2bWs-0002bI-Ow for ietf@megatron.ietf.org; Fri, 27 Jan 2006 16:53:14 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19919 for <ietf@ietf.org>; Fri, 27 Jan 2006 16:51:41 -0500 (EST)
Received: from currant.srv.cs.cmu.edu ([128.2.194.193]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1F2bh6-0000f2-E3 for ietf@ietf.org; Fri, 27 Jan 2006 17:03:49 -0500
Received: from CHOKECHERRY.SRV.CS.CMU.EDU ([128.2.185.41]) by currant.srv.cs.cmu.edu id aa11526; 27 Jan 2006 16:53 EST
Received: from bistromath-home.pc.cs.cmu.edu (c-67-186-56-211.hsd1.pa.comcast.net [67.186.56.211]) (authenticated bits=0) by chokecherry.srv.cs.cmu.edu (8.13.5/8.13.5) with ESMTP id k0RLquYk020442 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 27 Jan 2006 16:52:57 -0500 (EST)
Date: Fri, 27 Jan 2006 16:52:56 -0500
From: Jeffrey Hutzelman <jhutz@cmu.edu>
To: Spencer Dawkins <spencer@mcsr-labs.org>, ietf@ietf.org
Message-ID: <4CD2672290309C57FA3CA218@bistromath.pc.cs.cmu.edu>
In-Reply-To: <01cd01c6237f$f39ba380$6501a8c0@china.huawei.com>
References: <20060127200247.34217.qmail@simone.iecc.com> <43DA7E9D.2060904@cisco.com> <01cd01c6237f$f39ba380$6501a8c0@china.huawei.com>
Originator-Info: login-token=Mulberry:01Camkm3MRGQ9V9BwcPCfUCqAb28aQ3R12HtIAPyk=; token_authority=postmaster@andrew.cmu.edu
X-Mailer: Mulberry/3.1.6 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-PMX-Version: 4.7.1.128075, Antispam-Engine: 2.0.3.2, Antispam-Data: 2006.01.27.130609
X-Spam-OK: 7%
X-Spam-Score: 1.2 (+)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Content-Transfer-Encoding: 7bit
Cc:
Subject: Re: IETF65 hotel location
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org


On Friday, January 27, 2006 02:26:26 PM -0600 Spencer Dawkins 
<spencer@mcsr-labs.org> wrote:

> Hi, Mike,
>
>>> If we could morph it into a signup system that distributed people
>>> according to restauant capacity and avoided the problem that someone
>>> says "I hear there's a burrito place on X street" and a herd of 300
>>> IETFers shows up there, since they don't know any other places to go,
>>> then you'd really have something.
>>
>> I'm afraid it's beyond IETF's expertise to come up with
>> distributed burrito processing protocols.
>>
>> Mike
>
> If you think about this for a minute, you would realize that (1) we not
> only have protocols for this, but we have running code, and (2) "too much
> focus on distributed burrito processing" might explain a lot about where
> we are and how we got here! :-)
>
> Thanks,
>
> Spencer, who is wondering what a "dining protocol designers" multitasking
> algorithm might look like, with a burrito between every pair of protocol
> designers (with apologies to the dining philosophers)

Ah, but this is not that big a problem, because unlike forks, burritos are 
dual-ported.

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf