Re: [vmeet] strawman policy for handling geo-focused outreach: draft-atlas-geo-focused-activities-00.txt

Alia Atlas <akatlas@gmail.com> Mon, 10 July 2017 18:45 UTC

Return-Path: <akatlas@gmail.com>
X-Original-To: vmeet@ietfa.amsl.com
Delivered-To: vmeet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 977F8131852; Mon, 10 Jul 2017 11:45:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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] 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 wyg7eSHaZhjK; Mon, 10 Jul 2017 11:45:43 -0700 (PDT)
Received: from mail-wr0-x235.google.com (mail-wr0-x235.google.com [IPv6:2a00:1450:400c:c0c::235]) (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 18A1112EC04; Mon, 10 Jul 2017 11:45:43 -0700 (PDT)
Received: by mail-wr0-x235.google.com with SMTP id 77so150481743wrb.1; Mon, 10 Jul 2017 11:45:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=1cbbGIP2jnf56Weph3b0Ijr43fPGNT3CpIML7gQ7FtI=; b=gygtoB40SKxgXWQaj38Sf85s0nKDMChA2gZfeo2SxvFQ6/QirPEoBhN8RPOpHcxOlz ZyuPe76HJX6TvV7Q3JXbNkJ9XZJ+U+nZfIzKyhVcu34saALfZmnlWZNjN/akojekZPZY jsQdTCUW7iKUaeNiCirLHAxEtE+12QdgymDtAmb4d89wl8TiQadUb4uuY87SRbL4pbpn qmQnWFZoG54hWBhHw8LNI9CmdOsJnMBgjuzHjGsiHmjkfyoSdZNLOa5Q8XoBKSfuKwYU PT3mMLTsb/UAC7XsFuvs0NSgfzW4tme0RjGJmHhcp800dP3gkaSbKo/p74gSuv+L+fic imfg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=1cbbGIP2jnf56Weph3b0Ijr43fPGNT3CpIML7gQ7FtI=; b=ZF3a+w0CQgq4ERw1u4DGyv8Ec5HGhopHgczeMTZ3H/L2t4jsHFTPVrwgQcgFtTwNPm senl9JiUoCdw/8F55bminX6M+hD8IPJquLiyN6uSHYLTAYUDcLFOHDKq0rVG7ostLcGy LS1sVE+5uCyqBTZ/SYhIE4thDFcOsWvnFFLcbmqauOgurVs4DOLgNZqP7RvNQW4eKH/p 4bssjkv871dkex6YgoXxohk560zJEov8Cp5nhagoQSj2VZkHSGlTCarqTNWDiL5YbnQp laADQDrslL2y+BEx9Wd8MS3ADkSYCbTmoZpB13stkxe1j7KNZfj46FHFHG+Edh6jo/gs y4Lg==
X-Gm-Message-State: AIVw110OjHt32nnilHPZ6Y2+Thol/FDnIiiXH0nM4y8N7dUTOY2QgQ05 2n9mxYtLzfxqcOiycKK+l2kKXoDV5g==
X-Received: by 10.223.135.154 with SMTP id b26mr8975097wrb.48.1499712341497; Mon, 10 Jul 2017 11:45:41 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.130.179 with HTTP; Mon, 10 Jul 2017 11:45:40 -0700 (PDT)
In-Reply-To: <267eed1b-1157-dbf2-1d78-a25b596b9bff@gmail.com>
References: <CAG4d1rd+YcKwWnzSU8f_fdeSahGt=NY87bPcRU8G8Je=G9=FXw@mail.gmail.com> <CAHw9_i+YjRE0EFhoAyEp6kFv188v23VG55tFJQnp6FUf=ChpLg@mail.gmail.com> <CAG4d1rfREox3fOpRBmBDo_YPCJ8T7pyQfFNmWWDRuqEQW9wFgg@mail.gmail.com> <267eed1b-1157-dbf2-1d78-a25b596b9bff@gmail.com>
From: Alia Atlas <akatlas@gmail.com>
Date: Mon, 10 Jul 2017 14:45:40 -0400
Message-ID: <CAG4d1rcufKWgbd7BR_kJbNHJYotuF-ro_Ksva3AdJSUyDMuwZQ@mail.gmail.com>
To: joel jaeggli <joelja@gmail.com>
Cc: Warren Kumari <warren@kumari.net>, EDU Team <edu-team@ietf.org>, vmeet <vmeet@ietf.org>
Content-Type: multipart/alternative; boundary="001a11474ad46166b70553fafd86"
Archived-At: <https://mailarchive.ietf.org/arch/msg/vmeet/fKTa1dtXqMm5Jbct10TJUDhi3C8>
Subject: Re: [vmeet] strawman policy for handling geo-focused outreach: draft-atlas-geo-focused-activities-00.txt
X-BeenThere: vmeet@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF remote participation meeting services discussion <vmeet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/vmeet>, <mailto:vmeet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/vmeet/>
List-Post: <mailto:vmeet@ietf.org>
List-Help: <mailto:vmeet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vmeet>, <mailto:vmeet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jul 2017 18:45:49 -0000

Joel,

On Mon, Jul 10, 2017 at 2:34 PM, joel jaeggli <joelja@gmail.com> wrote:

> On 7/10/17 11:15, Alia Atlas wrote:
> > Hi Warren,
> >
> > Thanks for reading it and for the nits.  I'll handle those in the next
> > version.
> > Any comments on the substance?
>
> Definitionaly the IETF meeting is a plenary, most of the meetings at it
> are not (appart from the plenary(s)) we meet together, but not in
> plenary generally. The distinction is probably relevant, since it
> implies a higher level of coordination (meeting in plenary) between
> essentially unrelated activities then is otherwise the case.
>

Thanks - I'll clarify.  I was using Plenary to refer to the actual Plenary
session for sessions that a Remote Hub might be connecting to, but I may
have also referred to plenary meetings for the 3 face-to-face IETF-wide
meetings that we have.  Do you have a better term to suggest?

Regards,
Alia


> joel
>
> > Regards,
> > Alia
> >
> > On Mon, Jul 10, 2017 at 1:57 PM, Warren Kumari <warren@kumari.net
> > <mailto:warren@kumari.net>> wrote:
> >
> >     On Wed, Jul 5, 2017 at 12:30 PM, Alia Atlas <akatlas@gmail.com
> >     <mailto:akatlas@gmail.com>> wrote:
> >     > Here is a draft suggesting how to connect in the various
> >     > geographically-focused activities into the IETF with light
> oversight and
> >     > considering how various IETF policies should apply.
> >     >
> >     > I hope that it will spur conversation so we can determine the
> right way
> >     > forward.
> >
> >     Hi there,
> >
> >     I have a bunch of nits and similar for this document. As always with
> >     nits, feel free to incorporate, ignore, spindle , mutilate or fold...
> >
> >
> >     1.  Introduction
> >
> >        The IETF primarily focuses our activities on plenary meetings,
> >        mailing lists, and individual Working Group interim meetings with
> >        Internet Drafts, RFCs, and some structured text or code as
> >        deliverables.  There has been and continues to be interest in
> having
> >
> >     [O] There has been and continues to be
> >     [P] There has been, and continues to be,
> >     [R] grammar
> >
> >     ...
> >
> >     Some of the motivations and objectives include: 1. increasing
> >     awareness of the IETF's role in the Internet ecosystem, 2.
> >     providing...
> >
> >     [P] I suggest format this list as a list to make it more readable
> (or,
> >     xml2rfc fail?) . Also, should either start all list items with a
> >     capital letter, or none of them.
> >
> >
> >     These objectives can be summed up as increasing awareness of the
> >        IETF, doing outreach to encourage new IETF participation, and
> >        increase technical discussions and cross-learning to encourage
> faster
> >        and better technical output.  These are objectives that are in the
> >        best interest of the IETF.
> >
> >     [P] I don't now why we have that last sentence in the above
> paragraph.
> >     Seems slightly defensive...
> >
> >        The IETF works well when organization happens from motivated
> people
> >        who self-organize and the IETF can provide support and light
> >        oversight.  The IETF has an Education, Mentoring, and Outreach
> >
> >     [O]  The IETF works well when organization happens from motivated
> >     people who self-organize and the IETF can provide support and light
> >     oversight.
> >     [P] The IETF works best when motivated people self-organize, and the
> >     IETF provides support and light oversight.
> >     [R] readability
> >
> >
> >
> >     2.  Terminology
> >
> >        Geographically-Focused IETF Activities  An IETF Activity that is
> >
> >     [O]  Geographically-Focused IETF Activities
> >     [P] Geographically Focused IETF Activities:
> >     [R] consistency with other sections below, and grammar
> >
> >     ...
> >
> >     The focus is on growing a local group of people participating in the
> >     IETF and strengthening the professional and social relationships
> >     between them to encourage
> >     [O] between them
> >     [P] amongst them
> >     [R] grammar
> >
> >           collaboration.
> >
> >     Remote Awareness Hub  An event where video from one or more IETF
> >     [O] Remote Awareness Hub
> >     [P] Remote Awareness Hub:
> >     [R] consistency
> >
> >     ...
> >
> >      IETF Awareness Activity  An activity where "what the IETF is and
> >
> >     [O]  IETF Awareness Activity
> >     [P] IETF Awareness Activity:
> >     [R] grammar
> >
> >
> >     ...
> >
> >       Remote Participation Hub  An activity that is connected to an IETF
> >
> >     [O]  Remote Participation Hub
> >     [P] Remote Participation Hub:
> >     [R] consistency (... and same for rest of list)
> >
> >
> >     3.3.  One-Time Activities
> >
> >        Some Geographically-Focused IETF Activities may be one-time
> activity.
> >
> >     [O] may be one-time activity.
> >     [P] may be one-time activities.
> >     [R] grammar
> >
> >      A Geographically-
> >        Focused IETF Activity in a particular geography that do not have a
> >
> >     [O] that do not have
> >     [P] that does not have
> >     [R] grammar
> >
> >        Coordinator identified fall under the One-Time Activity
> Coordinators,
> >
> >     [O] fall under
> >     [P] falls under
> >     [R] grammar
> >
> >        even if that activity has or is repeating.  There may be a period
> >        where it isn't clear that specific Coordinators for the activity
> >        should be appointed; for instance, it may not be obvious for a
> year
> >        or more that the activity will continue to repeat.
> >
> >        The One-Time Activity Coordinators MUST appoint a Local
> Coordinator
> >        for any activity that the none of the One-Time Activity
> Coordinators
> >
> >     [O] that the none
> >     [P] that none
> >     [R] grammar
> >
> >        will be attending and running.
> >
> >     3.4.  Appointment, Term of Service, and Transitions for Coordinators
> >
> >        In general, a Coordinator should be familiar with the IETF and
> >        preferably be or have been an active participant.  For a new Local
> >        Community or a Repeating Activity, it is likely that there are
> good
> >        candidates for Coordinators.  If not, that may be a sign that the
> >        health of the activity is in question and more support is needed
> >        before appointing Coordinators.
> >
> >        It is not appropriate to assume that a Coordinator will serve for
> an
> >        indefinite amount of time.  The Directorate should check in with
> both
> >
> >     [O] both
> >     [P]
> >     [R] there should be between 2 and 5 coordinators, so using the plural
> >     and deleting "both" will cover that.
> >
> >        the Coordinators and with the associated mailing lists or
> activities
> >        to see how the activity is going and if the Coordinators are
> >        interested in continuing to do a good job.  The Directorate - and
> in
> >
> >     [O]  interested in continuing to do a good job.
> >     [R] Um. It seems odd to ask if they want to continue doing a "good
> >     job." -- do we want to delete "good"?
> >
> >
> >     3.5.  Support for Coordinators
> >
> >        The Directorate SHOULD provide support for Coordinators.  This
> should
> >        include the ability for Coordinators to learn from each others'
> >
> >     [O] each others'
> >     [P] each other's
> >     [R] grammar
> >
> >     4.1.  Keeping Attendance Records (Bluesheets)
> >
> >        In the IETF, there are three motivations for keeping track of whom
> >        attends a session.  First, there are logistics and tracking the
> >        health of the associated group; for instance, what size meeting
> room
> >        is physically required?  Second, there is documenting whom is
> >
> >     [O] documenting whom is
> >     [P] documenting who is
> >     [R] grammar
> >
> >        influencing the standards process by participating in the session.
> >        Third, there is documenting whom is in the room for legal issues
> >
> >     [O] documenting whom is in the
> >     [P] documenting who is in the
> >     [R] grammar
> >
> >
> >     5.  Use of IETF Resources
> >     ...
> >
> >       A shared on-line calendar that at least Coordinators can add events
> >
> >     [O]  A shared on-line calendar that at least Coordinators can add
> events
> >     [P] A shared online calendar that Coordinators, at a minimum, can
> >     add events
> >     [R] readability/grammar
> >
> >        to is needed.  This will provide a single place to check when and
> >        where various activities are happening.  Given that many IETFers
> >        travel for business, it also makes it easy for IETFers to
> discover if
> >        there is a local activity happening that is of interest.
> >
> >     6.  Social Media and Communications
> >
> >        Most of IETF communications activities are coordinated and
> >        accomplished by ISOC staff.  For Social media, industry media and
> >        other communication needs the Coordinator should contact
> >        comms@ietf.org <mailto:comms@ietf.org> for an appropriate
> >     messaging.  Through ISOC's support,
> >
> >     [O] for an appropriate messaging
> >     [R] I don't know what this means.
> >
> >        the activity will be better promoted and aligned with IETF
> >        expectations.  There is an ongoing revision of IASA activities
> that
> >
> >     [O] IASA -- first (actually, only!) use of IASA, please expand.
> >
> >
> >
> >
> >     W
> >
> >
> >     >
> >     > Regards,
> >     > Alia
> >     >
> >     >
> >     > ---------- Forwarded message ----------
> >     > From: <internet-drafts@ietf.org <mailto:internet-drafts@ietf.org>>
> >     > Date: Tue, Jul 4, 2017 at 1:35 PM
> >     > Subject: I-D Action: draft-atlas-geo-focused-activities-00.txt
> >     > To: i-d-announce@ietf.org <mailto: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
> >     >         Filename        : draft-atlas-geo-focused-
> activities-00.txt
> >     >         Pages           : 14
> >     >         Date            : 2017-07-04
> >     >
> >     > Abstract:
> >     >    The document defines how Geographically-Focused IETF Activities
> are
> >     >    organized and how IETF policies apply.  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/
> >     <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-00
> >     <https://tools.ietf.org/html/draft-atlas-geo-focused-activities-00>
> >     >
> >     https://datatracker.ietf.org/doc/html/draft-atlas-geo-
> focused-activities-00
> >     <https://datatracker.ietf.org/doc/html/draft-atlas-geo-
> focused-activities-00>
> >     >
> >     >
> >     > 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 <http://tools.ietf.org>.
> >     >
> >     > Internet-Drafts are also available by anonymous FTP at:
> >     > ftp://ftp.ietf.org/internet-drafts/
> >     <ftp://ftp.ietf.org/internet-drafts/>
> >     >
> >     > _______________________________________________
> >     > I-D-Announce mailing list
> >     > I-D-Announce@ietf.org <mailto:I-D-Announce@ietf.org>
> >     > https://www.ietf.org/mailman/listinfo/i-d-announce
> >     <https://www.ietf.org/mailman/listinfo/i-d-announce>
> >     > Internet-Draft directories: http://www.ietf.org/shadow.html
> >     <http://www.ietf.org/shadow.html>
> >     > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> >     <ftp://ftp.ietf.org/ietf/1shadow-sites.txt>
> >     >
> >     >
> >     > _______________________________________________
> >     > NOTE WELL: This list operates according to
> >     > http://mipassoc.org/dkim/ietf-list-rules.html
> >     <http://mipassoc.org/dkim/ietf-list-rules.html>.
> >     > https://www.ietf.org/mailman/listinfo/vmeet
> >     <https://www.ietf.org/mailman/listinfo/vmeet>
> >     >
> >
> >
> >
> >     --
> >     I don't think the execution is relevant when it was obviously a bad
> >     idea in the first place.
> >     This is like putting rabid weasels in your pants, and later
> expressing
> >     regret at having chosen those particular rabid weasels and that pair
> >     of pants.
> >        ---maf
> >
> >
> >
> >
> > _______________________________________________
> > NOTE WELL: This list operates according to
> > http://mipassoc.org/dkim/ietf-list-rules.html.
> > https://www.ietf.org/mailman/listinfo/vmeet
> >
>
>
>