management granularity (Re: Meeting "lounges" at IETF meetings)

Dave Crocker <dhc@dcrocker.net> Sat, 04 August 2012 20:32 UTC

Return-Path: <dhc@dcrocker.net>
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 C21B721F87E0 for <ietf@ietfa.amsl.com>; Sat, 4 Aug 2012 13:32:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KthNeZcZAR9r for <ietf@ietfa.amsl.com>; Sat, 4 Aug 2012 13:32:03 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id CC46921F87BD for <ietf@ietf.org>; Sat, 4 Aug 2012 13:32:03 -0700 (PDT)
Received: from [10.71.8.181] ([67.21.202.20]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q74KVwhn024965 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 4 Aug 2012 13:31:59 -0700
Message-ID: <501D86B5.9060404@dcrocker.net>
Date: Sat, 04 Aug 2012 13:31:49 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: James Polk <jmpolk@cisco.com>
Subject: management granularity (Re: Meeting "lounges" at IETF meetings)
References: <D7F9B7BE-0ED6-4B8C-808C-C75FA1A6800B@vpnc.org> <CAHBDyN6VaL3fgYe+C+o9d93VZ1bR_EDmrPN7-Sv+7BiJ9+Q9AA@mail.gmail.com> <m2ipczu5mu.wl%randy@psg.com> <42D7895B-8949-41FF-AE5B-0C9B813CEE8C@mnot.net> <m2d337u3fc.wl%randy@psg.com> <20104150-FCF4-4914-8656-72FFC9BA94AA@lucidvision.com> <CAHBDyN63_r2TEf7h81r9NYnQbdriC9Ztr-cT7vapO0uyRYB5_w@mail.gmail.com> <alpine.OSX.2.01.1208031505550.16675@173-11-110-132-sfba.hfc.comcastbusiness.net> <201208032240.q73Mc6OY008678@mtv-core-1.cisco.com>
In-Reply-To: <201208032240.q73Mc6OY008678@mtv-core-1.cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Sat, 04 Aug 2012 13:32:01 -0700 (PDT)
Cc: Mark Nottingham <mnot@mnot.net>, Ole Jacobsen <ole@cisco.com>, ietf list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
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: <http://www.ietf.org/mail-archive/web/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: Sat, 04 Aug 2012 20:32:04 -0000

Folks,


On 8/3/2012 3:38 PM, James Polk wrote:
> Having missed only 2 meetings in 13 years, I can say that no venue was
> perfect, but some were very good. It becomes a case of which venues have
> the fewest "bad" things.
...
> The crowded hallway we can't change.
>
> We can change where the snacks are served, and I have read that will
> happen for our next meeting in Vancouver here in 15 months.


Long before I started serving on the IAOC (last year) it was clear to me 
that the Secretariat & related staff knew/knows how to do their job, 
both in terms of planning and in terms of fixing problems.  My opinion 
hasn't changed in the last year.  Well actually that's not quite true. 
They seem to be a bit better than I thought...

It's not that a occasional suggestions are sure to be entirely 
unnecessary, it's that most of them are... (So, was it wrong that I felt 
a tiny glow of satisfaction at seeing a sign appear about a half-hour 
after suggesting it to them, at the beginning of the week?)


On the other hand, there's a macro-management point that /does/ need to 
fall within the community purview:

      Should we constantly seek new venues or should we prefer returning 
to a small set of them?


The tendency for the last 20 years has been to seek new venues quite 
often.  Our rate of returning has been relatively low.  That means that 
most meeting venues are unfamiliar and run the risk of some serious, 
unforseen problem.  And my own observation was that we have tended to 
suffer roughly one major venue problem a year.

Visiting familiar places means that a) we know the tradeoffs at a place, 
and b) we can tune our use of it.  Visiting new places means we can find 
/better/ places to return to, albeit while also finding worse.  Locking 
down on on a fixed set of venues means we miss these improvements. 
(It's also been noted that returning regularly often tends to get 
degraded performance over time.)

However the tendency of the community has been to express preference for 
the tourism of going to new places.

If we really want venues to function towards some ideal, we need the 
benefit of a multi-visit learning curve.

And it means we stop being tourists.

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net