[Emo-dir] next steps on IETF Outreach

Alia Atlas <akatlas@gmail.com> Mon, 30 October 2017 02:46 UTC

Return-Path: <akatlas@gmail.com>
X-Original-To: emo-dir@ietfa.amsl.com
Delivered-To: emo-dir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B268413FD6A; Sun, 29 Oct 2017 19:46:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UQBvseF2XPIy; Sun, 29 Oct 2017 19:46:33 -0700 (PDT)
Received: from mail-wr0-x22b.google.com (mail-wr0-x22b.google.com [IPv6:2a00:1450:400c:c0c::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 384DF13FD6F; Sun, 29 Oct 2017 19:46:33 -0700 (PDT)
Received: by mail-wr0-x22b.google.com with SMTP id p96so11080946wrb.7; Sun, 29 Oct 2017 19:46:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=EkAx9Mm5mMc0DyvA6kaqt8QTUjKH1AOogDPoClBY//4=; b=b6TixYKpnuLyuw3RBvUAq4VCmPKad8LuKSinarWb/LPJqvqcg2yLTs7Jg4efmkIwKb uxk/N5kRoEPqOzqN9XnVQsFIZMoFNTNs8NScyMaZi6szhdajqkIrF0br5ksCOrW28Cs4 E06Z2RYsQoMZZ6ruc0NQ79SxAuUVQBvuIGxdgWreVFPvwdlWknLml0HL6Z9ghMdtFp5N cUixnPEEUYN9WocrafLuiI598DXn2yQKR/GtcnMc+XoSf9rXtG29tn4DMlXFUKEiiOzI ipb4CVd7JLUZJb69A1i62qnMwH64rGKtNT3voqf8zQGxBmfuuspWE0KFTrRVkkHJE4Ha FrXg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=EkAx9Mm5mMc0DyvA6kaqt8QTUjKH1AOogDPoClBY//4=; b=fFL0Asg+ZW8Mg/X45khYrnfIkYyDKh1Rj6HPVs5tePlz8zlf7nHHIYewYpHObZYjcV jm1iFfEgsQSPI8b9dB+E/xfuKjqSi2Ai5VjnCRwYMJ8USMoyek5HJ/GHr+WsfLLPAKd7 IzKtr6MBdDAc/vKKn5+3AFiAeblvhe4WtPdUuGrg1pljuMdAE2fuVnp2VQGu59Ib35wV /3dmZ56iyTFGuJQBVfxVHlnLpQ7VEFDoaRHyxNsApYa4XnIbZELme+5RIfLViU7S1I8f 72+Kitbk46j7xYajDasa26m+w6r7qNBh1Fb2K0hL/Lvf9SXjvpA7aJbw1P0IZQ8yDSGj ly+g==
X-Gm-Message-State: AMCzsaUadTcfrurMK8Kq+J++xtaeUIq5t54kfoQs+vsAWRYrA5AVsiDw s9cimKKyMYkJeFT2OmZOvfMY0NdxJ4bQ+IyQLvCD3ZZ1
X-Google-Smtp-Source: ABhQp+SSkr2pU/ribDqKitJmIUG+atZ2lHzvMtJi6BI9D+aOvIQ0ZSaDNNdUvANzNQ7tB/Qqx/lPe1Jw9RU5WN04j/s=
X-Received: by 10.223.199.138 with SMTP id l10mr5766095wrg.121.1509331591259; Sun, 29 Oct 2017 19:46:31 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.150.10 with HTTP; Sun, 29 Oct 2017 19:46:30 -0700 (PDT)
From: Alia Atlas <akatlas@gmail.com>
Date: Sun, 29 Oct 2017 22:46:30 -0400
Message-ID: <CAG4d1reH5r7hLbX=pT4iD=wv3yS=KxUPb=Gq60yZW-T-C93-SQ@mail.gmail.com>
To: emo-dir@ietf.org, vmeet <vmeet@ietf.org>, IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="089e0820dd10586d62055cbaa5ef"
Archived-At: <https://mailarchive.ietf.org/arch/msg/emo-dir/GHN0eMp9bKSHMDXQF8Nzqs1LwU4>
Subject: [Emo-dir] next steps on IETF Outreach
X-BeenThere: emo-dir@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Education, Mentoring & Outreach Directorate" <emo-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emo-dir>, <mailto:emo-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emo-dir/>
List-Post: <mailto:emo-dir@ietf.org>
List-Help: <mailto:emo-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emo-dir>, <mailto:emo-dir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Oct 2017 02:46:36 -0000

After the webconference about IETF Local Communities and IETF Outreach,
I and my co-authors have taken another pass at what is the appropriate
structure
and necessary (very minimal) applications of policy in
draft-atlas-geo-focused-activities-01.
Feedback would be welcome. My expectation is to use this for the next year
or so for how the IETF Outreach work will be organized and improve it
before thinking about publication.  I would like to start having more IETF
Local Communities start up and would be delighted to chat with anyone who
is potentially interested in being a coordinator.

I am considering holding a side-meeting at IETF 100 also; please privately
email me
with thoughts.

For those curious about what an IETF Local Community meeting can be like,
do ask
on ietf-hub-boston@ietf.org or someone you know.  Organizational details
are on the
wiki at: https://trac.ietf.org/trac/edu/wiki/BostonLocal

Regards,
Alia

---------- Forwarded message ----------
From: <internet-drafts@ietf.org>;
Date: Sun, Oct 29, 2017 at 10:36 PM
Subject: I-D Action: draft-atlas-geo-focused-activities-01.txt
To: i-d-announce@ietf.org



A New Internet-Draft is available from the on-line Internet-Drafts
directories.


        Title           : Geographically-Focused IETF Activities
        Authors         : Alia Atlas
                          Christian O’Flaherty
                          Harish Chowdhary
                          Scott Bradner
        Filename        : draft-atlas-geo-focused-activities-01.txt
        Pages           : 13
        Date            : 2017-10-29

Abstract:
   The IETF has a variety of activities beyond those that are part of
   the standards process.  IETF activities that aren't part of the
   standards process are still quite useful for the IETF mission.  Some
   of these activities, such as IETF hackathons, tutorials, and
   mentoring, occur at in-person meetings.  There has been and continues
   to be interest in having such activities located in different
   geographical areas.

   The document defines how the IETF organizes our Geographically-
   Focused Activities.  It is intended for eventual publication as a BCP
   but this is currently an initial strawman proposal based upon the
   existing variety of experience with the experimental activities in
   this space over the past several years.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-atlas-geo-focused-activities/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-atlas-geo-focused-activities-01
https://datatracker.ietf.org/doc/html/draft-atlas-geo-focused-activities-01

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-atlas-geo-focused-activities-01


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt