IETF Logo Mail Archive

Re: Venue Announcement for IETFs 98, 99, 102 and 111

John C Klensin <john-ietf@jck.com> Wed, 06 January 2016 23:32 UTC

Return-Path: <john-ietf@jck.com>
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 75CFA1A1BDE for <ietf@ietfa.amsl.com>; Wed, 6 Jan 2016 15:32:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 rCnhzp9K2a0z for <ietf@ietfa.amsl.com>; Wed, 6 Jan 2016 15:32:06 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A9911A1BCB for <ietf@ietf.org>; Wed, 6 Jan 2016 15:32:06 -0800 (PST)
Received: from [198.252.137.10] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1aGxYj-0001HS-IT for ietf@ietf.org; Wed, 06 Jan 2016 18:32:05 -0500
Date: Wed, 06 Jan 2016 18:32:00 -0500
From: John C Klensin <john-ietf@jck.com>
To: ietf@ietf.org
Subject: Re: Venue Announcement for IETFs 98, 99, 102 and 111
Message-ID: <AB383E7EE1632A97AC7D544E@JcK-HP8200.jck.com>
In-Reply-To: <20160105210603.26728.22600.idtracker@ietfa.amsl.com>
References: <20160105210603.26728.22600.idtracker@ietfa.amsl.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/11NcvwYesHS3tc1VmZbu1mU5Iqs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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, 06 Jan 2016 23:32:07 -0000


--On Tuesday, January 05, 2016 13:06 -0800 IETF Administrative
Director <iad@ietf.org> wrote:

> The IAOC is pleased to announce the selection of venues for the
> following IEF meetings:
>...
> IETF 111:  San Francisco  July 25 - 30 2021

Ray,

Reflecting on the current discussion of hotels and observing
that several people have expressed concern about statements like
"can't do anything to change the policies or affect that date or
location because we are working three years out", does this
imply that you and the IAOC are making commitments we could not
change if we wanted to (even if circumstances changed) 5 1/2
years out.   I'm all in favor of pinning down dates well in
advance but, when we start talking about commitments to
"venues", it is a source of some small anxiety.

    john

v2.23.0 | Report a Bug | By Email