IPv6 at Internet2 Joint Techs

| | Comments (2) | TrackBacks (0)
I just got back from the Summer 2008 Internet2 Joint Techs Workshop in Nebraska. There was a heavy focus on IPv6 at the workshop. The IPv6 Working Group announced its IPv6 Challenge. This is a challenge to Internet2 members to IPv6-enable several aspects of their networks. Joe Nasal from TNS participated in a very interesting panel discussion on campus IPv6 addressing plans (video here). Both Penn State and Stanford were on the panel. We both have a /32 from ARIN, but we've chosen to use them in very different ways. I found that rather interesting. As usual, DREN gave a useful update on their IPv6 deployment in the Department of Defense.

I gave a lightening talk on a quick way to IPv6-enable lot of DNS servers (slides here). Essentially, there is a "clustering" effect in DNS, where one server will provide authoritative DNS for three or four other domains. For example, UC Berkeley provides DNS for Columbia, UC San Francisco and UCLA. So v6-enabling that one server provides considerable extra benefit. If you map out these "clusters" in DNS, you get a list of the most beneficial servers to target. It turns out that by v6-enabling 11 extra servers, you would give 31 domains v6-reachable DNS. Put another way, that's 15% of Internet2 members, but requires upgrading only 1.5% of its nameservers.

In non-IPv6 news, there was a good DNSSEC talk from NIST. This was especially interesting in light of the recent Kaminsky DNS attack. Suffice it to say, there are still a fair number of hurdles to integrating DNSSEC.

0 TrackBacks

Listed below are links to blogs that reference this entry: IPv6 at Internet2 Joint Techs.

TrackBack URL for this entry: https://blogs.psu.edu/mt4/mt-tb.cgi/13000

2 Comments

MAIREAD MARTIN Author Profile Page said:

Derek, while you were gone we decided to scrap all plans to move to IPv6. I think Phil Devan was the one behind the decision.

Phil Devan Author Profile Page said:

Re Mairead's comment... Heck, at the rate the IT service providers around the University are deploying v6 capabilities, they may as well wait until v8 comes along. Or just wait until after v6 is really needed and then try to play catch up. Like trying to prepare for Y2K on January 1, 2000.
/end sarcasm

Leave a comment