Re: [tcpm] Erik Kline's Yes on draft-ietf-tcpm-rfc793bis-25: (with COMMENT)

[Erik Kline <[e-mail]>]

On Thu, Sep 30, 2021 at 12:55 PM Benjamin Kaduk <[e-mail]> wrote:

> On Sun, Sep 19, 2021 at 06:08:23PM -0700, Erik Kline via Datatracker wrote:
> [...]
> > [S3.5, question]
> >
> > * Is there an example of what possible use a RST w/ data could serve?
> >
> >   I didn't see anything in S3.10.7(.*) that indicated the data in a
> segment
> >   with the RST flag set could get processed (I may have missed it).
>
> Section 4.2.2.12 of RFC 1122 (sorry, the section link doesn't work, though
> https://www.rfc-editor.org/rfc/rfc1122.html#page-87 gets most of the way
> there) has:
>
>             A TCP SHOULD allow a received RST segment to include data.
>
>             DISCUSSION
>                  It has been suggested that a RST segment could contain
>                  ASCII text that encoded and explained the cause of the
>                  RST.  No standard has yet been established for such
>                  data.
>
>
Ah, so including such text in 3.10.7.* would have elevated some
discussion to a level not (yet) warranted.  Makes sense, thank you.

I look forward to the forthcoming Proposed Standard for TCP RSTs containing
XML-encoded documents of error explainer text.  :D