The APNIC Executive Council has endorsed the three proposals reaching consensus at the APNIC 44 Open Policy Meeting in Taichung, Taiwan.
The use of IPv6-only networks at IETF 100 is allowing attendees to troubleshoot IPv6 issues during the meeting.
An idea has been floated at the IETF 6man working group regarding the customer end of IPv6 addresses.
The ISOC Fellowship to the IETF introduces representatives from a diverse range of fields to the growing need to consider IPv6 in their planning and decision-making processes.
Google has fixed an IPv6 fragmentation handling problem in their Public DNS Service.
Guest Post: Three well-known vendors share their thoughts on how to improve support for IPv6 on customer equipment.
Study meetings help non-technical people working in the Japanese communications industry to understand IPv6.
Guest Post: Why aren’t the good guys ahead of the bad guys when it comes to detecting covert channels and exploiting known vulnerabilities?
Learn how to use a raw socket interface in IPv6 to generate a UDP-based DNS server and a TCP-based HTTP(S) server that allows the application to exercise direct control over packet fragmentation.
Guest Post: Updated results from the IPv6 deployment survey as presented at APNIC 44.