This letter is available as a PDF.
July 14, 2011
Julius Genachowski
Chairman
Federal Communications Commission
445 12th St. SW
Washington, DC 20554
Re: A National Broadband Plan for Our Future, GN Docket No. 09-51
Dear Chairman Genachowski:
On May 6 of this year, Public Knowledge and New America Foundation’s Open Technology Initiative sent a letter urging the Wireline Competition Bureau to exercise its statutory authority to fully investigate the nature, purpose, and impact of data caps upon consumers. Since then, data caps have spread further across the industry. Verizon recently announced data caps for its new 4G wireless service, and left open the possibility of data caps on its FiOS service (a possibility they had long dismissed). The costs of data caps to consumers and society are becoming increasingly clear. We hope the Commission moves quickly to investigate what, if any, benefits balance those costs.
The case of Andre Vrignaud is a stunning illustration of how these data cap policies undercut the values espoused in the National Broadband Plan. After twice being informed by his ISP Comcast that he had exceeded his monthly data cap, Vrignaud has been blacklisted from Comcast for one year. In his account, Vrignaud suggests that remotely backing up two decades worth of photographs and music files is what triggered his yearlong removal from Comcast.
While we have no way to independently verify Vrignaud’s account of this specific incident, we are concerned because it represents an entirely plausible and legitimate use of a residential broadband internet connection. Data caps make this type of use punishable with one year without internet access. This conflict is unsustainable.
In light of this, we are expanding our original request to include an investigation into the data cap policies of all ISPs. There does not appear to be any restraint on the expansion of data caps, or expectation that they will not be widely adopted. Strict data caps are an industry trend that works to undermine the benefits of broadband that this Commission so enthusiastically champions.
The National Broadband Plan specifically mentions cloud-based applications as a benefit of more pervasive, robust broadband networks. As the Plan correctly acknowledges: “[s]oftware based in the cloud may allow more small businesses and consumers to access applications that were once only available to corporations with sophisticated information technology departments in the applications and content markets.” Because of the potential of cloud computing, the Plan recommended additional federal funding to aid in its development.
Interacting with cloud-based applications necessarily involves the transfer of data between a user and the cloud. As a result, increased use of cloud computing will drive a user ever closer to a data cap.
Perhaps most disturbing is the lack of clarity surrounding the legitimate purposes that data caps serve. Some data caps that charge overage fees, such as those imposed by AT&T, at least serve to enrich the ISP. Hard data caps, such as those imposed by Comcast, appear to be pointless.
In 2008, Comcast told the Commission that its data cap is “independent of, and should not be confused with” its congestion management practices. It went on to state that the “cap does not address the issue of network congestion, which results from traffic levels that vary from minute to minute.” Instead of addressing network congestion issues, Comcast’s monthly data cap is intended to curb “excessive use.”
In a direct contradiction these statements, Comcast now defends its caps as necessary to protect quality of service for other users: “[i]f someone’s behavior is such that it degrades the quality of service for others nearby — that’s what this threshold is meant to address.” Public Knowledge, Future of Music Project, and New America Foundation’s Open Technology Initiative find it unlikely that uploading data to remote servers at off peak times, a behavior pattern that could easily trigger Comcast’s data cap, somehow has a significant impact on network performance for other users.
It is unclear what additional interest Comcast has in curbing “excessive usage” that does not interfere with its overall network capacity or create network congestion. Comcast’s data cap appears to be aimed at users who are using “too much” data for Comcast’s liking, but not “too much” data to actually interfere with the functioning of the network. This is not a sustainable standard to use to decide who gets access to a critical service such as broadband.
Given these amorphous criteria, it is unclear how Comcast arrived at its 250 GB cap in 2008. Furthermore it remains unclear why, after three years of investing in network upgrades to “better prevent congestion and meet [Comcast’s] customers’ ever increasing demands for bandwidth” that cap has failed to increase. Today, customers with Comcast’s current high-speed offering could hit the 250 GB monthly cap in little more than five hours.
Data caps continue to raise many more questions than they provide answers. While it is clear that they work directly against the widespread use of broadband championed in the National Broadband Plan, it is unclear what legitimate purposes they serve. As such we urge the Commission now, as we did two months ago, to request customer anonymized reports from all ISPs regarding the following:
- Which ISP-offered services are excluded from the cap. This should include reporting on those services, such as voice telephony and video programming, that compete with internet-delivered non-ISP controlled offerings.
- How often the cap is enforced. This should include the absolute number of customers who exceed the cap as well as the percentage of customers who run afoul of the limit. Additionally, it should include amount by which the customers exceeded the cap and how many of those customers are repeat cap exceeders.
- Steps taken to warn customers. This should include the steps taken to warn customers, and when those steps are taken. Additionally, the reporting should include data on the effectiveness of these warnings in preventing overages.
- Average penalty incurred by customers. Caps such as AT&T’s charge additional fees based on how significantly the cap is exceeded. Reporting should include data on the size of the penalties incurred by customers.
- When and how often a penalty is waived. In addition to the publicly announced grace periods, the Commission would be well served by understanding how often and under what circumstances reporting ISPs grant additional waivers.
- The relationship of enforcement to times of network congestion. If used properly, data caps can a tool in easing network congestion. However, there is a constant threat that ISPs use network congestion as a pretext to act on other motives. The Commission would benefit from a nuanced understanding of the relationship between data cap enforcement and network congestion.
- How data caps are set. For example, why did AT&T choose 150GB for DSL and 250GB for U-Verse customers? What criteria are used to arrive at the cap? What criteria are used to determine appropriate overage fees?
- How data caps are evaluated on an ongoing basis. Data caps are often defended as necessary to address current network congestion issues. However, network technology is constantly being modernized and made more efficient. In light of this pattern of improvement, caps that are appropriate for today’s network may be inappropriate in the future. How do ISPs evaluate their existing caps, and what are the conditions under which those caps could be raised and/or eliminated?
We also request that the Commission include additional inquiries regarding the impact of local, regional, and national concentration on the adoption of data caps. Reduced competition at a local level would reduce the impact of a negative consumer response to data caps, and therefore may encourage the adoption of caps.
Although this most recent incident involves Comcast, we are not asking the Commission to investigate Comcast individually. Instead, the Commission should use this incident as an opportunity to begin the process of fully educating itself about the nature and impact of data caps across the industry.
We hope that the Commission recognizes the impediment to widespread broadband use that data caps represent and moves quickly to complete its understanding of their current application.
Respectfully Submitted,
Future of Music Coalition
New America Foundation’s Open Technology Initiative
Public Knowledge
_____/s/_____
Michael Weinberg
Staff Attorney
Public Knowledge
cc: Commissioner Michael Copps
Commissioner Robert McDowell
Commissioner Mignon Clyburn
Chief Sharon Gillette
Chief Rick Kaplan
stdClass Object
(
[nid] => 6283
[type] => documentfile
[language] =>
[uid] => 2258
[status] => 1
[created] => 1310654776
[changed] => 1310654922
[comment] => 0
[promote] => 0
[moderate] => 0
[sticky] => 0
[tnid] => 0
[translate] => 0
[vid] => 6344
[revision_uid] => 2258
[title] => Letter to the FCC Regarding Data Caps
[body] =>
This letter is available as a PDF.
July 14, 2011
Julius Genachowski
Chairman
Federal Communications Commission
445 12th St. SW
Washington, DC 20554
Re: A National Broadband Plan for Our Future, GN Docket No. 09-51
Dear Chairman Genachowski:
On May 6 of this year, Public Knowledge and New America Foundation’s Open Technology Initiative sent a letter urging the Wireline Competition Bureau to exercise its statutory authority to fully investigate the nature, purpose, and impact of data caps upon consumers. Since then, data caps have spread further across the industry. Verizon recently announced data caps for its new 4G wireless service, and left open the possibility of data caps on its FiOS service (a possibility they had long dismissed). The costs of data caps to consumers and society are becoming increasingly clear. We hope the Commission moves quickly to investigate what, if any, benefits balance those costs.
The case of Andre Vrignaud is a stunning illustration of how these data cap policies undercut the values espoused in the National Broadband Plan. After twice being informed by his ISP Comcast that he had exceeded his monthly data cap, Vrignaud has been blacklisted from Comcast for one year. In his account, Vrignaud suggests that remotely backing up two decades worth of photographs and music files is what triggered his yearlong removal from Comcast.
While we have no way to independently verify Vrignaud’s account of this specific incident, we are concerned because it represents an entirely plausible and legitimate use of a residential broadband internet connection. Data caps make this type of use punishable with one year without internet access. This conflict is unsustainable.
In light of this, we are expanding our original request to include an investigation into the data cap policies of all ISPs. There does not appear to be any restraint on the expansion of data caps, or expectation that they will not be widely adopted. Strict data caps are an industry trend that works to undermine the benefits of broadband that this Commission so enthusiastically champions.
The National Broadband Plan specifically mentions cloud-based applications as a benefit of more pervasive, robust broadband networks. As the Plan correctly acknowledges: “[s]oftware based in the cloud may allow more small businesses and consumers to access applications that were once only available to corporations with sophisticated information technology departments in the applications and content markets.” Because of the potential of cloud computing, the Plan recommended additional federal funding to aid in its development.
Interacting with cloud-based applications necessarily involves the transfer of data between a user and the cloud. As a result, increased use of cloud computing will drive a user ever closer to a data cap.
Perhaps most disturbing is the lack of clarity surrounding the legitimate purposes that data caps serve. Some data caps that charge overage fees, such as those imposed by AT&T, at least serve to enrich the ISP. Hard data caps, such as those imposed by Comcast, appear to be pointless.
In 2008, Comcast told the Commission that its data cap is “independent of, and should not be confused with” its congestion management practices. It went on to state that the “cap does not address the issue of network congestion, which results from traffic levels that vary from minute to minute.” Instead of addressing network congestion issues, Comcast’s monthly data cap is intended to curb “excessive use.”
In a direct contradiction these statements, Comcast now defends its caps as necessary to protect quality of service for other users: “[i]f someone’s behavior is such that it degrades the quality of service for others nearby — that’s what this threshold is meant to address.” Public Knowledge, Future of Music Project, and New America Foundation’s Open Technology Initiative find it unlikely that uploading data to remote servers at off peak times, a behavior pattern that could easily trigger Comcast’s data cap, somehow has a significant impact on network performance for other users.
It is unclear what additional interest Comcast has in curbing “excessive usage” that does not interfere with its overall network capacity or create network congestion. Comcast’s data cap appears to be aimed at users who are using “too much” data for Comcast’s liking, but not “too much” data to actually interfere with the functioning of the network. This is not a sustainable standard to use to decide who gets access to a critical service such as broadband.
Given these amorphous criteria, it is unclear how Comcast arrived at its 250 GB cap in 2008. Furthermore it remains unclear why, after three years of investing in network upgrades to “better prevent congestion and meet [Comcast’s] customers’ ever increasing demands for bandwidth” that cap has failed to increase. Today, customers with Comcast’s current high-speed offering could hit the 250 GB monthly cap in little more than five hours.
Data caps continue to raise many more questions than they provide answers. While it is clear that they work directly against the widespread use of broadband championed in the National Broadband Plan, it is unclear what legitimate purposes they serve. As such we urge the Commission now, as we did two months ago, to request customer anonymized reports from all ISPs regarding the following:
- Which ISP-offered services are excluded from the cap. This should include reporting on those services, such as voice telephony and video programming, that compete with internet-delivered non-ISP controlled offerings.
- How often the cap is enforced. This should include the absolute number of customers who exceed the cap as well as the percentage of customers who run afoul of the limit. Additionally, it should include amount by which the customers exceeded the cap and how many of those customers are repeat cap exceeders.
- Steps taken to warn customers. This should include the steps taken to warn customers, and when those steps are taken. Additionally, the reporting should include data on the effectiveness of these warnings in preventing overages.
- Average penalty incurred by customers. Caps such as AT&T’s charge additional fees based on how significantly the cap is exceeded. Reporting should include data on the size of the penalties incurred by customers.
- When and how often a penalty is waived. In addition to the publicly announced grace periods, the Commission would be well served by understanding how often and under what circumstances reporting ISPs grant additional waivers.
- The relationship of enforcement to times of network congestion. If used properly, data caps can a tool in easing network congestion. However, there is a constant threat that ISPs use network congestion as a pretext to act on other motives. The Commission would benefit from a nuanced understanding of the relationship between data cap enforcement and network congestion.
- How data caps are set. For example, why did AT&T choose 150GB for DSL and 250GB for U-Verse customers? What criteria are used to arrive at the cap? What criteria are used to determine appropriate overage fees?
- How data caps are evaluated on an ongoing basis. Data caps are often defended as necessary to address current network congestion issues. However, network technology is constantly being modernized and made more efficient. In light of this pattern of improvement, caps that are appropriate for today’s network may be inappropriate in the future. How do ISPs evaluate their existing caps, and what are the conditions under which those caps could be raised and/or eliminated?
We also request that the Commission include additional inquiries regarding the impact of local, regional, and national concentration on the adoption of data caps. Reduced competition at a local level would reduce the impact of a negative consumer response to data caps, and therefore may encourage the adoption of caps.
Although this most recent incident involves Comcast, we are not asking the Commission to investigate Comcast individually. Instead, the Commission should use this incident as an opportunity to begin the process of fully educating itself about the nature and impact of data caps across the industry.
We hope that the Commission recognizes the impediment to widespread broadband use that data caps represent and moves quickly to complete its understanding of their current application.
Respectfully Submitted,
Future of Music Coalition
New America Foundation’s Open Technology Initiative
Public Knowledge
_____/s/_____
Michael Weinberg
Staff Attorney
Public Knowledge
cc: Commissioner Michael Copps
Commissioner Robert McDowell
Commissioner Mignon Clyburn
Chief Sharon Gillette
Chief Rick Kaplan
[log] => Created by Sononaco Drupal Importer
[revision_timestamp] => 1310654922
[format] => 3
[name] => Michael Weinberg
[picture] => files/pictures/picture-2258.png
[data] => a:5:{s:7:"contact";i:0;s:15:"googleanalytics";a:1:{s:6:"custom";i:1;}s:14:"picture_delete";i:0;s:14:"picture_upload";s:0:"";s:14:"wysiwyg_status";a:1:{i:7;i:7;}}
[path] => letter-fcc-regarding-data-caps
[print_display] => 1
[print_display_comment] => 0
[print_display_urllist] => 1
[print_mail_display] => 1
[print_mail_display_comment] => 0
[print_mail_display_urllist] => 1
[print_pdf_display] => 1
[print_pdf_display_comment] => 0
[print_pdf_display_urllist] => 1
[last_comment_timestamp] => 1310654776
[last_comment_name] =>
[comment_count] => 0
[taxonomy] => Array
(
)
[files] => Array
(
)
[page_title] =>
[nodewords] => Array
(
)
[build_mode] => 0
[readmore] => 1
[content] => Array
(
[print_links] => Array
(
[#weight] => -101
[#suffix] =>
[#value] =>
[#prefix] =>
[#title] =>
[#description] =>
[#printed] => 1
)
[field_issue] => Array
(
[#type_name] => documentfile
[#context] => full
[#field_name] => field_issue
[#post_render] => Array
(
[0] => content_field_wrapper_post_render
)
[#weight] => -1
[field] => Array
(
[#description] =>
[items] => Array
(
[#title] =>
[#description] =>
[#printed] => 1
)
[#single] => 1
[#attributes] => Array
(
)
[#required] =>
[#parents] => Array
(
)
[#tree] =>
[#context] => full
[#page] => 1
[#field_name] => field_issue
[#title] => Issues
[#access] => 1
[#label_display] => above
[#teaser] =>
[#node] => stdClass Object
*RECURSION*
[#type] => content_field
[#printed] => 1
)
[#title] =>
[#description] =>
[#printed] => 1
)
[#content_extra_fields] => Array
(
[title] => Array
(
[label] => Title
[description] => Node module form.
[weight] => -5
)
[body_field] => Array
(
[label] => Body
[description] => Node module form.
[weight] => 0
[view] => body
)
[revision_information] => Array
(
[label] => Revision information
[description] => Node module form.
[weight] => 20
)
[author] => Array
(
[label] => Authoring information
[description] => Node module form.
[weight] => 20
)
[options] => Array
(
[label] => Publishing options
[description] => Node module form.
[weight] => 25
)
[comment_settings] => Array
(
[label] => Comment settings
[description] => Comment module form.
[weight] => 30
)
[menu] => Array
(
[label] => Menu settings
[description] => Menu module form.
[weight] => -2
)
[taxonomy] => Array
(
[label] => Taxonomy
[description] => Taxonomy module form.
[weight] => -3
)
[path] => Array
(
[label] => Path settings
[description] => Path module form.
[weight] => 30
)
[attachments] => Array
(
[label] => File attachments
[description] => Upload module form.
[weight] => 30
[view] => files
)
[itunes] => Array
(
[label] => iTunes feed information
[description] => iTunes specific information.
[weight] => 0
)
[path_redirect] => Array
(
[label] => URL redirects
[description] => Path redirect module listing
[weight] => 30
)
[print] => Array
(
[label] => Printer, e-mail and PDF versions
[description] => Print module form.
[weight] => 30
)
[xmlsitemap] => Array
(
[label] => XML sitemap
[description] => XML sitemap module form
[weight] => 30
)
[nodewords] => Array
(
[label] => Meta tags
[description] => Meta tags fieldset.
[weight] => 10
)
)
[#pre_render] => Array
(
[0] => content_alter_extra_weights
)
[body] => Array
(
[#weight] => 0
[#value] => This letter is available as a PDF.
July 14, 2011
Julius Genachowski
Chairman
Federal Communications Commission
445 12th St. SW
Washington, DC 20554
Re: A National Broadband Plan for Our Future, GN Docket No. 09-51
Dear Chairman Genachowski:
On May 6 of this year, Public Knowledge and New America Foundation’s Open Technology Initiative sent a letter urging the Wireline Competition Bureau to exercise its statutory authority to fully investigate the nature, purpose, and impact of data caps upon consumers. Since then, data caps have spread further across the industry. Verizon recently announced data caps for its new 4G wireless service, and left open the possibility of data caps on its FiOS service (a possibility they had long dismissed). The costs of data caps to consumers and society are becoming increasingly clear. We hope the Commission moves quickly to investigate what, if any, benefits balance those costs.
The case of Andre Vrignaud is a stunning illustration of how these data cap policies undercut the values espoused in the National Broadband Plan. After twice being informed by his ISP Comcast that he had exceeded his monthly data cap, Vrignaud has been blacklisted from Comcast for one year. In his account, Vrignaud suggests that remotely backing up two decades worth of photographs and music files is what triggered his yearlong removal from Comcast.
While we have no way to independently verify Vrignaud’s account of this specific incident, we are concerned because it represents an entirely plausible and legitimate use of a residential broadband internet connection. Data caps make this type of use punishable with one year without internet access. This conflict is unsustainable.
In light of this, we are expanding our original request to include an investigation into the data cap policies of all ISPs. There does not appear to be any restraint on the expansion of data caps, or expectation that they will not be widely adopted. Strict data caps are an industry trend that works to undermine the benefits of broadband that this Commission so enthusiastically champions.
The National Broadband Plan specifically mentions cloud-based applications as a benefit of more pervasive, robust broadband networks. As the Plan correctly acknowledges: “[s]oftware based in the cloud may allow more small businesses and consumers to access applications that were once only available to corporations with sophisticated information technology departments in the applications and content markets.” Because of the potential of cloud computing, the Plan recommended additional federal funding to aid in its development.
Interacting with cloud-based applications necessarily involves the transfer of data between a user and the cloud. As a result, increased use of cloud computing will drive a user ever closer to a data cap.
Perhaps most disturbing is the lack of clarity surrounding the legitimate purposes that data caps serve. Some data caps that charge overage fees, such as those imposed by AT&T, at least serve to enrich the ISP. Hard data caps, such as those imposed by Comcast, appear to be pointless.
In 2008, Comcast told the Commission that its data cap is “independent of, and should not be confused with” its congestion management practices. It went on to state that the “cap does not address the issue of network congestion, which results from traffic levels that vary from minute to minute.” Instead of addressing network congestion issues, Comcast’s monthly data cap is intended to curb “excessive use.”
In a direct contradiction these statements, Comcast now defends its caps as necessary to protect quality of service for other users: “[i]f someone’s behavior is such that it degrades the quality of service for others nearby — that’s what this threshold is meant to address.” Public Knowledge, Future of Music Project, and New America Foundation’s Open Technology Initiative find it unlikely that uploading data to remote servers at off peak times, a behavior pattern that could easily trigger Comcast’s data cap, somehow has a significant impact on network performance for other users.
It is unclear what additional interest Comcast has in curbing “excessive usage” that does not interfere with its overall network capacity or create network congestion. Comcast’s data cap appears to be aimed at users who are using “too much” data for Comcast’s liking, but not “too much” data to actually interfere with the functioning of the network. This is not a sustainable standard to use to decide who gets access to a critical service such as broadband.
Given these amorphous criteria, it is unclear how Comcast arrived at its 250 GB cap in 2008. Furthermore it remains unclear why, after three years of investing in network upgrades to “better prevent congestion and meet [Comcast’s] customers’ ever increasing demands for bandwidth” that cap has failed to increase. Today, customers with Comcast’s current high-speed offering could hit the 250 GB monthly cap in little more than five hours.
Data caps continue to raise many more questions than they provide answers. While it is clear that they work directly against the widespread use of broadband championed in the National Broadband Plan, it is unclear what legitimate purposes they serve. As such we urge the Commission now, as we did two months ago, to request customer anonymized reports from all ISPs regarding the following:
- Which ISP-offered services are excluded from the cap. This should include reporting on those services, such as voice telephony and video programming, that compete with internet-delivered non-ISP controlled offerings.
- How often the cap is enforced. This should include the absolute number of customers who exceed the cap as well as the percentage of customers who run afoul of the limit. Additionally, it should include amount by which the customers exceeded the cap and how many of those customers are repeat cap exceeders.
- Steps taken to warn customers. This should include the steps taken to warn customers, and when those steps are taken. Additionally, the reporting should include data on the effectiveness of these warnings in preventing overages.
- Average penalty incurred by customers. Caps such as AT&T’s charge additional fees based on how significantly the cap is exceeded. Reporting should include data on the size of the penalties incurred by customers.
- When and how often a penalty is waived. In addition to the publicly announced grace periods, the Commission would be well served by understanding how often and under what circumstances reporting ISPs grant additional waivers.
- The relationship of enforcement to times of network congestion. If used properly, data caps can a tool in easing network congestion. However, there is a constant threat that ISPs use network congestion as a pretext to act on other motives. The Commission would benefit from a nuanced understanding of the relationship between data cap enforcement and network congestion.
- How data caps are set. For example, why did AT&T choose 150GB for DSL and 250GB for U-Verse customers? What criteria are used to arrive at the cap? What criteria are used to determine appropriate overage fees?
- How data caps are evaluated on an ongoing basis. Data caps are often defended as necessary to address current network congestion issues. However, network technology is constantly being modernized and made more efficient. In light of this pattern of improvement, caps that are appropriate for today’s network may be inappropriate in the future. How do ISPs evaluate their existing caps, and what are the conditions under which those caps could be raised and/or eliminated?
We also request that the Commission include additional inquiries regarding the impact of local, regional, and national concentration on the adoption of data caps. Reduced competition at a local level would reduce the impact of a negative consumer response to data caps, and therefore may encourage the adoption of caps.
Although this most recent incident involves Comcast, we are not asking the Commission to investigate Comcast individually. Instead, the Commission should use this incident as an opportunity to begin the process of fully educating itself about the nature and impact of data caps across the industry.
We hope that the Commission recognizes the impediment to widespread broadband use that data caps represent and moves quickly to complete its understanding of their current application.
Respectfully Submitted,
Future of Music Coalition
New America Foundation’s Open Technology Initiative
Public Knowledge
_____/s/_____
Michael Weinberg
Staff Attorney
Public Knowledge
cc: Commissioner Michael Copps
Commissioner Robert McDowell
Commissioner Mignon Clyburn
Chief Sharon Gillette
Chief Rick Kaplan
[#title] =>
[#description] =>
[#printed] => 1
)
[#title] =>
[#description] =>
[#children] => This letter is available as a PDF.
July 14, 2011
Julius Genachowski
Chairman
Federal Communications Commission
445 12th St. SW
Washington, DC 20554
Re: A National Broadband Plan for Our Future, GN Docket No. 09-51
Dear Chairman Genachowski:
On May 6 of this year, Public Knowledge and New America Foundation’s Open Technology Initiative sent a letter urging the Wireline Competition Bureau to exercise its statutory authority to fully investigate the nature, purpose, and impact of data caps upon consumers. Since then, data caps have spread further across the industry. Verizon recently announced data caps for its new 4G wireless service, and left open the possibility of data caps on its FiOS service (a possibility they had long dismissed). The costs of data caps to consumers and society are becoming increasingly clear. We hope the Commission moves quickly to investigate what, if any, benefits balance those costs.
The case of Andre Vrignaud is a stunning illustration of how these data cap policies undercut the values espoused in the National Broadband Plan. After twice being informed by his ISP Comcast that he had exceeded his monthly data cap, Vrignaud has been blacklisted from Comcast for one year. In his account, Vrignaud suggests that remotely backing up two decades worth of photographs and music files is what triggered his yearlong removal from Comcast.
While we have no way to independently verify Vrignaud’s account of this specific incident, we are concerned because it represents an entirely plausible and legitimate use of a residential broadband internet connection. Data caps make this type of use punishable with one year without internet access. This conflict is unsustainable.
In light of this, we are expanding our original request to include an investigation into the data cap policies of all ISPs. There does not appear to be any restraint on the expansion of data caps, or expectation that they will not be widely adopted. Strict data caps are an industry trend that works to undermine the benefits of broadband that this Commission so enthusiastically champions.
The National Broadband Plan specifically mentions cloud-based applications as a benefit of more pervasive, robust broadband networks. As the Plan correctly acknowledges: “[s]oftware based in the cloud may allow more small businesses and consumers to access applications that were once only available to corporations with sophisticated information technology departments in the applications and content markets.” Because of the potential of cloud computing, the Plan recommended additional federal funding to aid in its development.
Interacting with cloud-based applications necessarily involves the transfer of data between a user and the cloud. As a result, increased use of cloud computing will drive a user ever closer to a data cap.
Perhaps most disturbing is the lack of clarity surrounding the legitimate purposes that data caps serve. Some data caps that charge overage fees, such as those imposed by AT&T, at least serve to enrich the ISP. Hard data caps, such as those imposed by Comcast, appear to be pointless.
In 2008, Comcast told the Commission that its data cap is “independent of, and should not be confused with” its congestion management practices. It went on to state that the “cap does not address the issue of network congestion, which results from traffic levels that vary from minute to minute.” Instead of addressing network congestion issues, Comcast’s monthly data cap is intended to curb “excessive use.”
In a direct contradiction these statements, Comcast now defends its caps as necessary to protect quality of service for other users: “[i]f someone’s behavior is such that it degrades the quality of service for others nearby — that’s what this threshold is meant to address.” Public Knowledge, Future of Music Project, and New America Foundation’s Open Technology Initiative find it unlikely that uploading data to remote servers at off peak times, a behavior pattern that could easily trigger Comcast’s data cap, somehow has a significant impact on network performance for other users.
It is unclear what additional interest Comcast has in curbing “excessive usage” that does not interfere with its overall network capacity or create network congestion. Comcast’s data cap appears to be aimed at users who are using “too much” data for Comcast’s liking, but not “too much” data to actually interfere with the functioning of the network. This is not a sustainable standard to use to decide who gets access to a critical service such as broadband.
Given these amorphous criteria, it is unclear how Comcast arrived at its 250 GB cap in 2008. Furthermore it remains unclear why, after three years of investing in network upgrades to “better prevent congestion and meet [Comcast’s] customers’ ever increasing demands for bandwidth” that cap has failed to increase. Today, customers with Comcast’s current high-speed offering could hit the 250 GB monthly cap in little more than five hours.
Data caps continue to raise many more questions than they provide answers. While it is clear that they work directly against the widespread use of broadband championed in the National Broadband Plan, it is unclear what legitimate purposes they serve. As such we urge the Commission now, as we did two months ago, to request customer anonymized reports from all ISPs regarding the following:
- Which ISP-offered services are excluded from the cap. This should include reporting on those services, such as voice telephony and video programming, that compete with internet-delivered non-ISP controlled offerings.
- How often the cap is enforced. This should include the absolute number of customers who exceed the cap as well as the percentage of customers who run afoul of the limit. Additionally, it should include amount by which the customers exceeded the cap and how many of those customers are repeat cap exceeders.
- Steps taken to warn customers. This should include the steps taken to warn customers, and when those steps are taken. Additionally, the reporting should include data on the effectiveness of these warnings in preventing overages.
- Average penalty incurred by customers. Caps such as AT&T’s charge additional fees based on how significantly the cap is exceeded. Reporting should include data on the size of the penalties incurred by customers.
- When and how often a penalty is waived. In addition to the publicly announced grace periods, the Commission would be well served by understanding how often and under what circumstances reporting ISPs grant additional waivers.
- The relationship of enforcement to times of network congestion. If used properly, data caps can a tool in easing network congestion. However, there is a constant threat that ISPs use network congestion as a pretext to act on other motives. The Commission would benefit from a nuanced understanding of the relationship between data cap enforcement and network congestion.
- How data caps are set. For example, why did AT&T choose 150GB for DSL and 250GB for U-Verse customers? What criteria are used to arrive at the cap? What criteria are used to determine appropriate overage fees?
- How data caps are evaluated on an ongoing basis. Data caps are often defended as necessary to address current network congestion issues. However, network technology is constantly being modernized and made more efficient. In light of this pattern of improvement, caps that are appropriate for today’s network may be inappropriate in the future. How do ISPs evaluate their existing caps, and what are the conditions under which those caps could be raised and/or eliminated?
We also request that the Commission include additional inquiries regarding the impact of local, regional, and national concentration on the adoption of data caps. Reduced competition at a local level would reduce the impact of a negative consumer response to data caps, and therefore may encourage the adoption of caps.
Although this most recent incident involves Comcast, we are not asking the Commission to investigate Comcast individually. Instead, the Commission should use this incident as an opportunity to begin the process of fully educating itself about the nature and impact of data caps across the industry.
We hope that the Commission recognizes the impediment to widespread broadband use that data caps represent and moves quickly to complete its understanding of their current application.
Respectfully Submitted,
Future of Music Coalition
New America Foundation’s Open Technology Initiative
Public Knowledge
_____/s/_____
Michael Weinberg
Staff Attorney
Public Knowledge
cc: Commissioner Michael Copps
Commissioner Robert McDowell
Commissioner Mignon Clyburn
Chief Sharon Gillette
Chief Rick Kaplan
[#printed] => 1
)
[links] => Array
(
[print_html] => Array
(
[href] => print/6283
[title] => Printer-friendly version
[attributes] => Array
(
[title] => Display a printer-friendly version of this page.
[class] => print-page
[rel] => nofollow
)
[html] =>
[query] =>
)
)
)