Hi All,
Anything behind these numbers "64 and 128" as specified in RFC 1144 [page
19]
" Each slot must be large enough to hold a maximum length TCP/IP header 128
{ The maximum header length, fixed by the protocol design, is 64
bytes of IP and 64 bytes of TCP} "
Regards,
Ramana.
-----Original Message-----
From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org] On Behalf Of
Valdis.Kletnieks@vt.edu
Sent: Monday, 2 December 2002 1:59 PM
To: ramanad@FUTURE.FUTSOFT.COM
Cc: ietf@ietf.org
Subject: Re: Clarification needed
<< File: ATT00013.dat >> On Mon, 02 Dec 2002 10:18:22 +0530, Ramana Divvi
<ramanad@future.futsoft.com> said:
> IHL ------> IHL is the Total IPv4 header length, maximum is
15
> ( 15x4 = 60 bytes) ----refer RFC 791
> DataOffset ------> DataOffset is total TCP header size ( in simple
words)
> , maximum is 15 ( 15x4 = 60 bytes) ----refer RFC 793
> From above two, combined TCP/IP header maximum length is 120 bytes.
Correct.
> But in RFC 1144 (page 13) , it was defined as 128 bytes. Is it correct? If
> so please clarify the same.
No. You need a 128 octet buffer *for the compressed header*. The hint is
"since the output packet can be larger than the input packet". Contemplate
the
algorithm, and see if you can see what states will cause the 120 byte header
to
require 128 bytes after "compression".
--
Valdis Kletnieks
Computer Systems Senior Engineer
Virginia Tech
***************************************************************************
This message is proprietary to Future Software Limited (FSL)
and is intended solely for the use of the individual to whom it
is addressed. It may contain privileged or confidential information
and should not be circulated or used for any purpose other than for
what it is intended.
If you have received this message in error, please notify the
originator immediately. If you are not the intended recipient,
you are notified that you are strictly prohibited from using,
copying, altering, or disclosing the contents of this message.
FSL accepts no responsibility for loss or damage arising from
the use of the information transmitted by this email including
damage from virus.
***************************************************************************