Re: [Tsv-art] Calling AD candidates

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Tue, 11 August 2020 15:37 UTC

Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6523D3A1113; Tue, 11 Aug 2020 08:37:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, 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 EQy85XYYf9Wq; Tue, 11 Aug 2020 08:37:30 -0700 (PDT)
Received: from mail-yb1-xb2a.google.com (mail-yb1-xb2a.google.com [IPv6:2607:f8b0:4864:20::b2a]) (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 585D63A110E; Tue, 11 Aug 2020 08:37:30 -0700 (PDT)
Received: by mail-yb1-xb2a.google.com with SMTP id y134so7278940yby.2; Tue, 11 Aug 2020 08:37:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=/HlYDXo228+r21+qz6QJ9qnsNB69TiQ5AxywWh6ZLXg=; b=D2enGU0JJ3x7hTgUqh4q6ghwW9n86KSUwGQaZTlkTilX6zP9PvGiCxbUfREEEd6wj8 2IC2I/klndaATJqYcVmr2HxI6+oex7+0ygEX5BLJsNRdpE1+ncQQaAYRgm9RFnDIYjzn nUjr6YtTQAbP4jjrcuf5dy0UbBsP8/boL0RuN8ChKUojP3Bwc2Uhh2tRGctFzA+0QIay w5jDy6xXLC/Wav4vwfYKrGiuXWRo1I7zEo4bSuuhU2lrbnIc0NnDysG61/m5J2QAVX+T aO4XX+/zA9GeUrHF/w8GN2h7sEjhnpk/AMLkkROys+rvuzMLQLBqfqcFpFKgSFp4q7/s U5vQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=/HlYDXo228+r21+qz6QJ9qnsNB69TiQ5AxywWh6ZLXg=; b=Ze9p/l8Hmq7D5qlb0Jj0+JU7weybsArg1xovNo+dJX/dPML0Ior903YewZ3SYmJdgb 9sNUOBxl2Ead7nrJ5iQoxl57Wri7R+OZPO+LOofVgrId64XzjlYmcRMLYwYptn5TXsAp bK/5HKBTU9qCwkh2Q7ZdG0Dlqqcb4+7buuP3sTRvQZ+whSatSGuwIPOG52n1w2o0o+xu vaTH9YzZXMmGjNgcBCQyUJegFLDDBLxce76GWcyncvkGRnXrrUj3RONtnV9yTH6DuZFE z6NOCyD7QemBUPKY8AreSySyH5LjTz+PpdyDgy1eSeHT5TCZKDnMzGmCfzFsDnohTea5 0LCg==
X-Gm-Message-State: AOAM5311O1tT2OSCDNbRkBwkW4eRhlRp5SGN2ku8y/0bP97k+D+0QDiK PerMgkEIMnCAloNbT3OCzOlAjkMcQ99EUoI8XrU=
X-Google-Smtp-Source: ABdhPJz260qY9x7wXDaorUJ/b5oyNKBVMJjGuN7Id1gKBWE/YJRH1dYGC8xiCFSI13S1MwxGWZ/JNic4OKt7SMxH7KI=
X-Received: by 2002:a25:40cb:: with SMTP id n194mr48031215yba.380.1597160249267; Tue, 11 Aug 2020 08:37:29 -0700 (PDT)
MIME-Version: 1.0
References: <CAM4esxR4hXC5S8z_L9Ej+L=ZWsq1QF3=3_mLBx4AEoT2B3K9+Q@mail.gmail.com>
In-Reply-To: <CAM4esxR4hXC5S8z_L9Ej+L=ZWsq1QF3=3_mLBx4AEoT2B3K9+Q@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Tue, 11 Aug 2020 10:37:03 -0500
Message-ID: <CAKKJt-eGzNSbhnxktNJuQ7=nWtfbKLzc73WtKqEc0DTFEU16Fg@mail.gmail.com>
Subject: Re: [Tsv-art] Calling AD candidates
To: Martin Duke <martin.h.duke@gmail.com>
Cc: "tsv-area@ietf.org >> tsv-area@ietf.org" <tsv-area@ietf.org>, tsv-chairs@ietf.org, tsv-art@ietf.org
Content-Type: multipart/alternative; boundary="0000000000004e9f2805ac9bd99f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsv-area/kesl68lq5RgjSGe9ZXA7hK5H5-0>
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Transport and Services Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsv-area/>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Aug 2020 15:37:33 -0000

Hi, Martin,

Top-posting - I'd add two more items under "what's great about being an
AD", which would be

   - watching new working groups become productive and new chairs learn
   their roles successfully, and
   - I was told that past ADs have a lifetime invitation to the transport
   chairs/TSVART dinners - again, when we meet again :-)

