Getting IPv6 working for World IPv6 Day

World IPv6 Day is tomorrow, June 8 — which also happens to be my birthday. I took it as a personal challenge to see if I could get IPv6 working at home, and to report back on how difficult it was. The answer: Extraordinarily difficult and beyond the reach of the average consumer.

Neglecting the fact that no major ISP (aside from Comcast, perhaps) provides native IPv6 service to the home, one is forced to use a tunnel broker, like SiXXS or Hurricane Electric. These organizations will let you establish an IPv6 tunnel between two IPv4 endpoints (i.e. their server and your router), and they will also assign and route you an IPv6 /64 subnet. The rest — getting all the moving parts up and running — is up to you. Continue reading

pictures of autocrats lecturing the people

There seems to be one common element to the Arab Spring: all the autocrats seem to take to the airwaves to lecture their people. Have a look:

Ben-Ali

Mubarak

???????



I’m sure this condescending and patrician attitude reflects their view towards their own people: that they’re too infantile or fragile to understand geopolitical issues. You can imagine Muammar al-Qaddafi thinking, as he wags his finger on state television, wouldn’t it be better for everyone involved if they just went back to their homes and schools and left the “governing” to the people who really understand power?

Could Usage-Based Billing work?

In my last post, I talked about why Internet usage-based-billing (UBB) is detrimental to both content producers and consumers. But my friend Davison raised an excellent question: could UBB work if the price was right?

After some deliberation, I would have to say yes, with some caveats. The argument in favour of UBB is about fairness: those who use more bandwidth should have to pay for it. Most rational people would agree that this method of billing has its merits. After all, that’s how we’re billed for electricity and gas; why shouldn’t it be the same for bandwidth? And don’t corporations pay for bandwidth this way already? Continue reading

A content producer’s take on Usage-Based Billing

The Canadian Radio and Telecommunications Commission recently issued a decision on usage-based billing and I’d like to comment from the perspective of a large-scale, Internet video supplier. (Insert the usual disclaimer about my opinions not representing my employer’s.)

As many readers know, I work for the Canadian Broadcasting Corporation in digital media operations. It’s extremely important for our customers — the Canadian taxpayer — to have cheap, unmetered bandwidth, so that they can watch our programming online. “Online” means not only the content that users can stream directly from our website using the CBC player, but also the content we send to our channel partners: iTunes, NetFlix, YouTube, and so on.

The adoption of usage-based billing across the board will drastically affect our ability to reach consumers over the Internet. It doesn’t take very long to go through 25 gigabytes of streaming data in a month. For Bell and other incumbent carriers to characterize anyone who uses over 25 GB/mo as a “bandwidth hog” grossly misstates the available capacity on the Internet today. Otherwise, why should it be possible for a commercial entity to purchase unlimited bandwidth ADSL service from Bell using essentially the same technology as home DSL, but without being metered?

I could continue, but let me instead quote some folks who have said it better than I could: Netflix. Here’s an interesting excerpt from Netflix’s investor relations website; specifically, their Q4 Letter To Shareholders (PDF). Obviously, I’m not speaking for CBC when I say this, but I think the comments here fairly represent the challenges that we, as an “Internet video supplier”, face under a usage-based billing regime.

Delivering Internet video in scale creates costs for both Netflix and for ISPs. We think the cost sharing between Internet video suppliers and ISPs should be that we have to haul the bits to the various regional front-doors that the ISPs operate, and that they then carry the bits the last mile to the consumer who has requested them, with each side paying its own costs. This open, regional, no-charges, interchange model is something for which we are advocating. Today, some ISPs charge us, or our CDN partners, to let in the bits their customers have requested from us, and we think this is inappropriate. As long as we pay for getting the bits to the regional interchanges of the ISP’s choosing, we don’t think they should be able to use their exclusive control of their residential customers to force us to pay them to let in the data their customers’ desire. Their customers already pay them to deliver the bits on their network, and requiring us to pay even though we deliver the bits to their network is an inappropriate reflection of their last mile exclusive control of their residential customers. Conversely, this open, regional, no-charges model should disallow content providers like Netflix and ESPN3 from shutting off certain ISPs unless those ISPs pay the content provider. Hopefully, we can get broad voluntary agreement on this open, regional, no-charges, interchange model. Some ISPs already operate by this open, regional, no-charges, interchange model, but without any commitment to maintain it going forward.

and

An independent negative issue for Netflix and other Internet video providers would be a move by wired ISPs to shift consumers to pay-per-gigabyte models instead of the current unlimited-up-to-a-large-cap approach. We hope this doesn’t happen, and will do what we can to promote the unlimited-up-to-a-large-cap model. Wired ISPs have large fixed costs of building and maintaining their last mile network of residential cable and fiber. The ISPs’ costs, however, to deliver a marginal gigabyte, which is about an hour of viewing, from one of our regional interchange points over their last mile wired network to the consumer is less than a penny, and falling, so there is no reason that pay-per-gigabyte is economically necessary. Moreover, at $1 per gigabyte over wired networks, it would be grossly overpriced.

I’ll close by giving you a sense of how outrageous a $1/GB charge is.

