Wasting time at Christmas by burning the site to the ground and starting over seems to be a tradition around here…
Wow, that year went quickly, on which more later.
I’d wanted to try my hand at brewing for a while, but was put off it by the (accurate) fear than ninety percent of the work was washing bottles and cleaning pots. Then, last winter, as a newly-minted father of a baby with an age measured in weeks, life consisted mainly of sterilizing bottles and not sleeping. I made an offhand comment to the effect that if I was going to spend so much time boiling glass I might as well make beer. Ariane gave me a starter kit, and a year later I’m about seventy liters in and think I have a reasonable clue what I’m doing.
I’m off to New York in a couple of weeks to present a paper at PAM (which I mentioned here, though sadly the flashy automated demo I was hoping to build was a bit optimistic). The question: “is it safe to turn on ECN on client machines by default, completing the end to end deployment of a simple fifteen year old protocol to give us a better way to signal network congestion than simply dropping packets on the floor?” The answer is: “define safe.“ Our key findings:
In German, there’s a word for an organization which takes its mission very seriously but is adorably incompetent at it: “Kaninchenzüchterverein” (lit. “rabbit-breeding club”). There’s another word for an organization which is bad at what it does because nobody cares: “Saftladen” (lit. “juice shop”).
The issues identified in of part one of this post led to yet another search for solutions to the problem of making (especially passive) measurement repeatable. Of course, this has been done before, but I took as an initial principle that the social aspects of the problem must be solved socially, and worked from there. What emerged was a set of requirements and an architecture for a computing environment and set of associated administrative processes which allows analysis of network traffic data while minimizing risk to the privacy of the network’s end users as well as ensuring spatial and temporal repeatability of the experiment. For lack of a better name I decided to call an instance of a collection of data using this architecture an analysis vault.
The key principle behind this architecture is if data can be open, it should be; if not, then everything else must be.
Part one of this post painted a somewhat bleak picture of the state of Internet measurement as a science. The dreariness will continue later this month in part two. And yet there seems to be quite a lot of measuring the Internet going on. It can’t all be that bad, can it?
In the back of the pantry at the house I grew up in in Memphis, there was always a stack of little plastic tubs of dried candied “fruits” of various colors (I say “colors” because the flavor was invariably “sugar”). My mother was never much of a baker, except at Christmas, when the baking would take two forms: fruitcake and stollen, both of which were filled with candied fruit. I’d try Mom’s fruitcake, the main ingredient of which seemed to be brandy, about once every five years to see if I was finally old enough to enjoy it. I never quite made it.
Stollen, on the other hand, was the main course of most breakfasts around Christmas. This was a bit odd in Memphis, doubly so because we didn’t have any particularly German ancestors; Mom just saw the recipe in a magazine sometime in the late 70s or early 80s and decided to make a tradition out of it. So I was thrilled when I moved to Switzerland and found out you could buy stollen in the grocery store at Christmastime. Almost as thrilled as I was disappointed when I found out that “real” Stollen is basically a marzipan delivery system.