TCP in 30 instructions (1993)
pdl.cmu.edu
TCP in 30 instructions (1993)
1–10 of 41 posts
Re: TCP in 30 instructions (1993)
#2This is a very famous post, and Van Jacobsen is the archetypical networking systems programming bad-ass. Important context here though: this is just the per-segment receive processing piece of TCP; it's describing a very simple fast path that segments can take, but not all the TCP logic!
Re: TCP in 30 instructions (1993)
#3If you liked this post you might like the "Appendix E: Extended Example: A Tiny TCP/IP Done as a Parser" by Ian Piumarta. The paper is available at: http://www.vpri.org/pdf/tr2007008_steps.pdf
Re: TCP in 30 instructions (1993)
#4This is a very famous post, and Van Jacobsen is the archetypical networking systems programming bad-ass. Important context here though: this is just the per-segment receive processing piece of TCP; it's describing a very simple fast path that segments can take, but not all the TCP logic!
Wouldn't "all the TCP logic" be the entire internet?
Re: TCP in 30 instructions (1993)
#5This is a very famous post, and Van Jacobsen is the archetypical networking systems programming bad-ass. Important context here though: this is just the per-segment receive processing piece of TCP; it's describing a very simple fast path that segments can take, but not all the TCP logic!
Wouldn't "all the TCP logic" be the entire internet?
No, it would not be anything close.
Re: TCP in 30 instructions (1993)
#6This is a very famous post, and Van Jacobsen is the archetypical networking systems programming bad-ass. Important context here though: this is just the per-segment receive processing piece of TCP; it's describing a very simple fast path that segments can take, but not all the TCP logic!
Wouldn't "all the TCP logic" be the entire internet?
No
Re: TCP in 30 instructions (1993)
#7This is a very famous post, and Van Jacobsen is the archetypical networking systems programming bad-ass. Important context here though: this is just the per-segment receive processing piece of TCP; it's describing a very simple fast path that segments can take, but not all the TCP logic!
>Van Jacobsen
Van Jacobson
He is probably most famous for his work on early congestion control algorithms in 1988 (http://ee.lbl.gov/papers/congavoid.pdf)
Re: TCP in 30 instructions (1993)
#8Re: TCP in 30 instructions (1993)
#9This is a very famous post, and Van Jacobsen is the archetypical networking systems programming bad-ass. Important context here though: this is just the per-segment receive processing piece of TCP; it's describing a very simple fast path that segments can take, but not all the TCP logic!
Wouldn't "all the TCP logic" be the entire internet?
The internet is a very large and general term. It comprises millions of servers, routers, generally includes things like web browsers, http, etc.
TCP is just one protocol of the thousands of protocols used for the internet, typically to carry other protocols. UDP is also used on the internet.
"not all the logic" means that this implementation is not a full implementation of the TCP protocol.
Check out: http://en.wikipedia.org/wiki/Internet_protocol_suite http://en.wikipedia.org/wiki/OSI_model
Re: TCP in 30 instructions (1993)
#10Earlier quoted context omitted.
No, it would not be anything close.
Well, TCP is a very simple protocol so I can't imagine what the OP means by "all of TCP" unless he's talking about IP and it's associated services.
Because TCP is very simple, you can't imagine that "all of TCP" means what it actually says? Huh?