[tcpm] Sequence number checking for incoming RST segments

 Hi,

 I had a question regarding the sequence-number check for acceptance of incoming RST segments. It seems that some TCP stacks (e.g. the Linux stack shown below) apply a different sequence number check to RST segments, than what is specified in RFC793 i.e. the {RCV.NXT, RCV.NXT+RCV.WND} check 

 If someone is familiar with this, could you pls send me an email mentioning what RCV.WUP means exactly (I was guessing that it was the last ACK sent by the local i.e. receiving device).
 Also, what is the commonly-accepted sequence-number check for incoming RST segments, in case the check in RFC793 is seen as inappropriate for RST segments (is there any RFC/other-doc that discusses this) ?

 Sorry for asking this question here, in case this is not the appropriate forum.

 Thanks in advance for any help,

 Indraneel 

http://www.cs.purdue.edu/homes/fahmy/software/flowmate/tcp_input.c

/* Check segment sequence number for validity.
 *
 * Segment controls are considered valid, if the segment
 * fits to the window after truncation to the window. Acceptability
 * of data (and SYN, FIN, of course) is checked separately.
 * See tcp_data_queue(), for example.
 *
 * Also, controls (RST is main one) are accepted using RCV.WUP instead
 * of RCV.NXT. Peer still did not advance his SND.UNA when we
 * delayed ACK, so that hisSND.UNA<=ourRCV.WUP.
 * (borrowed from freebsd)
 */

static inline int tcp_sequence(struct tcp_opt *tp, u32 seq, u32 end_seq)
{
	return	!before(end_seq, tp->rcv_wup) &&
		!after(seq, tp->rcv_nxt + tcp_receive_window(tp));
}

_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www1.ietf.org/mailman/listinfo/tcpm