[secdir] [new-work] WG Review: Meeting Venue (mtgvenue)

The IESG <iesg@ietf.org> Fri, 17 June 2016 16:26 UTC

Return-Path: <new-work-bounces@ietf.org>
X-Original-To: secdir@ietf.org
Delivered-To: secdir@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BEB9F12D86D; Fri, 17 Jun 2016 09:26:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1466180772; bh=dOGaclj1lk45Rr+okefZCuwz4WoL1Z8hdPtdZIlJQYs=; h=From:To:Date:Subject:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe; b=omDHpvyJnOIiEAqDqz53jy8GSsBcAL4AF7+yYOroOt649Qi45Zm25n9a8oKEJvz7h NQWfE0tKEOXVlZZ8270xY89J2FyJdIWRE9Jz7HbnbfQbiwu3u9VEMvvYbfEzIgIk9v 0RdFDQASc+87WcbEhy/MRRDR2IY7m6AvFoKO+En4=
X-Original-To: new-work@ietf.org
Delivered-To: new-work@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A89D12D84A for <new-work@ietf.org>; Fri, 17 Jun 2016 09:26:07 -0700 (PDT)
MIME-Version: 1.0
From: The IESG <iesg@ietf.org>
To: <new-work@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.23.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply_to: <iesg@ietf.org>
Message-ID: <20160617162607.9770.52383.idtracker@ietfa.amsl.com>
Date: Fri, 17 Jun 2016 09:26:07 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/new-work/5WDTM0ZephETwFdQEmlxtjeF31o>
X-BeenThere: new-work@ietf.org
X-Mailman-Version: 2.1.17
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: new-work-bounces@ietf.org
Sender: "new-work" <new-work-bounces@ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/4ZEQR6gLDW3petCXO4RgdBGJeDo>
X-Mailman-Approved-At: Mon, 20 Jun 2016 08:01:30 -0700
Subject: [secdir] [new-work] WG Review: Meeting Venue (mtgvenue)
X-BeenThere: secdir@ietf.org
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdir/>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jun 2016 16:26:13 -0000

A new IETF WG has been proposed in the General Area. The IESG has not
made any determination yet. The following draft charter was submitted,
and is provided for informational purposes only. Please send your
comments to the IESG mailing list (iesg@ietf.org) by 2016-06-27.

Meeting Venue  (mtgvenue)
Current status: Proposed WG


Assigned Area Director:
  Jari Arkko <jari.arkko@piuha.net>

General Area Directors:
  Jari Arkko <jari.arkko@piuha.net>
Mailing list:
  Address: mtgvenue@ietf.org
  To subscribe: https://www.ietf.org/mailman/listinfo/mtgvenue
  Archive: https://mailarchive.ietf.org/arch/search/?email_list=mtgvenue

Charter: https://datatracker.ietf.org/doc/charter-ietf-mtgvenue/

The selection of meeting venues for our physical meetings is a common
area of discussion at the IETF and feedback for the IAOC and its
meeting committee.

A specification of the venue selection process and criteria would be
useful. With community discussion and agreement such a specification
will be very helpful in improving the process and ensuring that the
relevant criteria are properly identified.

The discussion itself may also be helpful. For instance, due to recent
discussions, potential future destinations are announced to the
community to help identify potential issues early.

These processes and criteria support the overall IETF meeting
strategy. The IETF complements its mostly online work with three
physical meetings each year, obviously for the purpose of the
standards development work but also for the opportunities for
high-bandwidth collaboration, cross-pollination of ideas, and focusing
on running code. Existing geographic distribution policy explicitly
calls for rotating meeting locations equally among the largest sources
of IETF attendees, previously defined as North America, Europe, and
Asia, while reserving a possibility for exceptions. The exceptions
are, for instance, meetings outside those regions. The rationale is to
meet in different geographic regions in order to spread the difficulty
and cost of travel among the attendees. The rotation policy, known as
the 1-1-1-* model -- with the asterisk denoting the exceptions -- was
set by the IESG, documented in

The MTGVENUE working group is the forum where the IETF community can
discuss and agree on what should go into the policies, the selection
process, and the detailed criteria going forward. All criteria and all
other aspects of the process are open for discussion. The purpose of
the working group is to produce a community consensus document(s) that
help drive the meeting selection process in a manner that the
community is comfortable with.

The working group shall produce guidance on two areas:

1. A specification of the geographic IETF meeting policy, currently
described as the "1-1-1-*" policy. The policy going forward is up to
the working group.

2. A specification that describes the detailed meeting venue selection
process and criteria, the contents of which are also up to the working

The specification(s) are expected to be Best Current Practice (BCP)
documents. The specifications are expected to provide clear guidance
to meeting selections, be implementable in our operating environment,
and take into account the needs of the highly diverse IETF community.

  Mar 2016 - Initial individual draft on venue selection process and
  Jul 2016 - Initial individual draft on IETF meeting geographic
distribution policy
  Nov 2016 - Submission of the final working group draft on IETF meeting
geographic distribution policy to the IESG
  Feb 2017 - Submission of the final working group draft on venue
selection process and criteria to the IESG

new-work mailing list