[tsvwg] Re: [Editorial Errata Reported] RFC9435 (8081)

"C. M. Heard" <heard@pobox.com> Tue, 20 August 2024 14:33 UTC

Return-Path: <heard@pobox.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ABAB1C14F6B8 for <tsvwg@ietfa.amsl.com>; Tue, 20 Aug 2024 07:33:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.806
X-Spam-Level:
X-Spam-Status: No, score=-2.806 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=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=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=pobox.com
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 352aeaUWQQlP for <tsvwg@ietfa.amsl.com>; Tue, 20 Aug 2024 07:33:13 -0700 (PDT)
Received: from pb-smtp1.pobox.com (pb-smtp1.pobox.com [64.147.108.70]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 21D3CC14F5FA for <tsvwg@ietf.org>; Tue, 20 Aug 2024 07:33:12 -0700 (PDT)
Received: from pb-smtp1.pobox.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id 2C17D2B658 for <tsvwg@ietf.org>; Tue, 20 Aug 2024 10:33:10 -0400 (EDT) (envelope-from heard@pobox.com)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=pobox.com; h= mime-version:references:in-reply-to:from:date:message-id:subject :to:cc:content-type; s=sasl; bh=ZU+s7kNwZRmrZIlin357zToR1wq9fPHb g1pxS+Z8AqA=; b=rb5/i/+lRsnQDKDlu4CG62NGMrZijOtP9hOA9i4Q3huhkeQr prvWAFv4bJ5VRsTqeF7Zj1PsF3k5kmbmSG5Nkv/YdvrRcBPBCcZ7NZxkMgvCVfIT 4ugDkQCT/19ePimvY58BN6q/75zX1HhpdRL8wiAFOTe8+7UthCWGqfB8I68=
Received: from pb-smtp1.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id 212B62B657 for <tsvwg@ietf.org>; Tue, 20 Aug 2024 10:33:10 -0400 (EDT) (envelope-from heard@pobox.com)
Received: from mail-lj1-f171.google.com (unknown [209.85.208.171]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pb-smtp1.pobox.com (Postfix) with ESMTPSA id C1E632B652 for <tsvwg@ietf.org>; Tue, 20 Aug 2024 10:33:08 -0400 (EDT) (envelope-from heard@pobox.com)
Received: by mail-lj1-f171.google.com with SMTP id 38308e7fff4ca-2f040733086so55301571fa.1 for <tsvwg@ietf.org>; Tue, 20 Aug 2024 07:33:08 -0700 (PDT)
X-Forwarded-Encrypted: i=1; AJvYcCUe+D0NmgmaLMv6VX0AoYGs0ZJ7QLvBGPRF4I2zP/BPyqoioJqafmS8EMBWUVemWvSyAGFPlQ==@ietf.org
X-Gm-Message-State: AOJu0YzPduqv/qzXaGfKnyMyJQ3s5bcL6nAOJlWA62NO60OWL2+/ltai +cx+YAPdjN9BiIyUxTdSEer9EmqYOa2eZdmOdCYDvIzr7Xq0wNA9vbXDV/mJOjzqhtiwhI5NY48 Bqxp7x0t8Nxrk34rCXAAShyoAHHM=
X-Google-Smtp-Source: AGHT+IHpQlJbXLU+fis0uNcWTxHE8PXEoPkOTmvvixl9LEa00IvuBoLxwNGIZXvKnXq29WhRrFN2MSI+EH7zUIGX7Kc=
X-Received: by 2002:a05:651c:1992:b0:2ef:268b:3448 with SMTP id 38308e7fff4ca-2f3be574cb2mr115691821fa.9.1724164387245; Tue, 20 Aug 2024 07:33:07 -0700 (PDT)
MIME-Version: 1.0
References: <20240817051708.DAF143B874@rfcpa.rfc-editor.org> <d64d3db6-e734-4c27-b9ff-011b442030ea@erg.abdn.ac.uk> <59D1554A-E466-478E-93AD-8D025D50CF3B@strayalpha.com> <CAEh=tcdD+3s=Ake2PKQ+80Jy=mFV9Vmsn++_7FoVfgkNv_wAwQ@mail.gmail.com>
In-Reply-To: <CAEh=tcdD+3s=Ake2PKQ+80Jy=mFV9Vmsn++_7FoVfgkNv_wAwQ@mail.gmail.com>
From: "C. M. Heard" <heard@pobox.com>
Date: Tue, 20 Aug 2024 07:32:52 -0700
X-Gmail-Original-Message-ID: <CACL_3VHoeLK4L29G+DnRfrQyHvnytZ0HJdYvbx9RdUO_ey7b4w@mail.gmail.com>
Message-ID: <CACL_3VHoeLK4L29G+DnRfrQyHvnytZ0HJdYvbx9RdUO_ey7b4w@mail.gmail.com>
To: Zaheduzzaman Sarker <zahed.sarker.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000d6235806201e4d31"
X-Pobox-Relay-ID: 1ECCBBB2-5F01-11EF-A59C-2BAEEB2EC81B-06080547!pb-smtp1.pobox.com
Message-ID-Hash: KC5VXW7NOYJXP7DJUZTBW5XDBJZCTB4C
X-Message-ID-Hash: KC5VXW7NOYJXP7DJUZTBW5XDBJZCTB4C
X-MailFrom: heard@pobox.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tsvwg.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "touch@strayalpha.com" <touch@strayalpha.com>, Gorry Fairhurst <gorry@erg.abdn.ac.uk>, RFC Errata System <rfc-editor@rfc-editor.org>, angelos2225@hotmail.com, ana@erg.abdn.ac.uk, r.secchi@abdn.ac.uk, tsvwg@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [tsvwg] Re: [Editorial Errata Reported] RFC9435 (8081)
List-Id: Transport Area Working Group <tsvwg.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/LZEVIN2lmjItkPmisi1wIJhCV3Y>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Owner: <mailto:tsvwg-owner@ietf.org>
List-Post: <mailto:tsvwg@ietf.org>
List-Subscribe: <mailto:tsvwg-join@ietf.org>
List-Unsubscribe: <mailto:tsvwg-leave@ietf.org>

In the case of an editorial erratum such as this, isn't the custom to
accept the erratum but place it in a "hold for document update" status?

On Tue, Aug 20, 2024 at 6:56 AM Zaheduzzaman Sarker <
zahed.sarker.ietf@gmail.com> wrote:

> Hi,
>
> This has been reported as editorial hence RFC editor will handle this.
>
> //Zahed
>
> On Tue, 20 Aug 2024 at 15:40, touch@strayalpha.com <touch@strayalpha.com>
> wrote:
>
>> Hi, Gorry,
>>
>> The correction is valid, but as you note not substantive.
>>
>> Aren’t those still recordable as “editorial” rather than “technical”,
>> though?
>>
>> *Editorial* a spelling, grammar, punctuation, or syntax error that does
>> not affect the technical meaning
>>
>> Joe
>>
>> —
>> Dr. Joe Touch, temporal epistemologist
>> www.strayalpha.com
>>
>> On Aug 20, 2024, at 6:33 AM, Gorry Fairhurst <gorry@erg.abdn.ac.uk>
>> wrote:
>>
>> On 17/08/2024 06:17, RFC Errata System wrote:
>>
>> The following errata report has been submitted for RFC9435,
>> "Considerations for Assigning a New Recommended Differentiated Services Code Point (DSCP)".
>>
>> --------------------------------------
>> You may review the report below and at:https://www.rfc-editor.org/errata/eid8081
>>
>> --------------------------------------
>> Type: Editorial
>> Reported by: Angelos Vassiliou <angelos2225@hotmail.com> <angelos2225@hotmail.com>
>>
>> Section: 1
>>
>> Original Text
>> -------------
>> A common set of DSCPs are defined for both IPv4 and IPv6
>>
>> Corrected Text
>> --------------
>> A common set of DSCPs is defined for both IPv4 and IPv6
>>
>> Notes
>> -----
>> The subject of the sentence, "A common set" is singular, but the verb is plural.
>>
>> Instructions:
>> -------------
>> This erratum is currently posted as "Reported". (If it is spam, it
>> will be removed shortly by the RFC Production Center.) Please
>> use "Reply All" to discuss whether it should be verified or
>> rejected. When a decision is reached, the verifying party
>> will log in to change the status and edit the report, if necessary.
>>
>> --------------------------------------
>> RFC9435 (draft-ietf-tsvwg-dscp-considerations-13)
>> --------------------------------------
>> Title               : Considerations for Assigning a New Recommended Differentiated Services Code Point (DSCP)
>> Publication Date    : July 2023
>> Author(s)           : A. Custura, G. Fairhurst, R. Secchi
>> Category            : INFORMATIONAL
>> Source              : Transport and Services Working Group
>> Stream              : IETF
>> Verifying Party     : IESG
>>
>> Thanks for letting us know.
>>
>> The intent was to describe one common set, but an alternative that
>> describes multiple sets of DSCPs by PHB groups would be equivalent.
>>
>> While I do see the gammar could be improved, I don't think we need to
>> record this, because I do not see an ambiguity in meaning. So,  in this
>> case, I'd recommend we reject this Errata.
>>
>> Best wishes,
>>
>> Gorry Fairhurst
>>
>> (Author)
>>
>>
>>