TCPIP sequence number question

Ok, this isn't specifically VMS related but here it goes...

Say I am sending TCP data packets with sequence numbers #10 #11 #12 #13
#14 and #15.

Someone meddles with my traffic and changes, while in transit, the
sequence number of the second packet from #11 to #789

How will the receiver behave upon receiving the packet with sequence
number #789 ? Will it wait a certain amount of time to see if the
packet #11 will arrive out of sequence before declaring #11 to be lost
and sending NAK to the sender ?

How long will it wait before declaring #11 to be lost at sea ?

base on what I read, the recipient will send an ack confirming it has
received all data intact until/including #10. (instead of sending an
actual "I haven't received #11").

Once the sender has realised the recipient hasn't received #11, will the
sender then resend #11 and all subsequent packets ?

With windowing, will the sender end up stopping transmission at one
point, waiting for an ack ? Or will the "sorry I didn,t get #11"
realisation reach the sender before the sender has finished sending all
packets permitted in the sliding window ?

aka: will the data line become idle for some time, or will it remain
constantly in full use with packets flowing with retransmissions here
and there ?
.

Relevant Pages

  • Re: CSocketFiles / CArchive vs Raw Buffer Manipulation
    ... such as network packet transmission. ... UDP within a LAN often gives the effective illusion that it is reliable. ... fail without warning of any sort to either the sender or the receiver. ...
    (microsoft.public.vc.mfc)
  • Re: TCP segments reordering and covert channels
    ... guess the original order since sequence numbers are always increasing. ... receiver, and discarding damaged segments. ... If the destination is off the local subnet, a glitch (lost packet, routing ...
    (Vuln-Dev)
  • Re: Van Jacobsons net channels and real-time
    ... packages with real-time latencies. ... Finding the end point in the receive interrupt and send of the packet to ... through soft irq which might be busy working on IP packages. ... Each end receiver provides his own receive resources. ...
    (Linux-Kernel)
  • Re: Neutral Format as a Coupling reduction idea that doesnt work.
    ... There are potentially unlimited and unexpected side effects for both sender and receiver. ... That definition defines the semantics of the just the data packet. ... That represents a solution level coupling but at least it is very narrowly focused on the message definition rather than what each side does with the information. ...
    (comp.object)
  • Re: PostMessage and unprocessed messages
    ... The sender has no way to know when to delete the message, so making it the owner has no ... Since the receiver would have no way to know the message is deleted, ... collection, note that as long as something is in the queue, it is owned by the queue ... so adding memory management complexity to the ...
    (microsoft.public.vc.mfc)