On 21 jul 2010, at 05.06, Seiichi Kawamura wrote: >> >> Still, while I am somewhat agreeing with a standardized measurement of IPv6 readiness in an >> AS/ISP I think that it's more useful to work on measuring actually deployed >> clients that can be observed and publishing that data. Even better would be >> standardized quality measures of these deployments. There are many drawbacks >> on doing this based on only observed data at a server side ala looking at >> a web-server, but as Lorenzo and Google have shown in many presentations, >> at least it gives data to do a risk assessment for a service operator. > > I think that would be interesting work too. > > What I hear from small ISPs these days is > that they want a minimum list of things to do to be > able to communicate with the IPv6 world. > > Bringing an ISP to be fully dual stacked will take years. So I suggest that minumum is - PA Block - Customer Assignments - DNS resolvers IPv6 capable - Native (v6 only or dual-stack) upstream connection - SMTP relay / Submission IPv6 - IMAP/POP IPv6 With that you can run on v6. The last two I am not to determined on, but then a gradually increasing list of services that is supporting IPv6 - Native transport to customers - Web - Jabber - SIP - etc > I think a minimum guideline would be useful (is there one out there already?), and Not that I know of. Best regards, - kurtis -
Attachment:
PGP.sig
Description: This is a digitally signed message part