On 24-okt-2007, at 14:21, <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]> wrote:
Was it, or any of the other books on your list, vetted by enough
eyes to be trusted?
Books have technical reviewers before publication and reviews in
publications and on sites like amazon.com after publication. So I
wouldn't assume that their quality is necessarily worse than an RFC,
but if it is, this is usually something that you can easily find out.
Books written by IPv4 experts are particularly problematic, because
how
do we know that the author is not blinded by invalid IPv4 assumptions?
So which of those books is written by an "IPv4 expert"? :-)
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.
Writing a good book is hard and takes a lot of time. I assume the
same goes for writing a good RFC. Few people get rich from writing
books about network protocols, but at least you can expect to see
SOME money. Writing RFCs purely for the benefit of the community on
the other hand won't make you a dime. So I'm not surprised there
aren't any RFCs that are useful guidelines to people new to IPv6.
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?
The IETF can't do anything unless someone volunteers to do the work,
so answering in the affermative would be an empty gesture.
--------------------------------------------------------------------
IETF IPv6 working group mailing list
[email protected]
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
