Re: [101attendees] Registration for IETF 102, Montreal

Andrew Sullivan <ajs@anvilwalrusden.com> Sat, 21 April 2018 11:43 UTC

Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: 101attendees@ietfa.amsl.com
Delivered-To: 101attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D94512E85E for <101attendees@ietfa.amsl.com>; Sat, 21 Apr 2018 04:43:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=yitter.info header.b=C++YmI04; dkim=pass (1024-bit key) header.d=yitter.info header.b=gFOpHxsa
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 lD-vrOsEy1Pb for <101attendees@ietfa.amsl.com>; Sat, 21 Apr 2018 04:43:24 -0700 (PDT)
Received: from mx4.yitter.info (mx4.yitter.info [159.203.56.111]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C921412E858 for <101attendees@ietf.org>; Sat, 21 Apr 2018 04:43:24 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx4.yitter.info (Postfix) with ESMTP id 9AB28BECAD for <101attendees@ietf.org>; Sat, 21 Apr 2018 11:43:23 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1524311003; bh=jkQhEeX3pGiSQygnB3vu84oniTKn8nkDaMmeof72Dw4=; h=From:To:Date:In-Reply-To:References:Subject:From; b=C++YmI04MjyYnDI/jg0aG7Pzl01cSvYEZjK7Y7LOc4jNskw0eD93ZIMiEFe2aoOfk SudOcSHYhjfhC7Xuie99FPPfSgaXn+pIxgEwlGDIxxqaI+76gTzahrFjRO3QG5co8D vYD1lyZbFWS4g1S5YPICMGtw+O8GSoPGCaqOX7Hs=
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx4.yitter.info ([127.0.0.1]) by localhost (mx4.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h1uMwWrQVEk2; Sat, 21 Apr 2018 11:43:22 +0000 (UTC)
From: Andrew Sullivan <ajs@anvilwalrusden.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1524311001; bh=jkQhEeX3pGiSQygnB3vu84oniTKn8nkDaMmeof72Dw4=; h=From:To:Date:In-Reply-To:References:Subject:From; b=gFOpHxsaIp4m9jBVV2os8aMXmAulDThX+ml91+VWcqv/Qer36s8FDfFcgZC+xGoWR DM5r72dy7m68uAwtNxVwaSdqqPeObWZIjbDcKYxCfIllMe7pQNhJuv21nubIiBc/37 IcfFad4c0BASXHo/zVHrrZN42wvKbXCPz8XA+vk4=
To: 101attendees@ietf.org
Date: Sat, 21 Apr 2018 07:43:20 -0400
Message-ID: <162e80403c0.2772.55b9c0b96417b0a70c4dcaded0d2e1c6@anvilwalrusden.com>
In-Reply-To: <DB9C34A5-FA2D-4CD6-B849-E2AA6B0307ED@amsl.com>
References: <m28t9ik478.wl-randy@psg.com> <20180420024502.71E5D254669E@ary.qy> <5C4D8E08-625B-40F3-BB8F-047D3AEFCBF1@cable.comcast.com> <20180420130105.6lkyhwkdjsfhk2s3@mx4.yitter.info> <B7205D28-1524-4D90-BE15-6B41FB82196A@gmail.com> <DB9C34A5-FA2D-4CD6-B849-E2AA6B0307ED@amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="utf-8"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/101attendees/aEYxXxDJT9CbB5OYlijWj3K05qY>
Subject: Re: [101attendees] Registration for IETF 102, Montreal
X-BeenThere: 101attendees@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mailing list of IETF 101 attendees that have opted in on this list <101attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/101attendees>, <mailto:101attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/101attendees/>
List-Post: <mailto:101attendees@ietf.org>
List-Help: <mailto:101attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/101attendees>, <mailto:101attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Apr 2018 11:43:27 -0000

I should note, too, that while it is admirable for Alexa or anyone at AMS 
to take responsibility for an error, ultimately it is the IAOC that is 
responsible to the community for oversight. So if there are complaints, 
please direct them to the IAOC. Thanks!

A

--
Please excuse my clumbsy thums
----------
On April 21, 2018 03:37:03 Alexa Morris <amorris@amsl.com> wrote:

> Two things:
>
> 1) Registration for 102 was supposed to open 12 weeks out from the meeting, 
> not 10. The dates were inadvertently entered to the Datatracker incorrectly 
> and, as I did review those dates prior to their publication, I should have 
> caught it. I apologize. We are testing the 102 registration system early 
> next week to make sure everything functions properly and we hope to open 
> mid-week.
>
> 2) Historically we began actively working on the logistics for a new 
> meeting directly following the conclusion of the previous one. That worked 
> well for many years, but over time our meetings have grown increasingly 
> complex and that narrow intervening window of time squeezed in on us from 
> both sides like a vise. Recently we reexamined our planning cycle and made 
> some significant adjustments: we now start working on the meeting logistics 
> (registration, hotel reservations, LOIs) at least eight months out. This 
> gives us a lot more time to address the inevitable unforeseen issues that 
> arise. We are just starting to feel the positive effects of those adjustments.
>
> In addition, the IAOC recently indicated a willingness to decouple meeting 
> registration from the opening of hotel reservations: this will make a big 
> difference as it's often adjustments on the hotel reservation side of 
> things that delay the opening of registration.
>
> Again, I apologize for the error and the delay in opening registration for 
> 102. We will get registration open as soon as possible, and we are already 
> working on 103 so that we can open it in a timely manner.
>
> Alexa
>
>
> > On Apr 20, 2018, at 5:19 PM, Bob Hinden <bob.hinden@gmail.com> wrote:
> >
> > Andrew,
> >
> > The last time this became an issue for attendees, the IAOC promised to 
> open registration shortly after the previous meeting to allow for time for 
> folks who need visas.  This would have been late March or early April in 
> this case.  How did this get turned into May, over a month later?
> >
> > Bob
> >
> >
>> > On Apr 20, 2018, at 6:01 AM, Andrew Sullivan <ajs@anvilwalrusden.com> wrote:
>> >
>> > Hi there,
>> >
>> > On Fri, Apr 20, 2018 at 12:25:41PM +0000, Livingood, Jason wrote:
>>> > I'm vaguely curious why we hold back registration until 10 weeks.
>> >
>> > This was actually a topic of some informal discussion at the recent
>> > IAOC retreat.  I gather there have been some logistical issues in
>> > opening registration sooner, and they're being worked.  I don't have
>> > an ETA for details about the improvements, but I take this current
>> > thread as indicating some need to explain in detail the way the
>> > registration system is working and what plans there are for altering
>> > it.
>> >
>> > In the meantime, I urge anyone who needs a visa to register as early
>> > as possible and get the letter requests in, so that the Secretariat
>> > can process everything as quickly as possible.
>> >
>> > Best regards,
>> >
>> > Andrew (IAOC chair, but speaking as an individual IAOC member)
>> >
>> > --
>> > Andrew Sullivan
>> > ajs@anvilwalrusden.com
>> >
>> > _______________________________________________
>> > 101attendees mailing list
>> > 101attendees@ietf.org
>> > https://www.ietf.org/mailman/listinfo/101attendees
> >
> > _______________________________________________
> > 101attendees mailing list
> > 101attendees@ietf.org
> > https://www.ietf.org/mailman/listinfo/101attendees