Re: BCP97bis

"Murray S. Kucherawy" <superuser@gmail.com> Mon, 18 October 2021 14:40 UTC

Return-Path: <superuser@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 8FA3A3A14AC for <ietf@ietfa.amsl.com>; Mon, 18 Oct 2021 07:40:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 PO4xSFK-qV9s for <ietf@ietfa.amsl.com>; Mon, 18 Oct 2021 07:40:14 -0700 (PDT)
Received: from mail-ua1-x92f.google.com (mail-ua1-x92f.google.com [IPv6:2607:f8b0:4864:20::92f]) (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 C56B63A1490 for <ietf@ietf.org>; Mon, 18 Oct 2021 07:40:14 -0700 (PDT)
Received: by mail-ua1-x92f.google.com with SMTP id r17so1736658uaf.8 for <ietf@ietf.org>; Mon, 18 Oct 2021 07:40:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=9BGL4N1OYYw+k85AWgoHPjH/AWq/F9YSCaUAK9QF/+c=; b=CRrcMPYB+q2HYOJVQ1Oou6c7kb50BlZ1WuqtM26ipqLp7dpPiced4/mfkXLPVxZbaO k2eE2KuJ7xDRqmims1Uvx7E7UnxYnplMdY3FQfFqFJ3Y8jb65XEw4dGhfxiEEsu+EehT xrz0B8322JjIYf8wcmHOtwdIL+Dy0ElIHj1tyPXV3ow4zPnBUB2XU7qkvDx5dhsDB/7X a5FxZOJXqEznwh1Ipda6G0xuHhQs+sOOChQC8cu9UvK2SMiexQAhB6oLEzakPWE+rySj 3i8/98LLQ0OhOzYhl9cGVvBuTGz6Y7RrFsmIjIA+AWfBma2yEAp5PoFdC8QUD+Cl5x8n LBWA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=9BGL4N1OYYw+k85AWgoHPjH/AWq/F9YSCaUAK9QF/+c=; b=qWe5V3Bil7bjHlr8ELr1J2OIGfDO/+b21O5zf39ALdWfy0cTB0btb74eSQyAEEW41R pi1dM7MaH+sfpicObaAMTAFKjtALQKfVQ+YZjND4IhfMZCIGtL+PXT/0y1GrLOAgLEHU 4wJpzqfHS3uOxHuJgYHz5F8G6v7dWb6syDODectInYXXUe0g+9+/HlxuZRWaqDl0G7ua IvVYBXGv/HiJeN8yDWV3kwnZS/gOjolFTNKIe+h0p11K5TSmkD10tP3X09/azGWyPNxZ 4Or+sy0YwixaZ1+6JUhIbXJoefjo4yROZAtPKuxWfpFiDt5CnSuv5v/d5V0/xN2FZ9hQ 5p+Q==
X-Gm-Message-State: AOAM533P8IQMev+5Y4LOx/WJe49+smEccboyAYT/eibEs6Cc/V2sbyk7 1nju4hOBYEcCuVUC1+Ec+GGcZQnMhWbAq1HAqqg=
X-Google-Smtp-Source: ABdhPJzLQnoTMIJVAvFZYxDQ1ISXeQimQKGz5cDocqEeoIkLW79eDW7wRk1gOX4j0K1hHGsvDe/eRwOSgmdA5vEv9QU=
X-Received: by 2002:a67:d38e:: with SMTP id b14mr28036325vsj.13.1634568011048; Mon, 18 Oct 2021 07:40:11 -0700 (PDT)
MIME-Version: 1.0
References: <CAL0qLwbwvs2Cp_urgJ=hzc6yEMGDaz3C0xf6RQXRrB89wAx=Rw@mail.gmail.com> <CAL0qLwavK5dYdmYPVxdMT5rA=jBZv1cEyAsVBEWOD7p9MoZR1g@mail.gmail.com> <CAL0qLwa4ChOsuMkmoP_sAGv3Wn2AcSz1OkijmxZzP+MGvnwviA@mail.gmail.com> <849D7F9E-8AD4-4CE8-A66C-358FB1F2E6AE@tzi.org> <3AC61568-DBDC-4ADB-9935-9C53333AE7E2@akamai.com> <CAL0qLwZvCq7R=WBFsrwf51CKSN8ur0Yj-F=VOHnP=hQD0ooj-A@mail.gmail.com> <890A4965-D847-4606-849C-A0C8D8FD3B0C@akamai.com>
In-Reply-To: <890A4965-D847-4606-849C-A0C8D8FD3B0C@akamai.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Mon, 18 Oct 2021 07:39:59 -0700
Message-ID: <CAL0qLwZtBiuh5n3U_pKma1s4ymPOCy7CY0pFaaacx6NDYNu5AQ@mail.gmail.com>
Subject: Re: BCP97bis
To: "Salz, Rich" <rsalz@akamai.com>
Cc: Carsten Bormann <cabo@tzi.org>, ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a90e1c05cea185b9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/c-SAz7ewZLznZoopCR0KL_UMJYM>
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, 18 Oct 2021 14:40:27 -0000

On Mon, Oct 18, 2021 at 7:36 AM Salz, Rich <rsalz@akamai.com> wrote:

>
>    - The IESG has had multiple cases during my time there where we
>    haven't had access to some normative reference, and so we can't do our
>    job.  This has added long delays to document processing.  That's what we're
>    trying to address here.
>
>
>
> I believe it is far more common for the IESG to review and progress
> documents without having all normative references tracked down and read.
>

The role doesn't matter, does it?  As an Area Review Team member or even a
Working Group participant faced with a document with normative references
behind a paywall, you face the same problem.

Sure, you could make some assumptions that what's in the normative
reference is correct, or sane, or trustworthy, or whatever.  What if you're
wrong?  What if you want to be certain?

Shouldn't our processes err on the side of pushing for quality?

-MSK