How often and how long should IETF virtual meetings be?
draft-richardson-shmoo-how-many-fine-dinners-01

Document Type Active Internet-Draft (individual)
Author Michael Richardson 
Last updated 2020-10-19
Stream (None)
Intended RFC status (None)
Formats plain text html xml pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
shmoo Working Group                                        M. Richardson
Internet-Draft                                  Sandelman Software Works
Intended status: Best Current Practice                   19 October 2020
Expires: 22 April 2021

        How often and how long should IETF virtual meetings be?
            draft-richardson-shmoo-how-many-fine-dinners-01

Abstract

   This document recommends a model for IETF virtual meetings that
   emphasizes new work, community building and cross-area concerns.

   This document recommends virtual meetings be planned a reduced amount
   of overlap among sessions, with short sessions with generous gaps.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on 22 April 2021.

Copyright Notice

   Copyright (c) 2020 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents (https://trustee.ietf.org/
   license-info) in effect on the date of publication of this document.
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.  Code Components
   extracted from this document must include Simplified BSD License text
   as described in Section 4.e of the Trust Legal Provisions and are
   provided without warranty as described in the Simplified BSD License.

Richardson                Expires 22 April 2021                 [Page 1]
Internet-Draft             Dinners and Lunches              October 2020

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  IETF 107 experience . . . . . . . . . . . . . . . . . . .   2
     1.2.  IETF 108 experience . . . . . . . . . . . . . . . . . . .   3
   2.  Suggestions for future meetings . . . . . . . . . . . . . . .   3
     2.1.  Principles for for Recommendations  . . . . . . . . . . .   3
     2.2.  Recommendations on meeting structure  . . . . . . . . . .   4
       2.2.1.  Encourage Virtual Interim meetings for ongoing
               work  . . . . . . . . . . . . . . . . . . . . . . . .   4
       2.2.2.  Allow IETF Virtual meeting week to focus on
               community-wide activities . . . . . . . . . . . . . .   5
       2.2.3.  Number of Tracks for virtual meetings . . . . . . . .   5
   3.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   7
   6.  Changelog . . . . . . . . . . . . . . . . . . . . . . . . . .   7
   7.  Normative References  . . . . . . . . . . . . . . . . . . . .   7
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   IETF107 was the first pandemic IETF virtual meeting held in March
   2020.  IETF108 was the second pandemic IETF virtual meeting held in
   July 2020.

1.1.  IETF 107 experience

   IETF107 consisted of a light week with no more than about 4-hours of
   sessions over Monday to Thursday.  There were multiple tracks
   simultaneously, but not more three sessions at any one time.
   Priority was given to newly formed WGs that had not yet met, to Birds
   of a Feather session, and to cross-community sessions including
   specifically "dispatch" sessions.

   These sessions were done with XXXX (webex? right?)

   The timezone was approximately "Vancouver"-ish.  Most sessions
   started in late morning, which turned into mid-evening in Europe
   (going into midnight), and middle of the night in Asia.

   All other WGs were assigned a day in the weeks following IETF107 from
   March 30 to April 30.  The WGs were asked to pick a time (and time
   zone) convenient to them, and they scheduled webex meetings on
   "ietf.webex.com", although a few WG chairs decided to use "Zoom".
   Many meetings occured in the North-America/Europe optimal time slot
   of 1500UTC ("10am EDT").

Richardson                Expires 22 April 2021                 [Page 2]
Internet-Draft             Dinners and Lunches              October 2020

   Despite the "pick a time", a small number of WGs managed to pick
   times when other WGs were meeting, and there were in fact collisions.

   IETF 107 would be best described as a marathon rather than a sprint.
Show full document text