iPv6 Essentials 3ed (Anglais) Broché – 17 juin 2014
|Neuf à partir de||Occasion à partir de|
Les clients ayant acheté cet article ont également acheté
Aucun appareil Kindle n'est requis. Téléchargez l'une des applis Kindle gratuites et commencez à lire les livres Kindle sur votre smartphone, tablette ou ordinateur.
Pour obtenir l'appli gratuite, saisissez votre adresse e-mail ou numéro de téléphone mobile.
Détails sur le produit
Quels sont les autres articles que les clients achètent après avoir regardé cet article?
Commentaires en ligne
Commentaires client les plus utiles sur Amazon.com (beta)
Every chapter gets into RFC’s related to that topic, be it “Why IPv6,” IPv6 Addressing,” “The Structure of the IPv6 Protocol,” “Security with IPv6,” for example, and each is peppered with RFC and other references. The book is worth money for just the chapter-by-chapter topical collection of related RFC’s at end of each chapter--but it provides so much more. There is a very thorough explanation of the basics, of what happens on the wire, with examples of network captures/protocol analysis, throughout the book. The approach gives you insight on which you can build. There are many explanations of the various v4 to v6 transition problems. Security problems are highlighted throughout the book.
I found myself re-creating her packet captures and getting used to seeing the new structures—and thoroughly understanding the context based on her detailed documentation of how IPv6 works. I have, after doing so, and seeing how much IPv6 is already flowing, developed a sense of urgency. I have a new perspective. We are vulnerable to IPv6 issues even if we are not “officially” transitioning. It’s everywhere, basically an out-of-band network that we’re all running without necessarily seeing it.
There are references to Security issues throughout the book as well as the chapter dedicated to the subject. You get many insights into areas for concern, weaknesses that we can’t leave behind with IPv4, as well as new challenges with IPv6—but no hesitation to proceed. She addresses the benefits of dropping NAT for the ability to see the client and makes good arguments for working around our NAT mentality to look at Security from other perspectives. Does NAT really do that much for your security? It’s not like NAT helps a whole lot in our egress concerns. It’s not like NAT helps when the intellectual property can leave at the application layer. How much easier would many issues be without NAT? We already have to take deeper and stronger approaches to host-based protections and she stresses a new Security model tied more to identity and directories than to IP addresses.
It is going to take eons before we see the last of IPv4 but IPv6 transition is inevitable. This book provides extensive details on the transition technologies as well as the reasons to move forward. You already have IPv6 running somewhere (like all your Windows and Linux systems …and quite possibly your tablets and phones) and you already have vulnerabilities related to running both stacks even if your ISP does not offer IPv6. You might as well understand the transition issues and the existing IPv6 traffic. Get used to breaking the new picture down. Develop plans to analyze, document, isolate, …protect based on understanding IPv6. The detailed breakdowns of the issues, the RFC references, the byte-by-byte explanations of what happens under the hood are packed into “IPv6 Essentials.”
The book is a challenge but it is worth it, especially for Security engineers, consultants, and developers who need to understand what is going on at the byte-level. Ms. Hagen explains the issues, ties in the RFCs, diagrams the structure of the packets and extensions, provides examples of network captures and protocol analysis, and provides the insight that you need to continue on your own.
Overall I am satisfied with the book. It has a good combination of details and coverage on this topic, which is sufficient for required IPv6 knowledge needed in my new function at work.
You learn how stupid IPv6 is and how stupid IPv4 is. You get acres and acres of excuses of how stupid it is like "they just didn't know" but those excuses are bogus. IPv6 is just as insecure and has NO more eye towards security than IPv4 yet it was developed way after security had been proven to be a major concern.
They come up and effectively say that they have enough IPv6 addresses to uniquely address every grain of sand and they will solve all of IPv4s problems. Then they say "but you don't really wanna do that because its not secure". So they develop concepts just like IPv4 has but by different names. It is the classic "not invented here" syndrome.
All of the problems IPv6 claims to address were addressed by IPv4 before IPv6 even came out. That is why the adoption is so slow. It offers no advantages and lots of disadvantages. Seriously... the people who developed IPv6 should do the Thelma and Luise move and drive their car off a cliff.
The book itself is also very poorly done. It is not a reference nor a tutorial. It is a lot of ego and boosting about how great IPv6 is and then excuses about how that statement if blatantly fraudulent. This is definitely not the Steven's equivalent for IPv6.
My suggestion is just surf Wikipedia for the particular concepts that you need. You will end up doing that anyway.
Rechercher des articles similaires par rubrique
- Livres anglais et étrangers > Computers & Internet > Networking > Data in the Enterprise
- Livres anglais et étrangers > Computers & Internet > Networking > Home Networks
- Livres anglais et étrangers > Computers & Internet > Networking > Intranets & Extranets
- Livres anglais et étrangers > Computers & Internet > Networking > Networks, Protocols & APIs