Alexandru Petrescu wrote: > A book I'm pondering over, buying it maybe one day: > > IPv6 Advanced Protocols Implementation > at Morgan-Kaufmann of Elsevier > http://tinyurl.com/2cetvh
Did not see that one before, but I see one important name on the book, Jinmei, and as such indeed, if you are looking at actually implementing an IPv6 stack yourself, it most very likely will not be a bad book to read ;) /me puts it on the 'add to collection list' [EMAIL PROTECTED] wrote: >> Also online: http://www.ip6.com/us/book/index.html (first hit >> for google >> (ipv6 book) btw. > > I've already mentioned that one on http://www.getipv6.info but I can't > say that it is recommended unless I learn more about it. > > I trust Brian Carpenter's recommendation due to his history with the > IETF and I think I trust the French book because it is a wiki and Mohsen > claims it is being kept up to date. Well, you can also simply accept his recommendation based on the mere fact that a lot of people have and use the books by Silvia Hagen and she has been giving IPv6 lectures for quite a few years already, she definitely knows what she is talking about. But so go for the other books. The books I noted (thus hardcopies, not the web one) are all written by people who actively use IPv6, most have implemented IPv6 in a large environment and have participated in the IETF and also the various RIRs. As such they definitely know what they are talking about. Next to that they also have technical reviewers and nowadays in the age of the Internet there are sites where reviews are given about the books and you can base your opinion on that too. > I'm not sure that I trust the other > books in your list, especially since you reference Huitema's book which > is part of the problem. As I stated, it is the "old bible", it is from 1996 or so after all. As such it is FAR from current but still it is a great book, just a wee bit outdated. If you have an IPv6 book collection that that and also "IPng Internet Protocol Next Generation" by Scott Bradner and Allison Mankin is definitely a must on the shelf. The other books are all quite pretty recent (max 2 years old) and thus indeed contain more up to date information. Books need to be edited and published which takes quite some time and people are not going to redo them everyday. Though, as I noted, most of them have websites which will contain errata fixups and also new chapters or extra material to cover that gap though. Run into a bookstore, browse through them and then decide. It is also a matter of taste and what you want. [..] > Indeed. I'm not looking for a book at all, but an RFC which summarizes > the current state of IPv6 that can be used as an authoritative source to > win arguments with people who are still stuck in IPv4 thinking. Ehmm, you are trying to make an argument against people while you actually don't know what you are talking about? :) Really, that won't work. A summary won't help there either, you will need to know really what you want to talk about. Do it, then you know and then you can win arguments. That is if your only target is to always "win" in those things, sometimes the other party actually makes a very completely valid point... > A lot of mistakes are being made because too many people think of IPv6 > as IPv4 with more bits. Is it anything else than? s/ARP/ND+DAD/, s/subnetting/\/64/ and a few others, but there is not much else in the most basic parts that is really different. Then again, if you play with it too long you don't really notice a difference anymore I guess ;) >> Practical experience is of course the real way to learn to >> use it. Books are good references though and tend to read >> easier than RFCs. > > It takes years to get the practical experience, and even more years to > unlearn bad habits. As for readability, an overview RFC is not likely to > be as hard to read as a protocol specification. The big question is: would they then suddenly read it? No, they would still take a book, ask their friend/colleague. > The real issue here is, does the IETF's responsibility end with giving > the vendors the specs that they need, or does the IETF have a > responsibility to RIRs, network operators, enterprise network managers, > and end users? IMHO, for protocols (thus IPv6, IPv4, POP3, IMAP etc etc) it ends at the vendors, as those have to implement a protocol. End-users (thus including network operators, who are not implementing the protocols themselves) should read a good book about the subject. Or actually, the vendor should be doing a good job of making it easy to use and provide adequate documentation. Though INPUT on those protocols, what can be better, what should change etc, thus operational input, is of course very welcome as they do have to use them, and if they don't use them, what is the point of making them in the first place. Greets, Jeroen
signature.asc
Description: OpenPGP digital signature
-------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
