Cybertelecom
Cybertelecom
Federal Internet Law & Policy
An Educational Project

Internet Backbones :: Policy:

Navigation Links:
:: Home :: Feedback ::
:: Disclaimer :: Sitemap ::

- Backbone Policy
- Backbones 101
- Backbone Networks
- NSFNET
- Intl Settlements ICAIS
- Broadband
- Mergers
- Net Neutrality
- Statistics
- Traffic Reports
- Reference

- Broadband
- Sec. 706
- Stimulus Plan
- Natl BB Map
- FCC Natl BB Plan
- Dial Up
- DSL
- - Naked DSL
- - UNE
- - Net over Wireline (Info Service)
- Cable
- - Open Access
- Fiber
- Wireless
- - 3G
- - Wifi
- - WiMax
- - 700 Mhz
- Powerline
- Satellite
- Muni Broadband
- Telecom Services
- Computer Inquiries
- Network Neutrality
- Consumer Protection
- Forbearance
- Backbones
- - ICAIS
- Layers
- Interconnection
- - Negotiation
- Reciprocal Comp
- Mergers
- Federal Advisory Committees
- FCC
- Universal Service
- Statistics: Broadband


The Federal Communications Commission has left the Internet backbone market unregulated, as explained in an excellent paper by Michael Kende.

In summary, telecommunications providers are subject to common carrier regulations that ensure nondiscriminatory access to end users; together with antitrust enforcement, these regulations serve to protect against anti-competitive behavior by telecommunications providers with market power. In markets where competition can act in place of regulation as the means to protect consumers from the exercise of market power, the Commission has long chosen to abstain from imposing regulation. For this reason, providers of services that combine telecommunications with computer services are not regulated as common carriers. [Kende p 12]

DARPA built the 1st backbone: The ARPANet.
NSF built the 2nd backbone: The NSFNet.

Internet Backbones have been an issue in several proceedings before the FCC.  Internet backbone policy issues include

The issue of Internet backbones has been raised in the FCC National Broadband Plan NOI. It is not directly raised in the Broadband Report.

The FCC's Universal Service Telemedicine Pilot subsidizes the cost of backbone services.

Merger Proceedings:

The most significant FCC proceedings to date to address backbones have been merger proceedings (See also Industry :: Backbones listing major backbones and who has been acquired by whom).  After a sufficient number of proceedings, the orders began to have stock background language that read as follows:

109. The Internet is an interconnected network of packet-switched networks. End users (individuals, enterprise customers, and content providers) typically, though not always, obtain access to the Internet through Internet service providers (ISPs) using a “dial-up” modem, cable modem, DSL, wireless network, or a dedicated high-speed facility (which the companies often call “Dedicated Internet Access” (DIA)). ISPs provide access to the Internet on a local, regional, or national basis, and most have limited network facilities. In order to provide Internet service to end users, ISPs and owners of other smaller networks interconnect with Internet backbone providers (IBPs)—larger Internet backbone networks. The backbone networks operate high-capacity long-haul transmission facilities and are interconnected with each other. Typically, a representative Internet communication consists of an ISP sending data from one of its customers to the IBP that the ISP uses for backbone services. The IBP, in turn, routes the data to another backbone network, which delivers the data to the ISP serving the end user to whom the data is addressed.

110. IBPs may exchange traffic either through “peering” or “transit” arrangements. Under a peering arrangement each IBP “peer” will accept and deliver, without charge, traffic destined either for its own network or for one of its own backbone customers. Transit arrangements, by contrast, permit an ISP, small or regional IBP, or other corporate business, to reach the entire Internet using dedicated access lines linking it directly to the transit provider’s Internet backbone network. An IBP providing transit service enables the customer to send and receive traffic through the purchaser’s IBP to any other network or destination on the Internet. Frequently, IBP customers obtain transit packaged with a dedicated highspeed facility as part of a DIA service, with the transit customers paying fees for both the connection and the transit service.

111. IBPs generally can be categorized into tiers based on their size, geographic scope, and interconnections. “Tier 1” IBPs are a small group of the largest IBPs that sell transit and/or dedicated Internet access to substantial numbers of ISPs and corporate customers or other enterprise customers. These Tier 1 IBPs peer with all other Tier 1 IBPs on a settlement-free basis. Lower tier IBPs may peer with each other, but generally must purchase transit from a higher tier IBP to reach end users that are not customers of the networks of their peers.

[SBC / AT&T Merger Order 2005] [Verizon / MCI Merger para. 110-15 2005]

The FCC made the following conclusions in the individual merger proceedings:

Disclosure

The FCC's Network Reliability and Interoperability Council (NRIC) expanded the scope of its work with NRIC V to include packet based telecommunications.  Study Group IV of NRIC V addresses interconnection and peering.  In June of 2001, this study group recommended to NRIC that Internet backbones publish their peering policies.  While this is merely a recommendation letter of the advisory group, it is noteworthy that the subject matter is considered properly within the scope of an FCC advisory council.

See also Characteristics and Competitiveness of the Internet Backbone Market, GAO-02-16 (Oct 2001) ("We were also told that peering policies should be made public.")

