Re: [Recentattendees] Background on Singapore go/no go for IETF 100

Tim Chown <> Thu, 02 February 2017 15:58 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 9EC4112943E; Thu, 2 Feb 2017 07:58:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -7.5
X-Spam-Status: No, score=-7.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-3.199, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id gRlCI3WCg6kq; Thu, 2 Feb 2017 07:58:34 -0800 (PST)
Received: from ( [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 2F87112941A; Thu, 2 Feb 2017 07:58:32 -0800 (PST)
Received: from (localhost []) by (8.13.8/8.13.8) with ESMTP id v12FwQY5019646; Thu, 2 Feb 2017 15:58:26 GMT
X-DKIM: Sendmail DKIM Filter v2.8.2 v12FwQY5019646
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple;; s=201304; t=1486051106; bh=grgLkRHRSAcYL7qeFvkQOdZ5E+E=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=jKj7yabIRtfoBlGbCfA34DtA0jfZF8NpIjdh4yJAQQ/2S9ZWrKQYOAPAtX3HSBSLW yaZJxoaW+lWjDb41vEJaBcCE68IpqyTJCqXsvijoBwPagk5+w/R45UGaoMP/dUnPTQ Byjp25f7fncXdpazZV6LzSmzwGmt2wuNV+wk25V8=
Received: from ( [2001:630:d0:f102::25d]) by ( [2001:630:d0:f102::25e]) envelope-from <> with ESMTP (valid=N/A) id y11FwQ23562107846j ret-id none; Thu, 02 Feb 2017 15:58:26 +0000
Received: from [] ( []) (authenticated bits=0) by (8.13.8/8.13.8) with ESMTP id v12FwNeB032451 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 2 Feb 2017 15:58:23 GMT
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: [Recentattendees] Background on Singapore go/no go for IETF 100
From: Tim Chown <>
In-Reply-To: <>
Date: Thu, 2 Feb 2017 15:58:23 +0000
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|e79af8b0b5b4f94b1e7da0aa197d5644y11FwQ03tjc||>
References: <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <>
To: Randal Atkinson <>
X-Mailer: Apple Mail (2.3259)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=y11FwQ235621078400; tid=y11FwQ23562107846j; client=relay,ipv6; mail=; rcpt=; nrcpt=3:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: v12FwQY5019646
Archived-At: <>
Cc: "" <>,
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 02 Feb 2017 15:58:37 -0000


> On 2 Feb 2017, at 15:39, Randal Atkinson <> wrote:
>> On 31Jan2017, at 04:44, Naeem Khademi <> wrote:
>> The next IETF in the US after Chicago, would be in July 2018 in SF. I don't think it's even possible
>> to buy a flight ticket for that time as of now (most airlines wouldn't do such pre-sale). So, it's pretty
>> much possible to relocate that meeting elsewhere with causing no loss to anyone's already-made plans.
> The claim above that "most airlines won’t sell 6 months in advance" is false.  
> Most airlines, including all or nearly all major full-service international airlines, start selling tickets 
> at least 12 months before the departure date for the 1st flight on an itinerary.  
> To my knowledge, there are some people who already have purchased tickets to go to IETF in SFO.  
> This really ought not be surprising as the lowest-cost fares often sell-out earliest.  A number of
> IETF people don’t work for big companies and are traveling on their own money.   Those people
> would suffer greatly from a change in location less than 12 months out.
> I am aware that some have suggested the IETF do more remote meetings.  I think that is worth
> exploring. 
> I certainly would support IETF making all future meetings more accessible remotely  — and I think 
> that is a goal the IETF has been making progress on for some years now, using Jabber, VTC, 
> and so forth.  Expanding the remote access capabilities and coverage for all future meetings 
> (to the extent that is practical at a given point in time) only makes sense.

I just tried availability for flights from London to San Francisco for July 2018 IETF.  
None of BA, Virgin or United would offer tickets beyond January 2018. 
Perhaps it’s different for internal flights within the US?

I guess we simply can’t know how many people would be inconvenienced should 
the IETF announce that the July 2018 IETF is relocating to (say) Vancouver. In practice, 
there would be at least some moral obligation to refund those people if there’s no flexibility 
in the tickets.

Certainly being better placed to support remote participation will be increasingly 
important. The IETF has made great strides in recent years with MeetEcho, etc. But no 
doubt more can be done, and now we have an additional very good reason to do so.