On 10/24/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > > > I'm not so arrogant as to claim I am all-knowing. That doesn't help win > technical arguments. And although I can deal with my own educational > needs by plodding through RFCs and books etc., that doesn't help me find > a concise overview of the CURRENT state of the IPv6 art to recomment to > others, so that they too, can win technical arguments, or see the error > of their ways.
I think you hit the nail on the head with this one statement: "the CURRENT state of the IPv6". The real problem is that IPv6 is still evloving (closing the IPv6 working group non-withstanding). Thus new changes start to happen and new discussions about implementiaton occure all the time as people learn what works and what does not. Books takes months to write and more to publish - by the time they are in print the IPv6 world has moved on. RFCs are not much better, they also take months to get written, then can take years to be approved (the only one I was part of took more than 2 years from conception until approval). Maybe a wiki or other online / real-time solution would be best, but this will require someone to manage it and people who have a clue to monitor (moderate) it, and most of these people are either doing it or are working on improving it (i.e. writing RFCs).
-------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
