Re: [Secdispatch] Leadership changes in SecDispatch

Eric Rescorla <ekr@rtfm.com> Fri, 28 October 2022 02:31 UTC

Return-Path: <ekr@rtfm.com>
X-Original-To: secdispatch@ietfa.amsl.com
Delivered-To: secdispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D88EEC15257A for <secdispatch@ietfa.amsl.com>; Thu, 27 Oct 2022 19:31:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.903
X-Spam-Level:
X-Spam-Status: No, score=-6.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20210112.gappssmtp.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r3-8k0rlLtTF for <secdispatch@ietfa.amsl.com>; Thu, 27 Oct 2022 19:31:53 -0700 (PDT)
Received: from mail-io1-xd34.google.com (mail-io1-xd34.google.com [IPv6:2607:f8b0:4864:20::d34]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0AC23C1522B2 for <secdispatch@ietf.org>; Thu, 27 Oct 2022 19:31:53 -0700 (PDT)
Received: by mail-io1-xd34.google.com with SMTP id y6so590707iof.9 for <secdispatch@ietf.org>; Thu, 27 Oct 2022 19:31:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20210112.gappssmtp.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=Oq46zTDVVB+fHeXv7g2R+WtF4r4fiU+F9vbRRw+CSmo=; b=bTkx+ZpMm3hr/F+1GVcUskBshz8KgwHWX5r/WEYHO2x6NlId+5fYsRzXIzSkY6jfcA QwuOH5bVovRbw9er7FV1UCHdo24q5aKOQkcFEprIb8vCYAxSeCBMCmnsGmXk6hJWOEBJ NUR/pl7Zs4ibIEiMPyHgPDafx4YO0AOMYVR+zEnL1Qz07Jvco9ZRB8c92EORETGJ1CLQ IZ0GYSkT7QE4lsQNIOOVFesHrQPbQdh/uh9Jh2DdISvOHTmtICqJBZ9MgrCJVqwooJ9M xENURAlvvasn4mKn+rHdBOwLd5gTd7htDQIpoiQTN6ZLF14s91DNWvgQVq23AsZds4OS CC/A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=Oq46zTDVVB+fHeXv7g2R+WtF4r4fiU+F9vbRRw+CSmo=; b=rpkph1wxsEcM2KhJolCpIaQkNSRjB7YCdT9scSbm24vtjMTMhug9pOWKlckNLIfQ6R YzjIAH1W0ZfLjfJatAK6aDHKRC0PVZK5TdnMBhK1D3Ex2t8+UTzcXXFmqSqYBX6Uguio dw0HB5o5M9LYnqJhb99ey7quoBdwGjM5I2fuOE74ZwWSDVALZ1+isRv7Vq9JDCYYQ4xq fVP/Y2N438S91uQYczPogHqOYyM/9lAG97kSCvuUsiYRS0h3RjiYHLDvfnLfWtm6zKKI TR1eYlevj9yU1mYlT/pSEDEwWrl0BvJgjgtGVQOeIUiBqD8VqHpaEEo3h//dRA0Ld+tR yIfg==
X-Gm-Message-State: ACrzQf3N6rJhmQPRTW0C/Zst10ejkiufq/Yug84ADuqE8/REaNdFnuoF 7yVguOteW2CSgVPfnCbmSRcCdD+v1bz5zdrwjhNSg8uoUu4=
X-Google-Smtp-Source: AMsMyM7AWSojCpcrKrj5FVVSCajZZGONk8U3WR41uGszsOB4Kq/TPTKre2oToMbMuThphynO6aG6EqPoHi6EXeYorvk=
X-Received: by 2002:a02:7a46:0:b0:363:b724:1b29 with SMTP id z6-20020a027a46000000b00363b7241b29mr34898646jad.165.1666924312266; Thu, 27 Oct 2022 19:31:52 -0700 (PDT)
MIME-Version: 1.0
References: <BN2P110MB11074F2446B21A40ECDBC6F5DC339@BN2P110MB1107.NAMP110.PROD.OUTLOOK.COM>
In-Reply-To: <BN2P110MB11074F2446B21A40ECDBC6F5DC339@BN2P110MB1107.NAMP110.PROD.OUTLOOK.COM>
From: Eric Rescorla <ekr@rtfm.com>
Date: Thu, 27 Oct 2022 19:31:16 -0700
Message-ID: <CABcZeBNe5Qw+4WUJ8Qoj2Wi9MH-Z0eY5jUbtWTnEEMiX_=zBhg@mail.gmail.com>
To: Roman Danyliw <rdd@cert.org>
Cc: "secdispatch@ietf.org" <secdispatch@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000801dde05ec0f0fa5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdispatch/s-Bxv8cdM9LS8TnzR2hNkYWxlbk>
Subject: Re: [Secdispatch] Leadership changes in SecDispatch
X-BeenThere: secdispatch@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Security Dispatch <secdispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdispatch/>
List-Post: <mailto:secdispatch@ietf.org>
List-Help: <mailto:secdispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Oct 2022 02:31:53 -0000

This seems like a good plan in a number of ways. Thanks for putting such an
orderly system in place.

-Ekr


On Thu, Oct 27, 2022 at 10:39 AM Roman Danyliw <rdd@cert.org> wrote:

> Hi!
>
> SecDispatch has become an integral part of how new work is considered in
> the SEC area.  An integral component to the success of this WG has been the
> commendable leadership the chairs have provided to the group.
>
> A key part of that leadership team has been Mohit.  In a belated official
> announcement, Mohit has had to step back from the co-chair role due to the
> commitments of his new, day-job role
>
> Moving forward and considering that we are now almost five years after the
> WG launch, Paul and I believe that for the continued health of the WG an
> additional process refinement is necessary.  Specifically, how to handle
> SecDispatch leadership (co-chairs) service give that this is a standing
> WG.  With no positive action, WG chair service would be indefinite.  The
> only transparent and resilient-to-AD-turnover way we can think to handle
> this situation is to set in motion rough, preset term length.  We've landed
> on a service term for up 4 years to balance experience in the role and
> injecting new leadership into the team.  Of course, circumstance might
> prevent a chair from spending that much time in the role; or something
> might arise that would make the tenure a bit longer.  We've also decided to
> slim the team down to two chairs.
>
> After coordination with the sitting chairs who endorsed this approach, we
> will implement this process starting at IETF 115.  Bootstrapping into it
> this will look roughly as follows:
>
> ** Prior to the IETF 115 meeting, an additional SecDispatch co-chair will
> be named
> ** After the IETF 115, Richard will step down from the co-chair role
> ** At the IETF 117 meeting, an additional SecDispatch co-chair will be
> named
> ** After the IETF 117 meeting, Kathleen will step down from the co-chair
> role
> ** .. repeat ..
>
> There are many thanks to express in implementing this process.
>
> WG: It is our pleasure to announce that Rifaat Shekh-Yusef will be
> stepping into the role of the co-chair.  Rifaat: Thank you for your
> willingness to serve.
>
> Mohit: thank you so much for your service and being a steady hand in the
> dispatch process.  Congratulations on your new job.  We're excited for the
> opportunity this brings but sad that this means we'll benefit less from
> your counsel.
>
> Richard: the WG has benefitted from your leadership since we launched this
> new, at the time, experimental way, to consider new work.  It's now
> foundational to our operation.  Thanks for getting us there, and for your
> service!
>
> Kathleen and Richard: we're asking you to step down out of visible
> leadership positions despite doing commendable work.  Thank you!
>
> Regards,
> Roman and Paul
>
> _______________________________________________
> Secdispatch mailing list
> Secdispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/secdispatch
>