Re: IETF-100 maybe it's mostly been said? (Was: Re: [Recentattendees] Background on Singapore go/no go for IETF 100)

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Thu, 26 May 2016 21:35 UTC

Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7E8412DB48 for <ietf@ietfa.amsl.com>; Thu, 26 May 2016 14:35:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 fNH3ddIvecWL for <ietf@ietfa.amsl.com>; Thu, 26 May 2016 14:35:04 -0700 (PDT)
Received: from mail-yw0-x230.google.com (mail-yw0-x230.google.com [IPv6:2607:f8b0:4002:c05::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 430EB12D9C3 for <ietf@ietf.org>; Thu, 26 May 2016 14:35:02 -0700 (PDT)
Received: by mail-yw0-x230.google.com with SMTP id x189so89132035ywe.3 for <ietf@ietf.org>; Thu, 26 May 2016 14:35:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=yt939R6IP3pb9Qk8Pb1oo/WBcv4XEcOGowrkC52l98w=; b=EwfcQ9yvMJLcdNFvJgjQiEZPJcivheyy+siIQnE01/2mym7lV0umfhbaebe79ldGos iIa55Ynv3A496Ke46Fy93XT8ZfnZzCqjjMlqmP3FROhrFGjOmsTswfA5Goe1o3aafAVg eb4qzEc9rhO6XiFmp/YP1HYgNM+YuG6bG7A/TwBMvJHrosKU08yKlwaWx0OwLUWul+F0 9uRev3BUHNjB92YxruR5+ja60s6oTiXwGxIRSVxK1vsQxWmCvMm5JlX2kQW0Rt8eQVIM 4ldeGvR0NjHSD5Hr+qMzrSWa81mQfQxDWp88ScDwhfir1yCcPH/xsQBBPvMvSZzd7Uc6 DeEA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=yt939R6IP3pb9Qk8Pb1oo/WBcv4XEcOGowrkC52l98w=; b=WbkRdzyEuuZc2udIfWTacfqTziUTi+bcO8FQRhjYNP2KTvDxSf3N7g7tKcbTOi2gqk nbIv9Km2HhmT/EJzlfGrNp4JDkFFJRTQRReIm3b9nGYmgIXQecMXCUfzSuEHzYf/cpFw IuNbKtMc24cULdaQ2vNDFddE7RtYFc7ByH5N9Z0BdCMjnuZw0Qn6pXfg4IweOhArz3Mx zP89YdAuaxKfKg+Okrh7+hWLm3JMm4av+f8sXCu9Dkz7Mryb1lXBqGBk95fzWOOX/HLS 3OeebJ/YimRZLb4t+iaBkRqJDurXovt1kjgynV5JCldv/mbEF2iCXKpxudc7juhjUow2 zprQ==
X-Gm-Message-State: ALyK8tLSHjeZ3/SwPSRF7heyuShstcUK/ZyAy1dxGVMqUu/cDLF6fWZvdL+jPGllM3nGxzCBHB6ZWEY8AP6CbA==
MIME-Version: 1.0
X-Received: by 10.129.122.17 with SMTP id v17mr6672887ywc.219.1464298501364; Thu, 26 May 2016 14:35:01 -0700 (PDT)
Received: by 10.37.218.11 with HTTP; Thu, 26 May 2016 14:35:01 -0700 (PDT)
In-Reply-To: <57475D3F.8040702@cs.tcd.ie>
References: <20160525220818.18333.71186.idtracker@ietfa.amsl.com> <700D9CB7-4EFD-459B-AA12-133A6BB04E90@senki.org> <1C8639E6-1058-4D04-84ED-0C354E6567D1@cisco.com> <9CBABA69-1814-4676-9C69-E129F04AD24C@cisco.com> <5DFDEA43-8156-491D-A300-2BCED1AED1A4@gmail.com> <E449AFCA-A49D-42FE-A8FF-973CA61F302E@network-heretics.com> <6771A81D-EBE9-4A88-B7BA-E1CE9778C1BF@gmail.com> <57475D3F.8040702@cs.tcd.ie>
Date: Thu, 26 May 2016 16:35:01 -0500
Message-ID: <CAKKJt-dSkMeXwC3s5fOE9S+Dj1QWhxGH1h_MpLr1MaJJg67_SQ@mail.gmail.com>
Subject: Re: IETF-100 maybe it's mostly been said? (Was: Re: [Recentattendees] Background on Singapore go/no go for IETF 100)
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Content-Type: multipart/alternative; boundary=94eb2c07b4a004e8c20533c590e6
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/ZHEUig5A1_vZObBKDPolszvF6cw>
Cc: "Ietf@Ietf. Org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
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: Thu, 26 May 2016 21:35:06 -0000

Just to agree with Stephen,

On Thu, May 26, 2016 at 3:31 PM, Stephen Farrell <stephen.farrell@cs.tcd.ie>
wrote:

>
> Not really addressing Margaret, but us all...
>
> On 26/05/16 21:21, Margaret Cullen wrote:
> > What about the IAOC writing to the IETF list and/or recent attendees
> > when they are considering going to a new country, asking if anyone
> > has any feedback on the idea?  And then considering that feedback
> > _before_ making a final decision, signing a contract, etc?
>
> So we seem to be at the point where this mega-thread is so long
> that people haven't seen the start of it. Exactly the above was
> agreed to be done, and was done, some time back. (Sorry I don't
> have the URL to hand now.)
>
> Perhaps we ought all take this as a signal that the signal to
> repetition ratio for this thread has reached a point where we
> might all step back from the keyboards for a day or two and see
> what additional information the IAOC can come back with in about
> that time frame?
>
> I really don't see new points arising in the meantime that are
> so pressing that they can't wait, and for all the urgency of
> getting a decision about IETF-100, I don't think a day or two's
> breathing space for the IAOC will make a substantive difference
> to the eventual outcome. It might also give us all a while to
> ponder the difficult dilemma more thoroughly and even more
> thoughtfully, but a bit more calmly perhaps.


I'd say more broadly that we've seen enough e-mail in various threads on
this topic that if someone DOES want to introduce a new consideration, it's
like finding a needle in a haystack for other people to notice. That's not
to say there's nothing new that should be considered, only that if you have
a new topic you'd like to the community to keep in mind, you might want to
wait a bit to introduce it, just so it doesn't get lost in the flood.

For what it's worth, the IESG spent more than an hour on this week's
informal telechat discussing the feedback that we've seen on IETF 100, so I
can promise you that what people have already said is not being ignored.

I hope that's helpful.

Spencer