lit - literature

personally, i learned it by listening to podcasts, reading wikipedia and doing stuff myself (stack overflow and so forth). bump tho :)

Computer Networks by Tanenbaum or
Computer Networking: A Top-Down Approach by Kurose.

>>1387
seconding this

>>1387
>>1388
i am reading tanenbaum right now.It seems really similar to the book i wanted thx.

>>1386
What podcasts do you reccomend? Also thanks for bumping this thread

>>1390
none if you don't speak german :(

>>1391
post'em m8,maybe someone that speaks german could make use of it.

Rather than buying books you could just read the RFCs that introduced the protocols. Most are very readable, they explain the why, the how, the history and so on.

The only thing you don't get from the RFCs themselves is a filter of what's considered important or not, but you can probably just start reading about the protocols and systems that you use (http, dns, stp, smtp), finding out which ones are widely used is usually easy enough since they're being mentioned all over the place.

You'll be studying from the authoritative source, I'd say you can't go wrong there.

>>1732
While I think this approach in general is a good idea, using it to learn HTTP is a bad idea. The HTTP RFC is 176 pages of incredibly dense information. Other protocols like gopher (16 pages) have an order of magnitude shorter RFCs. IMO, HTTP is too complex a protocol to learn from RFCs