NO WAY! On 11/18/05, Christian Seberino <[EMAIL PROTECTED]> wrote: > Michael > > Thanks! > > > No. An entire IP packet (after defragmentation) is given to to the TCP > > stack. The stack then looks at the header to find out which 'socket' to > > put the payload into, and then pushes the payload onto the end of the > > socket buffer. > > Doesn't the IP stack peel off it's own IP header before giving > the IP packet payload to the TCP stack? Otherwise, TCP stack > would have to know about IP details which violates encapsulation right? > Then what do you have after you remove the TCP headers at your destination? NOTHING? Just because a protocol doesn't know the internals of another protocol doesn't mean it would do anything about it.
BTW encapsulation and naive protocols are quite passe. The most optimized performance comes from smart implementations that break just that rule. Have you heard of RTP....there was a great paper that Henning Schulzerene of wrote that prefaced that style of prototocol out there some where. -Tom -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
