IETF Logo Mail Archive

Re: [ietf-nomcom] Help with three errata against RFC8713

Lars Eggert <lars@eggert.org> Fri, 11 August 2023 11:22 UTC

Return-Path: <lars@eggert.org>
X-Original-To: ietf-nomcom@ietfa.amsl.com
Delivered-To: ietf-nomcom@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DC2AC15108D for <ietf-nomcom@ietfa.amsl.com>; Fri, 11 Aug 2023 04:22:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.108
X-Spam-Level:
X-Spam-Status: No, score=-7.108 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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=eggert.org
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 oHDIK6Ye33d2 for <ietf-nomcom@ietfa.amsl.com>; Fri, 11 Aug 2023 04:22:50 -0700 (PDT)
Received: from mail.eggert.org (mail.eggert.org [91.190.195.94]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 EF06FC15106A for <ietf-nomcom@ietf.org>; Fri, 11 Aug 2023 04:22:49 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by localhost (Mailerdaemon) with ESMTPSA id 6C88A80EFB; Fri, 11 Aug 2023 14:22:45 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eggert.org; s=dkim; t=1691752967; h=from:subject:date:message-id:to:cc:mime-version:content-type: in-reply-to:references; bh=ulnBgg5lQMS+ujOCAj2X5m3us2wBL33W8lA6I5iA6Uc=; b=uClnEYdtInJztxb/9JLwIwuTkarsnFZQTbJ0DurH0w283w1ZZXPG9v625cc4WHiGKkVV/v TskeoRnPgDL76q+TlsolRdzsdFH0oV8aYxbaZy+IrLhsAdwb3PPdnDTco/lLLXAp5U1/si HucQiCDd7mssqSh7FmqoOyxNAk/cSg+dJQLSIgMQ7HwHZR8XTTcjcBsFraHDdUTApb/01f feH1PGxGwTByt83R/wvBvV4ZJ/rgKdRQe9ajLvCabducJjfbBbal+EQmwq3y7PY0bKTBXx P5O7OE5w7MnQlIwBDr5uPg5a8GCFOLVmNYKoidq4suufIzXxZ9nEIZjAOT+LGQ==
Content-Type: multipart/signed; boundary="Apple-Mail=_E777F2B3-0E8E-4579-A251-316B95E7394E"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6\))
From: Lars Eggert <lars@eggert.org>
In-Reply-To: <5615F879-2141-43F5-B23F-CD930B25E49A@akamai.com>
Date: Fri, 11 Aug 2023 14:22:44 +0300
Cc: "ietf-nomcom@ietf.org" <ietf-nomcom@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, "Murray S. Kucherawy" <superuser@gmail.com>
Message-Id: <746C4EAB-709F-4135-AFED-24BDCD8DE03D@eggert.org>
References: <C8B9E859-A7EA-4419-B9EB-28FD0E7774B5@eggert.org> <5615F879-2141-43F5-B23F-CD930B25E49A@akamai.com>
To: "Salz, Rich" <rsalz@akamai.com>
X-Last-TLS-Session-Version: TLSv1.2
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-nomcom/R6GBDgR2ZxqnV0UmiAmJTCroJTA>
Subject: Re: [ietf-nomcom] Help with three errata against RFC8713
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-nomcom/>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Aug 2023 11:22:54 -0000

Hi,

On Aug 4, 2023, at 17:36, Salz, Rich <rsalz@akamai.com> wrote:
> Looking at https://www.rfc-editor.org/errata/rfc8713, I see seven.


thanks for the feedback. Based on it, and on my review of the proposed changes, I marked them all as "hold for document update", i.e., "The erratum is not a necessary update to the RFC. However, any future update of the document might consider it and determine whether it merits including in an update" per https://www.ietf.org/about/groups/iesg/statements/processing-errata-ietf-stream/

Thanks,
Lars

v2.23.0 | Report a Bug | By Email