Today’s best discussion on Slashdot is about how VoIP providers of PSTN interconnect may be regulated by the FCC to mandate emergency service (“911”) capability. There an excellent article at Voxilla from last December on 911 regulation that covers a lot of the same ground.
I’m going to argue the unexpected, and say that 911 service should be a mandatory regulated feature. But with a major twist I’ll leave until the end.
911 service is not a normal market product. The service that is summoned is provided through a compulsory levy on local businesses and residents. The fire brigade don’t ask for a credit card before turning the hoses onto your burning house. And if the caller is the beneficiary, you may be in no state to engage in any form of usual market interaction. The service always requires urgent response; there is no time to discover how the service should be accessed, or evaluate competing actions. When lives are on the line, you shouldn’t be reaching for the yellow pages.
The beneficiary of the service is often either not the caller or owner of the telephone line. There is an externality in choosing not to have 911 service; other people suffer without having a choice of exercising the market mechanism. If my babysitter has a heart attack, and I don’t have 911 service, some innocent third party suffers. It’s not reasonable for babysitters to have to inquire about the 911 service my telephone is attached to, because the heart attack cannot be reasonably foreseen. If my house burns down and takes the rest of the neighborhood with it, other people suffered for my parsimony. If I see the burglar breaking into the house opposite, but can’t call the police, more heartache.
Users are also mobile, and are not realistically able to create a personal comunications safety bubble around themselves. You’re dependent on other people having the service for when you get in trouble. You can’t escape the externality by being richer and buying better service. If you’re lying at the side of the road unconscious, the good samaritan passer-by isn’t going to frisk you down to see if you carry the thousand dollar Hypersafe Satphone™. At the point of use, there is a market failure. Market failures require regulation.
Externalities like pollution, health injury, or social damage call for regulation. By definition, they are at best addressed through indirect secondary market mechanisms like emissions trading to rebalance the costs more fairly. It’s hard to imagine such a system for a personal service like emergency calls. How do you provide financial incentives for everyone to adopt 911 service via market mechanisms? It just doesn’t fly.
The fire brigade or police department will effectively ask for a credit card for a business property that has repeated false alarms. So there is a degree of market encroachment. Abuse of service can be punished through quasi-market mechanisms. The capitalistic instinct to provide truly enhanced emergency response should also be encouraged. Burglar alarms and monitoring systems for the elderly and infirm are existing examples built atop the PSTN. Niche markets should develop their own enhanced response systems. Maybe epileptics will carry special equipment that monitors their wellbeing, calls for help, and uses a loudspeaker to advise passers-by what to do if the owner has a seizure. But society needs a baseline; a reasonable expectation of emergency response wherever you are, catering to the needs of the ordinary person.
So I hope you’ll agree with me by now, we need regulation. The only question is to what ends and how to achieve them.
The end-to-end principle tries to separate service from connectivity. Normally, that’s a laudable aim. In this one case, however, it’s the opposite of what you need. I might take my Vonage service on the road, and plug into a high-speed line in a hotel in Paris. If I have a medical emergency, I want to get a Parisian ambulance to come and take me to a Parisian hostpital. Au secours! I don’t want to speak to someone in the emergency response center in Overland Park, Kansas, no matter how nice, upstanding and midwestern they are. I want the service to be associated with the connectivity.
So here is what I propose. We don’t break the basic end-to-end nature of the Internet. But we regulate the provision of public Internet connectivity. We insist that basic IP voice 911 service is always included. Maybe we reserve a private IP address (168.9.1.1?) as the default route. It isn’t hard. If we’re feeling fancy, we include a default route to a WSDL directory to discover additional enhanced emergency services on offer. (Yes, I’d like to connect to a parlez-vous Anglais operator in that Parisian hotel room.)
Whether I’m wardriving around, sat in my hotel room, or feet up at home, the service is always there. We don’t yet have massive dynamic meshes of roaming users, and probably won’t for another decade or two. The end points of the Internet are always physical and fixed, to a reasonable approximation (i.e. at most one hop away to a cell tower). Paid-for Internet connectivity is always a hop away. Payments require a legal framework for commerce. Those contacts are regulatable. Taxing VoIP service providers and forcing 911 provision just doesn’t work, because the service will just move offshore. Connectivity can’t move offshore. Call it the revenge of geography. I want the ambulance to arrive at my very physical door, not my extremely virtual IP address. IP addresses and end-to-end are just abstractions. A heart attack isn’t.
Posted by Martin Geddes at 11:35 PMTrackBack URL for this entry:
http://www.telepocalypse.net/cgi-sys/cgiwrap/mgeddes/MT/mt-tb.cgi/66.
Listed below are links to weblogs that reference Slashdotdotdot dashdashdash dotdotdot:
»
911 and VOIP from The Next America
Martin at Telepocalypse(a genius site for anyone interested in telephony): 911 service is not a normal market product. The service that is summoned is provided through a compulsory levy on local businesses and residents. The fire brigade don’t ask for
[Read more]
»
911 should be a mandatory regulated service for VoIP from North American Bandwidth News
[Read more]
Wow! Great article...
Does this mean that the telco (ISP) needs a global standard for IP-based 911/999 connectivity? And does this also mean that VoIP device manufacturers will have to adhere to that standard - or is it the VoIP service provider? Does that require a certification and brand mark on devices which are compliant?
Should the standard cope with translation, i.e. if I'm an American Vonage user and I plug my device into a hotel room in London, can I still dial 911 but be connected to the local 999 service? This seems relatively easy to solve - the device should be aware of the user preference for "emergency service" dialing but there should only be one global concept of "emergency service".
The question is "How do you bootstrap such a system?" If precedence is anything to go by, one would suggest that the Swedish trade unions force their government to pass a law about it :-) which is then foisted on the EU nations and later leaks out around the world.
Posted by: at February 24, 2004 10:28 AM"The end points of the Internet are always physical and fixed, to a reasonable approximation (i.e. at most one hop away to a cell tower). Paid-for Internet connectivity is always a hop away."
One hop from a cell tower can be many miles.
802.11 in an apartment complex can cover many many doors to knock on "Anyone having a heart attack in there?"
I'm not in anyone's service footprint for their "wireless broadband", but I'm line of sight with someone 8 miles away on a mountain who is.
Dialup ISPs don't always have ANI (and the caller ID can be blocked).
(Some) VOIP providers currently let you give them their address and a promise that it is correct (but there was no way for me to tell them I had left the USA and was spending three weeks in the UK). That one also has obvious failures (no provisions for mobility, as well as the "stay in your country!" problem).
I think you are going to want to let devices say "I'm here" when they know (laptop with a GPS, cell phone with cell tower assisted GPS, or even with triangulation just based off of tower locations). Unfortunately they don't always know, sometimes they will only have some guesses ("I don't have a GPS, my user said "Maryland", and the closest location service is two IP hops away and says I'm in Manchester England"). For pizza delivery you can just ask the user to pick, for 911 you may have to send their message to call centers for both locations and let them try to figure it out (hard if all you managed to do was dial 999 or 911 before it all went black).
Posted by: at March 17, 2004 03:39 PMThe Mean Opinion Score (MOS) is the subjective scale by which telephone network end user quality is measured. According to a TechNewsWorld story, providers of traditional network services aim for scores of 3.5 to 4.2 on the five-point scale.
The challenge for VoIP providers is that their scores generally aren’t as high, the story says. The implication is that the disparity between traditional and VoIP quality grows as problems not apparent in small-scale VoIP tests and beta projects become issues in enterprise-wide rollouts.
The disparity between traditional and VoIP services is understandable. The legacy public switched telephone network (PSTN) has a headstart of, say, 100 years or so. It is robust, predictable and solid. VoIP networks all have sprung up during the past few years. They are built on a network infrastructure that simply wasn’t intended for voice services. Vendors and service providers have done an amazing job of scrambling — but scambling it is.
This means that the networks aren’t going to be perfect. It also means that VoIP is at a crossroads as it fights competitors’ high-quality voice services. The current dynamic — that VoIP is a huge hit and is dominating the deployment of new voice lines — won’t last if VoIP quality trends below that of the PSTN. Companies like to save money and take advantage of all the hyped features VoIP offers. But they are smart enough to recognize that such a strategy is foolish if the quality of the bedrock voice product isn’t as good.
VoIP isn’t going anywhere. It’s already part of too many business and operational plans to fade away. What could happen, however, is that consistent quality problems relegate VoIP to a secondary role in the enterprise. For instance, lines that are used to communicate with customers could be time-division multiplexed (TDM), while intraoffice communications could be VoIP. If such a two-tier scenario develops, it also is likely that enterprises will revisit and perhaps reverse decisions to go with VoIP before deployment begins.
Of course we don’t know how this is going to play out. The bottom line, however, is clear: Voice is the most important telecommunications service for every company. If VoIP doesn’t create networks robust enough to be the equal of the PSTN and, on top of that, develop the testing, quality control and remediative tools necessary to keep applications running smoothly, its star will begin to fade.
Posted by: at November 20, 2006 04:04 PM