Re: [93attendees] [IAOC] Meeting schedule

Ted Lemon <ted.lemon@nominum.com> Tue, 21 July 2015 14:07 UTC

Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: 93attendees@ietfa.amsl.com
Delivered-To: 93attendees@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 571C11B2E44; Tue, 21 Jul 2015 07:07:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, T_RP_MATCHES_RCVD=-0.01] 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 hU9Bwz0drVIa; Tue, 21 Jul 2015 07:07:05 -0700 (PDT)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E2431B2E3F; Tue, 21 Jul 2015 07:07:05 -0700 (PDT)
Received: from webmail.nominum.com (cas-03.win.nominum.com [64.89.235.66]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id 668B5DA0089; Tue, 21 Jul 2015 14:07:05 +0000 (UTC)
Received: from [10.0.20.218] (71.233.41.235) by CAS-03.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.224.2; Tue, 21 Jul 2015 07:07:04 -0700
Content-Type: multipart/alternative; boundary="Apple-Mail=_5D2BCD3C-07C2-4068-AE8B-44096BF292C7"
MIME-Version: 1.0 (Mac OS X Mail 8.2 \(2102\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <CY1PR09MB0634D3C4D8D9DDEEFB864CA8EA840@CY1PR09MB0634.namprd09.prod.outlook.com>
Date: Tue, 21 Jul 2015 10:07:03 -0400
Message-ID: <600FB557-9635-45C0-9C99-3DBE31E5CFE8@nominum.com>
References: <p06240602d1d3231e977e@130.129.14.251> <alpine.OSX.2.01.1507201630210.60032@rabdullah.local> <D2E48F4F-CE89-4C1F-ACB4-85F219651A8C@juniper.net> <CAJU8_nXo56kuodKCkWyWFW=sM95Hju216uPD_W3WyzSj3qiUrQ@mail.gmail.com> <p06240603d1d3c31599ff@[130.129.14.251]> <55AE1BF9.6060407@gmail.com> <55AE3545.4050403@dcrocker.net> <CY1PR09MB063444AFD8CFA87040CE4A79EA840@CY1PR09MB0634.namprd09.prod.outlook.com> <CY1PR09MB0634899D77D1B7C510AF92CCEA840@CY1PR09MB0634.namprd09.prod.outlook.com> <081364BF-3F03-4BFB-B5A6-FA2E7062041E@nominum.com> <alpine.OSX.2.01.1507210557550.62358@rabdullah.local> <B54303E8-2CAF-4762-9B75-E01DFDB67E72@nominum.com> <CY1PR09MB063485F125CB8D9AB103B6A8EA840@CY1PR09MB0634.namprd09.prod.outlook.com> <61F876E9-F161-4E0B-8E3F-1B96B8C0F475@nominum.com> <CY1PR09MB0634D3C4D8D9DDEEFB864CA8EA840@CY1PR09MB0634.namprd09.prod.outlook.com>
To: Henning Schulzrinne <Henning.Schulzrinne@fcc.gov>
X-Mailer: Apple Mail (2.2102)
X-Originating-IP: [71.233.41.235]
Archived-At: <http://mailarchive.ietf.org/arch/msg/93attendees/fW2FdrxZAVsEYSM4Xxn-z99zuso>
Cc: "iaoc@ietf.org" <IAOC@ietf.org>, Ole Jacobsen <olejacobsen@me.com>, The IESG <iesg@ietf.org>, "93attendees@ietf.org" <93attendees@ietf.org>
Subject: Re: [93attendees] [IAOC] Meeting schedule
X-BeenThere: 93attendees@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Mailing list of IETF 93 attendees that have opted in on this list. " <93attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/93attendees>, <mailto:93attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/93attendees/>
List-Post: <mailto:93attendees@ietf.org>
List-Help: <mailto:93attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/93attendees>, <mailto:93attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jul 2015 14:07:07 -0000

On Jul 21, 2015, at 9:55 AM, Henning Schulzrinne <Henning.Schulzrinne@fcc.gov> wrote:
> My experience differs - the working groups I have attended so far this week all made good use of their allocated time (and, in some cases, could have used a bit more). 

Hm.   Of the working groups I have attended, I’d say at least half of the working group time was wasted on long presentations about work that participants should already be familiar with.   Many of the comments, probably 50%, at the microphone did not reflect any serious thought on the part of the commenter, and did not add useful insight to the discussion.   I have seen some good discussions, but these have been in the minority.   I see a lot of working groups with packed agendas where each draft gets ten minutes.   It’s impossible to have a constructive discussion about a draft that needs discussion in ten minutes.   Ten minutes is way too long for a sales pitch about a draft.

I sympathize with your skepticism, but I haven’t seen a lot of effort to change the status quo.  What I am suggesting is that if we seriously just say “look, the hours we have for meetings are limited to business hours, and you have to figure out how you’re going to best use your limited time,” and divide the time up evenly between requestors, maybe with exceptions if they can be clearly justified, we will stop providing incentives for working group chairs to just ask for as much time as they can and not try to make good use of the time they get.

The reason we haven’t seen this work is because we haven’t tried it.   We haven’t really tried anything.   The only discipline that chairs have experienced in the past is as a result of schedule congestion, and in general the IESG just throws themselves on the scheduling sword and makes it work based on chairs’ requests.   I am proposing that we stop doing that.