Re: [tcpm] 793bis: purpose of RST w/ data

Hi, Wes, 

It’s worth including that statement. I recall discussing potential uses of that data, e.g, as a signal to why the RST occurred, with some people MANY years ago, but it never went anywhere. At a minimum, it should be allowed and ignored, as noted.

Joe

—
Joe Touch, temporal epistemologist
www.strayalpha.com

> On Jan 5, 2022, at 9:02 PM, Wesley Eddy <wes@mti-systems.com> wrote:
> 
> One of the IESG comments on RFC 793bis was in regard to this text:
> 
>  TCP implementations SHOULD allow a received RST segment to include
>  data (SHLD-2).
> 
> The question  was:
> 
> Is there an example of what possible use a RST w/ data could serve?
> 
> There isn't much to say about this, to my knowledge.  The only thing I'm aware of is the discussion of that requirement in RFC 1122, which only says:
> 
>             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.
> Do we want to repeat that in 793bis?  I didn't think it would be important to include, but since it was noted during the IESG reviews, maybe it should be stated.
> 
> 
> 
> _______________________________________________
> tcpm mailing list
> tcpm@ietf.org
> https://www.ietf.org/mailman/listinfo/tcpm