See also Industry :: Backbones (noting those networks that were found to post their peering policies)

Section 706

Incumbent Local Telephone Companies (Incumbent Local Exchange Service or ILECs) have also tried to raise the issue of the Internet Backbone in their arguments before the FCC.  The Telecommunications Act of 1996 sets for the policy goal of introducing competition into the local telephone market.  The problem was how to persuade the local telephone monopoly to give up its grip on the market.  The solution created by the 1996 Act was a carrot - the ILECs were be permitted to enter the lucrative long distance telephone market only when their local markets were opened up to competition.  The ILECs have argued vehemently against this restraint. 

This is where the Internet backbone comes in.  ILECs have argued that investment in Internet backbone bandwidth is anemic and that we are on the verge of a bandwidth crisis.  They have also argued that there are vast portions of this country that have no direct access to the Internet backbone (even though the entire country now has direct two-way satellite access to the Internet and, in the rural communities, the only ones complaining about this are the ILECs, not the thousands of other ISPs out there).  The ILECs argue that the restraint on entering long distance service should apply to voice service only, and not long distance data, and if they were allowed to enter long distance data, they would solve the Internet backbone problem.

In the first Sec. 706 Notice of Inquiry, the FCC asked whether there was a need for the FCC to get involved in peering issues. 

What can and should the Commission do to preserve efficient peering arrangements among Internet companies, especially in the face of consolidations of large proprietary gateways? We ask for comment whether the Commission should monitor or have authority over peering arrangements to assure that the public interest is served.  

[First Sec. 706 NOI, para 79] The comments filed reflected rough consensus that the FCC should let the free market work (one dissenting voice recommending FCC action was Bell Atlantic  - now Verizon). The FCC found that investment in Internet backbone was vigorous.  More facilities are being built and those facilities have greater capacity every day.  Furthermore, the FCC found that bits-is-bits.  Whether its voice or whether its data, its all bits and the ILECs don't get the carrot, access to the long distance market, until they fulfill the obligations of Section 271 and open their markets to competition.

The FCC released its second 706 Notice of Inquiry in April 2000.  Even though the FCC did not place the issue of Internet backbone bandwidth on the table, the ILECs nevertheless came back with arguments about an impending bandwidth shortage in the backbone.  In the summer of 2001 it has been widely discussed that there is glut of bandwidth in the backbone market with tremendous amounts of unused capacity. The FCC stated: "We conclude that there has been ample national deployment of backbone and other fiber facilities that provide backbone functionality. There is no indication that specific types of areas have inadequate access to backbone or functionally equivalent facilities."See ¶¶ 20-22, 208-09

Subsequent Sec. 706 Reports (Third and Fourth Reports) have made only brief mentions of Internet backbones.

GAO

In 2001, the Government Accounting Office released Telecommunications: Characteristics and Competitiveness of the Internet Backbone Market GAO-02-16, November 14., GAO 11/14/01 in which the GAO concluded

Network Neutrality

New policy deliberations have involved network neutrality, and whether backbone networks can discriminate against particular content, applications, or companies.

Addressing

Internet backbone networks acquire Internet addresses from Regional Internet Registries, and then distribute smaller blocks of addresses downstream to their customers. There are several significant issues related to backbones and addressing:

VoIP Interconnection

Proceedings which raised on addressed telephony interconnection, begging questions about Internet interconnection.

PSTN -> IP Transition

Universal Service Reform / Intercarrier Compensation

In order to reform universal service and intercarrier compensation (reciprocal compensation, access charges, settlement fees), and bring universal service into the broadband era, the FCC is striving to reform the entire system of settlements and payments between carriers. The old system was built in the era of a monopoly telephone network, and included the promise of universal service through, at that time, implicit subsidies, and involved the division between state and federal jurisdiction. As the network moves from the analog telephone network to an all IP network with VoIP applications, the FCC must reform the old PSTN interconnection rules as they will now apply in an IP environment. The problem, in the IP network environment, is how to distinguish and make rules for telephony interconnection as opposed to Internet interconnection (peering and transit).

1347. Alternatively, other comments seem to anticipate that IP interconnection policies could encompass IP traffic other than voice.2451 Would it be appropriate to encompass any non-voice IP traffic or services in such a framework, and how would they be defined? We note, for example, that the Commission historically has not regulated interconnection among Internet backbone providers. If a different interconnection policy framework were adopted in this context, how would it be distinguishable? To what extent would an IP-to-IP interconnection policy framework address interconnection rights for both voice and non-voice traffic, or to what extent would providers simply have the freedom to use otherwise-available interconnection arrangements to exchange particular IP traffic or services? [Universal Service Reform FCC No. 11-161 2011]

TW Telecom Petition on IP-to-IP Interconnection (2011)

Time Warner Cable Request for Declaratory Ruling that Competitive Local Exchange Carriers May Obtain Interconnection Under Section 251 of the Communications Act of 1934, as Amended, to Provide Wholesale Telecommunications Services to VoIP Providers. (2007)

 

Web services provided by Wyoming.com
:: Home :: About Us :: Contact Us :: Sitemap :: Discussion :: Disclaimer :: Search ::