Re: [93attendees] Meeting schedule

Randall Gellens <randy@qti.qualcomm.com> Wed, 22 July 2015 09:32 UTC

Return-Path: <randy@qti.qualcomm.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 C2AB51AC429 for <93attendees@ietfa.amsl.com>; Wed, 22 Jul 2015 02:32:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.011
X-Spam-Level:
X-Spam-Status: No, score=-7.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-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 iO4wEPbxu0tV for <93attendees@ietfa.amsl.com>; Wed, 22 Jul 2015 02:32:08 -0700 (PDT)
Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4C3BB1ACEE5 for <93attendees@ietf.org>; Wed, 22 Jul 2015 02:32:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1437557528; x=1469093528; h=message-id:in-reply-to:references:date:to:from:subject: mime-version; bh=/RCqGtaRX992X9q5gxTVlfm2y7odZ22xFBx1nmHFFsw=; b=GBxPhQhpZMGP6fIhLJ5vPTsCEdz4siMNF4DMQYVlXalBXVBOPQ/9uS5u yoQz19r51GG5hKP4mXv7VPHaqOnsEhvJ0b6/cve2LRfWYvH3ncHLdMkDo DwJ+LxihFjqsyEfq1XAYWeXBSDwj3iY0shhmRqDUDDBhSeQ0XgVpDBtGU E=;
X-IronPort-AV: E=McAfee;i="5700,7163,7869"; a="94339528"
Received: from ironmsg03-r.qualcomm.com ([172.30.46.17]) by sabertooth02.qualcomm.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 22 Jul 2015 02:32:07 -0700
X-IronPort-AV: E=Sophos;i="5.15,522,1432623600"; d="scan'208";a="967026595"
Received: from nasanexm02f.na.qualcomm.com ([10.85.0.87]) by Ironmsg03-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 22 Jul 2015 02:32:07 -0700
Received: from [130.129.14.251] (10.80.80.8) by nasanexm02f.na.qualcomm.com (10.85.0.87) with Microsoft SMTP Server (TLS) id 15.0.1076.9; Wed, 22 Jul 2015 02:32:05 -0700
Message-ID: <p06240602d1d5123f8463@[130.129.14.251]>
In-Reply-To: <822C7233-3ACC-4A03-A556-C907CF90684A@piuha.net>
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>
X-Mailer: Eudora for Mac OS X
Date: Wed, 22 Jul 2015 02:32:00 -0700
To: Jari Arkko <jari.arkko@piuha.net>, <93attendees@ietf.org>
From: Randall Gellens <randy@qti.qualcomm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Originating-IP: [10.80.80.8]
X-ClientProxiedBy: nasanexm01a.na.qualcomm.com (10.85.0.81) To nasanexm02f.na.qualcomm.com (10.85.0.87)
Archived-At: <http://mailarchive.ietf.org/arch/msg/93attendees/JEZdULN_zNcS0rW5dbd1AdShkkM>
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 09:32:12 -0000

At 12:37 AM +0200 7/22/15, Jari Arkko wrote:

>  We've discussed the plenaries in the IESG/IAB Sunday meeting, and 
> are considering a joint,
>  shorter (s2.5h) plenary for IETF-94. This would further compress 
> the time that we use for
>  reporting, but should still allow a brief(er) technical topic to be 
> discussed and some amount
>  of time for asking questions from the leadership boards. The saved 
> time could be used
>  for working group meetings, breaks for those important side 
> discussions or that important
>  rest. This is like we had it some years ago, but it would be an 
> experiment to see how it
>  works in today's IETF.

I think it's worth a try.

>  Also, we are very acutely aware of the tradeoffs between adequate 
> rest in an intense week,
>  time for the WGs to do their interesting work, time for the 
> unofficial and unscheduled discussions
>  to happen, and the constraints on lengthening the week. We have 
> always tried to balance
>  these, and feedback on where we are with that is very much appreciated.

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).

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
[To have] butter on your head: Hungarian expression meaning guilty
of something.