Amazon.com info for 'Internetworking with TCP/IP : Principles, Protocols, and Architecture'

---

Back to reviews and details of Internetworking with TCP/IP : Principles, Protocols, and Architecture

Amazon.com reviews:

Rating: 4 Summary: very good and technical, but not focused on minutia
Comment Many networking books I read (or other books on similarly technical subjects) have a tendency to get bogged down in technical minutia that distracts from the big picture. Not so here. Cormer does an excellent job of getting all the important information out there and explains the common networking protocols, what goes into them, and what they do, without losing the reader. Do not think that this is a superficial view though - I've been in the field for several years now and still use it as a reference on occasion.

Rating: 4 Summary: The fifth edition is out.
Comment Look for the 5th edition of this same book.
4th edition is much older than the newer 5th edition.

Rating: 5 Summary: Great Service
Comment I purchased the book titled: Internetworking with TCP/IP Vol.1: Principles, Protocols, and Architecture (4th Edition)for a class. The book arrived ahead of schedule, marking the service amazon provided as second to none. Keep up the great work.

Rating: 5 Summary: Superb!!!
Comment Want to really, really, really know TCP-IP???

Read this book and you will know it cold.

Rating: 5 Summary: Beginners look no further!
Comment I knew nothing about TCP/IP. As a result, I bought a book "learn TCP/IP in 24 hours" and trashed it after I bought this book, no more 24 hour books. I had no idea what routing is and were to start looking for documents on the internet. This book is scientific and puts it all together. Each chapter lists the RFC that he relied on so you know were the stuff came from. The book is not boring; the author is excellent in explaining ideas. He covers ICMP, GGP, OSPF, EGP, DHCP, DNS, BOOTP, ARP and more. I feel I have accomplished something big by reeading this book. If you are not a beginner in routing, then look at the RFCs they are the source.