IETF Community Hubs
draft-atlas-community-hubs-00

Document Type Active Internet-Draft (individual)
Last updated 2017-02-16
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)
Network Working Group                                           A. Atlas
Internet-Draft                                          Juniper Networks
Intended status: Informational                         February 16, 2017
Expires: August 20, 2017

                          IETF Community Hubs
                     draft-atlas-community-hubs-00

Abstract

   IETF Community Hubs are geographically-focused groups that facilitate
   participation in IETF activities.  An IETF Community Hub may have
   different focuses, depending upon the interests of those
   participating, such as cross-area learning, outreach, mentoring,
   problem refinement, implementation and interop testing, and social.
   An IETF Community Hub's focuses and the energy of its coordinators
   will determine what types of activities are organized.  Sample
   activities may include sessions of technical talks, social get-
   togethers, remote hubs during some IETF WG meetings, hackathons, etc.

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 August 20, 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

Atlas                    Expires August 20, 2017                [Page 1]
Internet-Draft             IETF Community Hubs             February 2017

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Benefits for Existing IETFers . . . . . . . . . . . . . .   3
     1.3.  Benefits for Outreach . . . . . . . . . . . . . . . . . .   4
   2.  Observations  . . . . . . . . . . . . . . . . . . . . . . . .   5
     2.1.  Extending the High-Bandwidth Part of Plenary Meetings . .   5
     2.2.  Working Group Interactions  . . . . . . . . . . . . . . .   5
     2.3.  Building a Connected Local Community  . . . . . . . . . .   6
   3.  What Has Been Tried in IETF-Hub-Boston  . . . . . . . . . . .   6
     3.1.  Getting Started . . . . . . . . . . . . . . . . . . . . .   6
     3.2.  Coordinators  . . . . . . . . . . . . . . . . . . . . . .   6
     3.3.  Picking Locations . . . . . . . . . . . . . . . . . . . .   6
     3.4.  Social Meetings . . . . . . . . . . . . . . . . . . . . .   7
     3.5.  Technical Talks Meetings  . . . . . . . . . . . . . . . .   7
     3.6.  Remote Hubs . . . . . . . . . . . . . . . . . . . . . . .   7
     3.7.  Publicity . . . . . . . . . . . . . . . . . . . . . . . .   8
     3.8.  Tools Used  . . . . . . . . . . . . . . . . . . . . . . .   8
   4.  Future Growth . . . . . . . . . . . . . . . . . . . . . . . .   8
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   8
   6.  Informative References  . . . . . . . . . . . . . . . . . . .   8
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   The IETF needs and wants to become more effective at outreach and
   growth of active participants, timely in developing needed
   technology, and maintain expertise in broad knowledge and review of
   Internet technologies.  IETF Community Hubs are one experimental
   approach that may assist in these goals.  Currently, there is one
   active IETF Community Hub in the Boston, Massachusetts area; it has
   been meeting periodically since May 2016.

   For a local group to be effective, it must either provide value to
   its participants to retain them or be able to do excellent outreach
   and bring those newcomers to actively participate in the IETF, but
   ideally both.  When doing outreach, having active IETFers involved to
Show full document text