19:00 Central European Summer Time
18:00 British Summer Time
13:00 US Eastern Daylight Time
10:00 US Pacific Daylight Time

The dial-in number will be +1 972 756 9798 with a conference PIN  of 009444.  Additional country-specific dial-in numbers can be found in the email announcement.

In the agenda announcement from Rifaat Shekh-Yusef the items to be discussed include:

1. draft-klatsky-dispatch-ipv6-impact-ipv4

• Discuss the feedback and how to continue the discussion on the DISPATCH mailing list
• *Talk about the options for moving the document forward (AD sponsor vs. new WG)

2. Discuss the text for two new sections that Mohamed Boucadair provided.
(See “IPv6 Implementation Guidelines” & “IPv6/IPv4 Interworking Function: Avoid IPv6 address Leakage?” in the attached document)

• Should these be added to this draft, which means that we are extending the scope of this draft? or
• Should we create a separate draft?

3. Happy Eyeballs

• draft-yusef-dispatch-happy-eyeballs-sip-00-02.txt
• With UDP

4. Sunset4 WG
We received an email of interest from Marc Blanchet, co-chair of sunset4 wg, stating that this work is relevant to the work they are chartered to do.
Marc suggested that we socialize this work with the sunset4 wg, which I did already. He also suggested that we present this work during the coming IETF in Berlin.

We’re delighted to see this ongoing work within the SIP Forum and that several documents are now under consideration.  We do encourage anyone interested in helping SIP work over IPv6 to participate in this call and to join the SIP Forum “IPv6″ mailing list for this task group.

For more information about VoIP / SIP and IPv6, please see our page on IPv6 and IP Communications.

What I personally found even more fascinating was that when I went to the World IPv6 Launch measurements page and clicked on the “IPv6 deployment” column header twice to get a list sorted by the highest percentage…

Google Fiber came out as #1 with a staggering 77.55% of all observed traffic being over IPv6:

To be clear, let us remember how these statistics are collected.

Google, Facebook and Yahoo all measure the amount of IPv6 traffic they are seeing coming in to their respective sites and services from all the participating networks. (You can read more about their specific techniques at the bottom of the Measurements page.) That information is then averaged and presented on the Measurements page for each ISP.

In this case 77.55% of the traffic received across those three measurement providers from the Google Fiber network was all over IPv6.  Amazing!  Congratulations to the Google Fiber team!

P.S. It’s also interesting to note the growth of many networks versus where they were when we last wrote about the statistics in April. For instance, the top 10 networks sorted on observed percentage of IPv6 are now all over 30%.

We’re planning to have our first in-person meeting on July 28th, 2013, in Berlin (most likely in the afternoon, between lunch and the IETF welcome reception). The venue would be either the IETF venue (InterContinental Berlin), or some nearby hotel/room (to be confirmed soon).

We’re planning to have some presentations (which MUST be accompanied with code ), and might also have an IPv6 mini-hackathon (i.e., work on code, test implementations, try stuff).

Fernando Gont has asked people who are interested in attending to complete a short survey so that he can know how many people are planning to attend.

If you are interested in IPv6 security, I have found the IPv6 hackers mailing list to be a useful list to monitor as a good number of IPv6 security researchers do participate in the list.  You can see from the archives some of the topics that are discussed. It is open for anyone to subscribe.  There is also a LinkedIn group but as Fernando notes he created the group to help people connect on LinkedIn not as a discussion forum – discussion happens on the email list.

I’d suggest another useful resource for people reading that article would be SURFNet’s white paper about enabling DNSSEC validation in DNS resolvers as that paper provides step-by-step guidance to enabling validation in BIND, Unbound and Windows Server 2012.

I’d also note for people wanting to experiment with DNSSEC validation, Google’s Public DNS servers do now support DNSSEC and so you can at least temporarily point your system to Google’s servers to try out validation.  As we’ve also noted in the past, anyone who is a Comcast subscriber in North America also has DNSSEC validation happening by default, as do people using many of the ISPs in Sweden, Brazil and the Czech Republic.

As I noted at the beginning, the article covers the validation side of DNSSEC, but for that to really work we also need to get more domains signed with DNSSEC.  I would encourage people to look at our tutorials on how to sign your domain using common registrars – and to ask your registrar when they will let you use DNSSEC if they are not on the list of DNSSEC-capable registrars maintained by ICANN.

Again, it’s great to see InfoWorld covering DNSSEC and I do hope they’ll provide more such articles in the future.  If we can get DNSSEC deployed more widely we’ll go very far in upgrading the security of the Internet!

