Re: Meeting rotation (was Hotel situation)

Andrew Sullivan <ajs@anvilwalrusden.com> Fri, 18 December 2015 23:36 UTC

Return-Path: <ajs@anvilwalrusden.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 4EFA91A0076 for <ietf@ietfa.amsl.com>; Fri, 18 Dec 2015 15:36:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 76BWj1utEKiA for <ietf@ietfa.amsl.com>; Fri, 18 Dec 2015 15:36:50 -0800 (PST)
Received: from mx2.yitter.info (mx2.yitter.info [50.116.54.116]) by ietfa.amsl.com (Postfix) with ESMTP id 5DF131A004D for <ietf@ietf.org>; Fri, 18 Dec 2015 15:36:50 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mx2.yitter.info (Postfix) with ESMTP id 4ED73107AA for <ietf@ietf.org>; Fri, 18 Dec 2015 23:36:48 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx2.yitter.info ([127.0.0.1]) by localhost (mx2.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mLWETNjD9Tw5 for <ietf@ietf.org>; Fri, 18 Dec 2015 23:36:47 +0000 (UTC)
Received: from mx2.yitter.info (c-73-142-157-135.hsd1.nh.comcast.net [73.142.157.135]) by mx2.yitter.info (Postfix) with ESMTPSA id 7F41E1066A for <ietf@ietf.org>; Fri, 18 Dec 2015 23:36:47 +0000 (UTC)
Date: Fri, 18 Dec 2015 18:36:45 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Meeting rotation (was Hotel situation)
Message-ID: <20151218233645.GG3294@mx2.yitter.info>
References: <1DEF233B-FBA8-4750-AB4B-3E0F55822C9E@isoc.org> <D297326B.8DCF8%glenn.deen@nbcuni.com> <CAC8QAcf=yAAGVN35tUCpX38y6_qGstGhK4iYuyhK94LVWrz-+A@mail.gmail.com> <CAHw9_iL+eAFtGHKXVWMHaqi=3mGO9H1CfE4e=yZCekE9UzPR6A@mail.gmail.com> <E7D065D8-CADC-4A65-8AC7-6ECE9CF63D4F@ecs.soton.ac.uk> <7A7519D5-FD9B-4F4D-A7E5-AC047F684623@netapp.com> <EMEW3|02dedadbe5e65aac9732e9359a7c2dberBHGjK03tjc|ecs.soton.ac.uk|E7D065D8-CADC-4A65-8AC7-6ECE9CF63D4F@ecs.soton.ac.uk> <CAHw9_iKtck6ZSp6ofNFKLRj7-o3_UR42McTNQqsqCXfcduxAeA@mail.gmail.com> <5674460C.1000107@krsek.cz> <4B81FA54-F79C-42CB-8024-1C653B0C9406@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <4B81FA54-F79C-42CB-8024-1C653B0C9406@cisco.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/wD0sTM2k1vIMDFvfdp_WOAhVZUo>
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: Fri, 18 Dec 2015 23:36:52 -0000

Hi,

This is my personal opinion, and it's one that states the kinds of
things I'd want to think about rather than something that reflects my
opinion.  I mostly don't have an opinion yet; and I think it's just as
well to have this sort of discussion in public, so that's why I'm
replying.

On Fri, Dec 18, 2015 at 09:31:06PM +0000, Fred Baker (fred) wrote:
> 
> What I am suggesting to the IAOC is that, over the coming 9 years (27 meetings)

One thing that worries me a little bit in discussing that kind of plan
is how far out we're talking about, and how much it assumes that the
IETF meeting system and pace of meetings will not change in that time.

The IETF is changing and is working in an environment which is itself
changing a lot.  We are seeing quite a lot more remote participation,
and there's little reason to suppose that will slow down.  The
standards environment is changing a lot, too.  Many standards are now
developed basically as online repositories of code and standard at the
same time.  The complaint that the IETF moves too slowly and too
bureaucratically is heard more often than ever.  We are having more
interims (most of them virtual).  And our population is changing: we
are having new people come to the IETF and, of course, some people are
retiring.  In 9 years, will we still be meeting three times a year?
Will the 1-1-1* approach still apply?  (Perhaps the vast majority of
IETF participants will be coming from India and China, for instance,
in which case North America might not be a good regular destination.)

Moreover, 9 years is a _really really_ long time past the term of
anyone appointed by nomcom.  Three years was already past the nomcom
horizon, but at least there is an argument that people on the IAOC are
likely to come to at least some meetings the year after their term
ends.  I confess I have no way of forecasting whether I'll still be
participating in the IETF in 9 years (given my track record on
predicting my own career, frankly, it's astonishing to me when I even
have a clue about next week).  My first IETF meeting (in person) was
10 years and one month ago, and if you'd asked me then whether I'd
still be participating after 10 years I couldn't have guessed.  

Finally, there's been a great deal of worry about the lack of
cross-area review that we get these days, but it doesn't seem to me
that the meetings obviously help with that except by accident.  It
could be that we will conclude that three giant meetings a year (as
opposed to, say, area meetings or something like that plus, say, one
all-IETF meeting a year) is a bad idea because of the practical
constraints.

The above are each topics where I have poor knowledge, and where that
knowledge would make a difference to how I'd respond to an idea like
this.  (They're probably not all the topics, but ones that I can think
of now.)  I just don't know what to think about this.  I'd be
interested to hear views, especially including those who are perhaps
less-frequent contributors to this list, people who've started
participating in the IETF in recent years (both at meetings and also
not at meetings or only infrequently at meetings), and those who've
been arguing that we need to do something to make the meetings less
important and return the important work to lists and other such ways
of working.

I solicit your advice (either on-list or off).

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com