Re: Updated IESG Statement "IESG Processing of RFC Errata for the IETF Stream"

Stewart Bryant <stewart.bryant@gmail.com> Tue, 11 May 2021 09:54 UTC

Return-Path: <stewart.bryant@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6430F3A0C33; Tue, 11 May 2021 02:54:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-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 FjKIBFQrNZ6R; Tue, 11 May 2021 02:53:59 -0700 (PDT)
Received: from mail-wr1-x42a.google.com (mail-wr1-x42a.google.com [IPv6:2a00:1450:4864:20::42a]) (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 C309C3A0C2A; Tue, 11 May 2021 02:53:58 -0700 (PDT)
Received: by mail-wr1-x42a.google.com with SMTP id l2so19466893wrm.9; Tue, 11 May 2021 02:53:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=E+sNY9RarMaHko8kG+8cOGQlQ5XA35Nf0DR2dbY3xhw=; b=JrOSBkcKpFgjMxE6yrjgnavieO6NsMVb0VUX2rKTgEVU2v31w+7EBqH++gS+qAMiYK qjcf4WQDYDAql1GAUP8o2dr/Tqm3TIYG1ldlRv28jRBzYHJRJdcC/7/t8dMR+MUi/iwp koPNfXKDqgk/UUALYteMb8WzSqnu4oXbPktvf8B6NDAs/0mB+p5OzPnZg0UnaDkfOHZo ukRaTbeybQmXw+E6GmT35DOFYTeRmOm5QsUFUdhHc3+79QjeXo1a1xCaHjPcb0eHyyvK rDRq/xsIbpkaZLRvpFUvtJv6i0JDq2DMwZGeOpisYCoTgJ3jLpDzexPEqsvRxKkm2y7s GkPg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=E+sNY9RarMaHko8kG+8cOGQlQ5XA35Nf0DR2dbY3xhw=; b=AXKu7dYV6Z77DeEu45JpH64vit4T0xEgyRVYko1/9WFY27N91bhKLAywawSHC4rCtb ghgKYjdK1czUPhvieyjy3FHhF9705kmVRDEId2oKEMsocO/1hUxCzgm5X4alAEiTgWMq Ft56VLL4jPdgIP7fVMHBldend4xAR+nz6M2eWEQIQLfGrnuMyTcc1Ck9hTWA7YiZytUb VwRYGgY8JL2JQkOfiaraI3oqpeiGwBocE85onLTlpIr6QXHkIZaz+SSnsJQOvP1yFFp1 dxvfEnFI4lKqlvMzK4EO9Xg3DHbfn1gDHYr+Q/IS4C7bZIvCuO9owXkmatLZb9cbcZ7Y q6Mg==
X-Gm-Message-State: AOAM530oILAdV3N7SeyhCtpzTzOGdQNnPrk/GOF/cxepVwlArsLI6B3+ F+3x5evziaTqCy4IFDxjwkA=
X-Google-Smtp-Source: ABdhPJyRkjkFHi+bBsHCRRIb/QfWKXpSrBkBYbZ9UyixrqcjFzD4MwtPcfQvxNQemxyuPwHcidRAEA==
X-Received: by 2002:a5d:5989:: with SMTP id n9mr36387920wri.60.1620726835495; Tue, 11 May 2021 02:53:55 -0700 (PDT)
Received: from [192.168.8.128] ([85.255.232.235]) by smtp.gmail.com with ESMTPSA id t11sm1731892wrz.57.2021.05.11.02.53.54 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 11 May 2021 02:53:55 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.6\))
Subject: Re: Updated IESG Statement "IESG Processing of RFC Errata for the IETF Stream"
From: Stewart Bryant <stewart.bryant@gmail.com>
In-Reply-To: <CAMMESswD=uTEY0P2BhySfAXORboJFiSUfT8mBd=iY-jStcpzEQ@mail.gmail.com>
Date: Tue, 11 May 2021 10:53:54 +0100
Cc: Stewart Bryant <stewart.bryant@gmail.com>, IESG <iesg@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, IETF <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <99746010-7D95-45D0-A77C-F0AA64D1D533@gmail.com>
References: <162040549861.22240.16336069769197991691@ietfa.amsl.com> <18d87dd8-3363-ef49-36f6-a34ff8c60e59@gmail.com> <63FC3945-4207-4CA9-8B25-38ACD4A51BCF@gmail.com> <CAMMESswD=uTEY0P2BhySfAXORboJFiSUfT8mBd=iY-jStcpzEQ@mail.gmail.com>
To: Alvaro Retana <aretana.ietf@gmail.com>
X-Mailer: Apple Mail (2.3608.120.23.2.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/zX7YB1yQW2cpiJr1Hs813uxepbE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 May 2021 09:54:03 -0000


> On 10 May 2021, at 20:22, Alvaro Retana <aretana.ietf@gmail.com> wrote:
> 
> On May 8, 2021 at 6:53:46 PM, Bob Hinden wrote:
> 
> 
> Bob:
> 
> Hi!
> 
> ...
>> I think something is needed where the reported problem can be accepted, but
>> the fix can be rejected. Perhaps some new states, or a change to how the
>> Errata system works.
> 
> You're right, *without proper explanation*, there is no explicit state
> that indicates a valid problem and an invalid solution.  Hold for
> Document Update is the closest as further discussion is obviously
> needed.
> 
> However, even with a proper explanation, it may still be confusing
> whether the proposed solution is valid or not.  One of the issues is
> that there is a single notes field that is used by both the submitter
> and the verifier.  Also, these notes appear *after* the
> problem/solution have been described, making it harder to find
> relevant comments.
> 
> Changing how the errata system works requires a wider discussion of
> course -- beyond what the current statement is intended for.
> 
> Thanks!
> 
> Alvaro.
> 

The AD can edit the text and provide a solution that works.

If there is a problem but no solution that would be quite worrying.

- Stewart