Re: IETF 97 - Registration and Hotel Reservations Open Now!

Dave Crocker <dhc@dcrocker.net> Fri, 12 August 2016 20:20 UTC

Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 903DC12D80E for <ietf@ietfa.amsl.com>; Fri, 12 Aug 2016 13:20:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.209
X-Spam-Level:
X-Spam-Status: No, score=-1.209 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RDNS_NONE=0.793, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dcrocker.net
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 08ZnujSyUHm5 for <ietf@ietfa.amsl.com>; Fri, 12 Aug 2016 13:20:30 -0700 (PDT)
Received: from simon.songbird.com (unknown [72.52.113.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3068012B01B for <ietf@ietf.org>; Fri, 12 Aug 2016 13:20:30 -0700 (PDT)
Received: from [192.168.1.168] (76-218-8-128.lightspeed.sntcca.sbcglobal.net [76.218.8.128]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id u7CKKY2F018714 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Fri, 12 Aug 2016 13:20:34 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1471033234; bh=DyMzBvnvSDkp/UJQg4quCh5+Ln11U3m7BVuanV35u/U=; h=Subject:References:To:Reply-To:From:Date:In-Reply-To:From; b=iBoAk6oVOgU9egas2JczzA1XYU+qVB4dPCWRvH2CD061i8QLeICePoZ7Nc+ca6wVW hU7xhbZWiOzgqyLEvSHKem+gxtHUbMFsalqFUo9fpL2c+rYhfsBB8QLOZuYBbiOki1 RMvbOSG96sULEo+PrStumEPp5Ni4/Fv3fCw7RvOQ=
Subject: Re: IETF 97 - Registration and Hotel Reservations Open Now!
References: <147094744424.21281.7915555432277043072.idtracker@ietfa.amsl.com> <57AD2730.8050602@swin.edu.au> <9916BCD4DBD65FB7D44A6F88@JcK-HP8200> <953016d5-6f64-bd94-c221-95d96f693c2c@dcrocker.net> <7594FB04B1934943A5C02806D1A2204B4BBDEDF4@ESESSMB208.ericsson.se> <036801d1f464$aaf1df20$00d59d60$@gmail.com> <42234065-1C6E-4224-A48C-1186F536E02F@piuha.net> <82A17B2FC06D1F8BD216D229@JcK-HP8200> <58ceaef5-77fc-5833-a7a0-c5eae8ed21a3@dcrocker.net> <2CD7D393-7ADD-4739-A923-79B0EBE6EB76@gmail.com>
To: IETF discussion list <ietf@ietf.org>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <3fe84e04-7ccf-6fd8-1622-eb1417631305@dcrocker.net>
Date: Fri, 12 Aug 2016 13:19:59 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <2CD7D393-7ADD-4739-A923-79B0EBE6EB76@gmail.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gqZA4Ciu5jootANHpaGEKKycqIU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Aug 2016 20:20:31 -0000

> The way it works at the moment seems to be that if you are lucky
> enough to be doing an email check at the right time and book at once
> you are OK, otherwise you miss out


I've been wondering about how to approach this topic in a way that makes 
sense for the IETF list and it occurs to me that it might be worth 
remembering that our industry is based on statistical multiplexing, and 
that's about probabilities and timing...

    If we make sure there is a room for everyone who might want one, we 
will allocate too many and will waste quite a bit of money, due to the 
guarantees we have to make to the hotel.

    So for practical purposes the room block needs to be of a size that 
is likely to be exceeded... at some point... almost always.

    Currently, that 'some point' is measured in minutes, or at best 
small numbers of hours.

    My question, therefore, is how large must the window be, before all 
the rooms typically sell out?

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net