Thoughts on Completely Virtual IETF Meetings
draft-manycouches-completely-virtual-meetings-04

Document Type Active Internet-Draft (individual)
Last updated 2017-01-12
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html 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)
manycouches                                                      D. York
Internet-Draft                                          Internet Society
Intended status: Informational                          January 11, 2017
Expires: July 15, 2017

              Thoughts on Completely Virtual IETF Meetings
            draft-manycouches-completely-virtual-meetings-04

Abstract

   This document captures initial thoughts about having IETF meetings
   that are completely virtual.  It explores the issues involved with
   both a "planned" virtual meeting and an "emergency" virtual meeting.
   The intent is to evolve this document to provide answers to the
   questions posed throughout the text.  This is currently a thought
   experiment.  There are no current plans to hold a completely virtual
   IETF meeting.

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 http://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 July 15, 2017.

Copyright Notice

   Copyright (c) 2017 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
   (http://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

York                      Expires July 15, 2017                 [Page 1]
Internet-Draft   Thoughts on Completely Virtual Meetings    January 2017

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Why Do IETF Meetings Take Place?  . . . . . . . . . . . .   4
     1.2.  Why Hold a Completely Virtual IETF Meeting? . . . . . . .   4
     1.3.  Conventions and Terminology . . . . . . . . . . . . . . .   4
   2.  Program . . . . . . . . . . . . . . . . . . . . . . . . . . .   5
     2.1.  Meeting Structure . . . . . . . . . . . . . . . . . . . .   5
     2.2.  Timezones . . . . . . . . . . . . . . . . . . . . . . . .   5
     2.3.  Deadlines . . . . . . . . . . . . . . . . . . . . . . . .   5
     2.4.  Plenaries . . . . . . . . . . . . . . . . . . . . . . . .   5
     2.5.  Breaks  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     2.6.  Tutorials . . . . . . . . . . . . . . . . . . . . . . . .   6
     2.7.  Hackathon / Code Sprint . . . . . . . . . . . . . . . . .   6
     2.8.  Other Physical Meeting Elements . . . . . . . . . . . . .   6
     2.9.  Sessions by non-IETF groups . . . . . . . . . . . . . . .   7
     2.10. Remote Hubs . . . . . . . . . . . . . . . . . . . . . . .   7
   3.  User Journey / Experience . . . . . . . . . . . . . . . . . .   7
     3.1.  Planning time to participate  . . . . . . . . . . . . . .   7
     3.2.  Registration / sign-up  . . . . . . . . . . . . . . . . .   8
     3.3.  Side meetings . . . . . . . . . . . . . . . . . . . . . .   8
     3.4.  Hallway conversations . . . . . . . . . . . . . . . . . .   8
     3.5.  Unstructured time . . . . . . . . . . . . . . . . . . . .   8
     3.6.  Participating in multiple sessions  . . . . . . . . . . .   8
     3.7.  Serendipity - discovering other users . . . . . . . . . .   8
     3.8.  Building relationships  . . . . . . . . . . . . . . . . .   8
     3.9.  Calendars for users . . . . . . . . . . . . . . . . . . .   8
     3.10. Voting / Hums . . . . . . . . . . . . . . . . . . . . . .   9
     3.11. Microphone lines  . . . . . . . . . . . . . . . . . . . .   9
     3.12. Disruptive Behavior . . . . . . . . . . . . . . . . . . .   9
     3.13. Mentoring . . . . . . . . . . . . . . . . . . . . . . . .   9
     3.14. Inclusivity . . . . . . . . . . . . . . . . . . . . . . .   9
     3.15. T-Shirts  . . . . . . . . . . . . . . . . . . . . . . . .   9
   4.  Technical Considerations  . . . . . . . . . . . . . . . . . .  10
     4.1.  Infrastructure  . . . . . . . . . . . . . . . . . . . . .  10
     4.2.  Capabilities  . . . . . . . . . . . . . . . . . . . . . .  10
Show full document text