High level guidance for the meeting policy of the IETF
draft-ietf-mtgvenue-meeting-policy-03

Document Type Active Internet-Draft (mtgvenue WG)
Last updated 2018-02-08 (latest revision 2017-12-06)
Stream IETF
Intended RFC status Best Current Practice
Formats plain text pdf html bibtex
Stream WG state Submitted to IESG for Publication
Document shepherd Charles Eckel
Shepherd write-up Show (last changed 2018-01-11)
IESG IESG state AD Evaluation
Consensus Boilerplate Yes
Telechat date
Responsible AD Alissa Cooper
Send notices to Charles Eckel <eckelcu@cisco.com>
Internet Engineering Task Force                              S. Krishnan
Internet-Draft                                                    Kaloom
Intended status: Best Current Practice                  December 6, 2017
Expires: June 9, 2018

         High level guidance for the meeting policy of the IETF
                 draft-ietf-mtgvenue-meeting-policy-03

Abstract

   This document describes a proposed meeting location policy for the
   IETF and the various stakeholders for realizing such a policy.

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 June 9, 2018.

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

Krishnan                  Expires June 9, 2018                  [Page 1]
Internet-Draft             IETF Meeting Policy             December 2017

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  The 1-1-1-* meeting policy  . . . . . . . . . . . . . . . . .   2
   3.  Implementation of the policy  . . . . . . . . . . . . . . . .   3
   4.  Re-evaluation and changes to this policy  . . . . . . . . . .   4
   5.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   4
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   4
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   The work of the IETF is primarily conducted on the working group
   mailing lists, while face-to-face WG meetings mainly provide a high
   bandwidth mechanism for working out unresolved issues.  The IETF
   currently strives to have a 1-1-1-* meeting policy [IETFMEET] where
   the goal is to distribute the meetings equally between North America,
   Europe, and Asia that are the locations most of the IETF participants
   have come from in the recent past.  This meeting rotation is mainly
   aimed at distributing the travel pain for the existing IETF
   participants who physically attend meetings and for distributing the
   timezone pain for those who participate remotely.  This policy has
   neither been defined precisely nor documented in an IETF consensus
   document.  This document is meant to serve as a consensus-backed
   statement of this policy published as a BCP.

2.  The 1-1-1-* meeting policy

   Given that the majority of the current participants come from North
   America, Europe, and Asia [CONT-DIST], the IETF policy is that our
   meetings should primarily be in those regions. i.e., the meeting
   policy (let's call this the "1-1-1" policy) is that meetings should
   rotate between North America, Europe, and Asia.  It is important to
   note that such rotation and any effects to distributing travel pain
   should be considered from a long-term perspective.  While the typical
   cycle in an IETF year may be a meeting in North America in March, a
   meeting in Europe in July, and a meeting in Asia on November, the
   1-1-1 policy does not mandate such a cycle, as long as the
   distribution to these regions over multiple years is roughy equal.
   There are many reasons why meetings might be distributed differently
   in a given year, and that is fine as long as the distribution in
   subsequent years balances out the disruptions.

   BACKGROUND NOTE:The IETF recognizes that we have not always been
   successful in following this policy over the past few years.  In
   fact, at the time of writing, going back 6 years the meeting

Krishnan                  Expires June 9, 2018                  [Page 2]
Internet-Draft             IETF Meeting Policy             December 2017
Show full document text