Re: [Eligibility-discuss] NomCom selection Fwd: Notification for draft-eastlake-rfc3797bis-00.txt

Eric Rescorla <ekr@rtfm.com> Mon, 22 May 2023 14:44 UTC

Return-Path: <ekr@rtfm.com>
X-Original-To: eligibility-discuss@ietfa.amsl.com
Delivered-To: eligibility-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B439EC151072 for <eligibility-discuss@ietfa.amsl.com>; Mon, 22 May 2023 07:44:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.896
X-Spam-Level:
X-Spam-Status: No, score=-6.896 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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20221208.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 yFNKuBKuQNpB for <eligibility-discuss@ietfa.amsl.com>; Mon, 22 May 2023 07:44:08 -0700 (PDT)
Received: from mail-yb1-xb35.google.com (mail-yb1-xb35.google.com [IPv6:2607:f8b0:4864:20::b35]) (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 363F4C14CE51 for <eligibility-discuss@ietf.org>; Mon, 22 May 2023 07:44:08 -0700 (PDT)
Received: by mail-yb1-xb35.google.com with SMTP id 3f1490d57ef6-b9e27684b53so5375547276.0 for <eligibility-discuss@ietf.org>; Mon, 22 May 2023 07:44:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20221208.gappssmtp.com; s=20221208; t=1684766647; x=1687358647; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=pJnixfQ6ayJBvrAGa6GzySzX++R3ftOOpPA14yiBWWg=; b=F22xu6Ux1Ak0xRnRkr/SO7wWQ0JXxPGMfGWNi850gcbzUr3z9g+k+J/RSfS/I3U3Va whunbNhGMNQPI9hbyMr0v5gJB8LqLqf2AmpftDYi8PLAJ0NdO1T8VMpGoRjvcEpV8U3q hzhMqANDwpJnkUw+G0uNcbmMXo3OT6La6Ukhsk6hkfjzHGftvEa3g25MxpcwBo1Bw7Y9 HLvmKjj8lcD2ujqf39XV5S5xb+pHPKbrjh0SqpHELrGdweanLqGqNVJ1aP+nOjXG0IrV wRfPhZCD0pbZngih6A6dWHUx6RYrdbrhPu9qKvRGVvZ8h06i/EOQb54FpLBEV1Euw9iz omig==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684766647; x=1687358647; 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=pJnixfQ6ayJBvrAGa6GzySzX++R3ftOOpPA14yiBWWg=; b=iXzBiF4NPkfT00WCK1wdkTlGq/Yq8f/cWxBaPfyvdNyUS1xvRwvBk1H87eQxNxoz7B WhANpnnmDdr3CEV6wYIAwehnXI6XoD7H6pVPH733DDQdr++h7rT0Yb63tRgoBsf3t4Mv KxStC89wwYHdRQquxw/avckWj1nlg1jy0nXux0VIRReMFX8ABmbU0MizJREpl1NuYN7x jVmJ+gFLb8UCLwNrAcKZY7RMaJ3bwDVyEGmwdfdw/dR6tUBPxK/PVAyqUwihjN8i8s+i h8MsxKvUOg/tX5YPY6sBQ+FQ8y54H7WRrOB+3Xg/e40DEXAvwc4ZzccW/JCFygGdxUXg Cwgg==
X-Gm-Message-State: AC+VfDxh6JNVz1NPPDnXlzYocCCvZTXmQ62ElbpSMlswisuTPFSOM19v q1MeNm0LlseRG2IMugfRZ+o/dxC2o4PJ8RNzga+iiQ==
X-Google-Smtp-Source: ACHHUZ5EV4xP4HGjpzeexQmwrBTrBrN3BYW0i6/32cm/hTHqNsLpaNv9CU2JU6Kha2QHuTlrlANln6GOpBUR8D/SUDQ=
X-Received: by 2002:a0d:c844:0:b0:565:207a:9ad2 with SMTP id k65-20020a0dc844000000b00565207a9ad2mr1325501ywd.5.1684766646872; Mon, 22 May 2023 07:44:06 -0700 (PDT)
MIME-Version: 1.0
References: <54F373CD-1E97-42BC-9AAB-0451ABD9D448@eggert.org> <889212B2-B102-4F37-96F5-63EC994EFA04@akamai.com> <CABcZeBOXbp7vmA1JsNx53c=X1d5n2Oqt-5nFWoqLkc0dJR+9rQ@mail.gmail.com> <B14D1209-66EC-47A9-9C15-2755FD7BD780@akamai.com>
In-Reply-To: <B14D1209-66EC-47A9-9C15-2755FD7BD780@akamai.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Mon, 22 May 2023 07:43:30 -0700
Message-ID: <CABcZeBOH2VkTuzLHWxDNKW5ntr9xxhwoHthx1MrBnw+s9ctaLQ@mail.gmail.com>
To: "Salz, Rich" <rsalz@akamai.com>
Cc: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>, Lars Eggert <lars@eggert.org>, "eligibility-discuss@ietf.org" <eligibility-discuss@ietf.org>, Donald Eastlake <d3e3e3@gmail.com>
Content-Type: multipart/alternative; boundary="00000000000084417905fc494d05"
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/-d_tsIbrMhjTMEUu_Ls5ZXZ5CWY>
Subject: Re: [Eligibility-discuss] NomCom selection Fwd: Notification for draft-eastlake-rfc3797bis-00.txt
X-BeenThere: eligibility-discuss@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF eligibility procedures <eligibility-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eligibility-discuss>, <mailto:eligibility-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/eligibility-discuss/>
List-Post: <mailto:eligibility-discuss@ietf.org>
List-Help: <mailto:eligibility-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eligibility-discuss>, <mailto:eligibility-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 May 2023 14:44:08 -0000

On Mon, May 22, 2023 at 6:59 AM Salz, Rich <rsalz@akamai.com> wrote:

> I'm not sure that this is in fact the consensus of those who have been
>
> in nomcom. For instance, I've been liaison twice, and I don't agree.
>
>
>
> That is a good point.  I’m not aware that any full NomCom has ever been
> asked that.
>
>
>
> Perhaps you mean "those who have been nomcom chair", but I'm not sure
>
> that that's really the relevant constituency for this decision, which,
> after all,
>
> is about community legitimacy, rather than minimizing work for the chair.
>
>
>
> Sure, it should be the community consensus
>

Yes, there should be community consensus on the procedure, but I'm saying
something
different, which is that the purpose of the exercise is to have communify
confidence in the
selection process.


.  But I do take exception to your ending phrase. I never once said “this
> is easier for me.”  The only issue I ever raised was the time it would
> take, and the impact on the schedule. In fact, I was quite diligent about
> performing all the steps should I have come
>
to that.
>

Fair enough, I apologize.

-Ekr