TCP end-to-end Semantics

From: [email protected]
Date: Mon Jan 08 2001 - 10:04:29 EST

  • Next message: Craig Partridge: "Re: TCP end-to-end Semantics"

    Can somebody shed some light on a few things pleas please?

    1.
    People claim that TCP semantics is not violated if TCP acks are "spoofed", as long as the initial 3-way handshake and the FIN are respected.
    Seems strange to me. Namely, the sending TCP will have lost the data because of spoofing and falsely assumes it has arrived if the link breaks down, i.e. there is a "false positive". Who says the sender wants to do a FIN, it could just stop and will
    notice nothing about the break down.

    2.
    What if I used large windows, but spoofed the initial SYN/ACK, i.e. the opposite. This will speed up small transfers, because there is no wait for the handshake to complete. The other side can not open the socket, the first data transfer will simply
    fail, so no false positives here? Good idea or not?

    3.
    What guarantee does an application have anyway. If I do a send in TCP, the data goes into TCP's buffer without error and is handled asynchronously, which could fail. How rock-solid is end-to-end reliability?

    Thank you,

    Eric Verlind
    SW Architect



    This archive was generated by hypermail 2b29 : Mon Jan 08 2001 - 10:40:12 EST