Thoughts on Completely Virtual IETF Meetings
draft-manycouches-completely-virtual-meetings-04
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Dan York | ||
| Last updated | 2017-07-17 (Latest revision 2017-01-12) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)