Amazon.com info for 'Internet Core Protocols: the Definitive Guide'

---

Back to reviews and details of Internet Core Protocols: the Definitive Guide

Amazon.com reviews:

Rating: 5 Summary: An exemplary discussion of network and transport protocols
Comment If you need to strengthen your knowledge of network-layer and transport-layer protocols (IP, ICMP, TCP and UDP), go no further than this book. Recommended. This is a critical reference. It's more readable than Comer or Stevens (and easily as complete) for learning about the network-layer and transport-layer protocols. For my money, this is the single most important book to have in this area. A sterling, untoppable effort from the O'Reilly label, and an absolute must for anyone learning about low-level internetworking.

Rating: 3 Summary: Learning may be hard; explaining is harder
Comment The better you know a subject matter, the better you can explain it to others...

Well, this is only 50% of what's required: the other 50% is being good at explaining.

And that's the problem with this book: everything is terribly (badly) explained!

I'm in no position to discuss the author's prowess when it comes to mastering Networking, but filling a book with "reference manual" type of data (something you can find in many others books -and websites, for that matter!) doesn't prove it, either. At all.

As other reviews exposed, repetitions, copy-paste style, are common in this book; also common is the definition that its writing style brings to mind: gibberish.

Let's say it out loud: writing a book is no mean feat, and every book on any matter _has_ its share of shortcomings, be it important or just anecdotical. But, honestly, I haven't found much to salvage from this reading.

Reviewer and author Richard Bejtlich mentions this book in his review of "The TCP/IP Guide: A Comprehensive, Illustrated Internet Protocols Reference" by Charles Kozierok, as belonging to an intermediate-level class of recommended books; and he mentions, too, Kevin Burns' "TCP/IP Analysis and Troubleshooting Toolkit" as belonging to the expert-level class.

Well, I've found Kevin Burns' book faaaaaaaar more instructive, readable, etc, than this other; they're as opposite as night and day (well, let's be a bit less harsh: as dusk and dawn) (an enlightening dawn and an obscure dusk, that is).

Buy that one, forget this one.

Rating: 5 Summary: Best book on the topic
Comment From beginning to end I found this to be the most substantive book on the topic(s). The book doesn't "hold your hand" but it takes you from the essentials right through more advanced concepts. Well done.

Rating: 5 Summary: Well done
Comment The best thing about this book, which covers protocols like TCP and IP in detail, is that the discussion is from the ground-up, not from the top-down. I know what TCP/IP does for me at an application level, but I didn't know how TCP, or IP, or any of the other covered protocols, worked under the covers. Now I feel like I have a much better understanding of the details, which means I have a better understanding of a lot of things that are built on top of these protocols, as well as of system administration type tasks. Even the page after page of 'this bit field does this' text, which in most books would be rarely visited reference material, is decent, because individual reference sections contain real-world 'this means that' information. I would have liked a bit more discussion of Internet naming, IP address details, and so on, but I can find that information elsewhere.

Rating: 2 Summary: good book but too much repeated stuff
Comment Very good presentation and description of core protocols (ip, icmp, igmp udp/tcp, arp) and at the right in-depth level I believe (if you want to get more in-depth, the rfc are there for that).
Anyway the book could be made much better just removing stuff since it contains way too much duplicated info. First there are whole paragraphs repeated exactly the same just a few pages away. I think this can get quite offensive (do you think I'm so dumb that I don't remember?).
And then there are the screenshots which are not very appropriate here since this is not an application review. A well formatted packet decode a'la tcpdump/snoop would be much better since screenshots display lots of useless stuff (menus, toolbars, etc) and for big packets a single screenshot can't fit the whole thing so you have to include two or more of them introducing discontinuities.
Furthermore screenshots are uselessly duplicated throughout the book. For example a simple ip header contains jsut 12 fields so a single screenshot can fit them all, anyway to describe these fields, the same screenshot is duplicated 14 times, from page 59 to page 77, and then a few more times. This happens for all the protocols and each screenshot takes about 66% of a page, so this is a real waste of paper! Often it gets really ridiculous when you have the same screenshot on 2 facing pages so you don't even have to slightly rotate your eyes to find them ;-)