CBC pays pennies per gigabyte to our CDN to deliver content to the ISP’s front door. Some portion of that is the CDN’s profit, and yet they are still able to meet the marginal cost obligations of expanding their network. In fact, by using a CDN, we are paying a premium to the actual cost of the delivery of the bits, for the benefit of leveraging the CDN’s robust infrastructure, ability to scale, and many points of presence.

From an network engineering perspective, there really is no difference between a CDN and an ISP; in fact, the CDN transfers far more data per year across a far more complex worldwide data network. If our CDN can do it for such a low cost, why can’t Bell? I can only arrive at the same conclusion as Netflix: that Bell and other incumbent “last mile” providers are using their monopolistic ownership of those connections to justify outlandish charges to the customer.

CBC.ca Operations Group is hiring!

My team at the CBC is hiring for two vacancies: System Administrator and Senior System Administrator.

Our group does day-to-day server and application management of the CBC.CA infrastructure, which runs almost entirely on Linux (so RHCT-level experience is needed for the former job, and RHCE for the latter). Equivalent experience, especially in the media industry, is welcome. Above all, since we’re a communications company, excellent communication skills and a pleasant demeanor are essential.

To apply, click on the links above. The postings close on Friday, November 26.

What Twitter Could Learn from the Telephone System

I used to read a magazine called 2600, which was billed as a “Hacker’s Quarterly”. The title refers to the audio frequency, in hertz, used as a control tone in early analog telephone systems. Enterprising hackers discovered that a free promotional whistle in boxes of Cap’n Crunch cereal could be used to generate this tone. A whole class of phone hacking — or “phreaking” — was born. (Trivia: Apple co-founders Steve Jobs and Steve Wozniak were phreakers; Woz’s "blue box" or DTMF frequency generator, is preserved at the Computer History Museum in Mountain View, CA.)

This is an example of a system using “in-band signalling”. Both the control and data signals (audio) on early phone systems were transmitted on the same channel, thereby making the system open to compromise. Today’s modern phone networks have a completely isolated signalling system known as SS7.

Twitter is also a system with in-band signalling. I’ve always been bothered by the fact that Twitter commands — DM, FOLLOW, LEAVE, etc. — are transmitted by the user as part of the data signal (your tweet). This leads to all kinds of mistakes. For example, users have publicly tweeted when they think they have DM‘d, because they forgot to prefix their DM with “DM “. Other users accidentally expose their intent to FOLLOW or LEAVE users, due to misspelling commands (e.g. “FOLOW”).

The “@” reply prefix is also problematic. Tweets beginning with “@[username]” are only seen by the receiver’s followers, and not the sender’s. If the sender wants a wider distribution, hacks like “.@[username]” are used.

In-band signalling on Twitter clearly originated from the fact that it was intended to be used via SMS. Traditional mobile devices have no way to send signalling data out-of-band. What you see in 140 characters is what you get. As Twitter migrates to the desktop (or at least to rich mobile devices like the iPhone), we begin to see Twitter addressing this long-standing flaw. For example, the retweet identifier (RT) is no longer considered as part of the actual tweet, as long as one is using the Twitter API. Other metadata like geolocation and user agent are already transmitted as signalling data through the API.

Eventually, I believe that even the remaining in-band commands will transition out of the data stream. It’s only a matter of time before a celebrity’s mistweet makes the news and forces Twitter to clearly separate control from data. (Could you imagine something like President Obama accidentally tweeting “DM tonyhayward You are a first-class douchebag”?) Fortunately, they already have an API on which to build the control system. Shall we call it Twittering System Seven?

Making a Hackintosh from a Dell Mini 10v

My Christmas break project was to build a Hackintosh out of a Dell Mini 10v. The Mini 10v is a $299 NetBook that, I swear, is deliberately manufactured with on-board parts suitable for creating a Hackintosh.

There are tons of guides out there with conflicting instructions on how to create a Hackintosh on a Mini 10v. I’ll just share with you what worked for me, in a really brief way, because I know you’re busy and want to get working on your new Hackintosh! Continue reading

How to get Groupwise Messenger for Linux to install on Fedora Core 11

Novell ships Groupwise Messenger for Linux clients only for SUSE Linux Enterprise Desktop. If you apply this diff to the binary nvlmsgr.bin, it will permit it to be installed on Fedora Core 11 too:

— nvlsmgr.bin.head 2009-11-12 15:29:05.000000000 -0500
+++ nvlsmgr.bin.fc11.head 2009-11-12 15:29:13.000000000 -0500
@@ -18,7 +18,7 @@
# Extract the tarball
echo -n “Extracting files, please wait…”
mkdir -p $TMP_DIR
-tail +$SKIP $0 | tar xz -C $TMP_DIR
+tail –lines=+$SKIP $0 | tar xz -C $TMP_DIR

# Run the install
if [ -d ${TMP_DIR}/nmclient ] ; then

My Novell Groupwise complaint list

I apologize for the lack of updates on the journal recently; things have been quite busy at $WORK and I’m also trying to kick off some extracurricular creative projects.

Our corporate e-mail system is Novell Groupwise and I am continually amazed at all its unnecessary features, while lamenting the fact that really useful features are nonexistent. This feature imbalance makes me think that the entire system was designed by senior marketing executives at Novell and targeted solely at C-level executives who have secretaries and don’t actually know how to use computers. Continue reading