http://www.ieee-jp.org/section/tokyo/chapter/ITS-38/conference/icves2015/index.php
I wouldn't be surprised if there is a bunch of intelligent IEEE folks that
did latch onto the excellent IETF hotel conference rate. WOuld be fun if IAOC
could request names for conference rate registrations and check againsst
actual IETF registrations. In fact, it would be lovely if hotel reservations
with conference rate where checked against IETF registrations.
And i didn't dare to look for even more cnflicting events.
On Mon, Aug 17, 2015 at 07:26:12AM +0000, Sprecher, Nurit (Nokia - IL/Hod
HaSharon) wrote:
Another strange aspect is that while it was possible to book rooms from
Sunday to Thursday, it was impossible to continue the stay after Thursday.....
I cannot imagine that the IETF guys join the meeting on towards its end.
-----Original Message-----
From: ietf [mailto:ietf-bounces(_at_)ietf(_dot_)org] On Behalf Of ext
Toerless Eckert
Sent: Monday, August 17, 2015 9:48 AM
To: John Levine
Cc: ietf(_at_)ietf(_dot_)org
Subject: Re: R: [BOFChairs] IETF 94 - Registration and Hotel Information - no
availablity
How many rooms does the hotel have ? What percentage of rooms did
we have blocked in other comparable sized hotels ? Is this on-par ?
I thought to remember we always had at least ca. 500 rooms blocked.
IMHO there is nothing wrong to have IETF less explore good tourist locations
but return to places of known good work environments. I loved visiting
friends in Tokyo and we had a great party at Landmark Tower for Yokohama
fireworks
last time, but pacifico didn't strike me as more than average and
the social event at the gym was memorable, but not in a good way.
On Mon, Aug 17, 2015 at 04:04:29AM -0000, John Levine wrote:
I can assure you that the room block size at the main hotel is as
large as the IETF could possible obtain,
Ole
That suggests that we should not have gone to this hotel.
If you're aware of another conference center near Tokyo that has
adequate affordable meeting space for the IETF, I expect the IAOC
would be grateful to hear about it for next time.
R's,
John
--
---
Toerless Eckert, eckert(_at_)cisco(_dot_)com