Re: [92all] IETF Hackathon at IETF 92, March 21-22, Dallas, TX

Dave Crocker <dhc@dcrocker.net> Tue, 24 February 2015 18:01 UTC

Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B3EE1A1B23; Tue, 24 Feb 2015 10:01:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.5
X-Spam-Level:
X-Spam-Status: No, score=-1.5 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
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 Lje7roNpRjLi; Tue, 24 Feb 2015 10:01:12 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 340E71A876F; Tue, 24 Feb 2015 10:01:10 -0800 (PST)
Received: from [192.168.1.66] (76-218-8-156.lightspeed.sntcca.sbcglobal.net [76.218.8.156]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id t1OI15EH022497 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 24 Feb 2015 10:01:08 -0800
Message-ID: <54ECBC5E.2030001@dcrocker.net>
Date: Tue, 24 Feb 2015 10:01:02 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Stuart Cheshire <cheshire@apple.com>
Subject: Re: [92all] IETF Hackathon at IETF 92, March 21-22, Dallas, TX
References: <20150224170152.6224.60832.idtracker@ietfa.amsl.com> <DBC7E705-B163-46E8-AC9B-97BDC33E7C68@apple.com>
In-Reply-To: <DBC7E705-B163-46E8-AC9B-97BDC33E7C68@apple.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Tue, 24 Feb 2015 10:01:08 -0800 (PST)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/r7y5BjZmCb0TI3XWiQyHr_j6u-0>
Cc: IETF Secretariat <ietf-secretariat@ietf.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 24 Feb 2015 18:01:13 -0000

On 2/24/2015 9:57 AM, Stuart Cheshire wrote:
> I realize that these things are often not planned a long way in
> advance, but for future events, as much notice as possible would be
> helpful.
> 
> It’s now less than four weeks to the IETF meeting, and many of us
> have (non-refundable) flights already booked.


+1

Very short notice is pretty common for these special activities
surrounding the IETF.

It would be worth getting some agreement on a reasonable deadline for
announcing them.  One month ain't it.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net