IETF Logo Mail Archive

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

Julian Reschke <julian.reschke@gmx.de> Tue, 11 May 2021 07:41 UTC

Return-Path: <julian.reschke@gmx.de>
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 171703A1548 for <ietf@ietfa.amsl.com>; Tue, 11 May 2021 00:41:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.net
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 b_6FbfhHJ1kH for <ietf@ietfa.amsl.com>; Tue, 11 May 2021 00:41:51 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B968A3A1547 for <ietf@ietf.org>; Tue, 11 May 2021 00:41:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1620718908; bh=JsckiUHG/doBK4VWYyfvY722E47mUow2H6NriX+2i+A=; h=X-UI-Sender-Class:Subject:To:References:From:Date:In-Reply-To; b=HFa4ey/qJcJPo3dNic9HnQ/67yy9L2+o++7IF3Sir4hAOFe633pQ5GOUqQaNwvu40 fLh4wCP4GazShSy+av9ScDiWUkszDl2shptRVlVgS5QW1M5sfCoxbi3ilZoWSpwjzh jUyBMxy2luLMWvTy6HM6nUSQ3gNxaiN7noJww5Do=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.178.20] ([84.171.150.36]) by mail.gmx.net (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1N7iCW-1lSmL80Pty-014i5k for <ietf@ietf.org>; Tue, 11 May 2021 09:41:48 +0200
Subject: Re: Updated IESG Statement "IESG Processing of RFC Errata for the IETF Stream"
To: ietf@ietf.org
References: <CAKKJt-e-z+pSAtzmtMrQj4fSDQ1yXE7uYxqypFJdyVnzorvvzw@mail.gmail.com> <B052B117-4A4E-49E6-AF66-E8EB7147988A@yahoo.co.uk>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <cfa51e4d-95e7-1b54-b70f-132ff1ce9e8c@gmx.de>
Date: Tue, 11 May 2021 09:41:47 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.1
MIME-Version: 1.0
In-Reply-To: <B052B117-4A4E-49E6-AF66-E8EB7147988A@yahoo.co.uk>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:h5SKFzTFKHg60KX8mIV7r6ZB5t/6/0ycTlMlJLgnBv+BJcrMHZu iUTCc/AiHOKzQsxfUmdvHWMbDDsnNT6JmH0u4rh1SWMpQ4IgaFHzI6XvGa1inHFyHqLIdcL xKZOeoFzrlwIH/c/CJQ8RegZRN51W9fkbTWyqsHPscumaqsL+1Oj4zdutCpXBRwwAmy7NeB Uz/YkFUYAY+OHpIS/2/OA==
X-UI-Out-Filterresults: notjunk:1;V03:K0:VTZJvjea+n8=:RHV5CdKWb+VHeLVvdmW5GP e+5uCiJ0ZqGi0iAU/1gdv7Q6lHODKjg+Rsa42yzXAoZZqgMh7Ar1/jtg017n3e+MA0u6pjson tFYsGEU1nrggwk6mIqire2fm5ZnkJ3YNelnPT1NAl8fAFCYhnS2CNbIgTCF2Nu3u49o0NEJmN 6Fq3gjxbO/zZVSQf6psXgUVLLdXBUF8DLizbUE2eUSzH0bDUJVZMU4MZFiUC/8MiwclO7sA3E 8VpJLpw0yqbzwPj2JgDBA38lHeKcTBtq1lkV1VpQVrlAk3s/7Re/1kalEvekxMFyhMI/9wcYE mbQArPnoTNy7RgD167ARk7ysSMRk7AMxDYBJdtK3uoCGHXgGcRo4zU0rQ4t58QExXZ8A+jD3M 1mUh8O+/WAPL5itdKWYdjq6vWNtIJ6jZNrwMoGZu7Iee83CEtMzWEok1GH3ef3hxxQLxo0YeE Pnm7QXBI5HEidiR61P3lihmm+0TalN2v+WnEdQxtV2ZEEPHzhXb1idEJEBHEQTvm0zG+EX18d gBCSjfDsN49HxLSBD61Aawz2iH8cz5nmZDsNfQ2+DiqRsN8rA9eBY0qzR4NO3RqWAiwNEQi8w oaHLZbnve6hib7YffftJMa5F1tB0TSRtRGmfEcRFfqI0Y2m65aeYRjkK2CbtOBjGrA/nCeNri UWn727KYwYfJxHrwJBq7EFDvjd9HS39xrubh2Narg5ZCKDgaW2GMBVuEsG6F8XqUZPBe+61K+ fnLPm9C8mszjnnMWCpsre2Nedinial0wPCMBBeSL1M/gYfIMVvc//5KZ1gHZ324KnUskR8vGa ZGfDNNRlhk1pWqVzarpxwhBWjaBFzpgKyMQOmhDwZf9iC5+8b8JDX5af/yQAyD5C1iIhQa4eW WqVM/2gF8NvAUqFSGclXBgLSgHTge5B1rlSc1ssZQoKNRlD8h7afnzKyBHgXs+T3BulcFH7VZ O8fIduV2RROWE8i5w+61uPDmiEEpvFgCNYcvaL8Tz4AuWCZu6IyTL+wng/hHW8yK5SBlDkU3U myAcwErfveBXuDPQteEghA4xyJgiPfPYDNWB0JDZcIs01GYJnAc87tVl5cUcdjb0mwOuhTnzk QxftK+myf3xtpzCIikqCe2w00mpV3J/FPU++pvlkqlWhU2HNlQYr0OCUcuooOMt1e3EsrRZse Yxk7cmcV++tDzlKFBaZkh9roj6HLxIjJcifTcY82j9puJgcbkHyJ63RqOeu70zJFWDoGM=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jGlE_5-aZYEJlcwFjxLz0HrAazc>
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 07:41:55 -0000

Am 11.05.2021 um 07:36 schrieb Lloyd W:
> Let me outline how this is all going to work in future. Prove me wrong.
>
> Every git pull request on a document being edited under git revision control is by its very nature an errata report. errata are verified by being committed to main branch.
>
> there are no final published documents, only git repositories with checkpoints, which are eventually given to the RFC Editor function to maintain as workgroups close. Implementations are based on document checkpoints, timestamped.
>
> If you want to read an RFC or internet draft, you need to fire up git to go get it. Or rather, its up to date authoritative main revision repo tree.
> ...

FWIW; even if all of the previous points were true: you wouldn't need to
fire up Git, but just open a specific HTTP(s) URL in a browser.

Best regards, Julian

v2.23.0 | Report a Bug | By Email