Since TCP header is a relatively large overhead, why don’t we compress it in the way that ACK and SEQ share the same field, and they can still be distinguished by flags in the header?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Since TCP header is a relatively large overhead, why don’t we compress it in the way that ACK and SEQ share the same field, and they can still be distinguished by flags in the header?
Because they are not used exclusively. Below is most important: connection negotiation, i.e. the Three Way Handshake:
(source: wikimedia.org)
The picture is from wikimedia commons. It presents how TCP connection is negotiated, and shows that ACK and SEQ are used together in the same header to establish a connection (I write this to be sure that the answer is helpful even if the picture would disappear someday).