[tcpm] Re: [Technical Errata Reported] RFC9293 (8171)

tuexen@fh-muenster.de Thu, 07 November 2024 09:39 UTC

Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.200.121\))
From: tuexen@fh-muenster.de
In-Reply-To: <20241106233032.5866A3B873@rfcpa.rfc-editor.org>
Date: Thu, 07 Nov 2024 09:38:41 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <9C70F06C-4E4C-4FEF-8F95-985BCE08F62A@fh-muenster.de>
References: <20241106233032.5866A3B873@rfcpa.rfc-editor.org>
To: RFC Errata System <rfc-editor@rfc-editor.org>
Message-ID-Hash: LJ4VUSYA5MIUB62DM7OYU2WWMRE6GNLH
CC: wes@mti-systems.com, tcpm-ads@ietf.org, abbrev@gmail.com, tcpm@ietf.org
Precedence: list
Subject: [tcpm] Re: [Technical Errata Reported] RFC9293 (8171)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/F6DgdIWjjY0qtZGLFnZDmijHX4Q>

> On 6. Nov 2024, at 23:30, RFC Errata System <rfc-editor@rfc-editor.org> wrote:
> 
> The following errata report has been submitted for RFC9293,
> "Transmission Control Protocol (TCP)".
> 
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid8171
> 
> --------------------------------------
> Type: Technical
> Reported by: Christopher Williams <abbrev@gmail.com>
> 
> Section: Appendix B
> 
> Original Text
> -------------
>    +-----------------+---------+------+--------+-----+--------+------+
>    | *  Dest Unreach | SHLD-25 |  X   |        |     |        |      |
>    |    (0,1,5) =>   |         |      |        |     |        |      |
>    |    inform ALP   |         |      |        |     |        |      |
>    +-----------------+---------+------+--------+-----+--------+------+
> 
> 
> Corrected Text
> --------------
>    +-----------------+---------+------+--------+-----+--------+------+
>    | *  Dest Unreach | SHLD-25 |      |   X    |     |        |      |
>    |    (0,1,5) =>   |         |      |        |     |        |      |
>    |    inform ALP   |         |      |        |     |        |      |
>    +-----------------+---------+------+--------+-----+--------+------+
> 
> 
> Notes
> -----
> This requirement has an X in the "MUST" column, but the X should be in the "SHOULD" column.
> 
> The relevant text for this requirement is "a TCP implementation ... SHOULD make the information available to the application (SHLD-25)."
The report is correct. The information is correct in RFC 1122, where it comes from.

Best regards
Michael
> 
> 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.
> 
> --------------------------------------
> RFC9293 (draft-ietf-tcpm-rfc793bis-28)
> --------------------------------------
> Title               : Transmission Control Protocol (TCP)
> Publication Date    : August 2022
> Author(s)           : W. Eddy, Ed.
> Category            : INTERNET STANDARD
> Source              : TCP Maintenance and Minor Extensions
> Stream              : IETF
> Verifying Party     : IESG
> 
> _______________________________________________
> tcpm mailing list -- tcpm@ietf.org
> To unsubscribe send an email to tcpm-leave@ietf.org

[tcpm] [Technical Errata Reported] RFC9293 (8171) RFC Errata System
[tcpm] Re: [Technical Errata Reported] RFC9293 (8… tuexen
[tcpm] Re: [Technical Errata Reported] RFC9293 (8… Wesley Eddy