All of lore.kernel.org
 help / color / mirror / Atom feed
* Why TCP does NOT have explicit LENGTH field like UDP & IP packets do!?!?
@ 2005-11-21 17:46 Christian Seberino
  0 siblings, 0 replies; only message in thread
From: Christian Seberino @ 2005-11-21 17:46 UTC (permalink / raw)
  To: netfilter

[-- Attachment #1: Type: text/plain, Size: 613 bytes --]


I'm curious why TCP does not have an explicit length field like
UDP and IP packets do.

It appears from TCP RFC 793 that lower (IP) layer must provide
*some* way for TCP to figure out length.  This is vague
and weird that length is handled this way.....

From RFC 793 page 50 with regards to layer below TCP...

"Any lower level protocol will have to provide the source address,
    destination address, and protocol fields, and some way to determine
    the "TCP length", both to provide the functional equivlent service
    of IP and to be used in the TCP checksum."



Any ideas?


Chris

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 481 bytes --]

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2005-11-21 17:46 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-11-21 17:46 Why TCP does NOT have explicit LENGTH field like UDP & IP packets do!?!? Christian Seberino

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.