July 28, 2014 archive

Recovering From The Wonderful Insanity of IETF 90

Today is the Monday after an IETF meeting.  For those who were following our “Deploy360@IETF” and other posts last week or are following us on social media, you know how insanely busy it was for us all. Today I think many of the 1200+ “IETFers” at IETF 90 in Toronto last week are getting back to our respective offices all around the world and “decompressing” from the wonderful craziness that makes up an IETF week.

Mostly, we’re just trying to recover from the pace.  Figure out what it is we need to do next… and start doing that.

There are so many action items I wrote down.  So many articles I want to write for here on Deploy360 and on other sites.  So many Internet Drafts I want to review.  So many drafts I want to write.

It will take a while.

Right now I find myself still caught up in all that happened.  IETF 90 was an excellent event.  Extremely productive on issues around IPv6, DNSSEC, TLS, routing security … and more. Like all IETF meetings it is a study in contrasts.  The large plenary sessions seating 1,000+ people:

ietf90-plenary-450

And the smaller, more intimate working group rooms that seat far fewer:

ietf90-wes-450

It’s the long microphone lines:

IETF microphone line

… and the passionate discussions that sometimes happen at those microphones:

IETF 90 microphone discussion

It was presenting our work in one session:

Jan zorz presenting

… and sitting in one of the most ornate conference rooms I’ve ever been in (owing apparently to the history of the Fairmont Royal York):

IETF 90 ornate ballroom

It was going to completely packed sessions at 9:00am in the morning:

ietf90-dnsop-packed-450

… and being amused to find that the Terminal Room contained an actual terminal :

ietf90-terminal-450

It was smiling when I saw this slide (in an excellent presentation about calculating where to locate authoritative DNS servers for a TLD registry operator) and realizing that my own knowledge of some types of mathematics is so rusty that my brain didn’t think of this as “simple”:

simple example

… and it was laughing when I saw that some IETFer modified the Fairmont Royal York’s warning that long dresses could get caught in an escalator to be a bit more appropriate for the audience:

warning - long beards

It was getting up for 7:30am breakfast meetings and not getting back to my hotel room until 11:30pm and then realizing on Thursday evening that I hadn’t left the hotel since Tuesday evening….  and it was going for a 6:00am run with 3 other IETFers on Friday morning:

Morning run in Toronto

It was a crazy, busy … and wonderful week.  Full of all the conversations, discussions, arguments, presentations… and random meetings… that move the open Internet standards along. Full of the amazing people that make the IETF the truly amazing organization that it is – all gathered together, and attending remotely… all trying to make the Internet work better!

And now… as we all return to our homes and offices… the next step is to translate all the work that happened last week into actions over the weeks and months ahead…

 

Code.DanYork.Com Now Back Available Over IPv6

worldIPv6launch-256pxAfter a Reddit thread started up that briefly referenced a 2011 post I wrote about adding IPv6 to Node.js apps, I was contacted by a Redditor who was surprised that my site wasn’t available over IPv6!

HUH???

I was surprised, too, because this site is hosted on a dual-stack server at Hurricane Electric and has been accessible over IPv6 since June 7, 2011, right before the World IPv6 Day event.

But in checking into it… there was no AAAA record in DNS for “code.danyork.com” that would point to the server, so the report was indeed accurate. For regular users this site was not available over IPv6.

It turned out to be one of those system administration issues that can bite you.  A month or two ago, TypePad, the provider I still use for my personal DanYork.com site, experienced a severe DDoS attack that took many sites offline.  They recovered but in doing so changed the way that sites were referenced a bit.  I had to switch to using a CNAME instead of an IP address as I had been doing.  The problem there is that due to the “no CNAME at zone apex” rule of DNS, I could no longer use just “http://danyork.com” – I would have to switch to using “http://www.danyork.com/”.

The episode highlighted to me, though, the need to be sure I have “Test over IPv6” in my list of things to check after making any major changes to any of my sites!

I didn’t want to switch and so I moved the DNS for “danyork.com” over to CloudFlare to make use of their “CNAME Flattening” so that I could still use “danyork.com”.

However, in moving the DNS info from my previous DNS hosting provider to CloudFlare, I messed up.  I didn’t bring across the AAAA record for code.danyork.com.  Also, very bizarrely, I didn’t have the “Automatic IPv6” setting enabled for danyork.com – even though it is now supposed to be on by default for all new domains.

So the fix was simple – I added the AAAA record for code.danyork.com, and I also flipped the switch on the Automatic IPv6 gateway.  Now both code.danyork.com and danyork.com are fully available over IPv6.

FIR #766 – 7/28/14 – For Immediate Release

Intro: Two interviews and an FIR Live are coming; Quick News: Scott Monty joins SHIFT, Reddit Live is open, Facebook's mobile future, relevance is key to native advertising; Ragan promo; News That Fits: PRSA report on social and emerging media in PR practice, Michael Netzley's Asia report, robot-written news has arrived, Media Monitoring Minute from CustomScoop, listener comments, Dan York's Tech Report, the top social media marketing trends of 2014, Igloo Software promo, the last week on the FIR Podcast Network, the slow adoption of internal social media; music from Winter Harvest; and more.