This Blog Is Not For Reading

A blog, just like any blog, only more so

  • Subscribe

  • Categories

  • RSS Bob Jonkman’s Microblog

    • bobjonkman repeated a notice by steve 16 September 2021
      RT @steve @bobjonkman I really appreciate it, Bob!
    • Favorite 16 September 2021
      bobjonkman favorited something by steve: @bobjonkman I really appreciate it, Bob!
    • New note by bobjonkman 12 September 2021
      #Stroopwafels FTW! https://en.wikipedia.org/wiki/Stroopwafel
    • Favorite 12 September 2021
      bobjonkman favorited something by guizzy: Today @mitsu and I went to a Spanish specialty grocery store, got sobressada and menorcan cheese. Then we went to an european specialty store and got stroopwaffels. And we went to Bagel St-Viateur, and got freshly made bagels (the real stuff, not New York pretenders) to enjoy with some smoked […]
    • New note by bobjonkman 12 September 2021
      Hang in there, Dr. Sekula. Your summer somewhat mirrors mine: Conflicted about working in a Covid environment; trying to stay engaged in politics (not physics research); the loss of my father and admitting my mom to a long-term care facility where Covid mortality is high. We'll pull through, and if the future looks different from […]
    • bobjonkman repeated a notice by steve 12 September 2021
      RT @steve "End of Summer, 2021" Ive gone silent in this blog. Take it as a sign of everything else that has been going on. Writing in this blog is the first thing to be sacrificed when life intervenes. Its been many months since I wrote here. Truth be told, I think I need to […]
    • Favorite 12 September 2021
      bobjonkman favorited something by steve: "End of Summer, 2021" Ive gone silent in this blog. Take it as a sign of everything else that has been going on. Writing in this blog is the first thing to be sacrificed when life intervenes. Its been many months since I wrote here. Truth be told, I think […]
    • Favorite 9 June 2021
      bobjonkman favorited something by lnxw48a1: Last year, while visiting #sonTwo and meeting #GS3 in person for the first time, I asked my daughter-in-law about smoke and carbon monoxide detectors. She said they had one of each, but she wanted more. So I ordered a few of each and they put them up. Tonight, the gas […]
    • New note by bobjonkman 2 May 2021
      But human labour only produces surplus value when it's being exploited. If humans are paid a fair value for their labour then there is no "surplus", ie. no profit for the corporate owners. This is why I favour worker-owned co-operatives instead of capitalist-owned corporations.
    • bobjonkman repeated a notice by lxo 2 May 2021
      RT @lxo the greatest challenge of automation for a capitalist economy is that machines don't produce surplus value, only human labor does

Archive for the 'dslreports' Category

Usage Based Billing Considered Harmful

Posted by Bob Jonkman on 13th August 2009

The CRTC approved Bell’s request to charge the customers of third-party ISPs “Usage Based Billing”, to take effect in 90 days (November 2009).

There’s much discussion on DSL Reports. Rocky Gaudrault, the president of Teksavvy ISP, weighs in with some advice: We’ll all need to make a concerted effort to curb our downloading to ensure we don’t give a dime more to Bell than we need to. We all know this is a cash grab and anti-competitive tactic […]

Teksavvy offers a Premium package for $29.95 with $0.25/GiByte over 200 GiBytes, and an Unlimited package for $39.95, but with the new rates Bell won’t allow Teksavvy to offer an Unlimited package. Customers who use more than 60 GiBytes of bandwidth would be charged an extra $22.50 a month. For Teksavvy’s Premium customers, this is nearly double the current price. Customers who use more than 300 GiBytes in month would be charged an additional $0.75/GiByte. For that extra money you don’t get faster speeds than today. For that extra money you don’t get more downloads than today. For that extra money you don’t get a higher quality Internet. And that extra money goes to Bell, not Teksavvy.

Teksavvy UBB rates chart

Image from the OpenOffice spreadsheet Teksavvy possible UBB pricing.

Disclaimer: This is presented strictly as a comparison between what Teksavvy offers today and what might be the costs after UBB is implemented. This is sheer speculation; there has been no contact with Teksavvy staff on this.

60 GiBytes isn’t much, today:

  • 1 GiByte is about 300 average Flickr photos.
  • 1 GiByte is about 3 hours of watching YouTube videos — if you watch an hour a day you’ll use about 10 GiBytes/month.
  • Using Bittorrent to download Ubuntu (or a movie) uses about 1.5 GiBytes.
  • Downloading one season of a TV show is about 16 GiBytes.
  • Downloading one High-Definition movie is about 40 GiBytes.

Remember that this is charged both coming and going, so you’ll be paying for all the spam that arrives in your mailbox, all the ads on websites, all the automatic Windows updates.

Customers who only use e-mail and do a bit of Web surfing probably won’t be affected by the rate increase. But anyone who uses the Internet more than casually will be paying more.

