Becoming an Internet Native
Become an Internet native is about more than seeing it as the "e-" version of the familiar. It is a chance to rethink the basic design of systems and see new opportunities.
21-Nov-2008Version 2: 2023-05-28 17:09:26

AV Technology Nov/Dec 2008You can read the printed version of this column in AV Technology Nov/Dec 2008 as the "The Way I See It:" column.

The Internet is not just another telecommunications service – it represents the idea that we can create our own solutions.

So what’s holding us back?

by Bob Frankston

Old PBXWe have been living in the land of telecommunications for over a century, going back to the days of the telegraph when we would entrust operator companies to send messages on our behalf using their wires. Over time, we got the talking telegraph, also know as the “telephone”. Then we moved beyond wires with radio and television broadcasting, and with cellular telephony, we gained mobility. But the basic business model of telecommunications is the same – the operators provide services using their own infrastructure. They use the revenue from selling these services to fund their infrastructure. Then one day, the Internet happened, and everything changed.

Well, not exactly. The change had been brewing for a while as we became adept at fashioning our own solutions. In the days of analog networking you needed a special infrastructure for each medium in order to preserve the signal – carrying a phone call across the country or across an ocean was an impressive engineering feat. The telephone companies invested in research and developed digital technologies. Unlike analog technologies, you could regenerate a digital signal over any distance. At first, "digital" was seen as a technology for the carriers to use to improve their ability to provide their traditional services.

In the 1960's and 70's we started to connect computers to each other using wires and sometimes radios. As long as the systems were close together, we didn't need to buy telecommunications services. We could just send digital packets between systems. If a packet got lost or garbled the software would just resend it until we had the complete message. This is the essential idea behind Ethernet. We considered it all to be networking but it was no more like telecommunication’s notion of networking than driving a car is like taking the train. A word like "networking" has so many meanings that we can seem to be talking about the same thing, when we are really talking about entirely different concepts.

The defining concept of the Internet is the “end-to-end” principle – we can create our own reliable solutions even over an unreliable network. We need to be careful to avoid confusing “end-to-end” with “womb-to-tomb”. The latter term assumes someone is making sure that everything works, whereas end-to-end means we are concerned only with the endpoints, and not an operator's network services.

We took the principle behind Ethernet and applied it over any distance, and leveraged existing telecommunications networks. We can't rely on the network operator to provide services, thus we had to discover what works and what doesn't. This end-to-end constraint is what has given the Internet its strength. By disallowing such dependencies we've grown stronger. We had to wait for the Internet to grow in order to be able to do voice over IP (VoIP), but today it's just another service with cost above the raw cost of the bits.

Internet Tourists

We're now at the point where we can pretty much assume that we can make an Internet connection between two points and expect it to work. We're ready to visit the Internet and take advantage of end-to-end connectivity.

As tourists we needn't be aware that today's Internet is only a prototype and we are likely to confuse the Internet with telecom. After all, a VoIP connection acts just like a phone call so isn't it the same? Yet even as tourists, we've discovered the possibilities of the Web and created peer-to-peer applications. And we accepted that applications only worked if we also made sure we had a billing relationship with all providers along the path. This is the "broadband" model.

We discovered that broadband is great for video. But then it should be, since we've repurposed a system specifically designed for video. It’s a testament to the power of the end-to-end principle that we've been able to rediscover that broadband is good for video. But it's also a testament to our confusion that we haven't been more frustrated by what we cannot do – for example, medical monitoring, because we can't presume even a low speed connection away from home.

As a visitor, you embrace the web and create your own sites. You expect everyone to have email and build applications that take advantage of messaging. You can deploy services using software and host it on your site or at the customer's site. You can maintain and update applications even after you deliver them. Yet for most people, the Internet is still just the "e" version of the familiar. We e-shop at the e-mall, and we exchange e-mail. "VoIP" is just another phone service.

Yet for most people, the Internet is still just the "e" version of the familiar.

Even as visitors we treat the Internet is simply "the network", and we are starting to build applications that call home. We're starting to use “cloud” services so that our information and even home computers are available everywhere. We're starting to watch YouTube and are starting to expect broadcast television to be available on or over the net. But it's still television. But then, many of us are still at the stage where we think of the car as a horseless carriage.

Becoming an Explorer

Now, we're starting to venture out a little. But we're not quite at the point where we wonder why a mobile device still called a "phone", when telephony is just another application. It's no surprise that we still think in terms of telephones and television because that's all we know from traditional telecom. We still don't treat our mobile devices as our digital agents who help us negotiate our way through an increasingly connected world. In fact, we still think of the Internet in terms of computing devices and not as the basic infrastructure behind everyday objects like light switches and traffic lights. But slowly we are starting to realize that the Internet allows us to focus on the relationships between two end points, be they people or devices.  We assume we can exchange messages between the end-points while being resilient when we can't connect.

We look for nascent ideas like Amazon's Kindle, where the contents of a book are simply "available".

Becoming an Internet Native

Today's Internet is indeed a prototype – like a bicycle with training wheels. We can apply the end-to-end principle in creating solutions.  You plug your device into the hotel's Internet connection and wonder why it doesn't work until you realize that you're up against those who think of the Internet as “the web”, and require you use a browser to make the connection as if you were placing a phone call.

When you rearrange the furniture in your house, you may start to wonder why you can't simply move the light switch by simply redefining its relationship with the light. After all, why should you define the relationship by the wires in the house any more than you depend on a dedicated wire between your PC and a web site? For that matter, why is the Internet something you access with your PC or "mobile"? Shouldn't it simply be available anywhere with or without a wire? After all, bits don't care whether they are wired or wireless. They are just bits.

You may ask why you need so many remote controls in your house rather than just having open protocols and your own controller. You recognize that today's protocols are just a first attempt, and that the IP address provides neither a stable identifier nor stable routing. You architect your products to work around these limitations while maintaining the high level model of simple end-to-end relationships.

As digital native, you recognize that relationships don't depend on any particular path. We see some of this in Skype, which maintains a list of your relationships and tries to find a path even as you move around. You no longer need a provider, but instead create your own solutions.

Moving Beyond Telecom

If it's about relationships, then you shouldn't be required to pay service providers. But today our infrastructure is controlled by carriers acting as gatekeepers, who force us to buy services to fund their infrastructure, just as they did a century ago. Being a digital native can be a very frustrating experience because you are leaving behind old paradigms. You no longer think of the Internet as a replacement for telecom, but as a new way to think about building systems and creating solutions. And you will be frustrated because even something as simple as having your physician monitor your health while traveling doesn't "just work". You have to first assure that there is a billing relationship with every carrier in the path. Today if you buy an Amazon Kindle, you simply press "buy" and the book appears on the device because Amazon had to negotiate a special deal, and it works only near Sprint cellular sites.

As a native you no longer think of the Internet as something apart from your day to day activities. When you run a wire to connect a microphone to a control panel then another a wire to each light and speaker you stop and then you realize the relationships needn't be defined by the wires. You can just attach all the devices to the common network and then define the relationships in software. It's not just that things become easier – you can now redefine the relationships dynamically and in response to events and start to wonder what else is possible.

You no longer think about doing everything "on the Internet", but instead try to take advantage of connected relationships. And then you look all around you, and you find you're still living in a 20th century world ruled by phone companies. You're stuck with plug boards because very wire is owned by someone who demands a cut of the action.

MIT-alumnus Bob Frankston co-developed VisiCalc, the first electronic spreadsheet application, and writes frequently on Internet policy issues and infrastructure.