But this is a great summary!

Best,

Spencer

On Thu, Aug 6, 2020 at 6:35 PM Martin Duke <martin.h.duke@gmail.com> wrote:

> As so often happens, Transport AD candidates are thin on the ground. I'll
> share some thoughts as someone who stepped into the role role with very
> little idea of IETF beyond the 2 or 3 working groups I was active in at the
> time.
>
> *TL;DR* being an AD is a professionally enriching and socially
> rewarding experience. It takes time but it usually doesn't hurt to ask your
> employer for that time. The procedural stuff is not hard at all. The most
> challenging thing is getting up to speed on unfamiliar subjects, which also
> probably has the biggest benefits.
>
> Others can judge if I've been successful, but at no point have I been
> overwhelmed or left without great advice and exceptional documentation on
> how to do things.
>
> Nominations happen here:
> https://datatracker.ietf.org/nomcom/2020/nominate/.
>
> *What's great about being an AD*:
> - Having an important say in shaping the area and the IETF as a whole,
> particularly by chartering groups and participating in IESG initiatives
> that interest you
> - Everyone has their examples of nonsense at the IETF but ADs are in a
> position to do something about it.
> - Working with some great WG chairs, and building our TSV community
> - Learning much more about what's going on in other areas, to become a
> more complete internet professional
> - There's a lot of freedom to focus on what you find most interesting
> - Meeting people from every corner of IETF - unfortunately I haven't
> gotten the full in-person version of this, but it remains true.
>
> *Time commitment*: This the biggest reason not to pursue the position.
> Like many things it depends on what you want to put into it, but it's not
> like a chair position that can be done in the margins of your day job.. I
> would definitely arrange with your employer to lose no less than 1/4, and
> probably half, of your current responsibilities.
>
> This is a huge mental obstacle for many people, but if your boss can be
> persuaded of the advantages for your organization, and that it will help
> you be a satisfied employee, you may be able to jettison the less appealing
> bits of your current work. That's how it turned out for me.
>
> *What's the work*? There's an official job description here:
> https://trac.ietf.org/trac/iesg/wiki/TransportExpertise
>
>  In roughly declining order of time commitment:
>
> 1. IESG review: you should review a healthy majority of documents that
> pass IETF Last Call. This can take a long time if you provide detailed
> reviews of everything, or not as much if you focus on the transport aspects
> of documents that have transport implications and lean on the area review
> team to do their usual good job.
>
> 2. Weekly meetings: No more than 3 hours unless you volunteer for more.
> Obviously, ramps up around IETF week.
>
> 3. AD Review: you really should take a close look at the document output
> of your WGLCs.
>
> 4. WG management: Chairs don't need to be micromanaged, but they'll
> sometimes ask your opinion.. You're also deeply involved in chartering,
> finding chairs, and BOFs in your area but these are not terribly frequent
> events.
>
> 5. IESG projects. This is purely optional, but you can take on a special
> project. For example, I was deeply involved in figuring out the remote
> meeting plan, and, well, you saw the result.
>
> 6. Miscellaneous: you will get random email about RFC errata, etc, and
> have to deal with it. It's not a huge time sink.
>
> I hope some of you will overcome the concern that you're "not ready" for
> this position, and/or the hesitation to ask your employer to explore an
> interesting opportunity.
>
> I happy to discuss further with interested people, either via email or
> using the chat or meeting technology of your choice.
>
> Thanks
> Martin
> _______________________________________________
> Tsv-art mailing list
> Tsv-art@ietf.org
> https://www.ietf.org/mailman/listinfo/tsv-art
>