All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Seberino <seberino@spawar.navy.mil>
To: netfilter@lists.netfilter.org
Subject: Why TCP does NOT have explicit LENGTH field like UDP & IP packets do!?!?
Date: Mon, 21 Nov 2005 09:46:11 -0800	[thread overview]
Message-ID: <1132595171.5180.98.camel@localhost.localdomain> (raw)

[-- 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 --]

                 reply	other threads:[~2005-11-21 17:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1132595171.5180.98.camel@localhost.localdomain \
    --to=seberino@spawar.navy.mil \
    --cc=netfilter@lists.netfilter.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.