March 2013 archive
How do you know when a domain is failing DNSSEC validation? What if there was a way to let the broader industry know about these validation failures? The folks over at Comcast’s DNS team have been trying an experiment for a while in posting these DNSSEC validation failures publicly to Twitter at:
If you are a system/network operator deploying DNSSEC and want to be alerted when sites are found to be failing validation, following this Twitter account is one way you can get alerts.
I don’t know whether publishing domains failing DNSSEC validation via Twitter will really be a long-term solution to letting the wider industry know about domains that are currently failing validation, but I applaud Comcast’s DNS team for trying something different … and I do follow the account myself because I find the occasional tweets interesting to see.
Looking for an interesting new weekend project? Are you interested in devices for the “connected home” or the “Internet of Things?” Have you been automating your home or building sensor networks? Do you like experimenting with hardware platforms like Arduino or the Raspberry Pi?
Would you like to potentially win $10,000 USD?
If so, check out the IPSO Alliance’s “IPSO Challenge 2013” where the About page explains the challenge:
The IPSO (Internet Protocol for Smart Objects) Alliance is sponsoring a worldwide challenge to showcase the use of the Internet Protocol (IP) in sensor/control and M2M applications enabling the Internet of Things (IOT). IPSO Challenge 2013 is a competition promoting the development of Smart Objects which use the Internet Protocol. Just 30 years after the official adoption of the TCP/IP networking protocol, nearly 10 billion devices can connect to the Internet; and before the end of the decade, that number is forecast to nearly triple. Over the coming years, the vast majority of newly connected devices won’t be computers, tablets, or smartphones, but will be intelligent embedded devices participating in the Internet of Things (IoT).
The deadline to submit a written proposal is coming up soon on APRIL 5, 2013, using the submission form at the bottom of the main IPSO Challenge 2013 page. Semi-finalists will be notified soon thereafter and will need to submit a functional prototype by May 17, 2013. Ultimately winners will be chosen who will receive $10,000, $5,000 and $2,500. More details about what you need to do can be found on the About page for the contest.
Why are we writing about this contest here on Deploy360? Simple. The reality is that to get the massive scale being considered for the “Internet of Things” many implementations will need to use IPv6.
We were in contact with the people behind this IPSO Challenge 2013 and they are very definitely interested in receiving IPv6 entries.
So we’d like to encourage any of you developers out there to submit some IPv6 proposals! It would be great if some of the semi-finalists or finalists were entries working over IPv6.
So… if you like working with these kind of projects, do check out the IPSO Challenge site and submit your ideas!
If you found this post interesting or useful, please consider either:
- following me on Twitter;
- adding me to a circle on Google+;
- following me on App.net
- subscribing to my email newsletter; or
- subscribing to the RSS feed
We noticed that our friends over at APNIC are offering DNSSEC training in Ulaanbaatar, Mongolia, from April 1-3 and since, well, we’ve never written anything about Mongolia on this site before, we figured we ought to do so!
The course is APNIC’s DNS/DNSSEC workshop and sounds like an excellent offering. Given that APNIC was recently tweeting about this event we are assuming there is still space available.
The training session is one in a whole series of training workshops APNIC is offering on topics including DNS/DNSSEC, IPv6, Routing and more.
Given that Mongolia’s .MN TLD is signed with DNSSEC (as shown in the list of signed TLDs), we’re looking forward to seeing more signed .MN domains and more usage of DNSSEC in Mongolia after this workshop!
The Jitsi audio/video softphone and messaging client supports both IPv6 and DNSSEC. How did it get started with IPv6 support? Why did it add DNSSEC? What value does DNSSEC add to VoIP and IP communications? We first wrote about Jitsi’s DNSSEC support almost a year ago, but earlier this month at IETF86 I had a chance to sit down with Jitsi project lead Emil Ivov and ask him these questions and much more:
Jitsi is available for Windows, Mac OS X and Linux from: http://jitsi.org/ It used to be called the “SIP Communicator” but when they added support for XMPP (Jabber) and XMPP/Jingle back in 2011 they changed the name to be Jitsi.
Given my own personal interest in VoIP / IP communications, I’m planning to write a bit more about Jitsi as I get a chance to do so. If any of you use Jitsi and create any screencasts about its IPv6 or DNSSEC support – or write up any articles about those capabilities – please do let us know as I’d like to include more on our site about this great project.