[Tsv-art] Nomcom candidates (including Transport AD)

Martin Duke <martin.h.duke@gmail.com> Tue, 01 June 2021 20:55 UTC

Return-Path: <martin.h.duke@gmail.com>
X-Original-To: tsv-art@ietfa.amsl.com
Delivered-To: tsv-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BA2C3A2723; Tue, 1 Jun 2021 13:55:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, RCVD_IN_DNSWL_BLOCKED=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 pJ2RPpaI6klo; Tue, 1 Jun 2021 13:55:38 -0700 (PDT)
Received: from mail-io1-xd2c.google.com (mail-io1-xd2c.google.com [IPv6:2607:f8b0:4864:20::d2c]) (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 EDF773A271E; Tue, 1 Jun 2021 13:55:37 -0700 (PDT)
Received: by mail-io1-xd2c.google.com with SMTP id r4so166635iol.6; Tue, 01 Jun 2021 13:55:37 -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=Yr2ttWKtGkyjJ7Qq1as6q3aPj7WD4a/PViKPKXcGZN4=; b=bjNGSJjHb3GofYv1qNIh/dRceKHQi9w6m4Uh4HAz4viFHN2DObXXKxBihrOEFgtkIY uMgi5+75bRkzPey2BIBfDnjmD08Wj8OrGZhH29hG0QoUYg3MPuqHKw7iTRneXiBLDrzl aJPPNGW74GQjWmScUgKqIoQtFH89Ktq9kzlBRlzgqD5TnkU81P3xFQ0u46nFG10p9GYG 9IH9zVQSc23OVXprV6xfmwH0YjBybG3Jzy2v4hYKpvFiRvH4AwoZ42r3gPHjJqIiyQFk GXDw6ZhfUlaOgR/6qLZTSqWr117kwj2VqfbbShOit83TrWVzh4VytD3CcUEoRkWKNCVY GTcw==
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=Yr2ttWKtGkyjJ7Qq1as6q3aPj7WD4a/PViKPKXcGZN4=; b=KzMeouWCl2hDDoL+wKoVpXiZrFKadvGYZTWnKzB6OCwUAIX/Xt3KntIf6KLXHPAaNJ XtTBXDRHSW9821EGNNg7kbhVG9G3BR0MN90bbkF/6dHmYlbCLaSStcTq/VQV72KB9iwT NNJilXxE/ff0zHys6WVPUyybGCMb+prUXhJ256dOPkYjDOqLsNWZclgyixAsRKKcwteA yZLIyo8wwFNKbebIhE+akaH8k3LDo6guQtAMToGFKmNb02wcuBUhwcqazNW5noTW8lo9 Ld3zlqD/Xv1aSyunR709geGi+wDzl3XcATku5tgfcoqpxJrEfh5tKfXrELOwr8iZ2EOK 1oPg==
X-Gm-Message-State: AOAM532W2yBrB+Njko6CqAcodYZ/tQ3082+23m2TNCvG4GT/9iK8mwbD 9DaBT/uWJyLXVrfnd1I2hXk6Ivu4U5WKJ/AQGJ9zqOvRIUE=
X-Google-Smtp-Source: ABdhPJzmfQwvZ6+ekvza9h9mxGySJkES6R/YzeseVsZAZ4Goj6ulWI9sjtVsNOaQcI/TxKXrVvBpuELYrmkXjGU/Q4E=
X-Received: by 2002:a02:cf32:: with SMTP id s18mr26633515jar.31.1622580936055; Tue, 01 Jun 2021 13:55:36 -0700 (PDT)
MIME-Version: 1.0
From: Martin Duke <martin.h.duke@gmail.com>
Date: Tue, 1 Jun 2021 13:55:25 -0700
Message-ID: <CAM4esxRQ6PgcN3149hh-WCpCd_e+iEE6sKc5vYspZyiCL2v6MQ@mail.gmail.com>
To: tsv-area@ietf.org, tsv-chairs@ietf.org, tsv-art@ietf.org
Content-Type: multipart/alternative; boundary="000000000000501fd805c3ba90b3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsv-art/6TdOCWBNkk9H7NjAOza2jSfhGh4>
Subject: [Tsv-art] Nomcom candidates (including Transport AD)
X-BeenThere: tsv-art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Transport Area Review Team <tsv-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-art>, <mailto:tsv-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsv-art/>
List-Post: <mailto:tsv-art@ietf.org>
List-Help: <mailto:tsv-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-art>, <mailto:tsv-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Jun 2021 20:55:41 -0000

Hello Transport Area,

NomCom is currently accepting nominations for various 2022 leadership
positions, including my seat as AD. I am standing for another term.
However, it is always good for the IETF to have alternatives to the
incumbent AD, so please consider nominating other promising candidates
<https://datatracker.ietf.org/nomcom/2021/nominate/>, and accepting the
nomination if you receive one.

Standing for the position is not much work -- you fill out a questionnaire
and do a pretty-low pressure interview around IETF 112.

For the benefit of those who are considering going for AD of Transport or
any other area, here is the informal pitch I gave last year.

Thanks,
Martin

*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.

*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 is 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 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'm happy to discuss further with interested people, either via email or
using the chat or meeting technology of your choice. For a less conflicted
experience, I'm sure Zahed would be equally willing to share his thoughts.