Even worse are the “Chilling Effects” – who’s going to develop new cool Web 2.0 applications if they’re constantly watching the meter to ensure they don’t exceed the 60 GiByte cap? Who’s going to sign up for online video services if the movies exceed the cap?

Canada has certainly fallen behind the technology curve. Usage Based Billing puts Canada in an even worse position than the OECD reported in 2008.

If you want to protest this, submit a complaint to the CRTC.
For the type of application select Tariff, and as a subject, use File Number # 8740-B2-200904989 – Bell Canada – TN 7181. Thanx to Antonio Cangiano for these instructions!

I sent them this complaint:

I was disappointed to learn that the CRTC has approved Bell’s request to charge Usage Based Billing on connections for independent resellers, despite the CRTC’s own admission that most submissions from Canadians are opposed to such a tariff.

Usage Based Billing adds a significant cost to Internet services supplied by independent operators, reducing their ability to differentiate based on bandwidth and price. Worse, Bell’s proposed rates to its own customers appear to be less than what it is charging to independent ISPs. The obvious conclusion is that Bell is trying to eliminate its competition.

Recent reports on global bandwidth have already placed Canada next-to-last in cost per megabyte of bandwidth. This latest tariff will only increase prices for consumers, without providing any increase in service. Canada will surely be in absolute last place globally when the next report is issued.

The CRTC is mandated to provide telecom regulation to benefit Canadians. With this tariff, the only Canadians to benefit are Bell shareholders.

–Bob.

Posted in Bell Canada, considered harmful, CRTC, dslreports, Net Neutrality, teksavvy, usage based billing | 5 Comments »

Blocking port 25 considered harmful

Posted by Bob Jonkman on 10th December 2008

Coffee cup with a broken handle on a cluttered desk

Coffeine abuse by maciekbor

Over in the Teksavvy Forum at DSLReports Rocky Gaudrault, the owner of my ISP, Teksavvy, started a discussion on blocking port 25 entitled “Argg…. UCEPROTECT… very frustrating!“. This is my reply:

Two cents I’d like to contribute:

The UCEPROTECT service isn’t blocking e-mail, it merely provides an opinion on an IP’s reputation as a mail server. Technically, this opinion is expressed with a DNSBL.

When mail doesn’t get delivered, it’s the receiving mail server that blocks it, not UCEPROTECT. The recipient may reject the mail based on the opinion of the DNSBL, but if that DNSBL gives bogus information then the recipient will be blocking legitimate mail. The fault is with the mail recipient for choosing a poor DNSBL. It’s not Teksavvy customers who can’t send e-mail, it’s the recipients who are refusing to accept it.

Even if Teksavvy did block port 25, there’s no guarantee that poor DNSBL services would whitelist Teksavvy’s servers. DNSBLs are run at the whim of their operators, and they can blacklist anything they like. The people who use these services need to understand that they’re letting someone else decide what mail they can receive, completely out of their control.

Port blocking is ineffective as a spam fighting technique — ISPs started port blocking in 2001, but if port blocking is so good, why is there still spam? Most spam still comes from disreputable bulk mailers running large-scale operations. Remember the McColo servers from a few weeks ago? When that one operation was shut down there were reports that spam volumes dropped by 30%. To fight spam, concentrate on the large-scale spammers.

There are lots of spambots running on poorly protected home computers, but that’s a symptom of poor security. Blocking port 25 won’t fix the security problem. To fight poor security it’s far better to identify the compromised computers, and provide them with tech support to fix the problem. Teksavvy is in a better position to do that than any other service provider I know.

There is no benefit to Teksavvy customers in blocking port 25 — It doesn’t protect Teksavvy customers from spam. It might protect other ISP’s customers from Teksavvy spammers, but it also denies Teksavvy customers full access to the Internet. Full, unblocked access is one of the main differentiators that Teksavvy brings to the market. Don’t give that up, Rocky.

Blocking ports also prevents legitimate services. ESMTP extensions like DSN rely on a direct connection to transfer Delivery Status Notifications. If a relay server doesn’t implement DSN then status notifications don’t get through. If port blocking is turned on, the smart host providing the relay service had better implement every ESMTP extension that exists. And that could still block other services that rely on unfettered access to port 25 (iMIP anyone?)

Blocking one port today is the thin edge of the wedge to blocking other services. Already I’ve seen requests for blocking ports 137 and other Netbios ports. If Teksavvy starts port blocking then every time there’s a new vulnerability the Teksavvy execs will need to agonize over whether to block or not. DNS is broken? Block port 53. There’s child porn on Usenet? Block port 119. CRIA threatens to shut down encrypted filesharing? Block port 443. If Teksavvy has a policy of no port blocking, all these decisions are moot.

I left Rogers because of port blocking, and came to Teksavvy because of unfettered access. Please don’t take that away.

–Bob.


Coffeine Abuse by maciekbor is used under a CC-BYCreative Commons Attribution license.

Posted in considered harmful, dnsbl, dslreports, port blocking, smtp, teksavvy | 7 Comments »

 
Better Tag Cloud