timing for venue contracting

"jordi.palet@consulintel.es" <jordi.palet@consulintel.es> Thu, 23 July 2026 08:56 UTC

Return-Path: <prvs=1664f49daa=jordi.palet@consulintel.es>
X-Original-To: ietf@mail2.ietf.org
Delivered-To: ietf@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 8349011D22BB9; Thu, 23 Jul 2026 01:56:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1784797000; bh=SC76EiCyQIYzyFBDH3ky6QQnCKZrIrNEp04HPDxX59U=; h=From:Subject:Date:References:To:In-Reply-To; b=Dy2lWQYVwqsZNyUh9wswdm55R8XAbcCzjouiekXZhWIO89cjPUPmzSpnHQpJpa05N wqxuhi5hdfkSTIdS/bnfSDHTgiiNpE4XkBBPidBPOw0QYI87byxk12hFhw/wkqtzbg 99kXVO/8V8EuurqwEEj1PVepOYwyud0D9TF3gLKY=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=consulintel.es
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xwTSPMLgzECV; Thu, 23 Jul 2026 01:56:39 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [IPv6:2001:470:1f09:495::5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id EFBB611D22784; Thu, 23 Jul 2026 01:55:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=consulintel.es; s=mailer; t=1784796917; x=1785401717; i=jordi.palet@consulintel.es; q=dns/txt; h=From:Content-Type: Content-Transfer-Encoding:Mime-Version:Subject:Date:References: To:In-Reply-To:Message-Id; bh=TUV2PMq+0jyg0SPAXcceTJDqpfXtsV/EE7 L622MiroY=; b=BVq70VagoTl3Za+dnU8BaskTQ5evu/QSCGuRD56eGZ8uf0Cd4a R9iVHUnxA84cAQd9A0x5bkIyjrd/yIIAiXJ+AfmtijpfYm5XcWcBD/ODObTWNhQm t7Ijk4iFLJkgzrqs2p1c+76hTdxGHDX4qZsIQzRUhBeEsIZW3Ql/MqjGiSjk/Gw5 4lf6nsrX7hG/EsdcWn0NNk+bRcmcKagJHYfnD8bQebQb3HLSBaCbF+3F9gYlVyGC 23WMk4wojjhQCCV7B+ODA/qyps01hRkq9oqp1bezhkE5rXgIbIATxv6WtknT4Kv0 ujwTitQKaeG7fRiSgdcYxRZ60omZOOP+XQYw==
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.es, Thu, 23 Jul 2026 10:55:16 +0200
X-Spam-Processed: mail.consulintel.es, Thu, 23 Jul 2026 10:55:15 +0200
Received: from smtpclient.apple by mail.consulintel.es (10.10.10.5) (MDaemon PRO v25.5.0) with ESMTPSA id md5001002830392.msg; Thu, 23 Jul 2026 10:55:15 +0200
X-MDRemoteIP: 2001:67c:1232:144:71d4:2600:f4e1:536b
X-MDHelo: smtpclient.apple
X-MDArrival-Date: Thu, 23 Jul 2026 10:55:15 +0200
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Return-Path: prvs=1664f49daa=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
From: "jordi.palet@consulintel.es" <jordi.palet@consulintel.es>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.600.51.1.1\))
Subject: timing for venue contracting
Date: Thu, 23 Jul 2026 10:55:00 +0200
References: <178463927038.371886.123681758424155871@dt-datatracker-d4d6ff9d9-fsx7d>
To: ietf@ietf.org, exec-director@ietf.org
In-Reply-To: <178463927038.371886.123681758424155871@dt-datatracker-d4d6ff9d9-fsx7d>
Message-Id: <9843B1B6-7076-4A35-A3D7-4519F264668A@consulintel.es>
X-Mailer: Apple Mail (2.3864.600.51.1.1)
X-MDCFSigsAdded: consulintel.es
Message-ID-Hash: 2PJJO6X34CJSHIIQ7ACS25UAPU2J5DLD
X-Message-ID-Hash: 2PJJO6X34CJSHIIQ7ACS25UAPU2J5DLD
X-MailFrom: prvs=1664f49daa=jordi.palet@consulintel.es
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: "IETF-Discussion. This is the most general IETF mailing list, intended for discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist." <ietf.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/yEP1k0cquENmKmUw15mgGikk0b4>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-owner@ietf.org>
List-Post: <mailto:ietf@ietf.org>
List-Subscribe: <mailto:ietf-join@ietf.org>
List-Unsubscribe: <mailto:ietf-leave@ietf.org>

