Re: IETF 100 Registration and Hotel Reservations Open!

Tim Chown <tjc@ecs.soton.ac.uk> Wed, 26 July 2017 16:50 UTC

Return-Path: <tjc@ecs.soton.ac.uk>
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 14B5C1320BA for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 09:50:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.302
X-Spam-Level:
X-Spam-Status: No, score=-4.302 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ecs.soton.ac.uk
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 twFv5aUrAwIP for <ietf@ietfa.amsl.com>; Wed, 26 Jul 2017 09:50:16 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED6A5131D28 for <ietf@ietf.org>; Wed, 26 Jul 2017 09:50:15 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id v6QGnmet022546; Wed, 26 Jul 2017 17:49:53 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk v6QGnmet022546
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1501087799; bh=cbA2TgoSv7nyD2RBd/k0NkGRJhA=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=jezSbimX9lrYDxsQPOSaubmcOD30U+729dFJUSLSuEOmZWkGpHJ6CreJOmf3E7nnB tOxsbORZ3zWncm5QGk1Di9/CKyXviQVRottpIjchL9c8lXmHM39/PYnMNRPxHTgI0j UY1+LSfM5Y0/FgSlM1B65+/B3PUPg2D9HKfAZClM=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id y6PHnm1133808654nL ret-id none; Wed, 26 Jul 2017 17:49:59 +0100
Received: from 20010a88d51011.ipv6.customer.clara.net (20010a88d51011.ipv6.customer.clara.net [IPv6:2001:a88:d510:1101:75b2:2069:32a0:8c99] (may be forged)) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id v6QGnh6c031665 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 26 Jul 2017 17:49:43 +0100
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: IETF 100 Registration and Hotel Reservations Open!
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <DCAD3478-067F-450A-AF3D-0D32B9C4ABC1@fugue.com>
Date: Wed, 26 Jul 2017 17:49:42 +0100
Cc: Stewart Bryant <stewart.bryant@gmail.com>, ietf@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|ebe142dc295fa56fb1b6505bd073e8a9y6PHnm03tjc|ecs.soton.ac.uk|4AE3A6AD-AFF1-4236-A2EF-0A0261A01812@ecs.soton.ac.uk>
References: <150107762165.23133.6738319854502205219.idtracker@ietfa.amsl.com> <6b56520c-8a19-85a4-c1af-5cb3d55eacdc@gmail.com> <DCAD3478-067F-450A-AF3D-0D32B9C4ABC1@fugue.com> <4AE3A6AD-AFF1-4236-A2EF-0A0261A01812@ecs.soton.ac.uk>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.3273)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-ECS-MailScanner-SpamScore: s
X-smtpf-Report: sid=y6PHnm113380865400; tid=y6PHnm1133808654nL; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=3:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: v6QGnmet022546
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mh2wycyajSYkaa9W5U5p4uGLgZY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
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: Wed, 26 Jul 2017 16:50:18 -0000

> On 26 Jul 2017, at 17:14, Ted Lemon <mellon@fugue.com> wrote:
> 
> On Jul 26, 2017, at 12:07 PM, Stewart Bryant <stewart.bryant@gmail.com> wrote:
>> I wonder if we need a ballot system for the HQ hotels?
> 
> Right now the system rewards those who are most attuned to the timing of the hotel announcement.   I actually have a filter in my email that notifies me when the announcement comes out.
> 
> I think it can definitely be argued that this is the wrong way to do things—I don't see it as being a particularly fair outcome that those IETF participants who are most proactive about signing up always tend to win.   Suppose everyone who cares about this were as proactive as I am.   Then it would just be a little bit more random who happened to win.
> 
> So, in principle, a lottery would be better, and maybe you get extra tickets if you lost last time (not sure how to make that work, but maybe some of the crypto wizards do).   The problem with this is that it's a _lot_ more tooling work for the secretariat.   I would hazard a guess that this is why it hasn't happened yet.
> 
> I don't think it's actually realistic to try to solve this problem.   But it does suck.   I suppose those of us who tend to win most often could voluntarily delay our registrations, but I doubt we could get sufficiently universal cooperation to achieve fairness.

In Singapore the second hotel is 85 metres away, the third is 200m, the fourth and fifth 500m, which is rather better than alternatives for many venues.  One of the 500m hotels is half the room rate of the main venue.  There’s more hotels being used, with the rooms spread more thinly between them.  The quick “sell out” of rooms may be because the main venue had only 160 rooms for the Saturday night before the meeting started, but 300+ for other nights.

If we can give such diversity in options for all meetings, assisted by local knowledge, that would help alleviate problems, as would giving some priority to those with genuine reasons to be on-site.

I note that it seems the IETF organisers organise around 700 or so rooms for us, so I assume 500 or so attendees found their own accommodation.  Presumably that 700 figure is based on past take-up of those rooms.

Tim