Re: [93attendees] Meeting schedule

Ted Lemon <ted.lemon@nominum.com> Wed, 22 July 2015 11:12 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 041901B2A68 for <93attendees@ietfa.amsl.com>; Wed, 22 Jul 2015 04:12:58 -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 VZvrEp-GoP_s for <93attendees@ietfa.amsl.com>; Wed, 22 Jul 2015 04:12:56 -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 05EF31B2A6D for <93attendees@ietf.org>; Wed, 22 Jul 2015 04:12:55 -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 B08BEDA0089; Wed, 22 Jul 2015 11:12:54 +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; Wed, 22 Jul 2015 04:12:54 -0700
Content-Type: multipart/alternative; boundary="Apple-Mail=_699E7EAF-AC95-41B3-8138-9B510CFFD4CC"
MIME-Version: 1.0 (Mac OS X Mail 8.2 \(2102\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <p06240602d1d5123f8463@[130.129.14.251]>
Date: Wed, 22 Jul 2015 07:12:52 -0400
Message-ID: <E0C70D9D-23C8-47FD-95D7-0C32952DD622@nominum.com>
References: <p06240602d1d3231e977e@[130.129.14.251]> <670E6EB2-3519-4B5A-B5BD-D323E15033D7@cs.ucla.edu> <p06240613d1d407147bfb@[130.129.14.251]> <9DEC79C9-F117-453A-8F8F-98BA0FC62B08@cs.ucla.edu> <822C7233-3ACC-4A03-A556-C907CF90684A@piuha.net> <p06240602d1d5123f8463@[130.129.14.251]>
To: Randall Gellens <randy@qti.qualcomm.com>
X-Mailer: Apple Mail (2.2102)
X-Originating-IP: [71.233.41.235]
Archived-At: <http://mailarchive.ietf.org/arch/msg/93attendees/EVDD23aOzt7RUQ4M1RJy5qezfW4>
Cc: Jari Arkko <jari.arkko@piuha.net>, 93attendees@ietf.org
Subject: Re: [93attendees] 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: Wed, 22 Jul 2015 11:12:58 -0000

On Jul 22, 2015, at 5:32 AM, Randall Gellens <randy@qti.qualcomm.com> wrote:
> I wonder if it might be possible to try and tweak this by:
> 
>  - Having most slots be shorter (e.g., 60 minutes)
>  - When WG chairs request slot(s), ask them to rate how critical f2f time is
>    o f2f time vital for making progress on x drafts
>    o f2f time useful for making progress in WG generally
>    o f2f time potentially useful
> 
> When scheduling is done, give priority to "vital" WG slots (some groups might not get a slot).

This is a great suggestion.   In addition, I would suggest:

Having a single slot per day that’s for cross-area advertising, takes a half hour, is not area-specific, and is short.   You get two minutes for an elevator pitch, and it’s about a document that would be discussed somewhere that day.   Competition for slots would be based on the amount and level of actual work that has occurred on that document since the previous IETF, plus the AD’s and chairs’ impression of how important cross-area review is.   No Q&A, and if you run to the end of your slot, your microphone gets cut and the next presenter’s microphone gets turned on.   In some cases it might make sense for someone who is not a document author to do a talk on a document because they are concerned about some issue in the document and want to raise awareness about it.

This is probably not correct as proposed, but trying it as proposed would help us to understand what would be correct.

Another suggestion: keep some slots open, so that when a discussion in one of the short slots turns out to be productive, an additional slot can be forked later in the week to continue it.  A bit of a risk that people would skip the last day if we did this, but people who want to get work done might not.