public interest

Content tagged with "public interest"

Displaying 21 - 30 of 80

Comcast, Caps, and the Public Interest

While I try to keep postings on this site to the subject of publicly owned networks, I think it important to discuss the ways in which some major carriers routinely flout the public interest. Thus, a little history on how Comcast has acted against the public interest. Most of the readers of this blog are probably aware that Comcast has been dinged by the FCC following its practice of interfering with subscribers legal content (and undoubtedly illegal content as well) by blocking and disrupting the BitTorrent traffic. BitTorrent is frequently used to transfer large media files because it efficiently breaks large files into many little pieces, allowing the user to download from a variety of sources concurrently - the file is then reassembled. When Comcast detected BitTorrent connections, it would effectively hang up on them, regardless of the congestion level on the network at the time. The FCC (the Bush Administration's FCC) said it couldn't do that and Comcast is currently in the courts trying to tell the FCC that it can't tell Comcast what it can't do on its network. Prior to a journalistic investigation that proved Comcast was doing this, net geeks had repeated asked Comcast if it were blocking the BitTorrent protocol. Comcast never admitted to anything, often claiming it did not "block" anything... as time would go on, Comcast would refuse to admit it was blocking anything - as if permanently delaying traffic was anything other than a blockage. "I'm not blocking you, try back in 20 million years." Around this time, Comcast quietly changed its policy regarding the maximum amount of bandwidth subscribers could consume in a month. At the time, I thought it was a result of the FCC cracking down on the arbitrary policies frequently used by cable companies, but it turns out we can thank the State of Florida for forcing Comcast to enact a transparent cap on monthly usage. Prior to the official cap, there was an unofficial cap. Every month, some number of people would be notified they were kicked off Comcast's service for using too much bandwidth - but no one knew how much was too much and, perhaps more importantly, how to keep track of how much bandwidth they were using. Discussions on geek-hangout Slashdot suggested a monthly cap of between 100 Gigabytes and 300 Gigabytes depending on the neighborhood.

Comcast, Caps, and the Public Interest

While I try to keep postings on this site to the subject of publicly owned networks, I think it important to discuss the ways in which some major carriers routinely flout the public interest. Thus, a little history on how Comcast has acted against the public interest. Most of the readers of this blog are probably aware that Comcast has been dinged by the FCC following its practice of interfering with subscribers legal content (and undoubtedly illegal content as well) by blocking and disrupting the BitTorrent traffic. BitTorrent is frequently used to transfer large media files because it efficiently breaks large files into many little pieces, allowing the user to download from a variety of sources concurrently - the file is then reassembled. When Comcast detected BitTorrent connections, it would effectively hang up on them, regardless of the congestion level on the network at the time. The FCC (the Bush Administration's FCC) said it couldn't do that and Comcast is currently in the courts trying to tell the FCC that it can't tell Comcast what it can't do on its network. Prior to a journalistic investigation that proved Comcast was doing this, net geeks had repeated asked Comcast if it were blocking the BitTorrent protocol. Comcast never admitted to anything, often claiming it did not "block" anything... as time would go on, Comcast would refuse to admit it was blocking anything - as if permanently delaying traffic was anything other than a blockage. "I'm not blocking you, try back in 20 million years." Around this time, Comcast quietly changed its policy regarding the maximum amount of bandwidth subscribers could consume in a month. At the time, I thought it was a result of the FCC cracking down on the arbitrary policies frequently used by cable companies, but it turns out we can thank the State of Florida for forcing Comcast to enact a transparent cap on monthly usage. Prior to the official cap, there was an unofficial cap. Every month, some number of people would be notified they were kicked off Comcast's service for using too much bandwidth - but no one knew how much was too much and, perhaps more importantly, how to keep track of how much bandwidth they were using. Discussions on geek-hangout Slashdot suggested a monthly cap of between 100 Gigabytes and 300 Gigabytes depending on the neighborhood.

Comcast, Caps, and the Public Interest

While I try to keep postings on this site to the subject of publicly owned networks, I think it important to discuss the ways in which some major carriers routinely flout the public interest. Thus, a little history on how Comcast has acted against the public interest. Most of the readers of this blog are probably aware that Comcast has been dinged by the FCC following its practice of interfering with subscribers legal content (and undoubtedly illegal content as well) by blocking and disrupting the BitTorrent traffic. BitTorrent is frequently used to transfer large media files because it efficiently breaks large files into many little pieces, allowing the user to download from a variety of sources concurrently - the file is then reassembled. When Comcast detected BitTorrent connections, it would effectively hang up on them, regardless of the congestion level on the network at the time. The FCC (the Bush Administration's FCC) said it couldn't do that and Comcast is currently in the courts trying to tell the FCC that it can't tell Comcast what it can't do on its network. Prior to a journalistic investigation that proved Comcast was doing this, net geeks had repeated asked Comcast if it were blocking the BitTorrent protocol. Comcast never admitted to anything, often claiming it did not "block" anything... as time would go on, Comcast would refuse to admit it was blocking anything - as if permanently delaying traffic was anything other than a blockage. "I'm not blocking you, try back in 20 million years." Around this time, Comcast quietly changed its policy regarding the maximum amount of bandwidth subscribers could consume in a month. At the time, I thought it was a result of the FCC cracking down on the arbitrary policies frequently used by cable companies, but it turns out we can thank the State of Florida for forcing Comcast to enact a transparent cap on monthly usage. Prior to the official cap, there was an unofficial cap. Every month, some number of people would be notified they were kicked off Comcast's service for using too much bandwidth - but no one knew how much was too much and, perhaps more importantly, how to keep track of how much bandwidth they were using. Discussions on geek-hangout Slashdot suggested a monthly cap of between 100 Gigabytes and 300 Gigabytes depending on the neighborhood.

Comcast, Caps, and the Public Interest

While I try to keep postings on this site to the subject of publicly owned networks, I think it important to discuss the ways in which some major carriers routinely flout the public interest. Thus, a little history on how Comcast has acted against the public interest. Most of the readers of this blog are probably aware that Comcast has been dinged by the FCC following its practice of interfering with subscribers legal content (and undoubtedly illegal content as well) by blocking and disrupting the BitTorrent traffic. BitTorrent is frequently used to transfer large media files because it efficiently breaks large files into many little pieces, allowing the user to download from a variety of sources concurrently - the file is then reassembled. When Comcast detected BitTorrent connections, it would effectively hang up on them, regardless of the congestion level on the network at the time. The FCC (the Bush Administration's FCC) said it couldn't do that and Comcast is currently in the courts trying to tell the FCC that it can't tell Comcast what it can't do on its network. Prior to a journalistic investigation that proved Comcast was doing this, net geeks had repeated asked Comcast if it were blocking the BitTorrent protocol. Comcast never admitted to anything, often claiming it did not "block" anything... as time would go on, Comcast would refuse to admit it was blocking anything - as if permanently delaying traffic was anything other than a blockage. "I'm not blocking you, try back in 20 million years." Around this time, Comcast quietly changed its policy regarding the maximum amount of bandwidth subscribers could consume in a month. At the time, I thought it was a result of the FCC cracking down on the arbitrary policies frequently used by cable companies, but it turns out we can thank the State of Florida for forcing Comcast to enact a transparent cap on monthly usage. Prior to the official cap, there was an unofficial cap. Every month, some number of people would be notified they were kicked off Comcast's service for using too much bandwidth - but no one knew how much was too much and, perhaps more importantly, how to keep track of how much bandwidth they were using. Discussions on geek-hangout Slashdot suggested a monthly cap of between 100 Gigabytes and 300 Gigabytes depending on the neighborhood.

Comcast, Caps, and the Public Interest

While I try to keep postings on this site to the subject of publicly owned networks, I think it important to discuss the ways in which some major carriers routinely flout the public interest. Thus, a little history on how Comcast has acted against the public interest. Most of the readers of this blog are probably aware that Comcast has been dinged by the FCC following its practice of interfering with subscribers legal content (and undoubtedly illegal content as well) by blocking and disrupting the BitTorrent traffic. BitTorrent is frequently used to transfer large media files because it efficiently breaks large files into many little pieces, allowing the user to download from a variety of sources concurrently - the file is then reassembled. When Comcast detected BitTorrent connections, it would effectively hang up on them, regardless of the congestion level on the network at the time. The FCC (the Bush Administration's FCC) said it couldn't do that and Comcast is currently in the courts trying to tell the FCC that it can't tell Comcast what it can't do on its network. Prior to a journalistic investigation that proved Comcast was doing this, net geeks had repeated asked Comcast if it were blocking the BitTorrent protocol. Comcast never admitted to anything, often claiming it did not "block" anything... as time would go on, Comcast would refuse to admit it was blocking anything - as if permanently delaying traffic was anything other than a blockage. "I'm not blocking you, try back in 20 million years." Around this time, Comcast quietly changed its policy regarding the maximum amount of bandwidth subscribers could consume in a month. At the time, I thought it was a result of the FCC cracking down on the arbitrary policies frequently used by cable companies, but it turns out we can thank the State of Florida for forcing Comcast to enact a transparent cap on monthly usage. Prior to the official cap, there was an unofficial cap. Every month, some number of people would be notified they were kicked off Comcast's service for using too much bandwidth - but no one knew how much was too much and, perhaps more importantly, how to keep track of how much bandwidth they were using. Discussions on geek-hangout Slashdot suggested a monthly cap of between 100 Gigabytes and 300 Gigabytes depending on the neighborhood.

Broadband Truth-in-Labeling

Kudos to the New American Foundation's Open Technology Initiative (OTI). Earlier this week, I told Geoff Daily that we would all benefit from some form of a truth-in-labeling requirement for broadband. This should be a no-brainer that both the FCC and FTC embrace because it will educate subscribers and allow them to make better, more informed choices - which is a requirement for a functioning market. One day later it became apparent that I was too slow in my idea, because OTI already had a prototype. They even have a sample label and have come up with a great set of required disclosures.
To make sure the broadband service is clearly expressed, the Broadband Truth-in-Labeling disclosure should be standardized to comprise several typical elements as indicators of broadband service quality, such as minimum expected speed and latency to the ISP's border router (where the ISP connects to the rest of the Internet) and service uptime. These minimum assurances will be supported by the ISP as guarantees in the delivery of broadband services, backed by technical support and service charge refunds or credits. In addition to the description of minimums being guaranteed of the service, the disclosure should include all applicable fees, a common description of the technology used to provide the services, any service limits such as a bandwidth cap or the application of any traffic management techniques, the length of the contract terms, and a link to all additional terms and conditions. Requirements should be established for disclosing any highly objectionable or surprising terms such as arbitration restrictions or information or data selling. 

Broadband Truth-in-Labeling

Kudos to the New American Foundation's Open Technology Initiative (OTI). Earlier this week, I told Geoff Daily that we would all benefit from some form of a truth-in-labeling requirement for broadband. This should be a no-brainer that both the FCC and FTC embrace because it will educate subscribers and allow them to make better, more informed choices - which is a requirement for a functioning market. One day later it became apparent that I was too slow in my idea, because OTI already had a prototype. They even have a sample label and have come up with a great set of required disclosures.
To make sure the broadband service is clearly expressed, the Broadband Truth-in-Labeling disclosure should be standardized to comprise several typical elements as indicators of broadband service quality, such as minimum expected speed and latency to the ISP's border router (where the ISP connects to the rest of the Internet) and service uptime. These minimum assurances will be supported by the ISP as guarantees in the delivery of broadband services, backed by technical support and service charge refunds or credits. In addition to the description of minimums being guaranteed of the service, the disclosure should include all applicable fees, a common description of the technology used to provide the services, any service limits such as a bandwidth cap or the application of any traffic management techniques, the length of the contract terms, and a link to all additional terms and conditions. Requirements should be established for disclosing any highly objectionable or surprising terms such as arbitration restrictions or information or data selling. 

Verizon Actions Show Carriers Will Not Wire Rural America

In a recent post the NY Times Bits Blog, Saul Hansell reports "Verizon Boss Hangs Up on Landline Phone Business" - something we have long known. Nonetheless, this makes it even more official: private companies have no interest in bringing true broadband to everyone in the United States. Verizon is happy to invest in next-generation networks in wealthy suburbs and large metro regions but people in rural areas - who have long dealt with decaying telephone infrastructure - will be lucky to get slow DSL speeds that leave them unable to participate in the digital age. These people will be spun off to other companies so Verizon can focus on the most profitable areas. For instance, Verizon found it profitable to spin off its customers in Hawaii to another company that quickly ran into trouble before unloading most of its New England customer on FairPoint, moves that enhanced Verizon's bottom line while harming many communities (see the bottom of this post and other posts about FairPoint). Isen has been writing about it recently - picking up on FairPoint immediately breaking its promises to expand broadband access in the newly acquired territories. No surprise there. Isen also delved deeper into Verizon's actions, with "Verizon throws 18 states under the progress train." He is right to push this as a national story - the national media focused intently on the absence of major carriers in the broadband stimulus package but they seem utterly uninterested in major carriers running away from broadband investments in rural areas. Though Frontier likes to position itself as a company focused on bringing broadband to rural areas, it offers slow DSL broadband and poor customer service to people who have no other choices - more of a parasite than angel. As long as we view broadband as a vehicle for moving profits from communities to absentee-owned corporations rather than the infrastructure it truly is, we will farther and farther behind our international peers in the modern economy.

Verizon Actions Show Carriers Will Not Wire Rural America

In a recent post the NY Times Bits Blog, Saul Hansell reports "Verizon Boss Hangs Up on Landline Phone Business" - something we have long known. Nonetheless, this makes it even more official: private companies have no interest in bringing true broadband to everyone in the United States. Verizon is happy to invest in next-generation networks in wealthy suburbs and large metro regions but people in rural areas - who have long dealt with decaying telephone infrastructure - will be lucky to get slow DSL speeds that leave them unable to participate in the digital age. These people will be spun off to other companies so Verizon can focus on the most profitable areas. For instance, Verizon found it profitable to spin off its customers in Hawaii to another company that quickly ran into trouble before unloading most of its New England customer on FairPoint, moves that enhanced Verizon's bottom line while harming many communities (see the bottom of this post and other posts about FairPoint). Isen has been writing about it recently - picking up on FairPoint immediately breaking its promises to expand broadband access in the newly acquired territories. No surprise there. Isen also delved deeper into Verizon's actions, with "Verizon throws 18 states under the progress train." He is right to push this as a national story - the national media focused intently on the absence of major carriers in the broadband stimulus package but they seem utterly uninterested in major carriers running away from broadband investments in rural areas. Though Frontier likes to position itself as a company focused on bringing broadband to rural areas, it offers slow DSL broadband and poor customer service to people who have no other choices - more of a parasite than angel. As long as we view broadband as a vehicle for moving profits from communities to absentee-owned corporations rather than the infrastructure it truly is, we will farther and farther behind our international peers in the modern economy.

Verizon Actions Show Carriers Will Not Wire Rural America

In a recent post the NY Times Bits Blog, Saul Hansell reports "Verizon Boss Hangs Up on Landline Phone Business" - something we have long known. Nonetheless, this makes it even more official: private companies have no interest in bringing true broadband to everyone in the United States. Verizon is happy to invest in next-generation networks in wealthy suburbs and large metro regions but people in rural areas - who have long dealt with decaying telephone infrastructure - will be lucky to get slow DSL speeds that leave them unable to participate in the digital age. These people will be spun off to other companies so Verizon can focus on the most profitable areas. For instance, Verizon found it profitable to spin off its customers in Hawaii to another company that quickly ran into trouble before unloading most of its New England customer on FairPoint, moves that enhanced Verizon's bottom line while harming many communities (see the bottom of this post and other posts about FairPoint). Isen has been writing about it recently - picking up on FairPoint immediately breaking its promises to expand broadband access in the newly acquired territories. No surprise there. Isen also delved deeper into Verizon's actions, with "Verizon throws 18 states under the progress train." He is right to push this as a national story - the national media focused intently on the absence of major carriers in the broadband stimulus package but they seem utterly uninterested in major carriers running away from broadband investments in rural areas. Though Frontier likes to position itself as a company focused on bringing broadband to rural areas, it offers slow DSL broadband and poor customer service to people who have no other choices - more of a parasite than angel. As long as we view broadband as a vehicle for moving profits from communities to absentee-owned corporations rather than the infrastructure it truly is, we will farther and farther behind our international peers in the modern economy.