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

Alvaro Retana <aretana.ietf@gmail.com> Mon, 10 May 2021 19:22 UTC

Return-Path: <aretana.ietf@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 3F4C23A2820; Mon, 10 May 2021 12:22:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, UNPARSEABLE_RELAY=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 GJToway7oaKR; Mon, 10 May 2021 12:22:07 -0700 (PDT)
Received: from mail-ed1-x534.google.com (mail-ed1-x534.google.com [IPv6:2a00:1450:4864:20::534]) (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 C9C963A281F; Mon, 10 May 2021 12:22:06 -0700 (PDT)
Received: by mail-ed1-x534.google.com with SMTP id r11so5188249edt.13; Mon, 10 May 2021 12:22:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc:content-transfer-encoding; bh=khJHU0N7cXIYPmwsdzoLQ7ualMD1YJsB3BJhs3LfUfo=; b=f6xa23kxCPaC1Zw9VfjNf6FZLVtUdMNFJ49L6Flfc+Q9uGnSOkKZ0qM1bZeHji2YyK g1Y6mNJxH3zE0RymPRmc9THSyou84RTWtkLudJpxRUAl4FLGZNGF9Mo8ylzqnjAapY9W OlLY7eCrVunKZb/qLTctdIbU2XdcqofEKv2n2/GmZBt9ICdqsThXh4AdrDeFX4ZH13ju pNdFomIIRYrkR5hAMj/mTELUl/hBJ+PVQ9+hN9p9jh/BW2UdeiZhL/2SMBtNZORxrLkL +xNYHRzwO9ytCeK3I9ggPY9ZXRLrY9C0Bue2PJ4tTPV/UZa9Ir+nU7eE+jF7oLTP8s+V 6GDw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc:content-transfer-encoding; bh=khJHU0N7cXIYPmwsdzoLQ7ualMD1YJsB3BJhs3LfUfo=; b=ZExkxDmKR30SY1MXg38xI/OJd3/fDffarOGZojPOv9bilvp123oUbQ9d7IcTnK+UTb J2/9dAVNCmOoDqPhgSoe3RwlOusTtd2o0/cIKezit7FTyXPyXGi6zGAO9gCISigFbbyu 2mbqKgnydJiy0FuDbsBsW8vsdb/7AvXrhCcWwDUjgM3DVfR/iaPEj76xvHvxeAnRCW/A BicUUtoBT9KOiZZ19RP3UXaIEIwHs14X8DCvTV7mFAaShEKNZ4yREHC8onM+KRsfbiJy e+jG5cV0zMEuabRUs70WkoYhxUZnyE8wRPWSSeW3b7SLc9DZoAFGTt8dbvPRhOqWinp2 RFjg==
X-Gm-Message-State: AOAM532ZxBjKvZLc7EEloP9prAvc5+yrzeO3WuCtHK1Y71s2gsFcjBNJ fQiwhHdw2GxTcpx7jEi6z2HAL76I5/dXqXDs4xl3AjrG
X-Google-Smtp-Source: ABdhPJzlrgUYeWllgifZUhtN8rYo0eM6nBC8rCdY9IqG9xST89vddP8ROhVv5oAgPbJij2374+4b6WbflGXsoriH1VY=
X-Received: by 2002:a05:6402:31a7:: with SMTP id dj7mr31058469edb.314.1620674524117; Mon, 10 May 2021 12:22:04 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Mon, 10 May 2021 15:22:03 -0400
From: Alvaro Retana <aretana.ietf@gmail.com>
In-Reply-To: <63FC3945-4207-4CA9-8B25-38ACD4A51BCF@gmail.com>
References: <162040549861.22240.16336069769197991691@ietfa.amsl.com> <18d87dd8-3363-ef49-36f6-a34ff8c60e59@gmail.com> <63FC3945-4207-4CA9-8B25-38ACD4A51BCF@gmail.com>
MIME-Version: 1.0
Date: Mon, 10 May 2021 15:22:03 -0400
Message-ID: <CAMMESswD=uTEY0P2BhySfAXORboJFiSUfT8mBd=iY-jStcpzEQ@mail.gmail.com>
Subject: Re: Updated IESG Statement "IESG Processing of RFC Errata for the IETF Stream"
To: IESG <iesg@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
Cc: IETF <ietf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/EcaZ4vO1f9cF56j-ha_CCfJuETA>
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: Mon, 10 May 2021 19:22:08 -0000

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.