Hi Jay,

I wanted to raise this point in the plenary yesterday, but I had to leave a bit earlier.

If I recall correctly, this is the 2nd time in the last few years (Brisbane was the other one), that a venue is announced extremely late.

May be this is not being realized, but it creates for some participants that pay traveling from their own pocket a very high penalty even inability to actually make it. Yes, they can still participate remotely, but we all know is not the same. On-site conversations, not just the WG meetings are very important, in addition to the difference of being in the same time zone for the meeting itself.

I’m not sure how many people can/prefers planning ahead, but I’m sure others can take advantage of that, and doing so doesn’t create any trouble for the rest of the participants. In my own case, the difference is quite significative. If I get my flights 11-12 months in advance, I can use my miles and just pay 250 euros or so (just taxes) to travel to KL. An alternative is to pay around 1.000 euros and get upgraded for free (because my status in the airline), or using my miles as well. Instead now, as checked yesterday, it will cost me over 5.000 euros for the same trip/cabin (seats or upgrades with miles aren’t anymore available).

I fully understand that many participants are funded by their employers, and may be the employers don’t care too much (or not at all) about that, but I’m sure I’m not alone with this and it doesn’t make any sense that even if is a small set of people being affected, not being considerate to them.

If I understood correctly, from you yesterday in the plenary, now you start working on contracts for meetings after 2027. I really don’t understand the need to hold that, and instead, considering that our meeting dates are set for at least 6-7 years in advance, work already in all the possible venues for the next 5 years in advance, contract and announce them at least 1-2 years in advance, but *never* later than 1 year in advance.

This will also give us the advantage, that in case of any venue failure (I recall we had that happening at some point in Canada some years ago), we have more time to react, possibly even with several options. Just consider if for whatever reason KL was not fixed a few days ago and time passes and we don’t have suitable alternatives or we need to pay much more for one of them. I don’t think we can take that risk.

I understand that doing this now means a lot of extra workload for a few months, but after that, when you have already contracted 4-5 years, you only need to take care of the 6th following year, and so on. I also understand that this may look difficult for new venues because the time required for on-site surveys, but there is a simple solution for that: for the next 3-4 years, just consider venues that we already had used before (we have several of them in every region, so not a problem).

In fact, I’ve been very surprised when I’ve asked in the last 3 meetings, if we are coming back to Madrid and if is already fixed, and the answer was NO, first possible slot is summer 2030. How come, if we know the participants were so happy (according to the survey and all conversations we had), we have not even started to talk with the venue again. Why we don’t start working with the venue immediately and fix it in a few months, even if it is 4 years in advance?

It doesn’t make any sense to me. I could only imagine, that if you try to negotiate with the hotel now for 2030 they will give you a higher price (I don’t think so, I actually think it will be lower, and you reduce the risk of not being available on our preferred dates by fixing it now, or even it can be negotiated with a price difference considering life cost increase, etc.). However, if this is the issue, you are moving the price difference to the traveling cost of the participants (in additional to other planing they may wish to do, such vacations or business side-by-side the meeting).

I used Madrid as a clear example, but of course, the same can be done, at least for the next 4-5 years, with venues that have been very well rated, as I think it was Berlin, BKK, Singapore, etc., and that may keep offering sufficiently good conditions for IETF.

Regards,
Jordi

@jordipalet

> El 21 jul 2026, a las 15:07, IETF Executive Director <exec-director@ietf.org> escribió:
> 
> The IETF Administration LLC is pleased to announce Kuala Lumpur as the location for the IETF 128 meeting, scheduled for 6-12 March 2027.
> 
> The support and commitment of our Global Hosts and meeting sponsors ensures that IETF participants can meet and collaborate in the highly productive environment of an onsite meeting. To find out more about these opportunities to support the IETF, please see:
> 
> 	https://www.ietf.org/support-us/sponsorship/
> 
> I look forward to seeing many of you there.
> 
> -- 
> Jay Daley
> IETF Executive Director
> exec-director@ietf.org
> 
> _______________________________________________
> IETF-Announce mailing list -- ietf-announce@ietf.org
> To unsubscribe send an email to ietf-announce-leave@ietf.org


**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.theipv6company.com
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.