The notion that DNSSEC has had a lot of problem (and you take "the widest test" as data for it!) it not true..SE has had _one_ major problem with DNSSEC and that was due to a bug in BIND which caused some equipment to fail. (The bug was that BIND set the AD bit by mistake, it was promptly fixed.)
Fact is that we have had no problems since, and we now expect a fast rollout. The major problem now is that there is still a lack of tools, not only for TLDs, but also hosting companies and other large nameservice providers.
I have not seen any large deployment of DNSCurve, and I know for a fact that NSD, BIND, Unbound and other major DNS software does not implement DNSCurve...
I was also in this meeting. One of the following comments (from whom exactly, I don't remember) was that all of the DNS namespace will never be signed using DNSSEC, there will for a very long time if not always, be gaps in the namespace that won't be signed at all.
There are also other reasons to run an unsigned zone for shorter times, but I won't go into details about that.
So we should probably strengthen the DNS protocol in other ways than using DNSSEC, but those improvements must not be ugly hacks.
I installed it a couple of hours ago, without even realizing it was a new release. I have been playing around with both fedora core 3 and Debian unstable on this Thinkpad X40 just before, and I am deeply impressed with the work they have put into this Ubuntu-release.
The only things remaining is getting some sort of wifi roaming-stuff working, and the dualhead. The X40 link on the documentation wiki is broken.
Nothing in the DNS infrastructure need to be upgraded. There is only us-ascii in the zones. BUT, you have to upgrade your applications in order to read them the names the way they are supposed to read, otherwise you will end up with www.xn--rksmrgs-5wao1o.se instead of "www.raksmorgas.se".
There are _so_ many applications using the domain name system that feeding UTF-8 through it will break most of them. Except for perhaps Internet Explorer.
The registries using UTF-8 (most notably.NU) are running IDN in parallell with UTF-8 now.
The Swedish registry is only using IDN. The reason for that is that UTF-8 in DNS is not an internet supported standard at all.
http://www.xn--rksmrgs-5wao1o.se/ will work if you are using a recend Mozilla. (Slashdot should upgrade to at least ISO-8859-1 or UTF-8... I couldn't write raksmorgas.se correctly.)
Microsoft are extremly slow in supporting IDN, and will probably not launch it until next OS release which is in 2006... There are plugins from Verisign.
Do a good thing, release an open source plugin for MSIE.
What exactly do you mean by "proven technology"? New software build on old technology (like in the science sense), that has been proved to be working. This is exactly like what Ogg Vorbis does, but without building it on top of patented science, which is a very Good Thing.
What you should do is to compare the codecs with your own ears, not just sit and look at how old the technology you use is.
Here is the quote sent through the mozilla announcement list to prove my point:
"The Mozilla 0.6 release does not contain many of the features or bug
fixes which can be seen in our current daily builds. Our most recent
daily builds are available at
http://ftp.mozilla.org/pub/mozilla/nightly/lates t/ "
This version is not a Milestone release, it is a Netscape/Mozilla compatibility release, for developers doing stuff that is supposed to be compatible for both Mozilla and Netscape versions.
I don't like Pike, but I definitely like the Roxen Webserver. It is also GPL, and I use it as much as I can. Roxen supports PHP4 now, and I like that better for web development.
Slashdot Mirror
.SE has had DNSSEC deployed for almost five years now. We should have found most bug by now...
You could use OpenDNSSEC from http://opendnssec.org/ ...
The notion that DNSSEC has had a lot of problem (and you take "the widest test" as data for it!) it not true. .SE has had _one_ major problem with DNSSEC and that was due to a bug in BIND which caused some equipment to fail. (The bug was that BIND set the AD bit by mistake, it was promptly fixed.)
Fact is that we have had no problems since, and we now expect a fast rollout. The major problem now is that there is still a lack of tools, not only for TLDs, but also hosting companies and other large nameservice providers.
I have not seen any large deployment of DNSCurve, and I know for a fact that NSD, BIND, Unbound and other major DNS software does not implement DNSCurve...
I was also in this meeting. One of the following comments (from whom exactly, I don't remember) was that all of the DNS namespace will never be signed using DNSSEC, there will for a very long time if not always, be gaps in the namespace that won't be signed at all.
There are also other reasons to run an unsigned zone for shorter times, but I won't go into details about that.
So we should probably strengthen the DNS protocol in other ways than using DNSSEC, but those improvements must not be ugly hacks.
So when can I reach Slashdot over IPv6?
The .SE-domain is running a signed zone since a couple of months as the first TLD in the world. Here is all you need to know.
Yes, but that will probably never work. I don't expect it to anyway.
I installed it a couple of hours ago, without even realizing it was a new release. I have been playing around with both fedora core 3 and Debian unstable on this Thinkpad X40 just before, and I am deeply impressed with the work they have put into this Ubuntu-release.
The only things remaining is getting some sort of wifi roaming-stuff working, and the dualhead. The X40 link on the documentation wiki is broken.
I agree with this. OpenVPN even has some nice little user friendly tools to access the VPN from Windows, etc.
http://openvpn.sourceforge.net/gui.html
Nothing in the DNS infrastructure need to be upgraded. There is only us-ascii in the zones. BUT, you have to upgrade your applications in order to read them the names the way they are supposed to read, otherwise you will end up with www.xn--rksmrgs-5wao1o.se instead of "www.raksmorgas.se".
There are _so_ many applications using the domain name system that feeding UTF-8 through it will break most of them. Except for perhaps Internet Explorer.
.NU) are running IDN in parallell with UTF-8 now.
The registries using UTF-8 (most notably
The Swedish registry is only using IDN. The reason for that is that UTF-8 in DNS is not an internet supported standard at all.
http://www.xn--rksmrgs-5wao1o.se/ will work if you are using a recend Mozilla. (Slashdot should upgrade to at least ISO-8859-1 or UTF-8... I couldn't write raksmorgas.se correctly.)
Microsoft are extremly slow in supporting IDN, and will probably not launch it until next OS release which is in 2006... There are plugins from Verisign.
Do a good thing, release an open source plugin for MSIE.
What exactly do you mean by "proven technology"? New software build on old technology (like in the science sense), that has been proved to be working. This is exactly like what Ogg Vorbis does, but without building it on top of patented science, which is a very Good Thing.
What you should do is to compare the codecs with your own ears, not just sit and look at how old the technology you use is.
Here is the quote sent through the mozilla announcement list to prove my point:
s t/ "
"The Mozilla 0.6 release does not contain many of the features or bug
fixes which can be seen in our current daily builds. Our most recent
daily builds are available at
http://ftp.mozilla.org/pub/mozilla/nightly/late
This version is not a Milestone release, it is a Netscape/Mozilla compatibility release, for developers doing stuff that is supposed to be compatible for both Mozilla and Netscape versions.
I don't like Pike, but I definitely like the Roxen Webserver. It is also GPL, and I use it as much as I can. Roxen supports PHP4 now, and I like that better for web development.