P.S. I was also intrigued by Grimes’ link to this video of a DNSSEC app for Android from back in 2011.  It looks like a basic browser to check the DNSSEC status of sites.  I may have to investigate a bit more..

Note that the sites below are domain names and websites with either good or deliberately mis-configured DNSSEC signatures.  If you are looking for web sites offering tools or services where you can test the status of DNSSEC, please see our list of DNSSEC tools.

Sites With Good DNSSEC Signatures

Today there are millions of domain names out there with valid DNSSEC signatures and so you have many, many options.  Two of the domains you can use to obtain valid signatures are:

• internetsociety.org
• ietf.org

If you are testing web validation, the addresses are:

• http://www.internetsociety.org/
• http://www.ietf.org/

Sites With Bad DNSSEC Signatures

The more interesting tests to perform are with domains that are bad and will generate an error in your application or service.  The following sites have been deliberately mis-configured with bad DNSSEC signatures:

• dnssec-failed.org   (operated by Comcast)
• rhybar.cz        (operated by CZ.NIC)

On the web, they are:

• http://www.dnssec-failed.org/
• http://www.rhybar.cz/

The DNSSEC Tools site at http://www.dnssec-tools.org/ also provides a test in that if you connect to the site and do not perform DNSSEC validation you will see an image appear on the page telling you that you are connecting insecurely.

Adding More Sites

If you have a site with an interesting DNSSEC configuration you think would be useful for others to use in testing, please contact us so that we can consider adding it to this list.

Please note that our list of DANE test sites includes sites and domains that are also signed with DNSSEC.

Here’s an overview of the agenda and speakers:

• Opening Remarks
  • Dan York (Internet Society)
• Internet Society Canada Chapter
  • Glenn McKnight (Internet Society Canada)
• Why Implement DNSSEC?
  • James Galvin, Afilias Limited
• Deploying DNSSEC: A .CA Case Study
  • Jacques Latour (Canadian Internet Registration Authority)
• IPv6 Deployment Update: Where Are We Today?
  • Tim Winters (University of New Hampshire Interoperability Lab)
• IETF Update
  • Dan York (Internet Society)
• Best Current Operational Practices: A Global Perspective
  • Jan Žorž (Internet Society)
• Panel: Improving The Resilience And Security Of The Internet’s Routing
  • Moderator: Dan York (Internet Society); Panelists: Merike Kaeo (Internet Identity), Andrew Sullivan (Dyn, Inc.)
• Closing Remarks and iPad Raffle Drawing
  • Dan York and Paul Brigner (Internet Society)

We are also very excited to have Afilias as a sponsor for ION Toronto!

We continue to build on the success of our past events, where we’ve had industry experts from across the globe answer your specific deployment questions and provided a mix of high-level strategic discussions, real-world deployment experiences, and hands-on technical training. ION Conferences also help us get your direct feedback on what else you need to get started so that we know what new resources to add to the Deploy360 site next.

ION Toronto is FREE to attend, including the Welcome Lunch and Welcome Reception. Choose “ION Only” from the Registration page for this option.

If you would like to attend the full three-day Canadian ISP Summit event, you are entitled to use code “ISOC_2013″ for a $100 discount on an all-inclusive registration pass.

