An IPv6 update - NTP, DHCPv6 and connectivity

| | Comments (5) | TrackBacks (0)

I wanted to post a few IPv6 updates since my last post.

The NTP pool project has been working to add IPv6 support for some time. This month, they've added partial IPv6 support. Hopefully by year's end they'll have full IPv6 support. Several OSes and NTP appliances already have IPv6 support, so there's a fair bit of infrastructure that could support this now.

Speaking of NTP, the IETF's NTP working group is working to define IPv6 NTP options for DHCPv6. The current draft of that spec has received some criticism, claiming that its redundant with the current SNTP option. I hope that is resolved at the next IETF meeting in a few months.

Speaking of DHCPv6, Microsoft has fixed several DHCPv6 bugs in the beta of Windows Server 2008 R2. This should significantly improve interoperability with Unix/Linux clients.

Several North American universities and R&E networks obtained IPv6 allocations in 2008. I pulled the list of allocations from ARIN and noticed some highlights:

* Arkansas Research and Education Optical Network
* Bryant University
* Bucknell University
* CENIC
* California Institute of Technology
* California Polytechnic State University
* Florida LambdaRail
* Furman University
* George Mason University
* Louisiana State University
* Lousiana Optical Network Initiative (LONI)
* National Center for Supercomputing Applications
* New York University
* Oregon State University
* Rutgers University
* South Dakota Board of Regents
* Stanford University
* Tufts University
* University of Alaska
* University of California, Irvine
* University of California, Office of the President
* University of California, San Diego
* University of California, Santa Barbara
* University of California, Santa Cruz
* University of Illinois
* University of Iowa
* University of Nebraska-Lincoln
* University of Pennsylvania
* University of Pittsburgh
* University of South Florida
* University of Wisconsin Madison
* Wheaton College
* Worcester Polytechnic Institute

Several of these allocations are already in use.

0 TrackBacks

Listed below are links to blogs that reference this entry: An IPv6 update - NTP, DHCPv6 and connectivity.

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

5 Comments

Ted said:

I've been beta-testing Windows 7, and while looking through the list of new features, I found some stuff about a new feature called DirectAccess, which seems to be a VPN-tunnel-like technology. However, it requires IPv6 connectivity (natively or via Teredo/6to4

Thought you might be interested.

http://technet.microsoft.com/en-us/library/dd367855.aspx

Bill Pier said:

Dang! I just recently pinged (no pun intended) the UC Irvine NACS (net folks) to request a delegation of IPv6 address space for the servers relating to the campus radio station.
They acted, at first, like I was crazy and then formally replied that "there are no plans for campus IPv6 rollout". WTF? This is major CA/USA educational institution with lots of "tech" and has been involved with Internet2, et. al. I'm just very frustrated and wondering how to ring their bell!

Derek Morr Author Profile Page said:

Bill,

Sorry to hear that. You should tell them that several of their UC peers already have IPv6.

These UC schools each have their own /32 from ARIN and are routing them:

* UC Berkeley (2607:f140::/32)
* UC LA (2607:F010::/32)
* UC Riverside (2607:F290::/32)
* UC Santa Barbara (2607:f378::/32)

UC San Diego has a /48 from Internet2.

Further, CENIC has native IPv6 support.

gps ntp said:

I have also been betatesting Windows 7, not quiet the DHCPv6 possibilites, but tweaking the NTP options. All works well (as on other versions of Windows).

I created an ntp server, while being connected to a local ipv6 network and everything worked liked charm (success in mantaining time with a local gps server)

Jane irresi said:

This was our first shot at providing network time synchronization to IPv6 hosts. This protocol was chosen for its simplicity. SNTP is very much like NTP in advanced GPS NtpServer, but less complex.

We have made a SNTP implementation which is "protocol independant" (it can use both IPv4 and IPv6). This implementation uses the Trimble Palissade GPS driver provided in the NTP distribution of David L. Mills.

After coding this implementation we went after the real NTP.

Leave a comment