Some policy advocates are taking shots at Verizon Communications for taking the position that a workable minimum definition of "broadband," for purposes of setting national broadband policy, is 768 kbps downstream and 200 kbps upstream.
"There seems to be some confusion around Verizon’s filing suggesting that the FCC keep a baseline definition for broadband as
768 kbps down and 200 kbps up," says David Young, Verizon VP. "The implication here is that we want to keep the speed set low so we won’t have to upgrade our networks."
"This is clearly absurd," he says. Indeed, in its filing Verizon itself suggests a goal of 50 Mbps for fixed broadband and 5 Mbps for mobile broadband.
But Verizon suggests that for reporting, tracking and measurement purposes, the FCC should maintain the current definition used in
the FCC broadband data reporting program (Form 477) for a basline, while continuing to track multiple higher “speed tiers” to get
a full view of what’s happening in the broadband marketplace.
This threshold definition also has the benefit of being the same one used by NTIA and RUS for the broadband stimulus program, Young argues.
There are lots of good reasons for being consistent about national data collection, the most obivious being that it is impossible to track progress over time if we keep changing the definitions. Many important changes that happen in national communications take 10 years or more, and it can make a huge difference if, along the way, the definitions of what we are tracking have changed frequently.
The other reason is that the definitions will cover networks of very type physical properties. Satellite, fixed wireless wireless, mobile and fixed networks all have different cost and capability profiles.
Beyond that, if what we are after is the fastest possible broadband availability, from the widest array of suppliers, with the most-robust growth in speeds and quality of service, at the lowest cost to consumers, the different speeds and investment profiles have to be harmonized.
Every communications engineer realizes there is a trade-off between capability and cost whenever a network is designed. Every engineer knows a network can be optimized--both in terms of performance and deployment cost--if a single application is supported. But multi-purpose networks inherently are tougher to design because there are more trade-offs.
Broadband networks generally are more expensive than narrowband networks, and networks featuring higher bandwidth generally cost more than networks of lower bandwidth.
If definitions are too stringent in the near term, it is possible some potential users, especially users in thinly-settled areas, will find that few, if any, providers can provide them service at any price those consumers would be willing to pay.
Finally, it would strike many as odd to accuse Verizon, which has been the most-aggressive tier one U.S. provider, of not being willing to invest heavily in broadband. Its FiOS fiber-to-home network is the most aggressive program in North America, and Verizon already is ready to start building a 4G wireless network even as it upgrades its 3G wireless network.
Floors are different from ceilings, and floors for some networks are ceilings for others. Customers, for example, cannot buy satellite broadband operating at more than 5 Mbps downstream, for any amount of money. And satellite is, by anybody's estimation, the absolute most affordable way to provide broadband to isolated locations. Fixed and mobile broadband are somewhat more expensive, but can support higher bandwidth.
In an isolated area, optical fiber or even digital subscriber line or cable modem service offers the most bandwidth, but at the highest cost. Cost and bandwidth, in other words, represent a standard engineering trade-off. The highest bandwidth also comes at the highest cost.
To the extent that retail prices are to be kept relatively low, the network investment must be matched to the anticipated revenue. It might, in some cases, be necessary to trade off some capability to keep costs low.
It would be a mistake to confuse that problem, and the other need to maintain comparable statistics to measure progress, with provider unwillingness to keep pace with growing market demands for broadband speed.
Providers that fail to keep pace will lose customer share. They know that. But unreasonable near-term definitions will not help potential customers get service, or even help existing customers get faster speeds, more quickly.
http://policyblog.verizon.com/BlogPost/661/title.aspx
No comments:
Post a Comment