If you’ll be there, please let us know by joining the Facebook event, talking to us on Facebook, Twitter, or Google+ (using the hashtag #IONConf), or emailing us.

If you can’t be there in person, we’re working on a way to webcast the event and will provide more information later. After the event, please check the ION Toronto page to find the featured presentations and other highlights. We can’t wait for this event and we look forward to revealing the insights shared by industry experts.

Register today!

(P.S. Announcement coming soon about the other ION Conference we have planned for 2013. Stay tuned!)

If so, and if you are planning to attend ICANN 47 in Durban, South Africa, the program committee (of which I am a member) for the DNSSEC Workshop at ICANN 47 is actively seeking proposals to include in the workshop.  As noted in the Call For Participation, we are seeking presentation ideas on topics such as:

• DNSSEC Activities in Africa
• The Operation Realities of Running DNSSEC
• DNSSEC and Enterprise Activities
• When Unexpected DNSSEC Events Occur
• Preparing for Root Key Rollover
• DNSSEC: Regulative, Legislative and Persuasive Approaches to Encouraging Deployment
• DANE and Other DNSSEC Applications
• Use of DNSSEC in the Reverse Space

Please see the Call For Participation for more details.

We are also open to presentations related to DNSSEC that don’t fit exactly in one of these listed topics.  We’ve already got a great list of presentations but we still could add a few more.

You can view the program and presentations from the ICANN 46 DNSSEC Workshop in Beijing to understand the kind of presentations we are seeking. I’ll note that we’re changing the format a bit for ICANN 47 to have fewer presentations for longer periods of time. We felt it was a bit rushed in the Beijing workshop.

If you are interested, all you need to do is send a brief description (1-2 sentences) of your proposed presentation to dnssec-durban@shinkuro.com, ideally by today, June 10th, as we are working to finalize the program to publish it on the website.

Thanks – and we’re looking forward to another great event in Durban!  If you are not able to attend in person, the event will be streamed live and also archived for later viewing.

He also touches on an effort to create a “fifth star” of IPv6 RIPEness that would measure whether LIRs are providing content over IPv6 and providing IPv6 access to end users. He also goes on to talk about their measurements showing the percentage of networks announcing IPv6 prefixes into the global routing system – and provides an excellent chart showing the growth (you’ll need to read the post to see it).

It’s great to see these measurements and statistics from RIPE NCC that coincide so well with the information we’re seeing out of other IPv6 statistics sites, including the World IPv6 Launch measurements.

• IPv6 Launch Day – One Year Later – In this Enterprise Networking Planet piece, Sean Michael Kerner interviewed the Internet Society’s Phil Roberts to catch up on what has changed in the last year.
• Happy IPv6 Day: Usage On the Rise, Attacks Too – The good folks at CloudFlare gave some stats around the IPv6 traffic they are seeing and also detailed a couple of attacks they have seen over IPv6. They also provided their guesses as to when we turn off IPv4 on either a linear or exponential case. Needless to say, we hope it’s closer to the exponential side of things!
• IPv6-Enabled Municipal WiFi Network in Douglasville, GA – While we don’t usually write about news releases related to IPv6 products or services, we did think this was a very cool milestone – the deployment of an IPv6-enabled municipal WiFi network in Douglasville, GA. From the news release: “The municipal WiFi network covers about 60 acres collectively, including downtown Douglasville, making it one of the largest public WiFi networks in Georgia.”  Apparently this was paid for by Google as part of its community outreach program and the company doing the deployment, Network Utility Force, also has  a TV interview online (and photos) where they explain the project more.  It would be great to see more of these municipal WiFi networks launch with IPv6 from the beginning!
• IPv6 in action: How Mythic Beasts does it - This piece on TechRepublic provides a case study in how Mythic Beasts, a hosting provider in the UK, has set up their systems to work over IPv6. Great to see technical pieces like this.
• Telefonica Pushes Ahead with IPV6 Support in Peru - Telefónica indicated that it has selected Peru as its first country for a wide IPv6 deployment. They also issued a press release reaffirming their support for IPv6 and stating that they are leading IPv6 deployment in Latin America.
• IPv6: Less Talk and More Walk – Over on CircleID, Bruce Sinclair had an interesting post about how they had tracked the “buzz” around IPv6 across tweets, blogs and news stories and found that there was less buzz and more just getting IPv6 done.
• Future Internet gets boost, courtesy of IPv6! – The European Network and Information Security Agency (ENISA) had a nice short post out but what I enjoyed was their note that ENISA was the first EU agency to adopt IPv6 way back in 2009!

Plus a great article from our friends at RIPE Labs that we’ll cover separately.

All great to see!

P.S. And while we generally don’t write about ads here, I will give a shoutout to Fluke Networks for posting to Google+ the only advertisement I’ve seen today that specifically calls out “World IPv6 Day”.  (Note to Fluke: We’ve only used “Day” back in 2011, but hey you’re not alone in that given other articles out there.)

P.P.S. And if you are looking to get started with IPv6, please check out our IPv6 resources, particularly our new tutorial on making content available over IPv6.

On this, the 1st anniversary of World IPv6 Launch, we are delighted to publish a new tutorial on this exact topic.  Titled simply “Making Content Available Over IPv6“, the new document is available at:

http://www.internetsociety.org/deploy360/resources/making-content-available-over-ipv6/

The tutorial is written by Sander Steffann, who has a great amount of experience with IPv6, and covers the steps for how you can make your content available over IPv6 using:

• Native IPv6
• Using load balancers
• Using IPv6-to-IPv4 proxy servers
• NAT64

He provides some excellent diagrams and examples of configuration files and assesses both the benefits and drawbacks of each solution.

We encourage you to take a read through this document and please do let us know if this helps you make your content available over IPv6!