Skip to Content

CRTC Net Neutrality Hearings

Monday July 20, 2009
CRTC Net Neutrality Hearing Open Door To Regulatory Action
Regulatory hearings on Internet traffic management practices held in windowless rooms in Gatineau, Quebec in the middle of summer are not likely candidates to attract much attention.  Yet, as my weekly technology column notes (Toronto Star version, homepage version) for seven days this month, hundreds of Canadians listened to webcasts of Internet service providers defend their previously secret practices while engaging in a robust debate on net neutrality. The interest in the Canadian Radio-television and Telecommunications Commission hearing may have caught the regulator off-guard (the webcast traffic was, by a wide margin, its most ever for a hearing), but it was the testimony itself that was the greatest source of surprise.

The seven-day hearing was billed as a debate over whether rules are needed to govern ISP network management practices. While many Internet users remain unaware of the issue, behind the scenes ISPs employ a variety of mechanisms to control the flow of traffic on their networks, with some restricting or throttling the speeds for some applications.

Those practices have proven highly contentious, with creator interests, technology companies, privacy rights organizations, and consumer groups all expressing fears that they may curtail innovation, invade user privacy, stifle competition, and create an uneven playing field for content distribution.  ISPs argue that such measures are essential to provide their subscribers with a good experience at an affordable price.

Days of testimony revealed the issue is far more complicated than the rhetoric might suggest. First, there is a wide variation in the use of traffic management tools with a different approach for pretty much every major ISP.  Some throttle all the time (Cogeco), some during large chunks of the day (Bell), some only during congested periods (Shaw), and some not at all (Telus, Videotron).

Second, ISP disclosures are woefully inadequate. For example, Rogers admitted that it charges tiered pricing for faster upload speeds but that all tiers are throttled to the same speed when using peer-to-peer applications.  In other words, subscribers to the Extreme service pay $59.99 per month and are promised fast upload speeds (1 Mbps) but actually get the same upload speed as Express subscribers who pay $46.99 per month and are promised upload speeds at half that rate.

Third, notwithstanding the perception that network traffic is growing dramatically, the reality is that the rate of growth is actually slowing. ISPs acknowledged the could cope with the growing demand through reasonable new investment in their networks.

Given all the competing evidence, what is the Commission likely to do? A four-pronged approach is possible.

First, it could adopt a test advocated by the Open Internet Coalition, a group of technology companies that includes Google, that permits traffic management practices so long as they further a pressing and substantial objective, are narrowly tailored to the objective, and are the least restrictive means of achieving the objective. This test would give useful guidance to ISPs and ensure that there are appropriate limits on traffic management practices that have no clear correlation with network congestion.

Second, it can affirm the role of current law against leveraging network management for unfair advantage. Third, the Commission can establish minimum disclosure requirements including information on traffic management practices such as time, targets, and the actual speeds consumers are likely to experience. Fourth, it can dictate limits on the use of personal data that ISPs obtain from traffic management.

Alternatively, the Commission could decide to do nothing and simply retain the power to address complaints as they arise. If so, significant political pushback is likely with political parties lining up in the fall in support of net neutrality legislation.

Regulatory hearings on Internet traffic management practices held in windowless rooms in Gatineau, Quebec in the middle of summer are not likely candidates to attract much attention.  Yet, as my weekly technology column notes (Toronto Star version, homepage version) for seven days this month, hundreds of Canadians listened to webcasts of Internet service providers defend their previously secret practices while engaging in a robust debate on net neutrality. The interest in the Canadian Radio-television and Telecommunications Commission hearing may have caught the regulator off-guard (the webcast traffic was, by a wide margin, its most ever for a hearing), but it was the testimony itself that was the greatest source of surprise.

Wednesday July 15, 2009
In Case You Missed It: Reflecting on the CRTC's Net Neutrality Hearing
In case you missed or avoided the CRTC net neutrality hearing, I thought I would post a few reflections (my summaries of the events are available at Day 1, 2, 3, 4, 5, 6, and 7; additional coverage NetNeutrality.ca).  While there were some notable anecdotes and quotes (Rogers comment about traffic managing a cure for cancer come to mind), I would point to six key revelations that evolved over the course of the week and a half. 1.   The rate of network traffic growth is slowing. This was raised midway through the first week by Professor Odlyzko and was subsequently confirmed by several ISPs.  The revelations ran counter to the general sense before the hearings that ISPs cannot keep pace with the rate of growth.  In fact, it turns out the opposite is true - reasonable new investment in the networks can address current growth rates. 2.   There is a wide variation in the use of traffic management tools with a different approach for pretty much every major ISP. There are those that throttle all the time (Cogeco), during large chunks of the day (Bell), only during congested periods (Shaw), or not at all (Telus, Videotron). There are those that throttle upload only (Rogers) or upload and download (Bell).  There are those that use "economic measures" such as bit caps effectively (Videotron) and others that doubt it can be an effective approach on its own (Bell).  This points to the fact that granular rules will be difficult, but broader principled tests are essential. 3.   The rules for retail and wholesale will be different. The hearing surprisingly included a near-rehearing of the Bell v. CAIP case.  Wholesale services were much discussed as the CRTC recognized the potential of independent ISPs to inject additional competition into the marketplace.  Based on the evidence, it would appear that the problems with wholesale are largely a Bell problem.  Many other ISPs that offer wholesale services do not traffic manage or have such small wholesale businesses that the impact is fairly small.  Bell is a big player in the wholesale side and they have designed their network in a manner that makes it difficult to fully exploit the competitive potential of smaller entrants.  While CAIP argued for rules against wholesale throttling but against retail restrictions (thereby abandoning consumer interests), the opposite seems more likely to occur. 4.   Disclosures are woefully inadequate in Canada. Each day brought new and surprising revelations about how little ISPs tell their customers about their traffic management practices.  By far the most egregious was Rogers, which admitted that it charges tiered pricing for faster upload speeds but that all tiers were throttled to the same speed when using P2P.  In other words, the Extreme subscriber who pays $59.99 per month and is promised fast upload speeds (1 Mbps) actually gets the same upload speed as the Express subscriber who pays $46.99 per month and is promised upload speeds of 512 kbps.  There were similar stories from many other ISPs, who disclosed actual speeds that bring P2P down to a virtual crawl.  Disclosure has improved over the past year as the issue has gained prominence, but there clearly is a long way to go. 5.   Managed networks vs. public Internet. ISPs do not focus on the fact that many run managed IP networks offering telephony and IPTV on the same pipe as the public Internet services.  When asked whether the two impact each other, the answer came back that it could.  In fact, ISPs were at pains to say that while it could happen, it would not happen since they ensure that they provision enough bandwidth for their managed services.  Yet in examples such as Bell's three users promised 5 megs but with only 10 megs to share, it was apparent that the same cannot be said for oversold public Internet services. 6.   The Commission takes privacy seriously. The ISPs seemed surprised that the Commission regularly asked about the privacy impact of throttling and deep-packet inspection. The Commission was similarly surprised when Bell admitted that Canadian privacy law would permit the use of DPI data for marketing purposes with the customer's consent. Where to from here?

The parties will have a couple of weeks to file final submissions and a decision will likely take several months.  My best guess is that the Commission will likely leave the wholesale side alone, though a best case might be to place restrictions on traffic management where the provider has the capability of differentiating between wholesale customers.  Bell says that they cannot do so today, but the introduction of usage based billing might change that equation.

On the retail side, I think a four-pronged approach is possible.  First, the Commission could adopt the Open Internet Coalition/CIPPIC style test based on Oakes that permits traffic management practices so long as they further a pressing and substantial objective, are narrowly tailored to the objective, and are the least restrictive means of achieving the objective. This test would give useful guidance to ISPs and ensure that there are appropriate limits on traffic management practices that have no clear correlation with network congestion. Second, the Commission can affirm the role of current law against undue preferences and work to stop any attempt to leverage network management for unfair advantage. Third, it can establish minimum disclosure requirements including information on traffic management practices such as time, targets, and speeds when shaping. Fourth, the Commission can establish a prohibition against the use of DPI data for any purpose other than network management.

Of course, the Commission could decide to do nothing and simply retain the power to address complaints as they arise. If that approach is adopted, I think there would be significant political pushback, with political parties seeking net neutrality legislative reform.

crtc net neutrality wrap

In case you missed or avoided the CRTC net neutrality hearing, I thought I would post a few reflections (my summaries of the events are available at Day 1, 2, 3, 4, 5, 6, and 7; additional coverage NetNeutrality.ca).  While there were some notable anecdotes and quotes (Rogers comment about traffic managing a cure for cancer come to mind), I would point to six key revelations that evolved over the course of the week and a half.

1.   The rate of network traffic growth is slowing. This was raised midway through the first week by Professor Odlyzko and was subsequently confirmed by several ISPs.  The revelations ran counter to the general sense before the hearings that ISPs cannot keep pace with the rate of growth.  In fact, it turns out the opposite is true - reasonable new investment in the networks can address current growth rates.

2.   There is a wide variation in the use of traffic management tools with a different approach for pretty much every major ISP. There are those that throttle all the time (Cogeco), during large chunks of the day (Bell), only during congested periods (Shaw), or not at all (Telus, Videotron). There are those that throttle upload only (Rogers) or upload and download (Bell).  There are those that use "economic measures" such as bit caps effectively (Videotron) and others that doubt it can be an effective approach on its own (Bell).  This points to the fact that granular rules will be difficult, but broader principled tests are essential.

3.   The rules for retail and wholesale will be different. The hearing surprisingly included a near-rehearing of the Bell v. CAIP case.  Wholesale services were much discussed as the CRTC recognized the potential of independent ISPs to inject additional competition into the marketplace.  Based on the evidence, it would appear that the problems with wholesale are largely a Bell problem.  Many other ISPs that offer wholesale services do not traffic manage or have such small wholesale businesses that the impact is fairly small.  Bell is a big player in the wholesale side and they have designed their network in a manner that makes it difficult to fully exploit the competitive potential of smaller entrants.  While CAIP argued for rules against wholesale throttling but against retail restrictions (thereby abandoning consumer interests), the opposite seems more likely to occur.

4.   Disclosures are woefully inadequate in Canada. Each day brought new and surprising revelations about how little ISPs tell their customers about their traffic management practices.  By far the most egregious was Rogers, which admitted that it charges tiered pricing for faster upload speeds but that all tiers were throttled to the same speed when using P2P.  In other words, the Extreme subscriber who pays $59.99 per month and is promised fast upload speeds (1 Mbps) actually gets the same upload speed as the Express subscriber who pays $46.99 per month and is promised upload speeds of 512 kbps.  There were similar stories from many other ISPs, who disclosed actual speeds that bring P2P down to a virtual crawl.  Disclosure has improved over the past year as the issue has gained prominence, but there clearly is a long way to go.

5.   Managed networks vs. public Internet. ISPs do not focus on the fact that many run managed IP networks offering telephony and IPTV on the same pipe as the public Internet services.  When asked whether the two impact each other, the answer came back that it could.  In fact, ISPs were at pains to say that while it could happen, it would not happen since they ensure that they provision enough bandwidth for their managed services.  Yet in examples such as Bell's three users promised 5 megs but with only 10 megs to share, it was apparent that the same cannot be said for oversold public Internet services.

6.   The Commission takes privacy seriously. The ISPs seemed surprised that the Commission regularly asked about the privacy impact of throttling and deep-packet inspection. The Commission was similarly surprised when Bell admitted that Canadian privacy law would permit the use of DPI data for marketing purposes with the customer's consent.

Where to from here?

Tuesday July 14, 2009
CRTC Network Management Hearing, Day Seven: Bell
Day seven of the CRTC's network management hearing featured just one company: Bell. As the prime target for much of the criticism associated with traffic management, Bell executives faced questions for nearly three hours, far longer than anyone else. Key points included new details on Bell's traffic and traffic management practices, claims that the company cannot separate retail and wholesale Internet traffic, and the company's support for a "reasonableness" standard, rather than the "least intrusive" approach advocated by several groups. Today's summary was again compiled by Sean Murtha, a law student at the University of Ottawa.  Other coverage available from the National Post liveblog, CBC.ca, the National Post, and twitter feeds from CIPPIC and me.

CRTC Net Neutrality Hearings – Day 7, Bell – Tuesday July 14th, 2009

Bell Aliant Regional Communications, Limited Partnership, and Bell Canada

Appearing for Bell is Mr. Jonathan Daniels, VP for Regulatory Law, and others.  In its opening remarks, Bell Canada stated that “at the heart of this hearing is a dispute about innovation.  Bell argued that some parties have argued, without any proof, "that the threat posed by application specific shaping is so severe, that it must be stopped. Bell posited that where some see the need to impose regulatory rules to protect application innovation, they see their demands as seeking regulatory rules that "would limit, or even ban, innovation at the network level."  Bell stated that "imposing ex ante rules that limit or ban innovation at any layer is by definition a greater threat to innovation than having no ex ante rules at all.

Bell put forward a 3 pronged approach to effectively address network congestion:

  1. Capital Spending - Bell stated that they continue to invest in their network, but noted that "unlimited capital spending is not a luxury the companies’ enjoy".  The economic and market realities of high-speed internet access clearly show that a pure capital spend solution not a sustainable model, and they argued that it is too simplistic to assume that Bell can build their way out of the problem.
  2. Pricing and New Business Models - In today’s market, prices are not granular enough to eliminate congestion during peak hours.  Prices motivate users to reduce consumption over the month and deal with average usage.  "While pricing helps, it is not the sole solution".
  3. Bandwidth Management - Bell stated that they "firmly believe that our traffic shaping practices are acceptable".  They are designed to improve the overall experience for the vast majority of users.  They noted that the practices they implement are (i) narrowly focused and limited to non-time sensitive traffic, (ii) confined to a defined period of time; and (iii) do not block access to content.

In regards to privacy, Bell confirmed that their DPI does not, and cannot, inspect the user content of communications, and guaranteed that "the DPI technology in our network is being used only for purposes of traffic management".  It does not inspect user content, and it is not being used for marketing purposes.

For wholesale, Bell stated that "two assertions must be corrected".  First, contrary to what many have told the CRTC, retail users and wholesale GAS users share the same network. As a result of this, wholesale traffic impacts retail traffic, and vice-versa.  Secondly, Bell stated that "wholesale ISPs have attempted to dismiss their impact on our retail network by pointing to their overall market share." They argued, however, that the reality is that wholesale traffic is significant, as in the month of May 2009, wholesale GAS traffic accounted for 31% or their total GAS and retail traffic, and GAS traffic accounted for 36% of their total P2P traffic.

Bell also noted that some want to adopt an "Oakes-type" test, including the least intrusive standard.  Bell argued that the appropriate test for ITMPs is not one which has the regulator substituting its opinion for that of market participants.  Bell submitted "that the appropriate test for reviewing an ITMP (and the one required by the statute) is a reasonableness test, not a least intrusive test".

Bell also proposed the following 3 guidelines, which they developed for the CRTC’s consideration:

  1. Limiting Negative Impacts - ISPs should make reasonable efforts to limit the negative impacts of ITMPs on users, services, protocols or applications.  Implicit in what is "reasonable" is the recognition that different networks face different problems and therefore ISPs require the flexibility to reflect those distinctions in adopting ITMPs.
  2. Transparency - ISPs should disclose to affected retail and wholesale customers "the general nature of implemented ITMPs in a manner that does not compromise the security of networks and commercially sensitive information.
  3. Privacy - ISPs should implement ITMPs in a manner consistent with applicable privacy laws.  As an example, Bell mentioned data used for the purpose of ITMPs should not be used for any other purpose without customer consent.

Bell stated that they felt that s. 36 of the Telecommunications Act will rarely be applicable to issues that arise with respect to ITMPs.  To the extent they do arise, Bell said it is possible to address them under the first guideline which provides as an example that ISPs should not implement ITMPs that block content based on criteria such as its source, ownership or destination unless such activity is necessary to protect the integrity of the Bell network. Bell concluded by stating that "imposing rules that limit or ban innovation at any layer is by definition a greater threat to innovation than having no rules at all".

Questions

Chairman: P2P seems to be a flashpoint in these hearings. We have heard that it is hard to detect what traffic is actually P2P, because some P2P traffic is encrypted.  What is your view of this, because you are obviously doing P2P throttling?

Bell: The short answer is the traffic shaping Bell does is sufficiently effective to achieve our objectives, as we wouldn’t be doing it if we did not think it was effective.  Bell has a very accurate ability to recognize P2P, the evidence of that is that, overall, 27% of our traffic is P2P, but at peak hours that is limited to 14% because of our traffic shaping.

Chairman: Do you do any ex post facto analysis to see if you have missed any P2P?

Bell: We know some P2P gets through.

Chairman: Is the P2P traffic from wholesale customers relatively proportional within your network?

Bell: There is a slight difference, but in terms of overall, it is roughly the same (i.e. it is not a major concern).

Chairman: VT said yesterday that they only use commercial pricing mechanisms to deal with congestion issues, Shaw monitors and throttles beyond a certain threshold, Bell throttles during peak hours, Cogeco throttles 24/7.  Why are there so many approaches taken by the different ISPs?

Bell: The short answer is that each ISP looks at it from the perspective of what works on their network.  We look at solutions that address needs in our network, and the solutions that we saw that would address it we followed.  Flexibility is important. That is why the CRTC should not dictate rules, because we are not aware of any unreasonable practices in the Canadian market today.

Chairman: Why can you not use the Shaw approach, which to me appears to be very appropriate.  As you approach the dangerous levels, that is when you throttle.  In your opening remarks, you have advocated for a "reasonableness" approach - wouldn’t it be reasonable to only throttle when it is needed?

Bell: You have to keep in mind that there is a big technical difference between cable networks and telephone networks.  The CMTS system makes a difference.  The equivalent in Bell is DSLAM.  On top of that, Bell’s network is "highly meshed", and congestion occurs in the aggregation network. Bell has 1500 links in that network.  You cannot manage on an individual link basis in a network like that.  This is a technological problem.

Chairman: So even if you wanted to, you couldn’t act like Shaw does?

Bell: Correct.

Chairman: What stops you from making your pricing more granular?

Bell: As we pointed out, the pricing mechanism is not granular enough to deal with peak period problems.  To do this, we would have to have pricing based on peak periods.  Sandvine discussed this issue earlier this week. 

Chairman: What is the difference between internet use and mobile phone use, because mobile phone plans have different prices for different times of the day.  Why can’t the same be done for the internet?

Bell: It has to do with consumer education.  Mobile phone consumers have been educated for years about mobile phone plans, and peak period rates etc.  I am not saying it is not possible, but we would have to educate the public.  However, this would likely lead to price increases.

Chairman: Are you afraid of being a market leader in this area, and are you afraid of losing customers?

Bell: The market is not there yet.  If the market moves there, then we can follow.  However, it would require a greater customer understanding of things like bandwidth levels.  We come back to the notion of what is the problem we are trying to address? Most customers are very happy with their internet services (Decima-Harris study, 87% of users are happy with their internet services). The trade off with doing to a peak period usage billing system would add a layer of complexity which would undermine the use of the internet.

Chairman: Rogers said that economic disciplines only go so far, because that only addresses the downstream, when upstream is also an issue.  What is your view? Would introducing economic incentives not address the upstream?

Bell: The difference between us and Rogers is that their problem is solely on the upstream, while Bell, with DSL, is more on the downstream.  Bell could fashion a "counter" to allocate more for upstream or downstream.  However, for economic discipline to be successful, the cap would have to be so low as to be punitive to the customers.

Chairman: VT talked yesterday about using only economic methods to deal with problems. If you throttle uploading, you also create an effect on the downloading.

Bell: If you are using the internet, you will use both the upstream and downstream, because it is dynamic.

Chairman:  If you have network problems, do you pass them down to your wholesale customers?

Bell: Anticipating this question, in our opening statement we have attached a diagram.  If you buy our retail service, or our GAS service, you will go through our aggregation network.  If an ISP wants to buy GAS service, they can interconnect at one point in the Bell network, at a Bell CO in the geographic area they are located.  At that time, the ISP then has access to all consumers that Bell’s technology can reach.  When the traffic hits the BAS, the BAS can distinguish between Bell’s retail and wholesale traffic.

ISPs pay Bell for each end user they sign up, and also pay a monthly fee for the total amount of bandwidth they need.  They are really paying a fee for a port, and that fee represents less than 2% of their payment for GAS.  ISPs are not actually paying for the bandwidth itself, they are "only paying for access to the door". So, how is it that they are not segregated (i.e. retail from wholesale)? The traffic is not segregated in the aggregation network, and that is where the congestion problem is.  However, ISPs do have the option of paying a higher price to skip the DPI, and they can also skip the traffic shaping.

Bell can clearly turn on traffic shaping on for retail customers, and off for wholesale customers. A problem is that Bell cannot turn their traffic shaping on for only 1 wholesale customer.  They have to either turn it on for all wholesale customers, or no wholesale customers.  Therefore, for those ISPs that go through the aggregation network, Bell’s traffic shaping applies.There is no way, technically, in the protocols to recognize the difference between the different wholesale customers.

Chairman: So your problem with congestion exists in Bell’s aggregation network?

Bell: Correct.

Chairman: What would happen if the CRTC said that throttling was a violation, and that you were not allowed to do it?

Bell: I think we have showed that P2P is a problem during peak periods, so removal of shaping would lead to congestion, and that in turn would lead to poor customer service.  Then, I could do 2 things: 1) I could do nothing and let customers suffer, which I would not do, or 2) Bell would have to invest more, which would mean that we would have to redirect capital within Bell, and raise prices for consumers.

Chairman: Yesterday we heard from UdC, and a speaker said that there should be clear evidence that there is congestion in the network, and he said that there is little evidence that this congestion actually does exist.  Can you, Bell, show me information that throttled applications cause significant congestion?

Bell: The answer is yes.  P2P represents over 27% of traffic on our network.  When people say it causes congestion, it is part of the problem for congestion, but is not the only problem.  The reason that we focus on it is because it causes congestion, but also because of how it uniquely acts in a congested state.  It is there that P2P takes a disproportionate amount of bandwidth. 

Chairman: I would understand if you do not want to make this data public but if you do, that is all the better.

Bell: I think that this information is already in the public record, so we will be happy to take you  through it.  The first part of the 3 part answer is that there is congestion in our network (page 32 of Bell’s July 8th 2009 submission, figure 12.

Chairman: I do not have that submission in front of me.  Why don’t you do it in a written format.

Bell: There are some things that would be better explained orally.  In reference to yesterday’s discussion of shallow packet inspection (SPI), this is what struck me, as a lawyer.  If you are doing SPI to make distinctions, you are trying to recognize what applications involve.  To say don’t do application specific, and use SPI, does not make any sense.  SPI is used to make distinctions based on applications.  The expert witness’ concluding remark was that there was no current commercial use of SPI.  We agree with that, as there is no SPI tool on the market right now.

Bell then showed another graph, attached to their submission.  It endeavoured to show that P2P takes an unfair, disproportionate amount of space in a congested state.  In a congested state, P2P is not as affected as users who are not using P2P.  By limiting only file sharing (as we do not touch time sensitive applications), we can increase overall user experience and the people using it are relatively unaffected.  Traffic shaping is necessary to guarantee user satisfaction.

Chairman: You seem to be the only ones who traffic shape the downloading as well as the uploading.

Bell: In Canada.  There are many international carriers who traffic shape both upstream and downstream.

Chairman: The reason that you throttle downloads, as well as uploads, is technical then? It is a technological requirement for you?

Bell Canada: Yes.

Chairman: I have changed my mind, can you take the panel through the document that you referenced earlier?

Bell: Our data shows escalating congestion.  Queues become overloaded, packets or cells are dropped, and require re-transmission, either by TCP or in the case of UDP, they are lost altogether.  If you are using TCP, the application will be asked to retransmit (a good example is a VOIP call).  Those packets are lost forever, so they are repeated.

So, P2P is a major cause of congestion.  Every packet that is going through a congested device is a contributor to that congestion.  In our case, 27% of our traffic is P2P.  So, why do we handle it the way we do? Most of the traffic on the network assumes some immediacy.  The issue is how do you handle customer experience at the peak? What we do is prioritize traffic which has immediacy (such as time sensitive applications) over machine to machine transfers.

Chairman: Do you use utilization data?

Bell: All companies use utilization data, we look at queues in the devices, and it is a reasonable proxy. Utilization is a reasonable proxy for large amounts of utilization data? Remember, we do not have a problem with P2P.  Our top 10% of users are responsible for 96% of P2P, amongst retail users.  Overall, we believe that this is a user-friendly way to do it, and users use P2P to increase their use of other functions.

Chairman: Switching gears, you have said that aggregated data is not being used for marketing purposes, and it should not be used for anything else without customer consent. This is weak, as you are not allowed to use it for other purposes.

Bell: What we are using DPI is for traffic shaping only.  Privacy legislation (PIPEDA) allows us to use it for other purposes, if we went back to customers and got consent.  We recognize that people are concerned about privacy.

Chairman: PIPIDEA would allow you to use data for marketing, if you had customer consent?

Bell: Marketing is absolutely not what we use it for.

Chairman: That was not my question. Are you telling me you could use it for marketing purposes if you had customer consent? Is that what the privacy legislation allows?

Bell: That is what PIPEDA is for - it is based on customer consent, but currently we do not use it for marketing.

Chairman: I am trying to understand why you are so focused on a "reasonableness test", instead of a "least intrusive test"? Shouldn’t traffic management be least intrusive, as it is consistent with your philosophy of acting for the benefit of your customers?

Bell: The problem I have with "least intrusive test" is that, ultimately, there has to be a judgement made as to the one correct least intrusive method.  Ultimately, if the test is "least intrusive", what is going to happen is many different people are going to come forward with suggestions as to what is "least intrusive".  Ultimately, the CRTC will have to decide what is least intrusive, and would force ISPs to act in a certain way.

Chairman: We have talked about essential services.  If you have to determine what is least intrusive, it would be on you to determine what you could do.  It would be a reasonable decision based on evidence brought before the Commission.

Bell: For essential services, there were actual determinations made.  The best way to think about this is the way that a judge looks at an administrative tribunal decision.  There is a difference between a correctness standard and a reasonableness standard. 

Chairman: This would be ex post, not ex ante.  Ex post would alleviate some fears for you, certainly?

Bell: Correct.  We are strongly opposed to ex ante.  The problem with protocol agnostic focuses on people who are using applications, and it will slow down all of a user’s traffic, even time-sensitive traffic.  Some will say this is good, because it does not differentiate between applications.  We do not think this is unreasonable, but it is not what we have done.  The OIC, and others, will say this is less intrusive than our method.  We disagree; we think our way of shaping applications is less intrusive.  Ultimately the CRTC would have to decide.

Katz: First, your proposal is directed at the public internet.  Do your networks co-exist, or are they independent?

Bell: Our networks are all "in the same pipes".

Katz: So if your managed IP has a high incidence of traffic,that could potentially congest the public internet?

Bell: Let me give you a broader answer.  In our network there are many traffic types, some have a higher priority throughout the network.  If we did not engineer the network correctly, there could be congestion.  If you are going to offer IPTV, you would not under-build, you will make sure to have the capacity.

Katz: Telus said last week that a company would not want to negatively impact the public internet.  Do you agree with their views?

Bell: I do. With IPTV architecture, you do not impact the capacity of the public internet.

Bell: Remember, as mentioned, we cannot, in our network, distinguish between ISPs, and have different rules.  We have to, in the aggregation network, treat everyone the same.

Katz: Primus does use DSL.  They claim that they can traffic manage and do some of the things you said you cannot do.  Are your networks the same?

Bell: I do not think they said that they cannot do something that we cannot.  They said, not when using our GAS service, they make a distinction between time sensitive data (i.e. VOIP and Gaming) and that which is not.

Katz: But Primus said that they only do shaping during congestion periods.  Your traffic shaping is not focused at all (it’s on for 10 hours a day). They then alleviate all their shaping tools when they are not required.

Bell: I am not aware of signalling mechanisms in the DSL network which allows one to identify real time in any automated fashion.

Katz: However, you have said your methods are "narrowly focused".  How is this the case when you have traffic shaping on so often (as I mentioned, 10 hours a day)?

Bell: The first aspect is that we make a distinction when it is close to peak periods.  The key aspect is that it is limited to only file sharing, non-time sensitive P2P traffic.  There are many reasons why people face problems, but we have not had collateral damage.

Katz: Is this traffic shaping method (i.e. throttling P2P) available for public consumption? Do you have information as to your traffic management available to the public?

Bell: We do have some information on traffic shaping methods, but we have not had the speeds we have throttled down to.  We are adding those speeds onto the website though, soon.

Katz: So 31% of wholesale customers use GAS?

Bell: No, 15% of end users and GAS end users, but they represent 31% of traffic.  While this is disproportionate, this is not generally a problem, only during periods of congestion.

Katz: For those customers that want, they can pass the "best efforts basis"?

Bell: No, they will pass our traffic shaping.

Katz: How many of your wholesale customers purchase non-traffic shaped services, on dedicated lines?

Bell: The number is low.

Katz: One of the reasons why the tariff is more expensive is because you are dedicating certain things to them?

Bell: No, it is "nailed up" right through to the aggregated high speed base. 

Molnar: Since we were talking about GAS, I have a similar question.  In our conversation with Execulink earlier in the week, we talked about 2 components.  I would like to understand, based on an example from Execulink where they said they can provide each customer with up to 11mbps, and their bandwidth is 100g, when you throttle on the customer. What impact does this have?

Bell: Certainly by lowering the P2P, if their customers are not going to do things with that extra bandwidth, it does not have an impact.  If their end users are mainly P2P users, then our practices could impact them.  What I can tell you is that, talking to our wholesale team, we bought a certain about of bandwidth (said the ISPs), and we have seen no correlation between our traffic shaping and reduction requests.  We have seen the same typical growth.

Molnar: You said you saw no difference after traffic shaping, with the amount of bandwidth as being transported?

Bell: I do not know about that.  Look at it from an ISP perspective. They say they need 1 pipe to connect to you whole network, and at that point, the ISP "chooses the door size" they will have. 

Molnar: Is there anything within the tariff that would prohibit them (an ISP) from moving down to a lower size, and getting a different capacity?

Bell: No, and factually, we have not seen it.  ISPs are signing up new end users, and want "more doors". That is not to say that individual ISPs have not gone down, but we are talking trends. For the most part, ISPs have not wanted to move down to a smaller door.

Molnar: But ISPs can change their "orders", and subsequently change their costs? This is possible for them to do?

Bell: Yes, I believe that is the case.  The reason I focus on a "door" instead of a "pipe", it is priced only at the point they connect, which gives them access to our whole network province wide.  They do purchase a "pipe" within our network, the purchase a "door" to access our entire network, within a province.

Molnar: You said that you want guidelines which are flexible enough.  Would you say DPI is a "network innovation"?

Bell: Absolutely.  DPI is a network innovation which allows us to improve the user experience.  Another example is our ability to block spam on our networks. We believe our practice is an innovation, and it is important.

Molnar: Juniper said that congestion management could occur at the customer level.  Instead of being the choice of a network provider, the choice could be with the customer.  They did mention this does not currently happen in Canada, but have you looked at these types of options? Is this part of the evolutionary plan, that these controls could one day be held by the customer? If you have to decide between the marketing person and the engineer as to who is going to answer, I think you already have answered it.

Bell: There are many different reasonable solutions out there, although they are not all currently reasonable.  From a white-listing point of view, it has potential.  I don’t think this would be viable in today’s market, and it is not something we will implement anytime soon. A network of our size, we have a very good track record of breaking things that do not scale well.  While that is an interesting model, I would like to see if go further in the market first. We are not going to rule out anything.  We will have to decide in the future whether that is the best way to go.

Lamarre: I want to try to answer one question you have asked us.  At the start of your presentation, you said at the heart of this hearing is a dispute about innovation.  While that is true, that is not all this hearing is about.  You have asked why traffic management practices are an issue if users are happy.  However, we have to be concerned about all users, even those that fall within the minority.  That is why we are inquiring, and that is why we are being picky, if that is how you think we are acting. You have also noted that some presenters at these hearings have made allegations, but without proof or data to support these allegations.  The problem is that the data is held by ISPs, and is not always available to the public.  Is there any way that from your perspective, you can demonstrate that there is actually no problem?

Bell: Us being Bell, when we do something wrong, we hear it from customers, who can speak with their feet and will leave us.  We do market research, and nothing has pointed to our P2P shaping as being a problem with consumers.

Lamarre: Let’s talk about consumer experience and price.  I still do not understand why you throttle P2P on both the upload and download. Rogers throttles only upload, not download, and this is done because customer experience is important as far as download is concerned.  I understand that Rogers is cable and you are DSP.  TELUS is also DSL, and they do not throttle at all. So, this system that Bell uses does not seem to be a good customer tailored approach, does it?

Bell: I cannot speak as to why TELUS does not.  If you had this hearing years ago, you would have asked Rogers why they do not, and Bell does. In the Atlantic Provinces, we do not traffic shape.  In the central provinces, we have seen congestion problems that we have not seen in the Atlantic Provinces.  There is not the same level of peak period use the Atlantic Provinces.  Also, the network is designed differently in Atlantic Provinces.  This does not mean that we will not traffic shape if congestion becomes an issue, but currently we do not find it necessary.

Lamarre: You have also put into place economic measures, reducing the amount of bandwidth by 10 times (20g to 2g per month).  However, the prices are almost the same as they were before, if not the same.  Is this not enough of a measure, or do you still need to throttle? By offering different packages, is this not enough?

Bell: For us, pricing does not seem to be enough.  While we feel that it is important (it is part of our 3 pronged approach), we feel the other steps we outlined are also necessary.

Lamarre: The guidelines you are proposing, would this be enough for traffic shaping on wireless, mobile wireless?

Bell: Absolutely. In limiting the negative impacts, different networks face different problems.  What is reasonable in a wireless network may be very different from what is reasonable in a wireline network. Flexibility is important.

Lamarre: Should we make a distinction between fixed wireless and mobile wireless?

Bell; If it is justified, it is part of the test.  If it is determined it makes sense to make a distinction, then yes.

Lamarre: On the one hand, PIPEDA is a law that is general in nature.  When the act was passed, internet traffic was not a major issue.  The public commissionaire raised the point that the CRTC’s role under the Privacy Act is that the CRTC has jurisdiction on privacy over communications networks.  Under the Telecommunications Act, we also have jurisdiction over privacy issues.

Bell: We understand that the CRTC has a mandate to protect privacy.  We are also subject to PIPEDA.  It is our responsibility to ensure that our organization meets obligations under PIPEDA, and other rules that flow from the CRTC.  Under the PIPEDA system we received some complaints, but the complaints always came through the OPC.  We now have a complaint filed by CIPPIC, and in collaboration with the OPC to settle the issue. 

Lamarre; Question about DPI vs. SPI.  The question raised by the UdC yesterday about privacy protection makes me ask, which of these is more invasive? 

Bell: As far as privacy issues, we do not have any information relating to the packet to which the technology applies.  We do not keep the information.

Lamarre: Even if you do not keep it, I think there are still privacy issues.  There are some worries on the part of users.

Bell: We apply the necessary policies for traffic shaping, then the process is over.  The intent of SPI is identical to DPI.

Lamarre: I know the intent is the same.  My question is, with DPI, do you get more detailed information?

Bell: There is a little more information available with DPI.

Lamarre: You also said you were not aware of any SPI technology that is currently on the market.  However, you must consider that it may be difficult to get something on the market if there is no demand.  So, does Bell plan on testing SPI technology, to see if it could be as accurate as DPI?

Bell: We feel confident that SPI is not as accurate.

Lamarre: In your guidelines you suggest, instead of an Oakes-type test, a reasonableness test.  I would state the Oakes test to ensure that citizens are protected, and have their fundamental rights protected.  Don’t you think that we should adopt an Oakes-type test when it comes to privacy rights?

Bell: It is a big difference, because the Charter protects rights infringed by the government, not private companies.

Lamarre: But the CRTC had the duty to protect privacy, and the CRTC is part of the government.

Bell: I agree, but there is a fundamental difference between how the government makes rules, and how companies operate.  Customers have options, and can change companies. The statute provides for a reasonableness test, and we do not think that a constitutional like test which applies to the government, which is the ultimate monopoly, should be the standard for private actors.

Lamarre: Not even to protect a fundamental right like privacy?

Bell: I do not want to downplay privacy, as privacy is very important for us. 

Denton: You mentioned that you were approaching a more "granular approach" to bandwidth management. Can you elaborate?

Bell: We have some stuff in the lab, and we are looking at the "Cox Solution" (in the U.S., they are trialing about time-sensitive vs. non-time sensitive distinction).

Denton: You have dropped your bit-cap by an order of magnitude.  Was there a reason?

Bell: We looked at market trends, customer needs, competition. We made our decision based on what the market would bare.

Denton: That was a market oriented answer.  Bell uses traffic management all the time?

Bell: Just to be clear, we do it from 4:30pm until 2am.

Denton: So you only do it at peak hours? Do those peak hours correlate to your periods of congestion?

Bell: Yes, those are our periods of congestion.  However, that is not to say that an event, like Michael Jackson’s funeral, can cause congestion at a non-peak period time.

Denton: Is traffic management at the wholesale level reasonable?

Bell: It is reasonable.  Bell cannot distinguish between wholesale providers.

Denton: Why is that? Is this just a software problem?

Bell: It is a protocol problem.  The tunnel IDs are dynamic.  At that level of the network, they are not permanently identified.  That is the technical issue, but the other issue is, say Primus gives priority over its traffic, how does that work once it is aggregated in our network? If they try to shape it, it will conflict with our methods, and would not matter if they are giving priority in their networks.  The only way we could leave it up to them would be if they did exactly the same thing we did, so we might as well do it for them.

Denton: So it seems to be a technical and economic reality.

Bell: Yes, and remember that we would have to make technical agreements with more than 100 companies, and they would have to end up following exactly the same practices that we already are doing for them.

Denton: Another major contention is that traffic management measures are an inadequacy of competition at the retail level. Do you have a comment on this?

Bell: People have pointed to England as the panacea.  However, many ISPs there institute traffic shaping.  Japan, which is considered a leader, in 2007 25% of ISPs traffic shaped (and this data is 2 years old).  So, to make the connection that competition is the reason may not be the answer.
I also should state that the industry is highly competitive in Canada.  There are many ISPs which differentiate themselves, and there are lots of options out there.  We disagree with anyone who says there is not strong competition in the Canadian market.

Chairman: I think in regards to a "least intrusive test", you want to make sure that it is least intrusive not only on its affect, but for the ISPs themselves.  The difference between that and "reasonableness" is not that great.

Bell: Our goal is the same in that regard.  Our definition of reasonableness means "reasonable efforts to limit the negative impacts of ITMPs on users, services, protocols or applications".

Chairman: I do not think we are very far apart. Thank you very much, we spent more time with you, but you did start the whole thing.

crtc network management hearing, day seven

Day seven of the CRTC's network management hearing featured just one company: Bell. As the prime target for much of the criticism associated with traffic management, Bell executives faced questions for nearly three hours, far longer than anyone else.

Key points included new details on Bell's traffic and traffic management practices, claims that the company cannot separate retail and wholesale Internet traffic, and the company's support for a "reasonableness" standard, rather than the "least intrusive" approach advocated by several groups.

Today's summary was again compiled by Sean Murtha, a law student at the University of Ottawa.  Other coverage available from the National Post liveblog, CBC.ca, the National Post, and twitter feeds from CIPPIC and me.


Tuesday July 14, 2009
CRTC Network Management Hearing, Day Six: Union des Consommateurs, Rogers, Videotron, Shaw
Day six of the CRTC's network management hearings opened with a final consumer group (Union des Consommateurs) and closed with three of Canada's biggest ISPs - Rogers, Videotron, and Shaw.  Bell was scheduled to appear today but has been pushed back until Tuesday. The big storyline of the day was the disclosure by Rogers and Shaw of previously undisclosed information.  Rogers revealed its traffic management practices (throttling P2P upload speeds) and shockingly admitted that all its tiers receive the same upload treatment, regardless of the price paid by the consumer.  This is true even though its promotional material tell customers that higher tiered service offer faster upload speeds. Shaw disclosed that it engages in similar practices and provided insight into its throttling practices, noting that it guarantees 80 kilobits per second for throttled P2P sessions and that it reserves 30 percent of its bandwidth for P2P use (it said that 10 percent of its users account for the P2P traffic). Videotron, the third cable ISP in the mix, complicated the analysis further by noting that it does not traffic shape.  Rather, it uses economic measures, the new euphamism for bit caps, to discourage overuse of P2P.  The ISP indicated that it is very happy with the effectiveness of its approach. Today's summary was again compiled by Sean Murtha, a law student at the University of Ottawa.  Other coverage available from the National Post liveblog, CBC.ca, the National Post, Cartt.ca, and twitter feeds from CIPPIC and me.
CRTC Net Neutrality Hearings - Day 6

Union des Consommateurs

The Union des Consommateurs (UdC), in their opening remarks, suggested that there has not been enough evidence of actual congestion, which many ISPs have complained of this past week.  The UdC said they wanted the CRTC to consider many issues, including concentration of ownership, quality of service affordability, and competition. UdC also said that one of the real reasons that ISPs are targeting P2P is because the existence of P2P, and its use by customers, threatens other businesses.  They argue that the whole issue of traffic management is about competition, not congestion.  Thus, discrimination as a result of traffic management will have the detrimental effect of stifling innovation.

UdC said that to motivate network management method of throttling a specific application, there should be clear measurement-based evidence that:
  1. there is congestion in the network;
  2. time sensitive applications are experiencing unsatisfactory Quality of Service; and
  3. the throttled application is a significant cause of the congestion.
There is little empirical evidence that these conditions exist.  Moreover, UdC argued that it is not clear from the presented data that P2P applications are the primary cause of the congestion, if it does exist.

The UdC stated that new data on recent traffic volumes does not show the exponential growth that was predicted in 2006 and 2007.  The rate of growth is decreasing, and P2P traffic volume is growing at an even smaller rate.  The UdC argued that “modest growth rates” in usage mean that increasing network traffic can be accommodated by reasonable increases in network capacity.  If it is determined that network management is necessary, there are several options that do not involve "application-specific throttling".  For example, during periods of congestion, it is feasible to control the rates of individual users, reducing the rates of high-volume flows irrespective of the protocol employed.

UdC also discussed deep packed inspection (DPI) vs. shallow packet inspection (SPI).  The method used by most ISPs is DPI, which involves processing the payload and the "application layer header", searching for known signatures associated with specific applications.  UdC argues that this practice raises privacy concerns, threatens robustness by violating layer design principles, and promotes the practice of data encryption.

UdC explained that SPI does not involve any examination of packet payloads.  Instead, statistical features are collected for each flow and, based on these features, the flows can be categorized into application classes.  Experimental studies have shown that this classification approach can be very accurate, but the classes must be more general.  UdC stated that the classes are sufficiently specific for network management.  Also, UdC said that the technique alleviates any privacy concerns.

UdC concluded by saying that ISPs can adopt positive approaches to improve the way P2P applications operate, benefiting both the users and the access network.  The P4P project promotes cooperation between P2P applications and the ISPs.  Field tests indicate that the methods both improve the performance perceived by the user and reduce cross-ISP traffic and the load on ISP aggregation links.

Questions

Chairman: You mention that there should be clear evidence of congestion.  Is this data publicly available? Is the data difficult, or economically unfeasible to collect?

UdC: The evidence is certainly collectable. It is more expensive to collect than utilization data, but it is certainly able to be collected.  Whether the companies collect

Chairman: Is shallow-packet inspection being practiced by anybody? It seems that everybody uses deep packet inspection. Is this being employed?

UdC: As far as I know, nobody uses SPI exclusively, but some ISPs do use it along side DPI.

Denton: Various ISPs have said that if there is going to be network control, it should be exercised by retailer, not the wholesaler. What do you say to this?

UdC: We question the motives of the ISPs.  If the issue is congestion, that can happen at the retail level.

Denton: Does traffic management interfere with innovation?

UdC: By allowing P2P, which is often targeted by traffic management, we can help with innovation, as P2P is used for very innovative purposes.  Targeting P2P can hinder innovation.

Denton: What is your final, take away message?

UdC: There needs to be clear measurement studies to show what is happening inside of the networks.  We need to find if there is congestion, the root causes of congestion.  SPI is an intriguing thing that we should look into.

Lamarre: In regards to SPI, is this the first step in DPI?  Should ISPs simply stick with this level of inspection (i.e. SPI)?

UdC: SPI is actually the 2nd step in DPI.  My suggestion would be, based on studies, SPI is very effective.  Get over 95% accuracy of classification of flows, without looking inside of the packets.

UdC: We have to remember that we must look at the internet as a public service, a public good (or a public utility). 

Rogers Communications Inc.

For Rogers, Ken Englehart, Senior VP Regulatory, appearing with others.  Rogers noted that Canada has the highest penetration of cable modem service in the world and the highest penetration of broadband in the G8 countries.  All of this has been accomplished with a minimum of government regulation.  Rogers argued that market forces, not government fiat, are responsible for this.  Rogers pointed out that many participants before the CRTC "want lawyers, not engineers, to design the networks". 

Rogers stated that they are committed to an open internet.  They stated that they do not manage their networks to favour their cable television business, demand fees from internet services for access by their subscribers, or stop independent documentary filmmakers from distributing their content.  They do not open email, inspect the contents of packets, or focus on specific packets.  Rogers would urge the commission not to set internet traffic management guidelines at this time. 

Rogers noted that the FCC rejected this approach (i.e. setting guidelines) in the Comcast decision.  As Rogers stated "the internet is to new and is changing too quickly to establish ITMP guidelines at this time.  It is better to adopt the FCC’s approach of looking at individual internet traffic management practices on a case-by-case basis.  In that way, the Commission will ensure that Canadian ISPs have the flexibility they need to manage their networks properly." Rogers pointed out that their traffic management practices do more than simply "traffic shaping".  Rogers does much to protect customers’ experience.  Rogers says they protect the network from spam, prevent denial of service attacks and virus attacks, and blocks access to child porn sites.

Rogers stated that they do rate shape upstream P2P.  They said that P2P can "clog the highway", and the traffic needs to be managed, to make it fair for other users.  They pointed out that it was not simply because it was P2P that they managed it, but because "this protocol is designed to swamp the network, and this is why it must be managed". Rogers said that their practices do not simply favour their own services, and argued that without their traffic management practices, competitive VOIP providers would be hurt by congestion.  While some interveners have claimed that Rogers should simply increase capacity, this would mean they would have to provide a huge amount of additional upstream capacity.  Rogers argues that this would significantly increase their costs, which would then increase the cost to all consumers, not only those who use P2P.  Rogers argued that they "believe that it is readily apparent that our traffic management practices are an appropriate network management solution".

Rogers also argued that that "have found that...customers have very little curiosity about the inner workings" of their traffic management practices.  Customers simply want fast reliable service, and do not inquire any further than that.  For wholesale customers, Rogers stated that they believe that there should be sufficient disclosure to allow them to understand the nature of the services they are acquiring and to respond to their own customers’ inquiries appropriately.

In regards to privacy, Rogers stated that they are concerned with privacy, and work to protect them.  They argued that privacy issues raised by consumer groups concern things which ISPs could do or might be able to do, not what they are actually doing.  Rogers urged the CRTC to look at what ISPs are doing.
In regards to wholesale services, Rogers noted that their wholesale services are not currently traffic shaped, but they reserved the right to do so in the future.  If wholesale traffic begins to impact their customer’s traffic, they will revisit this decision.

Rogers noted that they do not currently rate shape their mobile wireless data traffic, but think that with the growth of use of their wireless services, traffic management will be necessary in the future.  However, because costs are different, architecture is different, etc., it is too early to identify the traffic management practices that will be required for mobile wireless carriers.
Rogers also addressed section 36 of the Telecommunications Act.  Rogers’ traffic management practices do not control the content of P2P file sharing traffic.  While it may take longer to download a file, this does not control the content or change the meaning of or purpose of the file.

Questions

Chairman: What the CRTC is talking about is an analytical framework.  Would it not be good to lay out a clear analytical framework, would this not be helpful for the industry as a whole, including Rogers?

Rogers: Without guidelines, we have gotten along just fine.  Where there were guidelines, they came about after decades of experience. Secondly, some guidelines put forward by interveners, like the Oakes test, have a bias against network management.  This is dangerous.  If there is going to be an analytical framework, it should focus on the customer, it should focus on the customer experience.  Also, we should not assume that carriers are trying to upset customers; there should be a presumption that network management are for the benefit of customers.  Moreover, look at what other ISPs are doing.  Other ISPs are doing the same.

Chairman: If Rogers thinks that the analytical framework as put forward by interveners are not ISP friendly, then Rogers should suggest a different analytical framework to the CRTC.

Chairman: The chairman wanted clarification on technical issues, such as SPI and DPI.

Rogers: There was a differentiation between DPI and SPI.  The way that UdC described it, the first level was deterministic, and then the 2nd stage (SPI) was the classification stage.  Rogers uses a combination of both techniques (DPI and SPI).

Chairman: But the studies we have been told about show that SPI is effective, and accurate.

Rogers: We have not seen the rates of accuracy discussed this morning in regards to SPI (95%).  Rogers has seen much lower accuracy levels using DPI.

Rogers: P4P is a working group.  The challenge with these working groups which tries to come up with "network aware" ways of dealing with P2P, it relies on users.  For users who do not rely on guidelines, they continue to use P2P the same way they did before the guidelines were in place.  It relies on everyone being a good and responsible actor, and that is not the case on the internet.

Chairman: Like Cogeco, you said you only shape upstream traffic.  Is it mostly your own customers who download? By shaping upstream, do you also influence the downloading of customers?

Rogers: Obviously it will happen sometimes.  However, Rogers said that they tested this issue in a lab after the question was asked to Cogeco on Friday.  Rogers used a computer connected to the internet with a single video file.  20 worldwide users were downloading the video, but none were Rogers' customers, and none were Canadian users (users from U.S., Ireland, and Finland).  So, if Rogers traffic shaping was so oppressive, why would so many users be accessing the computer?

Molnar: Rogers spoke about guidelines, and whether there should be any.  One of the issues as to not having guidelines is the fact that if there is discriminatory practices, particularly as it relates to traffic management that is specific against content, if such practices exist, by the time an ex post review happened, you could cause a major economic impact on the targeted application.

Rogers: There is a danger to setting up guidelines.  The internet it so new, applications are arriving so quickly – there is so much going on, guidelines being set up now could quickly become obsolete, and would hinder ISPs ability to help their customers.  While there is fear, the actual evidence shows that ISPs, to be competitive, have to address customers’ needs and concerns.  Net neutrality concerns have been overblown.

Molnar: The OIC felt that discrimination against an application is discrimination under s. 27(2).

Rogers: Rogers does not think that 27(2) is supposed to protect applications themselves, but is meant to protect application providers.

Molnar: Rogers throttles on a 24/7 basis.  So, help me understand why it makes sense to throttle on a 24/7 basis, instead of when the need exists?

Rogers: It is useful to think of the analogy of the network as a highway, and traffic on the network as cars.  People may say that if there are too many cars, you should build a bigger highway.  In Rogers view, this misstates the problem.  Rogers wants more traffic, and they continue to build new capacity, although it is expensive.  The problem is if one car parks on the highway, or reserves an entire lane of the highway for themselves.

Molnar: Using your analogy, you have built a super highway, and if one car is parked on a lane for 1 hour, why do you feel the need to throttle the network 24/7?

Rogers: The problem is the behaviour of someone who abuses the system constantly.  Congestion problem we experience is at the node level.  But the traffic management happens at the router, which covers many nodes.  Congestion may happen at any node at any time of the day, and that is why we practice 24/7 throttling.While on average the network has "busy periods", a small cluster of users can congest the network at any time of the day.  We have tried to build our way out of this by increasing capacity, but P2P users have continued to absorb capacity within the network.  We have done tests where we turn off P2P traffic management in certain clusters, and even at 3am congestion has occurred in these test areas. While we traditionally think of peak utilization in the network, we actually do not have peak points of time, but peak periods of time, which can last for hours.

Molnar: Molnar wanted Rogers' data on P2P traffic.  She asked them to provide the CRTC with their data.

Molnar: What is the rational for throttling only on the upstream, and not on the downstream?

Rogers: We think we can control downstream flow through augmentation and pricing.  On the upstream, because we are constrained by a cable modem network, it cannot be controlled.  On the upstream, it is the "rest of the world", not only our customers, using the network. 

Molnar: Rogers commented that the Comcast agnostic approach would be more expensive, and would be more troublesome than the targeted approach which simply targets P2P. Can you elaborate?

Rogers: The Comcast methodology restricts all applications.  If we used this, we would have to limit what our customers could do.  It would be more costly than it would be today.

Molnar: Exactly how do you throttle P2P?

Rogers: It is the same for all packages, the same bandwidth allocation (the same speed) for all packages.

Molnar: I want to talk about the issue of disclosure.  As I understand, you have only recently begun to disclose to customers throttling practices.  You say that Roger’s customers "have very little curiosity" about traffic management practices.  Do you not think customers may want to know more about throttling practices, especially if they want to P2P? There is nothing in the package descriptions on the Roger’s website which mentions throttling, even in packages which are targeted to people who want to download a lot, and play games.  If you are concerned about the customer, shouldn’t they be informed?

Rogers: Our different services have different cap sizes.  What our descriptions are saying is that people who are concerned with downloading and game playing will want a package with a higher cap. We feel that our throttling information is still competitively sensitive information.  If the CRTC feels strongly about it, we could reveal more information.

Molnar: Some other ISPs have said that competition should address ITMPs, and this could actually be a form of differentiation between ISPs.

Rogers: There is a very competitive market in Canada, and all of the carriers are making huge investments to stay competitive.  Surely traffic management is part of this competition.

Molnar: What about traffic management as it relates to content management and protocol? Will this become part of the competitive marketplace?

Rogers: We are measured by subscribers based on the performance of the network, and users want a wide range of things which they can do using the internet.  Rogers benefits greatly from an open internet that continues to evolve.

Molnar: You mentioned that you do not rate shape on your network.  Are there differences between ITMPs on wireline and wireless?

Rogers: Because behaviour of users is different the solutions may be different, but the options would be the same.

Molnar: What is it when we talk about providing preferential content, or content under a different pay structure?

Rogers: All ISPs, wireline or wireless, have a homepage with content on that homepage.  Rogers has a homepage, with certain partners on the homepage, who work with Rogers.  The technology has evolved quite a lot, to the point where customers can go to any page, not simply the homepage of the provider.

Molnar: Is there any traffic management associated with this activity?

Rogers: No, there is not.

Katz: While you said the FCC has done nothing at all in regards to this.  What did Comcast do?  What would the cost be if you were to follow the net neutrality statement released by the FCC in 2005 which caused Comcast to change?

Rogers: The FCC statement dealt with net neutrality, not traffic management.  Comcast denied that they were engaging in packet reset methodology, and this did not help.  They hired people to come and clap at the hearing, and this behaviour annoyed the FCC.  The FCC did not tell Comcast what to do, and most US companies manage their traffic just like Rogers does. Rogers does not think the Comcast methodology is good at all.  We think it is a mistake.  In terms of the cost, it could be "fairly huge".

Katz: What would it take if you were required to follow the Comcast methodology? Could you explain what Comcast was doing, what did they change, and what did it cost them?

Rogers: Comcast was doing "session management", sending out phony "reset packages" saying that sessions were no longer needed, when in fact they were.  According to evidence at the FCC, this really only was meant to slow things down, not stop the flow completely.  What Comcast is now doing is using the "switch" that cable modems do.  It looks at congestion at the individual node, and will slow down individual users who are nearing their capacity for 15 minutes.  It targets P2P users, but slows down all of their traffic, not only their P2P.  Rogers does not want to do this, because it would be bad for customers, because not only would they be able to use P2P, they may not be able to make a VOIP call. As to what it cost, Rogers does not have that information, but they will try to get it from Comcast for the CRTC.

Katz: Or does this tariff limit the ability for wholesale customers to sell value added services?

Rogers: As long as the resellers are ISPs selling IS, they can enhance it any way they want.

Katz: Rogers has a usage based wholesale tariff for ISPs.  When you are charging based on usage, why would you use traffic management, when they are paying for what they are getting?

Rogers: We do not traffic manage them, but we reserve the right to do so.  Their impact on the network is the same as one of our customers.

Katz: Rogers reserves the right to manage, monitor content posted.  Does this mean that Rogers will go beyond DPI, and actually monitor the content?

Rogers: Rogers does not do that right now.

Lamarre: The way that Rogers is describing P2P leads me to great reservations.  You gave the example, several times, of downloading movies, as if this is the only thing that goes on.  Also, you discussed the experiment.  However, this is nothing more than "anecdotal information", this is not scientific data.  Do you have empirical, scientific data that most users doing P2P are doing it 24/7, and whether this goes beyond the actual use of the bandwidth sold to the customer?

Rogers: It cannot go beyond the bandwidth sold to the customer.  Rogers said they would try to get the CRTC more scientific data.

Lamarre: In regards to wireless, you mentioned you are not doing traffic management for wireless the same way that you are doing on the wirelines. 

Rogers: You could say we are using price to manage it.

Lamarre: Would you say that SPI would have less impact on privacy than DPI?

Rogers: As mentioned, we are using SPI, as well as DPI.  There seems to be a bit of a misunderstanding in regards to DPI.  DPI does not keep any records of which customers were doing P2P, it does not look at content, and it simply classifies the data.  Some DPI methods do raise major privacy concerns, and we could do that, but we do not.  It is against the law, and there is no business reason to do it.

Lamarre: But you do monitor.  To sort, you have to monitor.

Lamarre: Do you keep aggregated data as to what is going on in the network?

Rogers: We have to keep aggregated data to charge customers who go beyond the cap.

Denton: Different narratives exist.  The CIPPIC narrative states that traffic congestion can be addressed through increases to capacity and augmentation.  Also, some experts have argued that we should not overact to temporary problems.  You have said that rational people will fix the problem, and this has led to throttling.  Why does CIPPIC, and the OIC, not get the story right?

Rogers: We are always working to augment growth, and are spending 10s of millions of dollars a year in doing so.  We are trying to stay ahead of congestion. Secondly, we understand why some are concerned about application specific traffic management.  However, this is not a network neutrality issue.  We have a network which is designed to be a shared use network, and the fact is that we have to manage it.  When a certain application tries to use it too much, users who use those applications cannot reasonable expect that to be ok.  It is the behaviour of the application, not the application itself that we are concerned with.  If an application which could cure cancer acted in a certain way, it would be also be subject to traffic management. Rogers would agree that we should not overreact to temporary problems.  If we are only trying to help our video business, why would we not be targeting the downstream?  We disagree with the narrative as it has been presented my many interveners.

Chairman: Are there other ways, instead of throttling, to control the upstream?

Rogers: Before traffic shaping, we were in a state of congestion.  Pricing mechanisms would not work as well as what we are doing now.

Chairman: Why would a pricing mechanism work on upstream? Is there no economic solution, instead of traffic shaping?

Rogers: You would have to have a very low cap for upstream, and you would have to educate your customers about the true nature of P2P (i.e. that other users access their computer for information).  Also, you would need a sophisticated pricing mechanism.  Moreover, Rogers is not aware of other companies which have acted in the way that you propose.

Rogers: An unmanaged network is not a neutral network.  It does not make sense to say that because you are engaged in application traffic management that you are not neutral. There are always decisions that we make that which favour some users over others (i.e. latency decisions which affect gamers), but this is clearly not traffic shaping.  We are happy to explain to the CRTC, in private, about our traffic shaping measures.


Quebecor Media, on behalf of Videotron Itee

Videotron (VT), the largest service provider in Quebec, explained that they have invested over $100 million in their networks.  They said that if only 1 thing could be taken from their presentation, it should be that the internet is a dynamic and evolving medium, and that the CRTC should not impose regulation.  Also, they stated that they do not currently use technical ITMPs, and to this point they are happy with the use of "economic measures" to deal with potential problems.  However, VT refused to rule out the use of technical measures in the future. 

VT made it clear that regulation should only be implemented if a "real problem" is identified.  They argue that, at this time, there is a lack of proof as to actual problems.  The "problems" which have been discussed up to this point are, according to VT, only "hypotheticals", and such hypotheticals do not justify regulation.

They noted that resellers that have participated in the CRTC proceedings have generally maintained that ITMPs, both economic and technical, are wholly legitimate.  In their view, underlying networks should apply these practices only to their own end-users and not to their resellers end-users.  VT called this a "rather self-serving position", and pointed out that on a shared network, when one end-user or group of end-users causes congestion on a particular facility, the impact is felt by all end users who use the facility.  It is the network operator, and not the reseller, who must support the high costs of physically splitting the cable cell to increase capacity.  VT argued that a network operator which is refused the ability to apply its practices symmetrically would soon find itself the target of resellers in search of arbitrage opportunities, and these resellers would have an interest in attracting those end-users who seek to circumvent the network operator’s traffic management practices.  VT explained that the excessive cost arrangement would be supported solely by the underlying network operator, and all other end users would suffer degradation in service.  Such a result cannot, VT asserted, cannot be in the public interest. Also, there is a healthy competition in ITMPs.  This underlying competition is sufficient.  An intervention by the CRTC cannot be justified because of a lack of proof as to actual problems.

Questions

Chairman: You have mentioned that you use financial means to control use, and you have thresholds, and excess use is charged as surplus.  Rogers said that these surplus charges do work to control downloading, but the problem is with uploading, and there is no financial means available to control uploading patterns.  That is why they rely on technical means.  What has your experience been? Do you act as Rogers does?

VT: We do not use technical means, such as DPI, like Rogers does.  Indeed, you are asking us how efficient our financial tools are.  It is true that, theoretically speaking, using a usage threshold over the course of a month should not impact users.  In fact, we do see that there is a correlation.  The implementing of an uploading threshold does have an effect on overall usage.  For example, it changes the amount of information which is uploaded.  It is a strong enough correlation to show us that this is effective.

Chairman: Rogers has said if they do not use traffic management, P2P will flood their networks causing congestion. Do you educate your users, do you tell them that you can block uploading and can restrain the amount of uploading?

VT: No, we do not have a plan to educate our clients.  Over the last few years, since 1999, we have been using usage thresholds, and our clients have been very happy.  Videotron clients are informed, they know how the internet works, and they know that uploading is more limited than downloading. Clients know that P2P can clog networks.  Users either limit the amount they use P2P, or they disable this feature.

Chairman: Do you have precise data on uploading and downloading, because you are telling us the opposite that other carriers have told the CRTC.

VT: We will see what data we can supply.  We have some data.  When we have instituted thresholds in the past, I am sure that we have tracked some data.  However, our comments are not in contradiction of other suppliers comments.  They have moved towards technical traffic management methods.  But the implementation of thresholds has kept congestion under control, but we are not saying this is the only method.

Lamarre: In regards to economic means to shaping traffic, whenever we have raised this issue, we were told about 2 problems.  The 1st problem was to publicly educate consumers, the 2nd was to quantify customer satisfaction as to economic means of management.  You have said that 98% of users as per Léger marketing said they were happy.  Could you give this survey to the CRTC?
Also, how does the usage meter work?

VT: All the user has to do is identify themselves, and they can access the meter and get user data from it.  We were among the first to track usage, and this usage tracking system is fully functional. 
Lamarre: You have 1 million clients, do you have 1 million meters?

VT: Yes.

Lamarre: If the users have a complaint

VT: The main goal of these meters is to allow customers to monitor their usage.  If there is a complaint, then it can be investigated.  It should be noted that these meters are made available to resellers.

Lamarre: How much does it cost for these meters, per user?

VT: I am sure we have that data.

Lamarre: What is the life span of this equipment?

VT: We will try to get you that data and information.

Lamarre: You have said that Videotron reserves the right to change its rates when it is part of a new offer that has not yet been communicated to the public before it comes into effect.  What do you mean by this?

VT: This is in case Videotron has a new product, with a new usage threshold, this is the type of offer we do not want to announce ahead of time so that our competitors get a sneak preview.  We have inserted this clause to protect ourselves.

Lamarre: What is the link between this and your traffic management practices?

VT: If management practices include economic means and tools, then you understand that we cannot divulge economic tools ahead of time, because that would have a detrimental economic effect on us.

Lamarre: In your response, you said that Videotron has 6 packages.  Despite the fact that you do not impose maximum bandwidth quotas, you do not have a one size fits all system.

VT: Our clients do have a choice of 6 packages, and this benefits the consumer.  This choice is entirely to the client’s benefit.  A user that needs to download more than upload would choose a package which suits their needs best, while my Grandmother would choose a different package.

Lamarre: In your submission, you say that it would be unreasonable in terms of relations with the customer to require an extensive disclosure of methods used.  What do you anticipate would be non-productive, in relation to relationship with customer.

VT: Our main concern is with the complexity of the information.  It would force us to post very complex information, and would be very confusing, and would lead to calls to our customer service centre.  A certain disclosure yes, but not to that extent.

Lamarre: So you are trying to strike a balance, without having to give consumers a course on network engineering?

VT: Correct.

Lamarre: Even if you do not have technical measures in place, you do have economic management techniques.  Your position is to promote full openness of the internet, which is normal.  To defend this position, you say that there is an unpredictable side to all of this.  What kinds of predictions do you make to try to handle your internet traffic?  Are you thinking about offering different kinds of bandwidth elements? If we are trying to make predictions as a good ISP, what methods are you using when you decide whether or not to expand your network?

VT: Any network manager will try to predict the total load on their network.  The way we do it is to provide for the needs of the network 6 months in advance, just like Rogers.  We do not rely uniquely on our economic management techniques.  There is a lot of unpredictability, we cannot be sure of customer behaviour a year from now.   Our main message is we need flexibility, we need the ability to change quickly.

Lamarre: While you say it is unpredictable, Rogers says it evolves very quickly.  If we do not do anything, the Canadian population and your customers may be faced with ISP which cannot face the demand.

VT: It is in interest of ISPs to offer sufficient services to customers, in this very competitive Canadian market.  We do not see that market forces are such that ISPs have an incentive to degrade services to the customer.  It is possible companies will make mistakes, but these mistakes will be fixed.  If mistakes are made by a certain company, but their competitor does not make a mistake, then customers will shift to the company that does not make a mistake.

Lamarre: You mentioned quickly in your presentation about services you offer to your wholesale clients, the impact of bandwidth has been discussed at length.  Do you enforce your economic management practice

VT: Yes, in our agreement with our resellers, there are surcharges (TPIA tariff) for people who go over their maximum.  We do not enforce this on the end-user, but on the wholesale customer.

Lamarre: Currently you encourage your reseller to implement the same system of billing according to bandwidth, correct?

VT: They have access to the counter mentioned earlier, but it is up to them whether they use it.

Lamarre: The bandwidth offered to the reseller is not isolated?

VT: It is the local access where the congestion will occur.  The local access is a shared resource between our end users and the users of the whole sellers.

Lamarre: To get back to the topic of the various products offered, you have 6 different service levels.  Can you provide us with the information? Also, based on your experience, and the surveys you have done, do you think that having economic measures, and giving customers the choice of what to use, can you create a certain fairness, or are there improvements still to be made?

VT: Our satisfaction results from the survey show that things are working.  Our main concern is to show that we will still have the flexibility needed to adapt.

Lamarre: In regards to privacy, there is 1 method which raises concerns, DPI.  You have said that you want the flexibility to use the history that is collected, even if it is not used right now.  Does this mean that you do not currently keep information?

VT: When looking at a packet, to redirect it, there is no impact whatsoever on privacy.

Lamarre: Some people have a contrary opinion.  My question is what would you do if you decide to you this DPI technique, how can you ensure

VT: The way to ensure our customers is to never touch the content, and I have not heard anything in the description of practice by other ISPs that there are other providers that are looking into the content.  There is no concern of privacy, in my mind.

Katz: In regards to TPIA, do you currently offer TPIA services?

VT: Yes, quite a few.

Katz: Can you segregate or distinguish traffic between wholesale users and retail users.

VT: At some point we segregate it, to "hand it off" to reseller.

Katz: Do you know if your resellers use a disproportionate amount of network capacity? Can you let us know if there is a proportionality concern?

VT: Because we charge excess use charges, we should have data on that.  In our traffic analysis, we look at it globally.  To answer your question, I would have to analyze the data more closely, but I am not aware of any significant differences.

Katz: Theoretically, you do have sufficient financing to fund growth in network, because you charge people more if they go over their cap.  Similar to Rogers, you plan 6 months out.  So, the only reason you would not be able to service demand is if you under-forecast demand.

VT: The total amount of money that is collected from excess uses charges is far, far below what would be needed for network investment.

Katz: Under what reasons would you engage in traffic management in the future? The only reason I can think of is if you under-forecast demand.

VT: The whole process of determining capital expenditure is not a uni-dimensional decision, with many factors being balanced.  We try to spend smartly. 

Katz: You will only build capacity if it is economically viable.  Ultimately, you make decisions to grow network to serve customers, and provide a return to shareholders. 

VT: We have an eye on the competitive marketplace.  You are portraying network management as something you do when there is a failure.  That is not how we see network management.  Network management and congestion management are good things, in and of themselves.  If we can create a new management technique that allows us to save $10s of millions of dollars, that allowed us to offer cheaper services to our consumers, that would be a good thing.

Chairman: You said that when one end user makes an impact on the network, that impact is felt by all end users.  If you resell in a fixed quantity, how do the wholesale customers affect your network? Do you not have a "safety switch"?

VT: The TPIA model is not one where you sell to resellers an "amount" of capacity.  It says to the reseller go find new users, and we’ll treat them like our own end users.

Chairman: You have no way of restraining wholesale users?

VT: There is not a chunk of bandwidth set aside for them.  The key thing to remember is that the access network is shared.  In a moment of congestion, their end users and our end users are equally, temporarily affected by that congestion.

Chairman: Is this reality by necessity or by design?  Could you avoid this, so that the customers of resellers could not congest your network?

VT: It may be theoretically possible, but we are not aware of it being done anywhere, and we would be concerned with it being done.  In a shared network context, by setting aside guaranteed bandwidth, we would be setting up two classes of end users, which would degrade the service of our own end users.   

Shaw Communications Inc.

For Shaw, Ken Stein, Senior VP, appearing with others.  Shaw stated they respect the ability of ISPs to effectively manage networks.  They said they constantly invest in this highly competitive environment. Shaw noted that even with significant investments, they still experience network congestion challenges – especially as a result of P2P traffic which, if left unmanaged, would consumer all the available capacity.  Therefore, Shaw notes, they must continue to combine investment with appropriate and necessary network management strategies.  They noted that the Telecommunications Act already prohibits ISPs from granting an undue preference or from interfering with the meaning of a communication, and the existing regulatory framework is working effectively to protect consumers.

Shaw says that if they did not deploy traffic management strategies to address network congestion, there would be a severe degradation in quality of service.  As recently as February 2008, an internet chassis was without proper traffic shaping for over a month, and the result was a major congestion problem with a significant increase in customer complaints. Shaw stated that they use DPI technology to shape upstream P2P traffic because this is the most effective measure to address the bandwidth consumption of P2P applications on their network.

Shaw noted that their traffic management devices operate 24/7, but the devices shape traffic only during periods of congestion, where the devices automatically detect P2P applications and slow the upstream traffic. Shaw said it is acceptable for individual ISPs to select their own network management strategy that may include a combination of approaches such as DPI, bandwidth limits, excess bandwidth usage charges, time of day pricing, caching, increased capacity and any other practices that do not breach either ss. 27(2) or 36 of the Telecommunications Act. Shaw noted that their DPI traffic shaping does not influence the meaning or purpose of the communication.

In conclusion, Shaw stated that they believe that we should rely on market forces to the maximum extent feasible and to interfere with market forces to the minimum extent necessary.  The retail ISP market in Canada is very competitive, and no ISP operating in that market can afford to put itself at a competitive disadvantage by blocking customer access to content or rendering applications inoperable on their networks.

Questions

Chairman: How do you define congestion?

Shaw: We define congestion in a variety of ways.  For P2P, we allocate a certain amount of bandwidth per user, and when that bandwidth is used up, our automatic devices kick in.

Chairman: You traffic management only comes into effect when the congestion gets to a certain point?

Shaw: Yes, although it is always on, it automatically begins to have an effect when congestion becomes an issue.

Chairman: Does you shaping correspond to the "peak hours"?

Shaw: There is a correlation between the traffic management and the "peak hours", but it varies from region to region.  We do this on a congestion basis because we operate over 5 time zones.

Chairman: We have had evidence from some that actually identifying P2P traffic is very hard.

Shaw: We believe that the signatures left by P2P data are very accurate.

Chairman: Do you have evidence to show that you are capturing P2P accurately?

Shaw: Yes, we can give it to you.

Katz: Is the component that is public internet segregated?

Shaw: The networks are segregated, and we do not fluctuate them based on demand.

Katz: is there a document to look at which lists steps to take when there are congestion issues, or are they dealt with on a step by step basis?

Shaw: We do have a system that we use.  We also try to make customers aware of their over usage, because often they are not aware of them.  Our traffic management principles do not become more aggressive than the standard we have set.

Katz: You are very concerned with market forces, but what you are saying is "let us do what we feel is necessary", which is actually carrier driven.  Can you explain why the economic vision is not what you are trying to achieve?

Shaw: That is not what we are saying.  In a competitive market place, consumers do have a choice.  If consumers are unhappy for whatever reason, they can move to another ISP.  I think our customers are very happy with how we are operating. At the present time we have tried to fix the congestion problem.  What we are able to do right now is satisfy P2P users, so that they can have maximum use of the system, when the system is available to them.  We are trying to satisfy, to the extent that we can, all users using our network. The price would be so excessive for

Katz: What you are saying is some customers are subsidizing other customers (i.e. those who use P2P).

Shaw: That is not what we are saying.  This is a business, and nobody is subsidizing anybody.

Katz: You said your customers have choice. Do you offer bundles of service, where users lock into long term contracts?

Shaw: We bundle products, but none of them are bound by long term contracts.

Katz: We heard last week that there are certain services that are not application specific, that hog the network.  How do you deal with the questionable ones, at times of congestion; do you do what you need to do to protect your network?

Shaw: We always try to protect the customer; if we are not sure, there will not be throttling applied.

Katz: Do you know what the traffic volumes are for wholesale customers, as opposed to retail? Are they disproportionate (i.e. do wholesale end users use more than retail customers)?

Shaw: We can get the information for you, but I have not heard of the use being disproportionate.

Katz: You have said that you only feel required to disclose when changes would have a "material and adverse effect on the operation" of the competitive ISP.  Can you define it for us?

Shaw: We would make the decision as to what "material" means.  We view this as the same as any changes in network management.  Wholesale traffic is the same as our own traffic, and we wanted it handled in the most efficient way possible.

Katz: You have said that the CRTC should not put the significant benefits at risk by regulation which could increase prices and stifle innovation.  How would this be the result?

Shaw: What we mean by that is that we have to respond to the market, and that regulatory regimes that require prior approval generally are not amenable to that.  We believe that the current framework is the correct framework.

Katz: You have said that "blocking content" might breach s. 36.  Under what conditions might it not breach s. 36?

Shaw: The intent of the comment was that you do not know under what circumstances a carrier may block particular content.  For example, something which is required by law, or a public policy objective, may not breach s. 36.

Katz: What would be involved if you had to follow the FCC edict on Comcast? Could you incorporate this into your submission to us?

Chairman: We have heard that Comcast engaged in session management? Is Shaw?

Shaw: No we are not.  Shaw will slow down packets, but we do not act in the way Comcast did.  Comcast forged packets, and this is a very aggressive and noticeable experience for the customer. We have not done what Comcast did, so why would we have to do what Comcast had to do? We do not have the same issue to resolve.

Chairman: What we want to know is what options you would have, and what it would take to address the concerns the FCC outlined in the Comcast decision.

Lamarre: In your presentation, you have said that ISPs should only be required to tell wholesale customers as to traffic management.  How, then, are retail customers supposed to be able to make an informed decision as to which ISP they use?

Shaw: Customers make decisions based on service.  If they are unhappy, they can move to another ISP.

Lamarre: However, if consumers are not informed about traffic management, then how can they make an informed decision?  How can this be considered market forces?

Shaw: People do comparisons day by day amongst competitors.  Also, we do not have long term contracts, so consumers can always switch.  Also, dealing with speculative issues, we could do a better job in dealing with issues that people are not sure about.  However, we should do more in informing customers as to what we do for their benefit.  Shaw said that they could do more to inform their consumers as to their traffic management.

Lamarre: How does the slowing down of a file not interfere with the content?

Shaw: What the customer chooses to do is download a file, but to do so, they must also allow uploading. 

Lamarre: Consumers are quite savvy.  They actually do make the choice to upload as well.

Shaw: We have heard that these types of traffic management do raise privacy concerns.  How can you reassure your customers that you are minimizing infringement?

Lamarre: In Canada we have a very strong privacy framework, guaranteed by law.  Shaw has undertaken to respect those privacy rights, and are sensitive to privacy issues.  We have a privacy statement on our website.  We do think, however, that the current legislative measures in place are very strong protections.  Customer information belongs to a customer, and we only use it to manage our business within the law.

Denton: Many are coming to the conclusion that application specific measures are needed for the management of networks.  The OIC, CIPPIC say that this is wrong, that you need to achieve this result by another method.  Are you sensitive to the concern that the exercise of application specific measures may give rise to reasonable concerns about the future of the internet?

Shaw: These people say that the internet invents itself.  We do not know what people are going to be able to do with the network.  Our interest is ensuring that the system works.  We are concerned with dealing with congestion, and our total focus is to create a network that allows people to use it the way they want.  The type of applications that win are always a surprise, and this is the kind of environment that we want. 

Denton: So, then, P2P applications seem to generate a lot of congestion for carriers.  If this is going to be rationally managed, is there a way of solving this problem without affecting the right of creators to create these types of applications.

Shaw: We in no way are restricting people’s right to create new technologies, we are doing the opposite.  Our traffic management is not meant to restrict P2P, we are trying to allow all other protocols to flow in an efficient manner.  We actually give a disproportionate amount of "the pie" (i.e. we allow 30% of bandwidth for P2P, even though only about 10% of users use it).  

Denton: The notion that the growth of traffic on the internet is much slower than had been predicted a decade ago, and that ISPs have the ability to keep up with the traffic, has been presented to this panel.  What are your views on this?

Shaw: The growth of the product differs, based on the year.  Some years it has doubled, tripled, and right now it is growing at a rate of 50%.  If things stayed at this rate, we may be able to deal with it.  However, things change.  We did not predict that video file sharing would become as dominant as it is today.

Denton: What is the balance between appropriate prices and traffic management?

Shaw: We want to balance prices to keep ourselves competitive, just as we try to balance our traffic management mechanisms.  I am not aware of any complaints made by Shaw users based on traffic management?

Denton: What controls it best, prices or traffic management?

Shaw: Pricing is more important than anything we do with traffic management, because users are generally not aware of traffic management policies.

Molnar: Is targeted traffic management more expensive that 24/7?

Shaw: No it is not, not for us.

Molnar: Rogers said that putting in place a dynamic traffic management approach could result in unpredictable customer experiences.  What are you views?

Shaw: We do not believe that customers see any difference in their internet use as a result of traffic management.  We do not think they are aware of whether or not it is on or off.  Most customer complaints do not deal with this issue.

Molnar: Did I hear you say that when there is congestion, P2P can be throttled back to 80kbps?

Shaw: This is the minimum, and will allow P2P to work relatively well.

Molnar: I want to ask about a particular suggestion, about whether ISPs, along with advertising speeds, to advertise throttled speeds.  Do you have comments on this, as a means of full customer disclosure?

Shaw: Even if we did, this would not be very useful information for the customer to have.  It is not what the customer is looking for in the product.  Customers want to know about download speeds, customer service, etc.  They are not concerned with the throttling of P2P traffic.

Molnar: If in the future you needed to throttle other things, such as downloads, would you alert customers?

Shaw: That will affect directly the quality of service the customer receives.  That information would be made aware to them by their use of the service.

Molnar: There is a difference between being made aware of something before hand, and discovering it as the result of using the service.

Shaw: We do not disagree with that.  We want to increase speed.  We want to increase downstream capability.

Chairman: Question about the shared nature of the network with TPIA. 

Chairman: Can you segregate time sensitive applications, like Skype?  How can you tell what applications are time sensitive?

Shaw: We do not slow down applications that are time sensitive.  We have technicians that have developed methods of telling the difference between time sensitive applications, like Skype.
crtc network management, day six
Day six of the CRTC's network management hearings opened with a final consumer group (Union des Consommateurs) and closed with three of Canada's biggest ISPs - Rogers, Videotron, and Shaw.  Bell was scheduled to appear today but has been pushed back until Tuesday.

The big storyline of the day was the disclosure by Rogers and Shaw of previously undisclosed information.  Rogers revealed its traffic management practices (throttling P2P upload speeds) and shockingly admitted that all its tiers receive the same upload treatment, regardless of the price paid by the consumer.  This is true even though its promotional material tell customers that higher tiered service offer faster upload speeds. Shaw disclosed that it engages in similar practices and provided insight into its throttling practices, noting that it guarantees 80 kilobits per second for throttled P2P sessions and that it reserves 30 percent of its bandwidth for P2P use (it said that 10 percent of its users account for the P2P traffic).
Videotron, the third cable ISP in the mix, complicated the analysis further by noting that it does not traffic shape.  Rather, it uses economic measures, the new euphamism for bit caps, to discourage overuse of P2P.  The ISP indicated that it is very happy with the effectiveness of its approach.

Today's summary was again compiled by Sean Murtha, a law student at the University of Ottawa.  Other coverage available from the National Post liveblog, CBC.ca, the National Post, Cartt.ca, and twitter feeds from CIPPIC and me.

Friday July 10, 2009
CRTC Network Management Hearings, Day Five: Telus, Cogeco, Barrett Xplore
Day five of the CRTC's network management hearings featured at trio of ISPs, each offering a different perspective on network management issues: Telus (DSL), Cogeco (cable), and Barrett Xplore (satellite).  While the three presentations provided a valuable reminder about the differences in network architecture, each had its own important moment. The key Telus moment came during questioning from Commissioner Len Katz about the impact of the managed IP network (ie. Telus IPTv) on the public Internet.  Katz expected to hear that there was no impact, yet Telus admitted that there was an effect.  In other words, this is one big pipe and the managed traffic can have an impact on the IP traffic.  This is a crucial admission since it highlights how Internet-based activities compete on the same pipe as managed IP ones.  In other words, a video on the public Internet effectively competes with a video offered on a video-on-demand service and throttling of the Internet-based video necessarily raises competition concerns. The Cogeco presentation served to emphasize that without rules, carriers will be free to throttle or limit bandwidth, regardless of any concerns about congestion.  This came through when Cogeco was twice asked why it continually traffic shapes on a 24 hour, 7 day per week basis, rather than when there is actual congestion.  The response was essentially that it is their network and they are entitled to do as they see fit (assuming that the throttling is legal).  The Commissioners should take note that the Cogeco policy and response demonstrates that this is not - as von Finckenstein suggested earlier in the week - a hearing about dealing with network congestion since policies like that employed by Cogeco bear no direct relationship to network congestion. The Barrett Xplore presentation was highlighted by an attempt to play the P2P blame game.  The company began by explaining how it needed to manage traffic to deal with bandwidth hogging applications like BitTorrent.  Yet when asked why its disclosure policy did not reference shaping of P2P traffic, the company admitted that its traffic management policies were not P2P specific.  Rather, anyone using too much bandwidth (based on the company's assessment) would find their connection throttled.  In other words, Barrett Xplore has a bandwidth problem, not a P2P problem, yet P2P provides a convenient excuse. Today's summary was compiled by Sean Murtha, a law student at the University of Ottawa.  Other coverage available from the National Post liveblog and twitter feeds (CIPPIC, me). [update: National Post and CBC.ca articles]

CRTC Net Neutrality Hearing – Day 5, Friday July 10th, 2009

TELUS Communications Company

Michael Hennessey, Senior Vice President, Regulatory & Government Affairs

Hennessey began by stating that practices only relating to the public internet, and do not apply to managed wireline or wireless practices (or "ITMP"s).  He noted that TELUS does not currently impose any specialized traffic management practice however, this does not imply that TELUS would not invoke traffic management if congestion became more of a problem than it currently is.

TELUS noted that in 2009, it will spend $950 million on "next generation hybrid fibre and wireless HSPA networks because we need to be more competitive".  However, he noted that this is not the only solution to capacity challenges, and that traffic management innovation and consumption-based pricing are other potential ways to manage capacity. Hennessey explained that TELUS is troubled by the statements of some parties that assume that all that needs to be done to keep up with traffic is to keep investing with no guarantee of a return.  He said that it is "simply nonsense" to insist on the one hand that ISPs should invest more in capacity, and then suggest that that capacity must be shared, at a discount, with other ISPs that are not incented to invest, and worse still, that do not think there should be any restriction on the amount of someone else’s bandwidth they consume.

TELUS argued that regulation can increase risk for telecommunications companies.  The threat of new regulation that could constrain ability to earn a reasonable profit is a scary thing for ISPs. Basic issues are easy to identify and address: everyone agrees that access to an open internet is a good thing.  Everyone agrees that some action by ISPs to block certain things, such as spam, is a good thing.

TELUS urged the commission not to put a "one size fits all" regulation for all networks.  It does not impose any traffic management, but if it adopted such practices, then any ISPs using that platform would be subject to those technical measures.  As a result, ISPs wanting greater control would have to invest in their own platform. TELUS does not disagree with the CRTC outlining broad principles, however they oppose the calls for ex ante tests or rules of general application governing any aspect of the provision of internet access services - this would be "a recipe for unintended consequences".

Hennessey concluded by stating that if there is a problem of undue preference, then it should be brought forward, and dealt with.  Let’s not create new rules, or new committees, without proof of harm.  The same reality that all ISPs face is that Canadian internet users expect to be able to go anywhere they want.  The CRTC should be vigilant when it comes to undue preference, but, equally, it should be as vigilant in ensuring an environment that allows fair forms of discrimination.

Questions

Chairman von Fickenstein
Mr. Von Fickenstein noted that, in its opening remarks, TELUS included a large qualifier by stating that "TELUS does not currently use traffic management techniques, but that does not mean that it will not". Should there be an ex ante requirement? Mr. Von Fickenstein noted that the CRTC’s usual way of dealing with this is ex post (i.e. after a complaint has been made).  However, should we rule out ex ante rules?

TELUS -
TELUS argued that the CRTC should focus on fact, things that have already happened.  The representatives pointed out that because the internet is vibrant and dynamic, we should deal with things as they arise, and not try to deal with hypothetical situations before they arise.  TELUS said that you would not want to develop ex ante rules.  There is not an overwhelming body of evidence to justify, currently, an ex ante approach.

Commissioner Lamarre
Should ISPs be considered a "public utility".  She said she had a difficult time not seeing ISPs as a "public utility", or providing the equivalent of a "public utility".

TELUS -
Public utility rules were meant to deal with monopoly providers, and because there is competition in the form of many ISPs, this is not the same.  While the service (i.e. internet) is equivalent to a public utility, the form of how it is provided is not a public utility, because of the competition.

Lamarre -
Does TELUS feared regulation on the engineering of their networks?

TELUS -
TELUS believes that the management of the wireless networks will be very different from the wire line networks, and as such fear blanked regulation that might be well matched to one form, but not applicable or a good fit for another network.  Concerned that there must be a differentiation made between wireless networks and wire line networks.  The CRTC must be careful about applying too much rigidity at this stage.

Lamarre -
TELUS stated that most customers have no interest on the traffic management decisions of telecoms.  Where is the example of this?

TELUS -
Mr. Hennessey noted that TELUS "sticks to its guns" in believing that the vast majority of internet users do "not care how things work".  While internet users care about Michael Jackson’s death and funeral, the overwhelming majority of Canadian internet users do not care how things are done.  While people are following these hearings in the news, on blogs and on twitter, that is a very slim percentage.

Lamarre -
Do you think most users would care if these traffic management changes infringe their privacy rights, or would impact their privacy?

TELUS -
Of course users would care about that.  What TELUS is looking at is dealing with congestion management.  From the customer’s perspective, what TELUS is trying to do is provide better service.  Moreover, TELUS recognized federal privacy legislation, and noted that there is already a mechanism in place to deal with invasions of privacy rights.  Carriers have to ensure that they do not break federal privacy legislation.

Lamarre -
Would TELUS agree that anything the CRTC crafts here should have at its goal protecting the privacy rights of users?

TELUS -
Hennessey stated that "I would put it a little differently, which goes back to TELUS’ fundamental point that anyone should be able to access anything on the internet which is legal."  However, he noted that we want to avoid duelling forms of legislation (i.e. highlighting the fact that there is already privacy legislation in place). If a privacy issue arises, it should be dealt with by the existing mechanism, which is the privacy commissioners.  He noted that TELUS would "put the boots" to anyone in their company who created a traffic management process which infringed users privacy rights. TELUS admitted that privacy is not something they have really prepared to discuss, because right now it is not an issue for them, because they do not currently impose any traffic management processes (but they acknowledged that it is certainly a live issue). If the CRTC were to come across a privacy concern with the way an ISP conducted its traffic management, then in practice, the CRTC should not ignore the issue.  However, there is a concern about overlapping jurisdiction with existing privacy legislation.

Vice-Chairman Leonard Katz -
Would any growth within TELUS take away capacity from the public internet service?

TELUS -
TELUS is always trying to increase its capacity for the public internet.

Katz -
-However, what if TELUS was not able to expand capacity for some time - could a decision be made where TELUS favours IP management, or something else, to the detriment or exclusion of the public internet?

TELUS -
-TELUS struggled to give an answer which was satisfactory to Mr. Katz on this point.  However, they stated that theoretically, "if push comes to shove" and a choice had to be made, TELUS would favour the public internet.  They noted that we have to remember that this is a competitive marketplace - there is not wisdom at all in degrading the service, because TELUS customers do have other options in the form of other ISPs, because of competition within the industry.

Katz -
-Mr. Katz noted that TELUS said that they do not currently have traffic management in the retail/wholesale is this a business reason or a technical reason?

TELUS -
The network is set up in such a way that the retail and wholesale network is integrated, and it is very difficult to differentiate between the two.  For a large portion of the network, it would not be possible to differentiate between the - different parts of the network are in different parts of evolution, so it would be difficult if not impossible to segregate them.

Katz -
Mr. Kutz pointed out that Bell has been able to do this with their networks.  He asked TELUS to include in their final submission to the CRTC documentation about whether or not they can differentiate between the two networks.

Commissioner Timothy Denton -
-Mr. Denton asked whether it is TELUS’ view that there is no wholesale price which could be established which would make retail competition legitimate?

TELUS -
-At this point, a price that reflects the total cost that TELUS has to bear when it makes an investment risk would be appropriate.  There might be a price at which such leasing would be accessible.  Mr. Hennessey explained that the CRTC should continue to have the power to deal with unjust preference in the wholesale market. 

Commissioner Timothy Denton -
Clarify the term "next generation network", as it was used in TELUS’s oral submission.  "In your view, is "next generation network", as the term was used in your submission, connote a specialized term of art that needs to be explained?"

TELUS-
By that we mean cutting edge technology that can increase capacity and speed on our networks.

Denton -
Many of the parties that have appeared before the CRTC have expressed concerns about "application specific traffic management measures", which really dealt with the balance of power between creators, carriers and consumers.  He wanted to know if TELUS sees that aspects of application specific traffic management are legitimate?

TELUS -
TELUS answered that while we they do not practice this today, they feel that they are legitimate, as long as they do not result in anti-competitive dealing or materially degrade the internet service of users.  They are not prima facie illegitimate.  As an example, traffic management may be used for high priority public alerts, if such a system were to be developed (this is an example of traffic management for the public good).

Cogeco Cable Inc.

Yves Mayrand, Cogeco, VP Corporate Affairs

Cogeco began their presentation by noting that, in short, as an ISP, Cogeco acts in both retail and wholesale access services.  It stated that they currently employ traffic shaping measures as part of their network management activities.  At a certain point, Cogeco faced no choice other than implementing "traffic shaping measures as part of our network management activities". Cogeco acknowledged that this was not an "arbitrary decision", but was made as a result of P2P applications that consume a disproportionate amount of bandwidth.  Cogeco seeks to ensure fair and sustainable usage of the available bandwidth among the end-users on their internet network.

Cogeco identified the "key issue" of this proceeding "is to determine if the Internet Traffic Management (ITM) practices used by the Canadian ISPs, mainly the traffic-shaping measures implemented by Cogeco are used in accordance with the Act". Cogeco acknowledged that "for the foreseeable future" they would continue to rely on technical management tools to protect our network and ensure fair and manageable use among all Cogeco’s retail and wholesale end-users of their network.

Cogeco also summarized how their traffic-shaping tool worked:

  • It is not applied on the downstream, but only on the upstream.
  • It is carried out solely on P2P applications that are based on bulk transfer protocols, such as Bit Torrent applications.
  • Is not interfering with the content transmitted which is always delivered without change to the recipient.
  • It is not applied in a manner to block or disrupt the telecommunication, but has only the effect of slowing down the transmission of P2P traffic.
  • It is inspecting the header and payload of each packet to the minimum extent required in order to identify the specific signature of P2P protocols; and
  • It is agnostic to any personal identifiers. (Cogeco reaffirmed this several times during their submission, that they were agnostic towards personal identifiers).

Cogeco maintained that the traffic-shaping measures they used did not give them access to personal identifiers.  As they stated "to be clear, we have no idea of the identity of customers subject to traffic shaping".  It is impossible for Cogeco to use personal information for targeted marketing campaigns.  While some information is captured through traffic sharing, Cogeco also said that it was their position that no regulatory measures designed to regulate Canadian ITM practices are required at this time. In conclusion, Cogeco noted that they "see no reason for additional rules to ensure the protection of personal privacy at the present time".

Questions

von Finckenstein -
Surely if it is restricted on the downstream side, it would impact the upstream side as well. Is that not the case?

Cogeco -
While it may have a marginal effect (i.e. if one customer is downloading from another customer who is uploading), but, for sure, that effect would be marginal.

von Finckenstein -
Is this being done to all P2Ps, or does Cogeco distinguish between P2Ps?

Cogeco -
We distinguish by focusing on file transferring P2Ps (like BitTorrent), and not some real time P2Ps, like Skype.

von Finckenstein-
Is this throttling applied on a 24 hour basis? Why does it have to be applied across the board, even when there is not a congestion problem? Mr. Von Finckenstein noted that there is not a 24/7 need, and if the issue is congestion, then why apply the same management practices when congestion is not an issue?

Cogeco:
If we are employing this tool, why should we provide any possibility for by passing the management tool they have created? The fear is that if they limit it to certain times, then there may be unexpected spikes in use at that time.

Denton:
Why does Cogeco rely on a technological response to the congestion problem (i.e. traffic management) rather than an economic response.  Is there a state of dissatisfaction with economic measures, as opposed to technological measures?

Cogeco:
We have just begun to impose usage billing, so we do not have data on that yet in regards to congestion.  Also, Cogeco noted they were not convinced that usage billing or "economic measures" will cover all situations or new developments on the internet.

Denton:
Denton wanted further clarification on the question already asked by the Chair, about why Cogeco feels the need to throttle on a 24 hour basis, when there is not a 24 hour need?

Cogeco -
Cogeco does not see what purpose there would be in doing this.  They have the technology already in place, and why should they create a window of opportunity for bypassing it?

Denton -
After noting that Cogeco said in its introductory statements that they did keep some information that they collected during traffic-shaping, Mr. Denton also noted that Cogeco said that they did not keep this information for a long period of time.  How long does Cogeco keep information it captures through its traffic-shaping mechanism?

Cogeco -
Generally, the information on traffic patterns is not kept for longer than 30 days.  The data is used to characterize what is on the network, and is used to improve it.

Denton -
-Mr. Denton asked why there is the need to keep an eye on upstream traffic, as Cogeco does?

Cogeco -
Upstream network is far more limited than downstream (it is a much more finite resource).  Also, there is further information in the confidential section of their submission.  Also, Cogeco manages this because of its inordinate ability to use the resources on the upstream, and this is simply not a concern for the downstream.

Commissioner Molnar -
Commissioner Molnar referenced what Cogeco said in their oral submission, that, on the wholesale side, Cogeco sees no reason to extend the notification requirements imposed on Bell to cable ISPs, as the circumstances are quite different.  Commissioner Molnar asked why should TPIA customers not be made aware in a timely manner what impact Cogeco’s decisions would have on them?

Cogeco:
It would be perfectly in order for TPIA service providers to provide their own customers with the same type of information which Cogeco gives to its own customers.  Cogeco noted that its suppliers are very aware of the tools that they use, so they are not hiding anything from them.  There is no unjust or unfair treatment of the TPIA customers. Cogeco noted that, to date, there have been no complaints by wholesale clients on their management tools.

Molnar:
Is it right to notify wholesale customers as to changes to internet management, so that they can in turn alert the end users who will be affected?

Cogeco :
Cogeco answered that while they tell their own customers about any changes, if their wholesale customers are not made aware of any changes to their internet management tools, then they would be happy to forward them the same information.

Barrett Xplore Inc.

C.J. Prudham VP, General Counsel for Barrett Xplore

Ms. Prudham wanted to focus on traffic management from the perspective of a small ISP which focuses on rural communities. She noted that Barrett Xplore works in every province and every territory, under the Xplorenet brand name, using fixed wireless and satellite technologies.  Barrett has invested over $140 million. While the use of traffic management is important to all ISPs, it is especially vital to a small company like Barrett.

While interveners have suggested that all ISPs need to do is spend more money to deal with network congestion, that is a preposterous position, and it would threaten Barrett’s ability to provide broadband service in rural communities. Prudham noted that "as challenging as it is to expand fixed wireless networks, expanding satellite capacity is positively daunting".  Any physical upgrades to satellite networks is an extremely expensive, long term process.

Barrett believes that each ISP should be permitted to adopt traffic management tools that are consistent with its particular circumstances, network configurations and business models.  That way, all ISPs, especially smaller ones like Barrett, will be able to employ appropriate tools to manage traffic at peak usage times to ensure that best possible quality of service for all customers.

While some interveners have suggested that carriers are discriminating against certain types of applications (like Bit torrent), Barrett offered the following points:

  1. Since existing capacity is finite, the network cannot always carry all of the traffic presented to it an acceptable speed.
  2. From a business perspective, Barrett cannot thousands of customers off its service in order to carry the excessive volumes of traffic presented by a few of its customers at a given point in time.
  3. To discriminate against bandwidth hogging applications is not unjust or unreasonable under s. 27(2) of the Telecommunications Act - it is an entirely justifiable response to the use of a shared network by a large customer base.
  4. The traffic management technologies used in these circumstances are not directed at individual users or individual applications.  They are directed at excessive use of bandwidth at peak periods and are applied without discrimination to all customers who subscribe to a given service level.
  5. As long as customers are made aware of service limitations when they subscribe to the service, these traffic management tools are both reasonable and necessary.
  6. Without these tools, affordable services would not be viable for the rest of the customers and there would be no business case for the extension of services to rural and remote areas of Canada via satellite or terrestrial wireless networks.

Issues

Prudham then discussed the 6 specific issues that the CRTC had identified in their June 5th letter to interested parties:

Acceptable Internet Traffic Management Practices - Ms. Prudham noted that Barrett believes that each ISP should be permitted to adopt and implement traffic management practices that are appropriate to its circumstances.  In their view, there is no "one size fits all" traffic management technique that would be appropriate to all ISPs.  According to Barrett, the only criteria the CRTC should use to determine whether a particular traffic management practice is acceptable is to "assess whether the use of the technique complies with the 3 principles highlighted earlier: transparency, non-discriminatory treatment (i.e. treating like-traffic the same) and non-interference with the meaning of content."

ISP Disclosure - Barrett noted that they are "an advocate for transparency", and stated that each ISP should provide notice to its customers of the traffic management practices that it employs.  This does not mean setting forth in great detail in a contract, as Barrett simply advises its customers that there are limitations on their use of its service, and directs them to a website with further information.

Privacy - Barrett does not think that traffic management practices raises privacy concerns, as Barrett does not collect, use or disclose personal information when employing traffic management techniques, like DPI.  There is no evidence that the personal privacy of internet users is impacted by traffic management practices.

Wholesale Services - Barrett does not think there should be a rule limiting the use of traffic management practices with respect to wholesale services.  They believe such a rule would be unnecessary, and traffic management is an issue that should be left to commercial negotiations between parties.

Mobile Wireless Carriers - Barrett does not believe that there is any need for the CRTC to adopt rules specifying which traffic management practices are acceptable in relation to wireless carriers.  Each mobile wireless carrier must have the ability to adopt traffic management practices that best fit its network configurations and the capacity demands made by its customers.

Scope of Section 36 of the Telecommunications Act - In Barrett’s view, the analytical framework the Commission should adopt with respect to section 36 is twofold.  First, a party that alleges that a certain traffic management practice contravenes section 36 should be required to demonstrate that the ISP has, in fact, exercised some control over the content of the telecommunications or influenced the meaning or purpose of the telecommunications.  It is only after the factual burden has been met that an ISP should have any obligation to defend its practices and demonstrate that controlling the content or influencing the meaning of telecommunications is appropriate or necessary in the circumstances.

Questions

von Fickenstein -
Is it true that Barrett can reach any potential consumer in Canada?

Barrett -
Yes that is true, we can reach every Canadian.  There are greater capacity issues in Southern Ontario and Quebec, but Barrett is working to increase its capacity.

Molnar -
Ms. Molnar inquired about where Barrett controlled the ITMPs? What influence does Barrett have on the use of the traffic management?

Barrett -
While Barrett controls the economic measures, at no point does Barrett control the technological measures (at this point). However, Prudham noted that Barrett has input on the technological measures, but the final decision is out of their hands.

Molnar -
Ms. Molnar asked whether the internet management controls which are currently in place work on a 24 hour time frame (i.e. are they always operating)?

Barrett - While the controls themselves are in place 24/7, the controls are different at different times.  As an example, the controls are more stringent at peak times, and less stringent at less peak times.

Molnar -
As essentially a "reseller" is Barrett concerned about disclosure by the upstream provider? Have you ever been in a situation where your end user has complained about changes by the upstream provider?

Barrett -
Our upstream provider has always been forthright, and we have had no complaints from out end users at this point.  Also, Ms. Prudham pointed out that she thought that this type of disclosure was best left to private commercial dealings between the small ISPs and their upstream providers.

Lammare -
Ms. Lammare asked about privacy issues. Does Barrett dispose of any personal information which is gathered during traffic management?

Barrett -
The vast majority of Barrett’s data is aggregate data, and is not individualistic.  With respect to individual data, if the customer triggers the limit, that will be recorded on their file.

von Finckenstein-
Will Barrett slow down users who "excessively" use applications, such as Bit torrent?

Barrett -
Yes.  However, the system resets each hour, so it is true that if a user is "excessively" using an application, then they can be slowed down.

crtc network management, day five

Day five of the CRTC's network management hearings featured at trio of ISPs, each offering a different perspective on network management issues: Telus (DSL), Cogeco (cable), and Barrett Xplore (satellite).  While the three presentations provided a valuable reminder about the differences in network architecture, each had its own important moment.

The key Telus moment came during questioning from Commissioner Len Katz about the impact of the managed IP network (ie. Telus IPTv) on the public Internet.  Katz expected to hear that there was no impact, yet Telus admitted that there was an effect.  In other words, this is one big pipe and the managed traffic can have an impact on the IP traffic.  This is a crucial admission since it highlights how Internet-based activities compete on the same pipe as managed IP ones.  In other words, a video on the public Internet effectively competes with a video offered on a video-on-demand service and throttling of the Internet-based video necessarily raises competition concerns.

The Cogeco presentation served to emphasize that without rules, carriers will be free to throttle or limit bandwidth, regardless of any concerns about congestion.  This came through when Cogeco was twice asked why it continually traffic shapes on a 24 hour, 7 day per week basis, rather than when there is actual congestion.  The response was essentially that it is their network and they are entitled to do as they see fit (assuming that the throttling is legal).  The Commissioners should take note that the Cogeco policy and response demonstrates that this is not - as von Finckenstein suggested earlier in the week - a hearing about dealing with network congestion since policies like that employed by Cogeco bear no direct relationship to network congestion.

The Barrett Xplore presentation was highlighted by an attempt to play the P2P blame game.  The company began by explaining how it needed to manage traffic to deal with bandwidth hogging applications like BitTorrent.  Yet when asked why its disclosure policy did not reference shaping of P2P traffic, the company admitted that its traffic management policies were not P2P specific.  Rather, anyone using too much bandwidth (based on the company's assessment) would find their connection throttled.  In other words, Barrett Xplore has a bandwidth problem, not a P2P problem, yet P2P provides a convenient excuse.

Today's summary was compiled by Sean Murtha, a law student at the University of Ottawa.  Other coverage available from the National Post liveblog and twitter feeds (CIPPIC, me). [update: National Post and CBC.ca articles]

Thursday July 9, 2009
CRTC Network Management Hearings, Day Four: CAIP, CIPPIC for CDM, Execulink, Primus
Day four of the CRTC's network management hearings featured three of the world's leading experts on networks along with a trio of ISP perspectives.  The panelists included the Canadian Association of Internet Providers, CIPPIC on behalf of the Campaign for Democratic Media (CDM) (who brought experts Dr. David Reed, Dr. Andrew Odlyzko, and Bill St. Arnaud), Execulink Telecom, and Primus Telecommunications. An important theme during the day was debate on whether there really is a network congestion crisis.  CAIP argued that it is competition, not congestion that is at issue.  Odlyzko surprised the Commissioners by noting that traffic growth is actually declining and that a steady rate of capital expenditures should be sufficient to meet demand (this was later confirmed by Execulink). Moreover, St. Arnaud and Reed emphasized the diminishing importance of P2P as a video delivery channel, urging the CRTC not to fight yesterday's war. The second important development was the clear divide that has emerged on traffic management at the wholesale vs. retail level.  The wholesale issue was at the heart of the CAIP vs. Bell case and that case is effectively being re-argued during these hearings. Many ISPs have argued against any form of traffic management of wholesale traffic, noting that it prevents the potential for competition between providers.  Moreover, in repeated questions about the impact on carrier networks (such as Bell) it is becoming apparent that the problem may lie with Bell, not with the ISPs.  Independent ISPs note that Bell promises certain speeds and bandwidth at the wholesale level, but seemingly has difficulty meeting those promises. Some providers (ie. MTS Allstream) have network architectures that ensure that this is not a problem.  The sense is that Bell does not and so resorts to traffic management practices.  It is noteworthy that CAIP focused very heavily on the wholesale issue and basically abandoned any pretext of protection against traffic management for consumers. The retail side of the issue has many ISPs arguing that anything should be permitted with appropriate disclosure.  Fighting for some limitations are consumer groups, creator group, Saveournet.ca, and the Open Internet Coalition.  They have proposed a test to determine whether the traffic management practice is permissible under Canadian law. The Commission will ultimately have to decide both (1) the wholesale issue, which may involve an acknowledgement that it got the CAIP decision wrong; and (2) the retail question including disclosure practices and tests (if any) to determine appropriate conduct.  Today's summary was again compiled by Yael Wexler, a law student at the University of Ottawa.  Other coverage available from the National Post liveblog, CBC.ca and twitter feeds from CIPPIC and me.

CRTC Net neutrality Hearings – July 9, 2009

Canadian Association of Internet Providers (CAIP)

Summary:

  1. The issue before the table is competition on the Canadian ISP landscape; congestion is a symptom of the lack of competition.
  2. CRTC should prevent Dominant Carriers (DC) to stop ITMPs on their wholesale traffic, except for network security.
  3. In order to drive competition, the use of ITMPs (for retail) should be end-user determined, that is, consent to technologies must be required by the ISP.
  4. ITMPs that traffic control in an aggregate fashion, absent customer's consent, is contra s.36, 27(2) by interfering with the "purpose or meaning of telecommunications."
  5. Need to develop a uniform, quantifiable measure for congestion

Opening remarks:

Chris Tacit - Counsel
Tom Copeland – Chair of CAIP

CAIP brings to the table the perspective of independent ISPs on the commercial issues surrounding ITMPs. The role of the independent ISP industry is crucial for increasing competition and innovation. For example, VOIP was first adopted by independent ISPs. Independent ISPs are threatened by the market power of DCs: independent ISPs must obtain wholesale customers from the DCs while the DCs are the main competition with an overwhelming market share (95.5% of residential subscribers). This makes it difficult for independent ISPs to offer Internet services that are different from those of DCs. End-user consent to ITMPs is necessary for driving product differentiation and thus, competition, in the market.  Building network capacity and unbundling networks are integral and less intrusive methods for network management. The assumption that unrestricted increases in Internet traffic can lead to "congestion" is unfounded and untested and undefined. Moreover, congestion should not drive the policy determination regarding ITMPs. ITMPs may be necessary for stopping spam, viruses and network attacks, but they should not be used on the wholesale level otherwise. Availability of diversity in service packages would be an indicator of healthy competition at the end-user level.

Responses to CRTC:

  1. ITMPs should be based on business model of the ISP, to drive competition
  2. ITMP disclosure: ISPs should disclose ITMPs to wholesale customers (but not the technical details), but these should only be for network attacks. Traffic management in retail services should be disclosed upon customer sign up.
  3. Privacy concerns: there is no need to use personal data in ITMPs although it may occur in the future for commercial reasons; there is also no need to go beyond the existing privacy framework (PIPEDA and CRTC decisions on confidentiality).
  4. Is application of ITMPs to wholesale services by retail ISPs appropriate? No, except for network attacks. DCs must refrain from applying ITMPs on wholesale customers on behalf of competitors, under s.27(2) and 36. If the retail ISP is going to make any modifications, it should be subject to wholesaler notification and also to end-users.
  5. The same rules should apply to all ISPs regardless of wireline or wireless
  6. Congestion should never drive policies relating to ITMPs.
  7. The situation warrants the development of uniform, quantifiable measures for congestion.

Questions:

Chair -
What do you mean by "Dominant Carrier"
CAIP -
The duopolistic nature of the market makes them jointly dominant; we don't think that CAIP would be here if it weren't for joint market dominance of cable companies and telcos.

Chair -
Are you suggesting that more unbundling will mean no more congestion?
CAIP -
Unbundling is a crucial part of the solution for the competitive industry.

Chair -
You submit that there should be no ITMPs as a wholesaler, which is tied in with your conjecture that we assume the presence of congestion. We are here because there is congestion, it's not an assumption.  We are here to make sure that everybody can enjoy the Internet but that people who are capacity hogs don't hinder others.
CAIP -
Wholesale users have tiny fragment of the industry (95.5% come from cablecos and telcos) - when there's a congestion problem it's with their end-users. So, the wholesalers shouldn't suffer. Moreover, wholesale and retail traffic can be disaggregated, so there's no justification for retailers to control the traffic of a wholesaler who's internal traffic doesn't affect them.

Chair -
If congestion is the wrong lens to look at it, what is?
CAIP -
It's about consumer choice and competition. ITMPs can be used to provide for end-users bill management. When it hasn't been demonstrated that wholesale is causing any kind of congestion in the ILECs networks, and even if there were there would be other ways to deal with it.

Commissioner Katz -
How do your members differentiate their services from the DC where you are competing with them?
CAIP -
Many use the underlying infrastructure to develop private networks so the traffic never touches the public Internet, it just goes between computers internally (private LAN). Providers also have done VOIP protocol between two customers that never touches the pub Internet, just through the providers.  Also our competition is in the fact that our wholesalers serve customers locally, but there's not much room to differentiate ourselves further b/c of the ITMPs.

Katz -
So a wireless retailer should be able to provide a better service than the incumbent who may have congestion practices?
CAIP -
The cost of consumption is the driving factor; so it's hard to draw that analogy just based on the market. Industry Canada has been focused on increasing spectrum. Existing competitors want to become masters of their own networks, by focusing on owning your own capacity.

Katz -
There's been evidence that if you look at international markets, they work better, partly because  there is no distinction made between retail and wholesale. British Telecom (BT) is a monopoly in the UK, their retail arm is treated as all the other wholesalers, they've got to subscribe to it, but BT retail is treated no differently than resellers.
CAIP -
No one's saying there's no difference between retail and wholesale; the MTS evidence shows that in the UK they've unbundled a lot of the wholesale, so there's been a lot more competition and competition has made the net neutrality problem obsolete. CAIP is not in the reselling model of the UK. The CRTC shouldn't make its determination on ITMPs without the whole picture, we're trying to deal with the problem of net neutrality by looking at congestion - when it's about ensuring more competition in the marketplace.  In the UK, the vertical integration of BT was causing problems with the expansion of the network. Since they've changed the model competition is vibrant and the unbundling model has been helping. There's no controversy because the marketplace is taking care of it, there won't be any regulation of ITMPs.

Katz -
We do have a competitive market in Quebec. Two players - Videotron and Bell - with distinguishable services. 
CAIP -
I'm pleased that until today Videotron hasn't applied ITMPs and have increased the capacity of their network. But regardless, there's evidence of duopolistic behavior in our market. This isn't a real distinction between the two. At the retail level, let them decide; just don't force all the wholesalers into a particular model (especially where Videotron isn't…).

Katz -
Well, why don't your customers go to Videotron if Bell is imposing ITMPs?
CAIP -
That's not practical at all; you're not just switching providers, you're switching technologies.  There's practical implications of what's sustainable in the marketplace and just switching to the one other provider is not it.

Katz -
In reading GAS tariffs, one provides a dedicated pipe and one doesn't. Yet the tariff doesn't clearly allow for the guaranteed level of service (QOS), or the independence to manage your network as you seek.
CAIP -
Well then I suppose retail ISPs could get a 2-bit service from Bell, but that's not what anybody wants nor what the tariff is for. The guaranteed level of service issue is that no one contemplated ITMPs as the way to ‘guarantee the service'. To say that the tariff reads this way so it is that way is just poor logic.

Commissioner Denton -
The last few days we've been told that the issue is congestion. But you're telling us that it's not the real problem. You said there was no evidence that wholesale was causing a congestion problem; so there's no congestion arising from the offer of wholesale?
CAIP -
We as wholesale customers are not causing congestion - our markets are way too small. If you look at the sequence of Bell applying ITMPs it was first applied to their retail markets, then later to the wholesale. This shows two things - they can segregate the two and we weren't a problem.

Denton -
Drawing on the UK example, you've said that the competitive market will take care of congestion. If retailers were allowed to buy from wholesalers without ITMPs, there would be significantly greater competition?
CAIP -
Yes, the presence of capacity constraint is the effect of duopolistic structure. This is classic business behavior: price as high as possible and constrain. Unified, the infrastructure company in the UK now has the goal of providing service to all companies; the one wholesaler has one wholesale goal.  But to increase competition, you need unbundling. It's not just a congestion issue, it's a competitiveness issue. If a wrong policy is implemented on the ITMPs, and later there's unbundling the ITMP policy will have negated the potential of the unbundling to create competition! There's a difference between increased competition and increased differentiation of services.

Denton -
Is publicity at retail level sufficient to handle congestion problem?
CAIP -
Yes. Congestion is caused by users. ITMPs are penalizing behaviours though. What we're trying to address is the behavior; it's extreme to be managing the behavior of all Canadians using a platform when many of them do not have a problematic behaviour.

Commissioner Molnar -
If wholesale services wasn't throttled, could you guarantee that the wholesale users weren't causing congestion to the retailers?
CAIP -
The size of the wholesale market is too small to cause problematic congestion; ITMPs are implemented on a network, not a node or office; so they're implemented as a blanket even though it can be segregated.

Molnar -
You submit that there should be no restrictions on retail and ITMPs are a form of competitive differentiation. You believe that with customer consent, any form of ITMPs should be allowable.
CAIP -
Yes, if there's consent, they can do it. It's a competitive choice for the consumer and for the ISP.

Molnar -
I'm concerned that providing access to applications is becoming confused with competition. I see these as different, the consumer should be choosing.
CAIP -
The only reason packages exist with different features is because there's consumer demand - please don't anticipate a problem that doesn't exist!

Commissioner Lamarre -
I'm concerned with your take on privacy.
CAIP -
There's no need for an a priori rule, there's already laws about it. Is an ISP is going to break the law, PIPEDA or another law will deal with it, and then the ISP may be in double jeopardy before this commission and another.

Chair -
You submit that since we're so small we can't be the problem. And they applied it to themselves and only then you. Doesn't this show you might have been the problem if their initial measure was insufficient? It can be interpreted in both ways.
CAIP -
The problem is exactly that there isn't enough info on this problem, and we shouldn't prioritize one interpretation over another at risk of serious setbacks for competition.


Canadian Internet Policy and Public Interest Clinic on behalf of Campaign for Democratic Media (CDM)

Summary:

  1. CDM recommends the establishment of normative guidelines and boundaries for ISP behavior, especially for determining whether something is in violation of s.36 or 27(2).
  2. CDM hopes the CRTC will be forward-thinking, and not reactive, in approaching these matters.
  3. The problem is the encroaching on the physical and theoretical space of the "public Internet" in service of private concerns and the creation of a false dichotomy between the two.
  4. When thinking about congestion, both the user and supply side of the equation need to be taken into account in determining solutions. The ISPs are not provisioning to the best of their ability, nor is P2P a reason for the congestion. "Functional marketplaces meet demand with supply - not by squashing demand."
  5. Traffic interference like application-based throttling is anathema to the open Internet and are unnecessary for the daily operation of the ISP.
  6. The CRTC must take into account both s.36 and s.7 when determining whether there has been an infringement.

Opening remarks:

David Fewer - Acting Director of CIPPIC
Steve Anderson - Co-founder of the Campaign for Democratic Media and SaveOurNet.ca
Dr. David Reed - Adjunct Professor at MIT
Dr. Andrew Odlyzko - Prof. U Minnesota in Mathematics, leading independent source for tracking Internet patterns
William St. Arnaud - Chief Research Officer for Canada's Advanced Internet Development Organization (CANARIE Inc.)

Anderson

The main issue at stake is who will determine how we use the Internet? The values inherent in the open Internet are values attracting widespread citizen action. If we fail to create the right balance between maintaining networks and keeping the Internet open, there will be grave consequences. The main way to allow ISPs to compete is to increase bandwidth offerings, so they don't monetize on artificially created scarcity.

David Fewer

We are here to convince you of the value of an open Internet. We propose a test for establishing a normative and prospective framework for how to guide ITMPs, and to support competition. This hearing needs to establish a forward looking results, not a reactive tone - we need to set boundaries for ISP behavior with the objective of providing ISPs with competitive security and Canadian consumers and business with confidence in an open Internet. Establishing rules for the open Internet doesn't amount to lawyers running the Internet. No one has a legitimate proprietary claim to the Internet, because it is in the public interest and thus greater than the sum of its parts - it's not the property of the ISPs.

CDM agrees with the objective of this hearing, but takes issue with some of the definitions and assumptions. The CRTC's definition distinguishes between the "public Internet" and "private services" only creates a space for the ISPs to encroach more and more on the public Internet space for the sake of private services. The CRTC assumes that unrestricted traffic increases will lead to congestion and then to the deterioration in services. This simple equation only takes into account the supply side. CDM would replace it with "unrestricted increases in Internet traffic can lead to congestion in all or part of an ISP's network if these increases are not met with adequate provisioning." The ISPs' contention that they are provisioning to capacity but still need to traffic shape all P2P applications is unreasonable in light of the evidence that when Comcast was throttling in order to control growth, it did so by throttling less than 1% of users for no more than 15 minutes at a time. Further, the CRTC assumes that certain ITMP's may be appropriate. The CRTC's language of "traffic management practice" should be referred to as Traffic Interference, because that's what it is at the user end. The language of "integrity of the network" also is imprecise, and doesn't address when an ISP should intervene in the network.

The bottom line is that ISPs have no incentives to tailor their ITMPs to the requirements of the Telecommunications Act.

  1. P2P specific traffic management is discriminatory against a class of applications and users and is a prima facie violation of s.36 by controlling content and message. This practice also sets up the framework for ISPs to prefer their own services. The purpose of the telecommunication is to speedily pass communication; slowing down P2P applications does just the opposite.
  2. P2P traffic management is unacceptable. Only peak period traffic amounts to congestion. Targeting P2Pis not in line with the Act. The CRTC cannot be swayed by ISPs' speculation that one day they won't be able to meet demand with provisioning.
  3. The CRTC must provide a principled framework to guide ISPs in the future. The CRTC should interfere in ISP practices only where it is clear that the market forces can't realize the policy, or ss. 27(2) and 36 are taken into account by an ISP.


Questions:

Chair -
When the ISP sells to the wholesale customer, and there's congestion there, will the provider be affected.
CDM -
It's not a yes or no, it can happen or it might not, it depends on the service the wholesale retailer is giving to the wholesale customer. If the wholesale customers are using more capacity than they had agreed upon, it will degrade their network, and this can have upstream effects. Because the business arrangement might not amount to user capacity, we can run into problems. The best solution would be to have a notification process whereby the wholesaler will approach the customer that they are overusing, and will either increase their capacity or will ask their customers to pay more etc… The issue is solved by business arrangements, not ITMPs.

Chair -
So any application based throttling is unacceptable? I'm not going to make any a priori decisions about what kinds of applications or practices are acceptable or not.
CDM -
Using application throttling is always offside, that's going to be overbroad. There can be many sources of congestion and application-based throttling will have negative downstream effects.

Commissioner Denton -
Some of the criteria developed in the Internet Engineering Task Force (IETF) might be helpful guides here. Is that possible?
Dr. Reed -
The IETF is good at vetting alternatives, providing a broad set of inputs, but its outputs are not regulatory or standards.  It has a role to play as a technically neutral forum for discussion but it's not ‘king of the Internet.'
St. Arnaud -
This is really a business regulatory issue, not an IETF issue.

Denton -
Can you weigh in on what we've been hearing about the creation of inadequate capacity caused by insufficient competition?
Dr. Odlyzko -
Demand is not growing very rapidly but is comparable to the rate at which technology is improving. Maintaining a steady rate of capital investment can satisfy increases in capacity to meet demand. There's no need to increase the prices to consumers to meet the increase in capacity.

Denton -
If you had a message to leave us with, what is it?
Dr. Reed - forward looking process that doesn't overreact to what's going on, not overreacting serves the Internet well. Go slow and think forward.

Dr. Odlyzko -
Collect data on a continuous basis, say on traffic levels, and don't go contrary to the findings. At this point, there's no evidence for exponential traffic growth like people are predicting if suddenly all video was watched online suddenly and no other media; if you assess rates of growth for previous technologies too, there's no need for a priori traffic controlling over capacity increasing. I was surprised in my findings to see traffic growth slowing down recently.

St. Arnaud -
The concern is not to fight yesterday's war by targeting P2P. The early adopters are going to be the big users of a new market opportunity. We need to encourage this kind of business development, not slow it down.

Commissioner Katz -
Universities in general consume high bandwidth. What are universities doing to meet their infrastructure demands?
Dr. Odlyzko -
I can't speak about universities as a whole. But at U of Minnesota, there are rules against piracy, and we have attorneys that deal with constant ‘take-down' notices. They have to discuss personally with the users because it's generally been found to be a legitimate use.


Execulink Telecom

Summary:

  1. There is a need for unique regulation of wholesale different from retail.
  2. The use of ITMP technologies does not raise privacy concerns.
  3. The use of ITMPs are generally acceptable for retailers, but disclosure is needed although not necessarily for technical details.
  4. Applying ITMPs to wholesale Internet traffic is unacceptable.
  5. It is the duty and right of every ISP to manage their network; allowing competitors to dictate or restrict a competitor's network management is asymmetrical, discriminatory and thus in contravention of the Act.

Opening remarks:

Keith Stevens - Chairman of Execulink

Execulink is a small TSP that offers local phone, cable TV, and Internet access. It purchases some wholesale services (as Bell GAS product) and provides some wholesale services; in both capacities it can bring a holistic understanding of the issues to the table today. Wholesale must be defined because it is different when used as an input for a distinct service or for resale. Wholesale is used to refer to services that are a) resold to customer with no transformation; b) services that are transformed to tailor customers' need, used as an input for a specific service. Wholesale, when used as an input, should be regulated.

Issues:

  1. Privacy - TSPs have always had access to customer's private info and ITMP technologies don't raise privacy concerns.
  2. Acceptability of ITMPs- non-technical ITMPs should be the solution of choice. Technical solutions can be helpful.  For retail customers, ITMPs are generally acceptable, but with the ISP disclosure to the customer. For wholesalers, it's different.
  3. Wholesale services - technical solutions when applied to wholesale customers has negative consequences and when combined with the market dominance of DCs, small ISPs are at an undue disadvantage. This is against s. 27(2). These negative consequences have ramifications on the viability of the small ISP businesses.

Questions:

Chair -
Is it possible that wholesale customers cause congestion problems to their retailers?
Stevens -
There's a difference between wholesale and retail that is important here. Wholesale customers buy capacity on volume and speed from the retailer and then the wholesale customer responsibly manages their caps. If the wholesaler is not exceeding these agreements then there is no problem; it's just a contractual agreement both have to uphold. From a retail point of view, if they haven't designed their network to meet their commitments, they have a problem.

Commissioner Molnar -
To what extent are you relying on wholesale facilities rather than your own? Do you use ITMPs on your own network?
Stevens -
It's shifting, now there's more on wholesale but it's shifting to our own. Currently it's roughly 50/50. The mechanisms are there for an attack but they are not being used on our customers yet. We're not even using economic ITMPs like bit caps or anything. Also, we are increasing our capacity just by reinvesting and we've met our demands.

Molnar -
DPI does raise privacy concerns, but your contention is that ITMPs do not raise privacy concerns.
Stevens -
I believe that the current rules and proceedings on privacy are adequate. Privacy concerns on the Internet are no different than telecommunications have dealt with since the telephone.

Molnar -
We've been told by some to prohibit application-based ITMPs.
Stevens -
Some of our customers don't want to download movies, and we could use an ITMP on their package in order to maximize their speed for the services they do want, or for a business person to block gaming etc… But there shouldn't be general restrictions.

Molnar -
You submit that there should be disclosure of ITMPs characteristics but not their technical details. Roks suggested that you need to advertise the throttle speed as well as burstable speed.
Stevens -
With respect to the "up to 25" and are advertising something that is never going to happen, from a network perspective it's very difficult to guarantee speeds. Our customers haven't contracted for volumes. If we did though, there would be a cap.

Molnar -
If there were no ITMPs applied to GAS, could you guarantee that your network users wouldn't compromise others' network integrity?
Stevens -
I can guarantee that we will stay within our contracted volume and speed from Bell. Of course, we all affect each other, but the contracts are there to govern it.

Molnar -
Is there anything particular to the fixed wireless technology that we should know with regards to ITMPs?
Stevens -
Fixed wireless providers have an ability to affect each other more, so you might want to put ITMPs on it before another type. The difference is in the timing of the need for ITMPs.

Commissioner Denton -
You contend that your reinvestment (appreciation rate) is enough to cover the cost of increasing infrastructure capacity, at what rate is it?
Stevens -
The appreciation rates are also relative to how long we think the equipment will last. But yes, it is enough.

Primus Telecommunications Canada Inc.

Summary:

  1. All ISPs should be able to manage their networks and employ ITMPs as they see fit.
  2. All ITMPs are generally acceptable and with consent, there is nothing a priori wrong with them.
  3. If users do not change their habits though, the commercial ITMPs are useless
  4. Primus does not use aggregated information; DPI is only for network management and planning in congested moments

Opening remarks:

Matt Stein - VP of Network Services

Operates as a reseller but makes significant inroads in innovation. They were the first to employ VOIP. They employ a DPI two-part process. First, determine the nature of the traffic to prioritize it and second, classify and prioritize it on the network. When there is no congestion, there is no prioritization even if only for a few minutes. They don't employ application-based throttling, but only during the moments of congestion. Primus is committed to increasing capacity, but ITMPs are necessary and complementary with a holistic approach to network health. ITMPS are only for unexpected surges in traffic. Primus is not a broadcaster, does not produce content nor is it affiliated with content creators.  DPI ITMP is only for network management and not for aggregate information storing, except information on network usage for network planning purposes.

All ISPs should be able to manage their networks and employ ITMPs as they see fit. All ITMPs are generally acceptable and with consent, there's nothing fundamentally wrong about them. If users do not change their habits though, the commercial ITMPs are useless and will lonely result in increased costs. Our customer feedback tells us that our DPI usage is utilized well and in a balanced manner so that their service is as they want.

Primus believes that all ISPs should disclose their ITMPs on both retail and wholesale services, but not about the security related ITMPs. Upstream retailers should be required to notify downstream customers of the ITMPs and detail the foreseen impact on the downstream customer's service. Primus discloses DPI usage in advance, on its Web site. But when Bell used the ITMP without disclosure to Primus, it had a negative impact on Primus' customers and resulted in much dissatisfaction.

Upstream ISPs should not be permitted to impose traffic management practice upon their downstream ISPs as it hinders innovation and precludes the ISP from giving adequate service across regions and customers.

Questions:
Chair -
You don't share the view that the application-based control should never be allowed?
Primus -
It's between an ISP and its end-users. End-users need to have choices, and ITMPs are part of this informed choice. If an application were very highly valued on the network, they should receive priority whatever it is.

Chair - you're a wholesaler provider and customer. As a customer from Bell, should they be able to use ITMP?
Primus -
No, an ITMP should only be allowed between an ISP and its direct customer, an ISP and the end-user. Our direct customers are not customers of Bell it is unacceptable that Bell should affect our direct customers.

Commissioner Katz -
Have you asked Bell for the type of notification you recommend?
Primus -
Yes we have, but we have no answer.

Katz -
So you only apply your own QOS on your own infrastructure?
Primus -
Yes, a customer can pay the same amount of money for the Bell DSL service and the Primus DSL service, and our customers can see a difference between the two, and thus transferred them to the Primus ONNET. The nature of the QOS is how we apply ITMP.

Commissioner Molnar -
As a content provider, you're offering two different experiences for someone streaming and someone downloading a P2P file.
Primus -
People have different experiences of video - streaming begins within a few seconds, but downloading P2P it doesn't begin immediately. Yes, there is a different caliber being offered for these two applications, but the user expects that to be different based on how they work, not because of the ITMP.

Molnar -
An ISP should deliver content, and not compete on what content is available and when moves you from being a communications carrier to a "semi-dumb pipe."
Primus -
We are still building capacity and there isn't a blanket ITMP. We only use the ITMP in a discrete instance and place.

Molnar -
You say you disclose your ITMP. So if I go, what does it explain to each customer? And is it in a way that a customer can understand?
Primus -
We'll include a copy of what's online in our final filing; it was written for the customer to understand and explain why it's good.

Commissioner Lamarre -
You explained that the most popular applications get high priority. This is inevitably going to disadvantage a customer using less popular applications, marginalizing them? And most popular applications begin as marginal ones, don't you see it as counterproductive then?
Primus -
Well, at most times of the day, all applications are flowing just fine; we only use ITMP in discrete instances and not as a blanket on applications. Indeed, new protocols maybe only given ‘normal priority' at moments of congestion, but they will become popular as they are used during other moments when there is no congestion.

Lamarre -
For the customer who disagrees with the implications of the DPI, is there another choice of package or do they have to change carriers?
Primus -
No, there was no other offering.

Lamarre -
Privacy being a personal right, we need to be concerned about this. You say you don't collect the information except for network planning. But the fact remains that with DPI you're "snooping in." Where is the assurance that you did anything else prior to invading privacy?
Primus -
Because of the way we apply it, this is the least invasive on customers' usage of the Internet, which would lead to great dissatisfaction. Because we don't collect information except in aggregate form, we don't feel it's an invasion of privacy.

Molnar -
How difficult is it to change your policy rules on DPI?
Primus -
We spend more time making sure that our rules won't upset our users or affect their usage. If you've deployed it in a varied distribution, rigidly, then you might need to make some changes to the network physically or otherwise. It's all to ensure the customer satisfaction. The overwhelming majority didn't notice that the network was congested at all during the Michael Jackson memorial because of the targeted way our ITMP is deployed.

crtc net neutrality hearings, day four

Day four of the CRTC's network management hearings featured three of the world's leading experts on networks along with a trio of ISP perspectives.  The panelists included the Canadian Association of Internet Providers, CIPPIC on behalf of the Campaign for Democratic Media (CDM) (who brought experts Dr. David Reed, Dr. Andrew Odlyzko, and Bill St. Arnaud), Execulink Telecom, and Primus Telecommunications.

An important theme during the day was debate on whether there really is a network congestion crisis.  CAIP argued that it is competition, not congestion that is at issue.  Odlyzko surprised the Commissioners by noting that traffic growth is actually declining and that a steady rate of capital expenditures should be sufficient to meet demand (this was later confirmed by Execulink). Moreover, St. Arnaud and Reed emphasized the diminishing importance of P2P as a video delivery channel, urging the CRTC not to fight yesterday's war.

The second important development was the clear divide that has emerged on traffic management at the wholesale vs. retail level.  The wholesale issue was at the heart of the CAIP vs. Bell case and that case is effectively being re-argued during these hearings. Many ISPs have argued against any form of traffic management of wholesale traffic, noting that it prevents the potential for competition between providers.  Moreover, in repeated questions about the impact on carrier networks (such as Bell) it is becoming apparent that the problem may lie with Bell, not with the ISPs.  Independent ISPs note that Bell promises certain speeds and bandwidth at the wholesale level, but seemingly has difficulty meeting those promises. Some providers (ie. MTS Allstream) have network architectures that ensure that this is not a problem.  The sense is that Bell does not and so resorts to traffic management practices.  It is noteworthy that CAIP focused very heavily on the wholesale issue and basically abandoned any pretext of protection against traffic management for consumers.

The retail side of the issue has many ISPs arguing that anything should be permitted with appropriate disclosure.  Fighting for some limitations are consumer groups, creator group, Saveournet.ca, and the Open Internet Coalition.  They have proposed a test to determine whether the traffic management practice is permissible under Canadian law. The Commission will ultimately have to decide both (1) the wholesale issue, which may involve an acknowledgement that it got the CAIP decision wrong; and (2) the retail question including disclosure practices and tests (if any) to determine appropriate conduct. 

Today's summary was again compiled by Yael Wexler, a law student at the University of Ottawa.  Other coverage available from the National Post liveblog, CBC.ca and twitter feeds from CIPPIC and me.

Wednesday July 8, 2009
CRTC Network Management Hearings, Day Three: IFTA & CFTPA, CCD & ARCH, ACTRA, MTS Allstream
Day three of the CRTC's network management hearings brought in the views of several additional stakeholders along with the first large telco of the week.  Witnesses included the Independent Film and Television Alliance, the Canadian Film and Television Production Association, Council for Canadians with Disabilities, the ARCH Disability Law Centre ACTRA, and MTS Allstream. While all the creator and producer groups expressed support for net neutrality, it was their position on BitTorrent that was particularly noteworthy.  Perhaps heralding an end to the demonization of file sharing, ACTRA emphasized that it wants to compete with illegal downloading and that the best way to do that is to ensure that its members can use applications like BitTorrent to distribute their content.  In other words, copyright alone won't address their concerns (they added the need for copyright reform) as network management practices that create a level playing field are essential. Meanwhile, the independent producers emphasized the economic potential of BitTorrent-based distribution.  Moreover, ACTRA argued that it was not the role of ISPs to determine the legality of content on their networks.  That position is a far cry from what groups like CRIA would like to see happen. The other big story of the day was MTS Allstream arguing that dominant carriers should never be permitted throttle wholesale services (ie. they argue that any throttling should only occur at the retail level).  This led to repeated discussion about the nature of wholesale services (referred to as GAS or Gateway Access Service) with MTS explaining that wholesale service is not like buying Internet access as a retail customer (it was described as akin to a private virtual network).  For that reason, there is no valid claim that congestion concerns are the basis for throttling wholesale services (left unsaid is why a company like Bell would throttle - competition from the very ISPs to whom it supplies wholesale access).  The discussion was stunning since it left the distinct impression that the Commission did not fully understand what was at issue in the CAIP throttling case. There was two other exchanges involving Commissioner Len Katz worthy of note.  The first was a question in which he suggested that Bell and Rogers do not have a dominant position in Ontario, something that will be news to the overwhelming majority of broadband subscribers in the province.  The second was the recognition that prioritization of content is effectively the same thing as throttling of content since the effect in both instances is to place some content on a fast lane and other content on a slow one. These issues may arise again tomorrow when CAIP appears.  Today's summary was compiled by Yael Wexler, a law student at the University of Ottawa.  Other coverage available from the National Post liveblog, CBC.ca, and the cippic twitter feed (or mine for MTS).

CRTC Net neutrality Hearings – July 8, 2009

CFTPA and IFTA

Summary:
1. Independent producers are important content creators in Canada and the US.
2. The Internet is a necessary tool - sometimes the only tool - for financing, producing and distributing independently produced works.
3. Industry consolidation - the vertical integration of ISPs with production companies - threatens independently produced works with slower distribution in favour of preferential treatment for allied productions. 
4. Network congestion must be more clearly defined.
5. Increasing capacity is the best way to ensure broadband service meets demand
6. Traffic management practices must be disclosed and transparent to the customer.
7. Urge the CRTC to reconsider whether ISPs should be immune from s. 27(2) of the Act

Opening remarks:

John Barrack, National Executive Vice-President Counsel, CFTPA:

Come before the CRTC to share the perspective of independent producers - the content creators - at home and abroad on the worldwide issue of ISP traffic control. Since CAIP v. Bell, the CRTC has taken initiative to develop a unified policy on this matter.  The Alliance asks that the Internet remain a forum of direct, unfettered access to audiences for independent producers, via wireline or wireless.  The Internet is the most efficient distribution method and is necessary for the very viability of Canadian independent production. ISP traffic management practices (ITMPs) create insurmountable barriers for independent producers to monetize their productions. Moreover, ITMPs hinder the innovation of new content-creating (new media) business models and practices. Another concern is that allowing ISPs ITMPs to go unfettered will result in a two-tiered Internet, whereby the big ISPs that are vertically integrated with production companies will give their productions preferential treatment at the expense of independently produced works.

Susan Cleary, vice President and General Counsel of IFTA

Ms. Cleary highlighted the situation in the United States, having first-hand knowledge of the issues there in her role at IFTA. IFTA puts the focus on independent content creators and the vast potential of the online space to finance, produce and distribute content. In many cases, the Internet is the only way for independent producers to work and recover revenues lost in tv, theatrical and DVD sales. The problem for independent producers is industry consolidation - the ISPs are also the cable, radio, newspaper and production company owners. In 2003 only 18% of US primetime was independently produced. Industry consolidation risks preferential treatment and carriage under guise of network management of congestion without a clear idea justification as what that is.  ITMPs such as throttling and packet forging are likely to contravene s. 27(2) and 36. These offer a reasonableness standard for ITMPs, not targeting of specific applications given that they represent the only way to access non-conglomerate productions.

Brad Fox - Producer, Strada Films and Rocket Ace Moving Pictures

New media content-creators can't run the costs and risks required by an 'after-the-fact, case-by-case' basis regulatory approach to traffic throttling. Discriminatory ITMPs are being erroneously portrayed by the ISPs as being in the public's interest when they are not at all. The CRTC should use its powers under s.24 to prohibit discriminatory ITMPs. This would promote competition in the ISP industry and set a straightforward standard for acceptable ITMPs.

Dan Hawes - President and Founder of March Entertainment

There are preferred means of managing traffic. First, increasing capacity is the best way to ensure broadband service meets demand. An inquiry to how US federal spending on national broadband infrastructure has worked leaves Canadians with broadband envy.  The CRTC's call for national digital media strategy can help in this regard. “One of the pillars of any such strategy must be to reclaim Canada's place as a legitimate leader in broadband speed, access, and affordability.” A second option is to increase last-mile capacity and a third is deploying content delivery networks. There are others; they all indicate that there are other solutions to traffic management other than throttling.

Reynolds Mastin - Associate Counsel, CFTPA

Traffic mgmt practices must be disclosed and transparent to the customer. The CRTC should impose notification requirements on ISPs so that consumers can have greater understanding of their Internet service and give them greater control to the service they pay for. We support Score Media's proposal of disclosing the proportion of physical access link that is dedicated to Internet access in order to see if there is ‘fast tracking' of types of files.  Another proposal is for symmetrical regulation of wireless and wireline services, by reconsidering whether ISPs should be immune from s. 27(2) of the Act and including an undue preference/discrimination clause in the New Media Broadcasting Undertakings. CFTPA continues to advocate for the inclusion of ISPs under “broadcast undertakings” and therefore under the purview of the Broadcasting Act.

Questions:

Chair -
The problem with the Alliance's submission is that the CRTC has laws against undue preference. On what basis can we as regulators believe that “throttling” will be a future business strategy ISPs employ knowing it is against the law? I'm not convinced that a condition of license would have better adherence than the same as a provision of the law

Alliance (Reynolds) -
Knowing something is against the law is different from abiding by it, or hedging your bets that a small time producer isn't going to fight a big player ISP on the issue. There is potential for throttling to become the dominant mode of ITMP. If it becomes an established practice, plus the exigencies of filing a complaint under 27(2), could have a damaging impact on independent and emerging producers' ability to get their product to market. The best way to avoid this practice is to include a rule against it as a condition of the license for an ISP to operate.  The difference between having it be a law and a condition of service is the difference between ‘may' and ‘must.'

Chair -
Is it a lie that P2P takes more bandwidth than direct access sites?

Alliance
Comcast decided to throttle all Bit torrent regardless of the content, which they lied about, and then paid people to sit in public hearings about it to contravene the democratic process. The FCC was enraged, and did not fine them, but made them to disclose their throttling practices.

Commissioner Timothy Denton -
How did you come up with the three part test?

Reynolds -
3 stage analysis is common among the people testifying in this proceeding. Whether the practice is reasonable and in the public interest, and it provides a clear lens for reaching a decision.

Denton -
Congestion is the basic problem carriers are trying to deal with?
(Alliance) Barrack -
When an ISP is building up its network, it's economically viable to build it up to full capacity. But when you under-provision, you run the risk of congestion. We recognize the need for flexibility in ISP management, except in this one respect of throttling certain types of carriage.

Denton -
Will this allow for the propagation of obnoxious practices by those who would use the public rules to get around them?
Alliance (John) -
Transparency is the answer. We're not suggesting that publishing is the solution, but it would allow for the opportunity for everyone to know what's going on.
Alliance (Reynolds) -
We need to have an informed consumer. As a general principle, when it comes down to how something is being trafficked, the maximum amount of information disclosed is optimal.

Denton -
A complaints-driven process may be necessary but it might give undue weight to one side.
Alliance (John) -
It's extremely useful to hear the voices of the independent producers who can't afford to carry through the entire legal process. We can learn some of the lessons about solutions from other self-regulating models.

Commissioner Leonard Katz -
Risk of independent producers being squeezed out by ISP gatekeepers vertical integration. What if businesses engaged in transactions between non-aligned producers for preferential treatment, how would that not be any different than vertical integration? Would you be opposed to that?
Alliance (Cleary) -
Independent producers can't find aggregators interested in those kind of transactions, they‘re not interested in one-off productions or even medium sized catalogues. Hulu is the closest we've come to that type of arrangement.
Katz -
So you're issue is broader, you're interested in the way we regard independent productions as people and as an industry?
Alliance (Barrack) -
Yes, but we're most concerned about this democratic forum of the Internet. Wireless devices are indistinguishable.
Katz -
But you acknowledge why wireless has had a more flexible environment.
Alliance (Fox) -
A significant proportion of our audience that we hadn't anticipated are commuters, who use wireless.

Commissioner Suzanne Lamare -
The last mile in wireless access is spectrum management, which is part of the infrastructure. In order to manage traffic, building on infrastructure is a good way to go. But it's much easier to unroll cable than spectrum. So when you talk about the greatest degree possible of symmetrical regulation of wireline and wireless, the regulations aren't the same b/c they have different capacities.
Alliance (Reynolds) -
By maintaining scarcity, it creates content management issues and veils it as capacity issues. Scarcity could be used to the advantage of independent producers.

Lamare -
Is it your opinion that P2P is the way for independent producers to monetize their work?
Alliance (Cleary) -
P2P doesn't equal piracy. You can monetize it, and you don't have to go through an aggregator. We don't advocate it industrially because the practices aren't there yet for great monetizing, but it has potential. When people talk about P2P they think Bit torrent, which sometimes has a negative framing as being unprofitable.


Council of Canadians with Disabilities and ARCH Disability Law Centre (ARCH)

Summary:
1. People with disabilities rely on the Internet to improve their quality of life.
2. Traffic management practices must not be directly or indirectly discriminatory, and should not force people with disabilities to forego on their privacy.
3. ARCH presents its own three-step approach to s.36 disputes.
4. The advantageous programs on the Internet and inventive ways of combining programs are too many to count. Therefore a whitelist approach to obtaining special exemptions or recourse for traffic control of necessary services for disabled people is impractical.

Opening remarks:

We advocate and represent the expansion of the world of accessible technology and software applications. We recommend that the CRTC establish clear guidelines for s.36 against controlling content carriage. However, ARCH welcomes the initiatives only if the guidelines directly make provisions for accessibility that is their legal obligation, just as it is in privacy considerations. We hope the result will provide accessibility without needing the commission's specific direction every step of the way or after-the-fact. ARCH suggests its own three part test for determinations under s.36, but that is different than the Oakes-like test the Open Internet Coalition suggested yesterday. However, ARCH would hold on creating a test for s. 27. If the Oakes-like test is applied to.s27 the CRTC risks undoing years of s.27 jurisprudence.

1. Consideration of whether ITMP is caught under s.36
2. Determination of whether the ITMP practice is contrary to law. This is different from the Oakes test. You are asked to determine if there is a contravention of s.36 by asking, does it amount to unjust discrimination and against the law?

Assessment must be made

3. The practice can be saved if it's found to be neutral or a positive intervention. Then the min impairment test may apply (as suggested by the OIC).

Expert Dr. Gregg Vanderheiden:

People with disabilities are now enjoying a greater lifestyle due to the many services of the Internet. The captioning of non-captioned movies by crowd sourcing, availability of film and entertainment outside of the regular channels of commerce for people with intellectual or social disabilities are just some examples of how the Internet can be used advantageously for disabled people. We're looking for a level playing field, where people with disabilities can use programs without needing to register them as ‘special' or name themselves. 

Traffic management needs to be non-discriminatory. ISPS that require that consumers use specific programs rather than those of their choosing precluded people w/ disabilities from finding the programs that are best for their circumstances. Users must be free to use any combination of programs -whether it's preferred by the ISP or not - so that they can use the Internet freely and to better their lives like everyone else.

Whitelisting is not a solution - it would be impractical because of the tailoring to individual's needs. Also, it's not that these people are using alternative programs, it's that they're using mainstream programs in a different ways in order to accommodate their needs. Whitelisting also can be used to target people for marketing, or discriminated against for employment, insurance purposes, which the individuals do not want.

People with disabilities do not require significantly larger bandwidth, but it may be needed in some areas. For ex: phone calls, lower bandwidth for talking than for video with sign language, so it would require higher bandwidth. However, both of these are nothing compared to an HD movie. But if an ISP decides that the audio is important but not the video, it affects people with disabilities. Disclosure of ITMPs is critical for people with disabilities. Accordingly, the CRTC must not take a wait and see approach and trouble shoot problems only after occur.

Questions:

Chair -
You're saying that when private information exists, the ISPs will use it in wrong ways, for marketing for instance. But there is no grounding for an assumption that the ISP will give out private info to marketers about people with disabilities.

ARCH -
Well, when things are vertically integrated, like they are in the US, the ISPs can misuse their customer information in a manner that violated privacy. ID fraud happens all the time - once you're in databases with specific personal info is out there, it is out there and you're vulnerable to targeting. There is information harvesting done from sources of information.  Our concern is with whitelisting. For the ISP to take that information for service provision purposes, the ISP is doing more than just being a pipeline, it advertises and directs users to a server with advertising. It is a common practice for ISPs to direct specific advertising.

Commissioner Leonard Katz -
Self identification levels the playing field and helps people with disabilities. But you're saying that whitelisting won't work. So what will work?
ARCH - -
If barriers to accessibility on the Internet are broken down, and the creation of software applications continues, then we'll get to a place where one won't need to self identify as disabled. If the CRTC does this right, people won't need to declare and forego on their privacy. We're not saying that if you want a discount, you shouldn't have to self identify, but just for disabled people to get the regular service, at the regular price, shouldn't demand self-identification.

Katz -
If the CRTC was going to look into getting special rates for people with disabilities, how much that would cost?
ARCH -
The amount is minimal because for instance, the cost of having captions doesn't increase even if bandwidth does, it's a standard price. The Internet provides the option of not needing extra costs like other telecoms need. The Internet gives us the option for multiple types of communication at once; if we are able to use the Internet without barriers, there is the potential for no extra costs and time for people with disabilities.

Alliance of Canadian Cinema, Television and Radio Artists (ACTRA)

Summary:
1. ISPs giving undue preference to their content threatens the content creators' ability to reach audiences
2. Traffic throttling is an abuse of power by the ISPs
3. ITMPs are against the Telecommunications Act and moreover, ISPs should be governed by the Broadcasting Act.
4. ITMPs should be a temporary solution, the need for which should be publicly justified as it happens by the ISPs

Opening remarks

Ferne Downey - National President

Canadian artists do not want the CRTC to hand over the keys of the Internet to Canadian ISPs. We help create the content, and so we're worried about Internet traffic management. More Canadians are using the Internet to access our work. About 70% of Canadian Internet usage is for AV files, and the Internet is helping us to compete in local and international markets. 

Two specific concerns:
1. The risk of ISPs giving undue preference to  content they own: The ability of the Internet to provide open access is threatened if ISPs can give preference to their own content.
2. The potential of ISPs to slow down Internet traffic - to abuse their power as gatekeepers: Vertical media integration is a threat to diversity and the same is true for ISPs.

Stephen Waddell - National Executive Director

P2P like BitTorrent (BT) receive undue criticism by the ISPs as a scapegoat to traffic control. BT is the standard for distributing large files, for legitimate copyright holders (even CBC used it to distribute “Canada's Next Great PM”).  ACTRA is not endorsing illegal file sharing, but it's not the job of ISPs to determine the legality of files going through their networks. Therefore, ITMP is against the Telecommunications Act. Moreover, we ask that the CRTC reconsider its jurisdiction over ISPs under the Broadcasting Act.

Traffic  management should be only to avoid serious problem and a temporary solution to them.
The CRTC should regulate it according to the following principles:

1. Onus should be on ISPs to prove they need to manage traffic to manage the integrity of the system
2. ISPs must fully disclose what types of traffic mgmt practices they are using and when
3. There should be no discrimination as between wholesale and retail clients
4. There should be no discrimination as between end users
5. There should be no differential treatment between different applications of content
6. The only exceptions to these principles would be the ability for ISPs to give preferential access to any emergency service authorized by public authorities.

Questions:

Chair -
This is a utopian picture you're painting. The fact is that there's more usage than their pipes, just like cars and we have to make regulations and discriminate fairly. So how can you come here and say that there should be no throttling or controlling? Presumably, ISPs are doing the best they can, after all, they're business people who want to satisfy their customers. We clearly have more demand than capacity.

ACTRA (Waddell answered all the questions) -
It is utopian indeed. ISPs who are making significant profits should reinvest in their own system, their own infrastructure.  ACTRA had no hard evidence to present to the Chair when he asked for evidence of self-preferences occurring contrary to the law.

Chair -
In terms of p2p, is your industry a heavier user of p2p than others? Will ITMP hurt Canadian film industry harder than anybody else?
ACTRA - 
Yes. Since the Canadian AV industry relies on P2P heavily.


MTS Allstream

Summary:

1. Competition in the market should be promoted because that would obviate the need for regulation or traffic controlling
2. ITMPs should never be imposed on a wholesaler from the dominant carrier. ITMPs should only be in a retail context.
3. The CRTC should implement a case-by-case approach to assessing and justifying ITMPs.

Opening remarks:
Theresa Griffin-Muir - VP, Regulatory Affairs
Kelvin Shepherd- President of the consumer market division
Paul Frizado - Chief Information and Technology Officer

Principles:
1. Competition in the market should be promoted b/c it has a direct impact on the need regulation. The UK example illustrates our point that the more competition, the less need for Internet neutrality regulation, like in the UK.  Each ISP can decide how best to manage its own practice and consumers can choose among them.
2. No ITMPs other than normal network management should ever be imposed by a dominant carrier on wholesale access customers. Wholesale access customers should be able to decide their own practices subject only to the CRTC, and if the dominant carrier oversteps their boundaries, the CRTC should step in. Bell's contention that they can't identify if the traffic is being controlled by their users or a wholesalers is a red herring and isn't true.
3. The CRTC should take a pragmatic, case-by-case approach to assessing the use of ITMPs. Not every control will be problematic. For example, with spamming, ITMPs are considered reasonable. The reasonableness of other measures might be judged by assessing whether such arrangements are applied to all content providers.

Paul Frizado -
How should ISPs deal with congestion? Regardless of the view on traffic, the best approach to network management is the same:

1. Network planning and engineering
2. Compliance with laws of general application
3. Measures that are agnostic in the their treatment of content
4. ‘CAP' based measures - content application protocol based on latency of an application, blocking, expediting, throttling, Deep packet inspection (DPI).

Are CAP measures necessary? Yes, in some cases. The debate around DPI has become inflammatory for nothing. It's just one tool among many for a larger network management strategy, and the large ISPs have been saying this. It would be a mistake to attempt to regulate Internet technology.  The solution is a marketplace where there is enough competition to provide their users differential retail options which would mitigate the issues around net neutrality and customer satisfaction.

Questions:

Chair -
You explain that traffic shaping should only apply in the retail, not wholesale, context. Won't you get congestion then? Don't you need wholesale ITMP?
MTS (Frizado)  -
Once it's sold to a wholesaler, it's out of the dominant carrier's network. We're not buying Internet access like a retailer. Bell's diagram shows that they can identify the different traffic, even prior to DPI equipment was invented.

Chair -
Are there economic decisions that motivate Bell or a dominant carrier to traffic control usage not on their networks?
MTS -
Not that we know.

Commissioner Lamarre -
In category 1, do you really mean infrastructure building?
MTS (Frizado) -
Yes. The one exception is some types of filtering like anti-virus and measures to prevent denial of service attacks are considered category 1.

Lamarre
Do you demonstrate to your customers the due diligence you took in determining that category  1 techniques have been applied before others?
MTS (Shepherd) -
Category 3 measures are legitimate starting points, and where services are defined around the speed of the Internet, you start with cat. 1, but cat. 3 and 4 come into play when you want to increase the quality of service being offered to customers. So they can be employed to ensure the performance and the network to end users. So the answer isn't to apply cat 1 techniques first all the time, because cat. 3 and 4 do play an important part.

Lamarre -
Do you really need to go to cat. 4 prioritization ever?
MTS (Frizado) -
Yes for reasonable quality of service. It's not always possible to anticipate traffic surges on the network, like the Michael Jackson funeral. Traffic management was necessary because it's unpredictable. Predictable issues on the network warrant the cat. 1.

Lamarre -
In justifying a discriminatory infringement of 27(2), you mentioned that the consent from the user is an element that could help the CRTC to determine whether or not the measure was just. How do you reconcile these?  Being an informed consumer is one thing, but whether or not the consumer has been informed and even consented doesn't make it just. Our market isn't such that if I have a contract for three years, and you disclose something to me about network management and I'm faced with a choice of breaking the contract, at a cost, and finding another network, at a cost, there's nothing just about it. We don't have a market with so much choice and ease of movement between them.
MTS (Griffin-Muir )  -
Once you've transparently disclosed the practice and the customer has consented (as against another ISP who doesn't disclose) then it is just.  We advocate for more competition in the market. Consent is only one factor, as is the degree of choice. There's legislation around privacy and we would have to be compliant with it and couldn't force a customer into consent simply because they have no other choice of ISP. Explicit consent for marketing, let's say, doesn't seem problematic to us.

Lamarre -
Dominant, as in “dominant supplier,” is a relative term. For instance, MTS is the dominant player in Manitoba. So when you're on the dominant side of the coin, do you agree to act accordingly to the rules you've put forward today?
MTS (Griffin-Muir) -
Yes.

Commissioner Katz -
Can you tell us whether there are ITMP employed by British Telecom. All the competition is on a retail basis, buying space from British Telecom.
MTS (Griffin-Muir) -
British Telecom is on a retail basis; it doesn't do ITMP on a wholesale basis.

Katz -
Can you clarify what you mean by exclusive content to end users?
MTS (Shepherd) -
There are customers who want quality of service agreements for their service which is possible to get into.  If you throttle everybody else for someone, as opposed creating agreements, there is a difference in what you're doing. If it's exclusive, there's potentially a discriminatory element that may exist. You have to assess whether the arrangement is being offered to all application providers, the competitiveness in the market.  This is an emerging area and it's not something that has been implemented in the market yet. Offering those applications might require a performance in capacity more than what is available.

Commissioner Candice Molnar -
If there is no traffic management on the wholesale service, as the wholesale customer, can you provide guarantees that the GAS customer would have no impact on the underlying network, even if all cat. 2/3 was pulled off of that service. If all traffic mgmt was removed from GAS as a wholesale customer of that product, you can guarantee the incumbent that their service wouldn't be affected.
Shepherd -
Yes. Unaffected.  Requires that the services you're using have the capacity. Congestion hits where multiple slams hit the Internet access piece.

Molnar -
Are there any concerns particular for the business market which you serve? Ex: SME's use the Internet for debit cards in rural areas, lottery terminals.
MTS (Griffin-Muir)-
No, there's nothing specific. SME's look very much like consumers in the applications they're using. Typically, large businesses aren't using the public Internet for large applications. 

Commissioner Denton -
You're saying it's on the retail service provider to engage in traffic management? Yesterday they were talking about the need between the retailer to signal the wholesaler on its traffic management.
MTS (Frizado) -
That was to indicate that congestion is going on. That's a plan for the future, but not something now.

Denton -
How is your four-part classification to be implemented, if the CRTC were to accept the proposals?
MTS (Griffin-Muir)  -
If you accept that beyond cat.1 generally speaking there is no need to go further, if there is sufficient competition in the retail industry, our suggested measures could be adopted. Anything beyond that would go to the CRTC if it were allegedly discriminatory. But the CRTC shouldn't be telling us that we can't use certain types of tech  like DPI.

Denton -
The complaint is that smaller players can't keep coming to the CRTC to deal with issues. So in order to do something preventative, what would you do? We want to know about how you would implement your own suggestions.
MTS (Griffin-Muir) -
We would still have it be case by case dispute resolution, but we will submit a more detailed plan in the final submissions.

crtc network management hearings, day three

Day three of the CRTC's network management hearings brought in the views of several additional stakeholders along with the first large telco of the week.  Witnesses included the Independent Film and Television Alliance, the Canadian Film and Television Production Association, Council for Canadians with Disabilities, the ARCH Disability Law Centre ACTRA, and MTS Allstream.

While all the creator and producer groups expressed support for net neutrality, it was their position on BitTorrent that was particularly noteworthy.  Perhaps heralding an end to the demonization of file sharing, ACTRA emphasized that it wants to compete with illegal downloading and that the best way to do that is to ensure that its members can use applications like BitTorrent to distribute their content.  In other words, copyright alone won't address their concerns (they added the need for copyright reform) as network management practices that create a level playing field are essential. Meanwhile, the independent producers emphasized the economic potential of BitTorrent-based distribution.  Moreover, ACTRA argued that it was not the role of ISPs to determine the legality of content on their networks.  That position is a far cry from what groups like CRIA would like to see happen.

The other big story of the day was MTS Allstream arguing that dominant carriers should never be permitted throttle wholesale services (ie. they argue that any throttling should only occur at the retail level).  This led to repeated discussion about the nature of wholesale services (referred to as GAS or Gateway Access Service) with MTS explaining that wholesale service is not like buying Internet access as a retail customer (it was described as akin to a private virtual network).  For that reason, there is no valid claim that congestion concerns are the basis for throttling wholesale services (left unsaid is why a company like Bell would throttle - competition from the very ISPs to whom it supplies wholesale access).  The discussion was stunning since it left the distinct impression that the Commission did not fully understand what was at issue in the CAIP throttling case.

There was two other exchanges involving Commissioner Len Katz worthy of note.  The first was a question in which he suggested that Bell and Rogers do not have a dominant position in Ontario, something that will be news to the overwhelming majority of broadband subscribers in the province.  The second was the recognition that prioritization of content is effectively the same thing as throttling of content since the effect in both instances is to place some content on a fast lane and other content on a slow one.

These issues may arise again tomorrow when CAIP appears.  Today's summary was compiled by Yael Wexler, a law student at the University of Ottawa.  Other coverage available from the National Post liveblog, CBC.ca, and the cippic twitter feed (or mine for MTS).

Tuesday July 7, 2009
CRTC Network Management Hearings, Day Two: Open Internet Coalition, Zip.ca, CISP, Roks, Mezei
Day two of the CRTC network management hearing featured some great presentations from the Open Internet Coalition, Zip.ca, CISP, and two knowledgeable individuals - Jean-Francois Mezei and Jason Roks.  The presenters had some strong words about the lack of Canadian competition for high-speed Internet service, the debatable claims about the impact of P2P on congestion, and the overstated advertising claims.  Unfortunately, it would appear once again that the Commission has accepted the ISP claims regarding congestion and network costs, leaving the panelists with the challenge of overcoming those basic assumptions. That said, the day featured some startling revelations including Zip.ca's Rob Hall stating that it is currently cheaper to spend hundreds of thousands of dollars on postage to send DVDs via the mail, rather than distributing the same content electronically through the Internet given the bandwidth costs.  Moreover, Jason Roks emphasized peering arrangements, where he stated that Bell is the only major Canadian ISP that refuses to peer with anyone else. Potential solutions to come out of the day included: 1.   Establishing a test for acceptable traffic management.  The OIC three-part test focused on whether the traffic management furthers a pressing and substantial objective; is narrowly tailored to the objective; and is the least restrictive means of achieving the objective. 2.   Truth in advertising.  Emphasis on disclosure as well as possible limits on over-subscription. 3.   Regulated peering to bring greater efficiences into the Canadian Internet. 4.   Strong anti-competitive action to stop any attempts to leverage network management or pricing plans for unfair advantage. Full report on the day's proceedings are posted below, again thanks to Frances Munn.  Additional coverage from the National Post liveblog, CBC.ca, and CIPPIC's twitter feed.

CRTC Net Neutrality Hearings: July 7, 2009

Open Internet Coalition

Opening Remarks: Jacob Glick, Google's Canada Policy Counsel

The Open Internet Coalition described their main purpose as working to keep the Internet fast, open, and available to everyone. In their submission, they made four main arguments:

1. Open Internet drives innovation.
They argued that robust access to an open Internet is important to public policy. They urged the Commission to act in a way that promotes the development of an open Internet since it is a key economic engine.

2. Practices that undermine the Internet's openness are bad for innovation.
The Coalition argued that application specific traffic management practices make the Internet less attractive to users. They pointed out that slower applications will change user behaviour and undermine the Internet's competitive market in applications.

3. It is okay to manage some internet traffic.
They argued that some traffic management is normal and okay. As the Internet has moved towards a greater multimedia format overtime, congestion has become a greater problem. However, they emphasized that increased capacity has been the primary means of dealing with this evolution in the past.

4. Acceptable traffic management will pass the light-touch test derived from the interpretation of s. 27(2) and 36 of the Telecommunications Act.
They distinguished between useful traffic management and traffic management that discriminates. They claimed that evidence shows that carriers can manage their networks, reduce congestion, and keep the Internet open at the same time.

After noting that they believed discrimination between applications constituted discrimination under s. 27, they went on to explain their three-part “test” derived from s. 27 and s. 36 of the Telecommunications Act:

1. Does the traffic management practice further a pressing and substantial objective?
2. Is the traffic management traffic narrowly tailored to address the objective?
3. Is the traffic management practice the least restrictive means to reach the objective?

The Coalition argued that a debilitating network could be a substantial and pressing objective. However, they pointed out that the evidence in this proceeding has not established the existence of debilitating network congestion. They also expressed doubt that applications like BitTorrent and P2P "exploit" the Internet.

Addressing step two of the test, they argued that throttling is almost never narrowly tailored. Further, they argued that throttling has negative effects on innovation and that there are better means of lessening congestion.

For the third arm of the test, they argued in favour of techniques that were more effective at reducing congestion and that did not discriminate between applications. For the foremost alternative, they pointed to increased network capacity. They also pointed to application-neutral and price-based levers.

Questions

Von Finckenstein opened the questions, asking the Open Internet Coalition to describe how they defined "openness." In response, the Coalition described "openness" as an Internet where users are free to engage with the World Wide Web and where application creators have the freedom to make new applications without having to go through a gatekeeper.

Finckenstein went on to address their three-part test, comparing it to the Oakes test. He asked what constituted a "pressing" and "substantial" objective. The Open Internet Coalition replied that the test was flexible and served as a guideline. They argued that its main strength was that it could be applied on a case-by-case basis. However, they admitted that it was ultimately a value judgement. They went on to point out that there should be a higher standard applied to a practice that discriminates between applications than one that is application neutral.

Timothy Denton continued with the questioning. He wanted to know what kind of system they imagined for the application of their test - e.g. whether they envisioned a complaint based system. The Open Internet Coalition replied that they wanted the players to first know the rules of the game and, further, that they would have to seek specific exemptions. They went on to say that in other contexts, there could be complaints to the Commission on a case-to-case basis.

Denton asked for their view on price-based systems and the utility of a price-based system to alleviate congestion. In response, the Open Internet Coalition said they saw a variety of price based systems developing in the future. In addition, they expressed concern that price-based systems might have unintended consequences such as discouraging Internet use overall. However, they said that the Commission's role was to continue to promote competition, not to regulate fees.

Denton then asked whether their proposal to increase network capacity was an optimal solution. In response, the Coalition pointed out that increasing network capacity is key to the history of the Internet. In the past, increasing Internet capacity has encouraged innovation, leading to a win-win "virtuous circle." They cited an Internet2 study that demonstrated that adding capacity was a more beneficial way to deal with increased activity than managing the network. In addition, they pointed out that some traffic management was desirable as long as it satisfied their three-part test.

Denton asked about the future, wondering if the CRTC would be dealing with the traffic management controls on an ongoing basis or whether it would be a permanent part of their work. The Coalition responded that if clear guidelines were developed, the Commission would not be overburdened with requests. Further, they pointed to past experience where there have been periods of time with greater congestion. They claimed it would be an overreaction to allow the networks to control scarcity. Instead, policies should be developed that are aimed at increasing capacity and promoting innovation.

Leonard Katz took over the questioning and asked about the goal of increasing capacity. He wanted to know how increasing capacity benefits shareholders in a market based economy. While he accepted the argument that it might lead to innovation, he was concerned that it would lead to greater costs for shareholders. In response, the Coalition pointed to a U.S. study that showed that costs have gone down in telecommunications but that prices have gone on. They implied that prices were based on market power rather than costs. Further, they argued that if increasing prices were necessary for more innovation, it was worth the trade-off.

Katz pressed them for evidence that consumers were willing to pay more for an open Internet. The Coalition said they had no studies or statistics either way, but maintained that consumers wanted open access to the Internet and they pointed to the millions of consumers who have joined their coalition. Further, the Coalition disagreed with the premise that the only available traffic management techniques were those that discriminated among applications. As well, while they thought added capacity was a better alternative, they were not asking the Commission to mandate it - it should be open to the providers with incentives.

Molnar took over the questioning, asking about the "virtuous circle" between increased capacity and the consumer. She wanted to know whether there were any obligations for an application maker to create an application in an efficient manner.  In response, the Coalition pointed out that there was a highly competitive market in the application sphere and that creators face pressures from users to provide fast applications. Molnar went on to wonder if P2P is an inefficient use of bandwidth. The Coalition replied that it serves no one to have a congested network. Consequently, there is a built in incentive to reduce congestion.

Molnar asked about this built in "incentive" for application providers to be efficient. The Open Internet Coalition replied that users would avoid network congesting applications and instead seek applications that did not cause congestion. Further, if the application is causing congestion, it is due to high user demand for the application. Consequently, the question is one of dealing with user demand. They argued in favour of methods that did not arbitrarily discriminate among applications for dealing with user demand.

Von Finckenstein wondered if it would be just to use application discrimination in a congested Internet if there was no other choice. The Coalition did admit that under their test, application discrimination would be a last result, but could be used if there was no other choice.

Molnar finished her questions by asking about technologies that allow the consumers - rather than the provider - to choose their applications. The Coalition responded that having the consumers in charge of their own Internet was one way of dealing with the congestion problem. They argued that the service provided by the Internet is set by the consumer. That is, the user should control the packets of the Internet and that putting the consumer in charge was consistent with that.

Lamarre asked how privacy can be preserved on an open Internet. The Coalition responded that in the Canadian context, privacy is preserved through private sector incentives. They claimed that Canada is further along in terms of privacy than in the United States. In addition, they pointed out that an open Internet is still subject to law. That is, applications created on the Internet would be subject to Canadian privacy laws.

Zip.ca

Zip.ca opened their submission by arguing that it was difficult to set universal rules because there had to be some way of looking at individual practices. Further, they encouraged the CRTC to find a way to identify infractions and settle them quickly. Zip.ca is a DVD delivery company that uses the Internet to stream live video to its customers. As this requires a fair amount of bandwidth, they were particularly concerned with congestion techniques that target applications.

They were also concerned with DPI technology. Since Zip.ca can follow what their viewers watch, they can provide recommendations to their consumers. They worried that their competitors may use DPI technology to do the same thing and thus harm their business.

They also raised the issue of timing. As Zip.ca is a time sensitive business, they expressed concern that rulings could take long periods of times - maybe even years - to be resolved. Such long periods would put their business in danger since they would not be able to deliver to their customers. They encouraged the CRTC to maintain a fast Internet system.

Further, they addressed some of the negative criticisms of BitTorrent, arguing that it is an efficient way of delivering content to customers. As such, BitTorrent can be used in legitimate ways and application discrimination would hinder this delivering ability.  They were also concerned about the idea of "walled gardens." Since much of their content is streamed from the U.S., such a policy could harm their business.  Finally, they argued that choice should lie with the consumer.

Questions

Von Finckenstein opened the questioning by inquiring into their business model. Zip.ca explained that their system of recommendations differentiated them from video on demand. They said they offer a system similar to a DVD delivering system, but that content is downloaded from the Internet rather than received by mail.

Von Finckenstein expressed concern about Zip.ca as a third party being carried over the Internet and using a network such as Bell or Rogers. In response, Zip.ca disagreed with the idea that big carriers should have the right to give their own applications priority over theirs. Zip.ca argued that they carried the same service as a big network and that it was an unfair business practice for providers to favour their own services. They argued that rules to manage network traffic should not exempt the applications belonging to the carrier. They argued that throttling based on caps could also lead to the same unfair business practice. While they said that volume caps make the most sense, they could be problematic if carriers could throttle outside applications like Zip.ca while allowing their own applications through unhindered.

Lamarre asked about the size of the bandwidth that Zip.ca would need to download movies to their customers. Zip.ca replied that it depended on the size of the resolution and that with new compression technologies, they can deliver movies for under 1G. They said they were concerned that bandwidth caps would be set just below what they could deliver a movie for.

Lamarre inquired into the cost of changing the delivery system from mail to the Internet. In response, Zip.ca said that it costs more to deliver a video through the Internet than through the post. They hoped that it would be cheaper in the long-run, but that with higher resolutions coming out, it is currently more expensive.

Denton asked about the cost of delivering movies by mail. Zip.ca replied that it was about a dollar each way plus some handling fees. They reiterated that with bandwidth costs, it was still more expensive to deliver movies over the Internet.

Coalition of Internet Service Providers

They opened by expressing concern over the use of DPIs but arguing that Internet Protocol flow management is in the public interest. They made three key points:

1. Encryption

They argued that when encryption is used for security reasons, it makes DPI inspection impossible and leads to congestion. Moreover, if ISPs could detect encrypted traffic, the encryption would be no good and quickly replaced by a stronger one. They went on to argue that it only takes a small percent of users engaged in P2P traffic to congest the network. Further, they argued that if they remain encrypted, there is no evidence that throttling will be able to reduce congestion.

2. Congestion Signaling

They argued that if there was a way for ISPs to signal to applications that their network is congested, the application would slow down or desist. They pointed to the work of Dr. Lawrence Roberts who advocated a system of flow management. Under this system, technology signals the presence of congestion by selectively dropping IP packets to slow down the system.

In addition, they criticized the current system of measuring gigabytes per month as arbitrary. Instead they pointed to gigabytes downloaded per hour or per minute as the real problem. They claimed that the Commission took an easy way out in ruling that it was non-discriminatory to set a monthly rate.

3. Wirespeed Aggregation

The Coalition described wirespeed as any device that processes data without reducing the overall transmission rate. In other words, the cable box itself never becomes a choke point. The system would require a big, fat "pipe" that is not congested.

The Coalition compared aggregated DSL to the widening of telephone networks. They argued that changing the architecture is the only way to solve the problem of Internet congestion. They urged the Commission to support wirespeed aggregation because it would lead to a system without traffic management and without discrimination against applications.

Questions

Von Finckenstein pointed out that their presentation was full of jargon and asked for a simple explanation of Dr. Roberts's idea for congestion signalling. In response, the ISP Coalition explained that under the characteristics of P2P, speeds are limited by the speeds of uploads. They argued in favour of pacing the packets so that the system can function properly. However, it would require new technology that can "signal" in times of congestion. The main idea is that after applications are signalled, they slow down.

Von Finckenstein asked if the technology was available today and why it is not being used. In response, the ISP said that while the technology is available, the technology does not work on IP protocol. ISPs would have to make an investment in new technology.

Von Finckenstein wanted to know what would happen if the technology was deployed on a large basis. In response, the Coalition said that the technology would have to be deployed by the ISPs. However, since the technology remains expense, some ISPs would be unwilling to make the investment since they are currently free to engage in traffic shaping. They added that under today's system, network operators have to engage in traffic management because the network is not strong enough to engage in P2P applications.

Panel of Jason Roks and Vaxination Informatique (Jean-Francois Mezei)

Jean-Francois Mezei

Mezei is a self-employed citizen aiming to share his opinion on this issue. He began his presentation by emphasizing how much people depend on Internet for their day-to-day life. He compared it to a utility like electricity where the supplier does not care how much the consumer uses.

He argued that in order to be competitive, a country needs a competitive telecommunications industry. He pointed out that if we don't have a competitive environment in telecommunications, Canadian businesses will leave the country and Canada will come to depend on telecommunications products developed by others.

He claimed that he got involved due to the myth that P2P and BitTorrent file sharing is "bad." He pointed out that when users are limited by speeds - e.g. 5 MB - it is not possible to download eleven times more than other users. 

He argued that the networks have no business saying that P2P unfairly takes up bandwidth. He pointed out that the now defunct Bell store allowed for full 5MB per second downloading without throttling when it used just as much bandwidth as a P2P download.

Further, he argued that P2P is more efficient than Youtube. Since Youtube videos come from one link, P2Ps are more efficient because they can come from several users at the same time. He described this situation as unfair because when it comes to throttling, the networks should look at how much bandwidth is actually being used as opposed to the application itself.

He argued that ISPs did not throttle Youtube because of its popularity. P2P, in comparison, remains an emerging technology. He theorized that carriers are attempting to throttle it before it becomes popular. In comparison, Youtube is putting out HD content that is non-regulated and not throttled. Finally, he argued that P2P is democratic - people can create their own media and distribute it themselves. Youtube, in comparison, can be controlled.

He pointed to the Montreal based VIF Internet system for dealing with heavy users. After hitting 100 GB a month, a customer is given a slower throughput and there is no need for DPI.

He urged companies to stop advertising high speeds that are impossible to reach due to throttling and to instead advertise their true speeds to promote competition.

Jason Roks

Roks started with P2P and BitTorrent. He called BitTorrent a "shipping container" and expressed concern that someone could be blocked just because of the shape of the box. He called it "essentially the same" as any other file sharing application out there. Further, he expressed scepticism at the idea that a technology could be banned, blocked, or hindered and described such methods as stifling innovation. He pointed out that DPI cannot manage encryption, arguing that it is therefore ineffectual. Further, he argued that there was simply no way to stop file sharing and that it would not go away.

He said that there were two options - adopting to the new technology or stifling it. He argued that speeding up torrents is one method of dealing with congestion. Since staying in the queue is what blocks the network, speeding up the queue would get them out of the way.

He said that ISPs were responsible for congestion because it happened on their networks.  He claimed that while ISPs say that changing the system would be a "lot of money," no ISP has ever said exactly how much money it will be. However, using inflated numbers, he claimed that an upgrade would cost them no more than 2 dollars per user per month over the next three years.

He addressed the market ploy that ISPs use to sell higher speeds. He pointed out that on the one hand they sell higher speeds and then turn around and claim that there is too much data in the system. He argued that people now pay a certain amount per month for a speed and that it is unfair for ISPs to charge more - e.g. people pay for 1MB for speed, and should not have to pay extra for using it.

He pointed out that there are two types of bandwidth:

1. Peer Bandwidth: Data that goes amongst the ISP's network and does not cost anything extra. He claimed that it in fact speeds up the network and maintains geographic integrity. He pointed out that Bell is the only major company in Canada that does not peer.

2. Transit Data: A request goes outside the network of an ISP and it costs the ISP money to connect to another network.

In sum, he said there should be no traffic management aside from controlling malicious software. He urged traffic management only in times of congestion and only while the network is being upgraded. He also argued in favour of full disclosure and transparency on the part of the ISP for the end user.

Questions

Von Finckenstein said that he was confused about P2P because other sources he had heard from claimed that it took five times more bandwidth than other applications.  In response, the panel said that P2P remains a tool of early adopters. They pointed out that Youtube videos use as much bandwidth and have even expanded to HD. They also said that focusing only on P2P does not work in the long-run as new technologies will come along. For instance, BitTorrent now uses a new technology that avoids throttling. As such, throttling in itself makes the network inefficient as the targeted application is avoiding it.

Von Finckenstein asked the panel to justify its recommendation that networks should upgrade their system. The panel argued that ISPs are selling customers an insufficient network. They argued that if the ISPs cannot afford to upgrade its system to meet demand, they should not keep subscribing to new consumers.

Leonard Katz addressed the issue of ISPs marketing the service with speeds "up to" a certain point and then delivering speeds that are much lower. He asked the panel if ISPs should instead be advertising a minimum speed. The panel agreed that it is a problem when ISPs advertise high speeds and then claim that they do not have the capacity for it. They urged the Commission to insist that ISPs publish their throttling speed. They explained that if ISPs were forced to advertise it, their throttling speed might go up. They referred to "up to" speeds as "false advertising" since the ISPs cannot deliver it. Further, requiring minimum speeds would provide them with an incentive to upgrade their networks.

Katz asked why ISPs continued to throttle. In response, the panel said that ISPs have targeted P2P in particular for throttling. They pointed out that many of the big companies that also sell television subscriptions are the ones that target P2P. They claimed that the smaller networks - which are not threatened by downloadable television programs - can control their networks and do not complain about congestion.

Katz went on to ask Roks about the evolution of P2P. Roks pointed out that there are many different ways to use P2P and that sharing data is the point of the Internet. He also claimed that many of Bell's throttling practices are unclear. He argued that Bell is being selective and targeting certain P2P applications that perhaps pose a risk to their business. Roks also said that if Bell is going to be allowed to throttle, there should be better disclosure.

Molnar brought up the consumption model where users have to pay for their bandwidth use. She asked if the panel opposed the consumption model. In response, the Panel said that it depended on how it was implemented. They said that the Internet is a utility and that it is fair for users to pay for what they are using. However, they pointed out that people are all ready limited by speed because there is only so much bandwidth a user can access on a specific speed.

Molnar wondered if the consumption model was only useful during the "steady state" model but no longer useful during times of unforeseen peak congestion. She asked if there were any more reasonable technological solutions to managing trafficking. In response, the panel said that there are technologies that can manage usage, e.g. the Montreal VIF model. They pointed out that the Internet was designed to handle congestion and that the majority of users did not notice congestion on a daily basis. They said there should be a balance and that it is reasonable to expect a small amount of congestion.

Von Finckenstein asked about Bell's peering policies. Roks explained that ISPs who share their networks can increase speeds. Bell, in comparison, refuses to peer with anyone which makes the experience less efficient.

crtc network management hearings, day two

Day two of the CRTC network management hearing featured some great presentations from the Open Internet Coalition, Zip.ca, CISP, and two knowledgeable individuals - Jean-Francois Mezei and Jason Roks.  The presenters had some strong words about the lack of Canadian competition for high-speed Internet service, the debatable claims about the impact of P2P on congestion, and the overstated advertising claims.  Unfortunately, it would appear once again that the Commission has accepted the ISP claims regarding congestion and network costs, leaving the panelists with the challenge of overcoming those basic assumptions.

That said, the day featured some startling revelations including Zip.ca's Rob Hall stating that it is currently cheaper to spend hundreds of thousands of dollars on postage to send DVDs via the mail, rather than distributing the same content electronically through the Internet given the bandwidth costs.  Moreover, Jason Roks emphasized peering arrangements, where he stated that Bell is the only major Canadian ISP that refuses to peer with anyone else.

Potential solutions to come out of the day included:

1.   Establishing a test for acceptable traffic management.  The OIC three-part test focused on whether the traffic management furthers a pressing and substantial objective; is narrowly tailored to the objective; and is the least restrictive means of achieving the objective.
2.   Truth in advertising.  Emphasis on disclosure as well as possible limits on over-subscription.
3.   Regulated peering to bring greater efficiences into the Canadian Internet.
4.   Strong anti-competitive action to stop any attempts to leverage network management or pricing plans for unfair advantage.

Full report on the day's proceedings are posted below, again thanks to Frances Munn.  Additional coverage from the National Post liveblog, CBC.ca, and CIPPIC's twitter feed.

Monday July 6, 2009
CRTC Network Management Hearings, Day One: Sandvine, Juniper, Consumer Groups
The first day of the CRTC's network management hearing featured some interesting discussion from deep packet inspection providers Sandvine and Juniper as well as Canadian consumer groups.  A summary of the day, thanks to University of Ottawa student Frances Munn, is posted below.  There is additional coverage from the National Post liveblog, CBC.ca, and lots of posts on Twitter [update: CRTC transcript]. While the Sandvine comment that an unmanaged network is not a neutral network captured the headline, I thought the more important part of the DPI provider discussion was Juniper's focus on consumer-controlled prioritization.  This is not currently available in Canada, but the notion that consumers should choose how to prioritize the bandwidth they pay for would address many concerns. It was the consumer presentation that did the most to link network management to the law and it also highlighted reason for great concern.  I think that the consumer groups rightly focused on who should bear the burden of demonstrating that DPI and other Internet traffic controls are consistent with current Canadian law.  The groups argued that these are prima facie violations of Section 36 of the Telecommunications Act and that the onus therefore should fall on the carriers to show that there is a serious problem, the solution minimally impairs users' rights, and is proportional to the harm. Unfortunately, the questions that followed suggest that the CRTC Commissioners start these hearings having accepted the carriers' claims that congestion is a problem and that inhibiting the use of deep packet inspection could result in increased consumer costs for Internet access.  This suggests that there is a steep mountain to climb in these hearings, leading me to believe that the issue will ultimately be a political one with pressure on the Conservatives to join with the Liberals and NDP in supporting net neutrality.

CRTC Net Neutrality Hearings, July 6, 2009

Sandvine Incorporated

Opening remarks: Don Bowman, Chief Technology Officer

Sandvine is a Canadian company that provides technology for internet service providers.
Their primary argument was that congestion on the internet is inevitable and that an unmanaged network is not a neutral network. Applications that require large amounts of bandwidth can slow down the internet for time-sensitive activities like VoIP and online gaming. As such, they design technologies prioritizes traffic in times of congestion.

They argued that prioritization can serve several legitimate purposes such as scrubbing malicious traffic from networks and guaranteeing quality for emergency transmissions.

Prioritization is done through a variety of ways and through a variety of technologies. As such, Sandvine argued that any new regulations for traffic management would quickly become outdated. For instance, the policies for DSL and Cable would have to differ because DSL is not usually oversubscribed due to upstream use while the opposite is true for Cable.

Part of the problem is the difficulty of predicting networks over time. Congestion occurs during peak times, but peak times cannot always be predicted due to unforeseen events such as Michael Jackson’s death.

Sandvine also cautioned against a policy targeted at disproportionate users of bandwidth. For example, both VoIP and online gaming do not use much bandwidth. However, a policy that targets all disproportionate users would also hurt those using VoIP or other low bandwidth activities. Instead, Sandvine advocated a policy that prioritizes time-sensitive applications that are not bandwidth intensive. Therefore, even in times of congestion, the goal is to maintain their quality.

Sandvine briefly addressed the privacy concerns raised by traffic management. They argued that the technologies do not raise privacy concerns because they do not read content such as email or video. They pointed out that privacy issues depend on how the technology is used rather than the technology itself.

Finally, Sandvine argued that there is an understanding that some traffic management is necessary. However, they argued against the imposition of absolute rules. Since traffic management practices quickly become outdated, they submitted that each traffic management practice be judged individually at a moment in time.

Sandvine finished by implying that regulations were unnecessary. They pointed to the small number of complaints and asked whether anything was broken that required a real-world need for new guidelines.

Questions

CRTC Chair von Finckenstein opened the questions by asking Sandvine to clarify what they meant by traffic management, and how their submission conformed to the objectives of the hearing. In response, Sandvine argued that their submission was based on how to best manage internet traffic to create an equal space for everyone. They claimed their main purpose is to manage congested internet traffic. For instance, their technology will delay a live streaming video if there is a call attempting to go through the network.

Von Finckenstein then asked how voice and gaming can always be prioritized. Sandvine described how VoIP packets are prioritized over other packets. First, a service provider has to identify the VoIP packets. All VoIP packets have similar qualities - they are low packet and use relatively little bandwidth. When given priority, the idea is for the VoIP packets to precede non-voice packets.

Von Finckenstein pointed out that there has been some criticism levelled at congestion remedies and he wanted to know how advanced the technology was. Sandvine said that the technology is improving over time and that Sandvine products are evolving to measure and detect congestion in a simple fashion. Von Finckenstein followed up by inquiring into the cost of investing in these technologies. Sandvine said it depended on the goals of the company. Sandvine is a commercial business out to make a profit and so it designs its technologies to meet the demands of its customers.

Von Finckenstein asked about a system where users are charged extra for the excessive amount of bandwidth they use. Sandvine said that this was an area of active research where the person pays for the amount of network usage they use. However, Sandvine expressed scepticism that monthly usage charging could impact congestion. An economic model that deviates from the simple flat rate 40 dollar/month model would have to have transparent and visible measures of when charges are and are not incurred. Sandvine argued that it could become a powerful model in the long run, but that it would require a change in consumer understanding and acceptance. For the most part, consumers do not have an understanding of the value of a byte, and so shifting to an economic model would require further consumer education.

On the privacy question, Von Finckenstein asked for a simple explanation on why the network requires any information on content to manage traffic. He said he did not understand why they had to look into it or use it. In response, Sandvine claimed to have no interest in the user’s actual content - e.g. "Spiderman" or "a phone call to your niece." Sandvine did say that knowing how many people are engaged in an activity allows the operator to provide a better service.  Sandvine claimed it is useful to know the duration of the session, the amount of bandwidth used, and the number of people engaging in the activity.

Von Finckenstein finished his questioning by asking about the difference between wireless and non-wireless technologies. Sandvine explained that wireless operators suffer from mobility issues. For instance, wireless networks overloaded after Michael Jackson was taken to the hospital. As such, Sandvine admitted that additional tools for wireless technology were likely necessary.

Leonard Katz proceeded with the questioning. He opened by asking whether networks can design their technologies around predictable peaks. Sandvine replied that long-term peaks are predictable, but stressed that events like Michael Jackson or the Olympics lead to congestion at unpredictable non-peak hours.

Leonard Katz then asked how network providers can turn Sandvine products into profits. In response, Sandvine claimed that providers strive to maintain quality for all users. Sandvine products help measure events that lead to diminished capacity so that they can protect users when the internet is congested.

Leonard Katz asked about how much the provider needs to know about his online activities - e.g. when Leonard Katz plays online games. Sandvine said that measures are made in several ways, but that the technology has not reached a point where it can measure how long a single individual is playing a game and how much technology he is using. However, Sandvine said that the technology could be heading that in direction. Theoretically, the user could one day call their network provider and ask how much bandwidth they are using when they do a particular activity.

Katz pointed out that providers advertise their speeds "up to" a certain level when, in reality, the speed level is often below the advertised level. He wanted to know if it would be possible for providers to advertise a service with a minimum guaranteed speed. Sandvine replied that this was "absolutely" possible and that some businesses already had this guaranteed service.

Suzanne Lamarre, the Regional Commissioner for Quebec, opened her questioning by asking for a clarification on "malicious traffic"" and from whose perspective they were defining it. In response, Sandvine claimed that they look at everything from the consumer's perspective - e.g. spam or unsolicited pornography. In addition to being unsolicited, he said that the "malicious" traffic can also have an economic or quality cost to an operator by slowing down the system.

Timothy Denton, the National Commissioner, inquired into the Sandvine position that "an unmanaged network is not a neutral network." In response, Sandvine claimed that when the internet was first created, users were on equal footing. Over time, however, users have become self-interested and use more bandwidth than others. Consequently, an unmanaged internet leads to some users being able to serve their interests at the cost of others.

Juniper Networks

Opening Remarks: Scott Stevens, Vice-President of Technology for Juniper Networks

Juniper focuses on building networks that are fast, reliable and secure. In their submission, they made a differentiation between two methods of traffic controls called "White Listing" and "Black Listing."

White Listing: Users that require a certain amount of "enhanced" treatment on a network. E.g. when it comes to VoIP there is a higher priority given to 911 calls.

Black Listing: Specific users or applications are restricted from using the network. E.g. malicious users that are blocked from accessing the network.

Juniper explained that there are several traffic management tools that can be used for traffic management:

1. Network Level Processing Controls: These refer to how actual packets are controlled over the network. They are "static" in nature and unable to respond to new network requirements.
2. Application Processing Controls (DPI): They are more dynamic and are used for security, to prevent malware and attacks, etc.
3. Policy Management Processing Controls: They create communication links between the network and the customer or application and are used primarily for VoIP and video.

These tools give providers the ability to respond to new applications in dynamic ways. The ability to interact with user experiences gives the network the flexibility to innovate and keep up with the innovation currently occurring in applications today.    

In sum, they stressed that the ability to innovate and to interact with users is key to moving forward. Fifteen years ago, the internet was primarily made up of file transfers and some email. The types of applications running today are fundamentally different than the ones used fifteen years ago. Applications like VoIP, gaming, and live streaming change the network and the way it is delivered to the customer. Consequently, it is important that users are able to interact with the network.

Questions

Von Finckenstein opened by asking how dynamic controls can properly deal with congestion problems. He wondered if, like Sandvine, Juniper believed the technology was still unable to deal with congestion problems. Juniper responded that dealing with congestion can be the "weakest link" because you have to determine where it is and how to deal with it. They stressed that strategies depend on where the congestion occurs.

Candice Molnar, the Regional Commissioner for Manitoba and Saskatchewan, asked about the consumption model as a form of managing traffic. In response, Juniper said that consumption models are useful in dealing with the five percent of "heavy users" that take up 50 percent of internet traffic. However, they added that the consumption model does not help in dealing with unexpected world events. For instance, the internet became congested after Michael Jackson’s death, but such congestion was not a predictable peak. The congestion model is only useful when peaks can be predicted. They also added that most heavy users are not aware that they are heavy users.

Molnar asked about using consumption models to manage all internet traffic on both off peak and peak hours. Juniper argued that part of the problem in the consumption model is that consumers do not understand when peak and off peak hours occur. For instance, consumers understand that phone calls are more expensive during the day. However, consumers do not have such an understanding with regards to IP technology.

Molnar then asked for a clarification of the Black Listing and White Listing methods. Specifically, she inquired about an "open garden" in White Listing application where a user prioritizes certain activities (i.e. live streaming of news). Juniper said that the idea is for a user to signal that they want an application prioritized - e.g. gaming or live streaming. In this way, consumers are able to indicate what applications are most important to them. Further, Juniper pointed out that while it is impossible to guarantee a certain amount of bandwidth, this system could allow providers to guarantee a certain application as an alternative form of a minimum guarantee. For instance, if live streaming of news is guaranteed, another user in the household would find his or her traffic slowed down to guarantee the live streaming. Juniper went on to clarify that while the technology exists, it is not widely deployed.

Juniper pointed out that, in some cases, service providers decide which applications to prioritize. For instance, some providers have publicly stated that VoIP will take priority in times of congestion. However, Juniper argues that this technology is static and that more dynamic options exist such as being able to indicate to the provider what sort of applications are valued to the individual users.

Juniper clarified that while the technology does exist, it has not been deployed in Canada yet. In addition, they also pointed out that prioritizing cannot satisfy everyone. For instance, if Scott Stevens prioritizes live streaming news, his kids will not have a good gaming experience.

Molnar changed the focus to deep packet inspection (DPI). She asked how it can be used to manage traffic - i.e. peer-to-peer downloading. In response, Juniper claimed that it can be used in many different such as for security interests. They called it a "broad" technology beyond regulating peer-to-peer.  

Molnar shifted her question to privacy concerns. She referred to DPI being used to "sniff" out traffic flows by observing what consumers are using and the amount consumed. She asked what the purpose of this monitoring is. In response, Juniper claimed that monitoring was important to the quality of the service. Further, Juniper explained that it is important to identify the high bandwidth users. If congestion is being delivered by a small number of users, taking action on a small number of users benefits everyone. This way, Juniper can respond to a certain number of users rather than everyone at once.

Katz wondered if there were tools available to shift non real-time downloading to reduce congestion in networks. Juniper argued that some consumption based models can shift when downloads are done. However, Juniper pointed out that it does not address unexpected events. It is possible to move people around to deal with predictable problems on a daily basis, but not the unexpected events.

Lamarre finished the questioning by asking at what point the privacy issue becomes a concern when these technologies are sold to their clients. Juniper argued that their focus was not on obtaining information, but to protect users from malicious software.  

Canadian Consumer Groups

The panel described themselves as representing the interests of Canadian consumers. They argued that traffic management should be used to help consumers access the activities they would like over the Internet. They submitted that where there is a conflict between providers and consumers, the priority should be in delivering content to the consumer.

They addressed some of the Commission’s assumptions that it is necessary to violate some of the consumer rights under the Telecommunications Act in order to protect the integrity of the network. Further, they argued that it is up to the providers to justify interfering with the purpose of s. 36, which prevents Canadian carriers from interfering with content except when the Commission approves otherwise.

They argued that all DPI and other Internet traffic controls are prima facie violations of s. 36 and should have to launch individual applications. They went on to argue that none of the ISPs who presented fully explained their DPI levels and how they are carried out. Since such understandings are key to evaluating how content is being impacted, they presented a three-part "test" with the burden of proof on the provider to show that the violation of s. 36 is necessary:

1. There is a serious problem and a pressing need to address it.
2. The solution minimally impairs the user’s rights.
3. The solution is proportional to the harm

Further, if the application is granted, the consumer should be fully informed of the impact on their content rights.

The panel argued that legitimate violations of s. 36 would protect the end users from harmful and unsolicited content such as malware and spam. Further, the guidelines should treat all providers and consumers equally and protect the privacy and security of users.

In Canada, the Commission retains the right to regulate Internet traffic in a way that is not available in the United States. As such, the panel urged them not to give up this authority. In the U.S., Obama and others have indicated their support for net neutrality. In addition, bills have been passed in the U.S. that promote the equality of applications and provide notice to consumers.

The Consumer Groups reiterated that DPIs should only be used to protect users from unsolicited and malicious content. They stressed that it is "totally unacceptable" when DPIs are used for a provider’s financial gain-such as for advertising goals or targeting specific kinds of content.

Finally, the Consumer Groups addressed disclosure. That is, whether the ISP has made its practices known to it costumers. The Consumer Groups argued that such disclosure should be made prominently on the ISP’s website. Bell, for instance, has refused to indicate how its throttling policies are carried out. The Consumer Groups seek information on the time of day when throttling is carried out and whether it could lead to extra billing for customers. They also expressed concern when ISPs claim confidentiality over their DPI practices. They argued that if DPI practices are used solely for trafficking reasons then there is no need for confidentiality.

For their final point, the Consumer Groups addressed privacy. They argued that the policies are "highly invasive" and that DPIs look deeply into packets that reveal what websites are visited and for how long. They argued that this clearly violates the Telecommunications goal of protecting the privacy of users.  ISPs do not get their customer’s permission for this information nor do they make it clear that they are collecting this information.

Questions

Von Finckenstein opened the questioning by asking the Consumer Groups to clarify their position on DPIs and whether they are by themselves a violation of the Telecommunications Act. He wanted to know why it was a privacy violation for ISPs to use DPI technology solely to manage their networks. In response, the Consumer Groups argued that privacy violations occur even when the DPIs are only used to preserve the integrity of the network. Further, they argued that the burden is on the ISPs to show that the congestion justifies the privacy violations. The Consumer Groups argued that unregulated DPI use could lead to abuses of the system.

The Consumer Groups went on to explain that the burden of proof is key. In the United States, the burden is on the carrier to prove that its actions are necessary. In Canada, the Telecommunication Act stipulates that carriers must provide their services without discrimination. Per the Consumer Groups, the problem is that carriers are not fully explaining how and why they are using this technology, which opens the door to possible abuses.

Von Finckenstein argued that he was not prepared to accept that using DPI technology is a violation of privacy in of itself, but moved on with the questioning.

Suzanne Lamarre proceeded with the questioning. She asked about the pricing differentiations in services. The Consumer Groups pointed out that the ability to tailor Internet prices to individual users currently exists. For instance, under this type of scheme, gamers might have to pay an extra 30 dollars a month for service just for being gamers.

Lamarre pointed out that different pricing systems are in itself discriminatory and asked if the Consumer Groups were suggesting that everyone pay the same rate regardless of their usage. In response, the Consumer Groups said it was not unreasonable to charge users extra for using a certain amount of bandwidth (e.g. more than 200). However, they were concerned that that DPI technology might be used to charge users extra based on their activities rather than their actual usage. For example, they pointed out that a gamer could be charged more simply for gaming even though he might not be using more bandwidth than someone who watches Youtube videos.

Lamarre went on to address the five percent "high end" users who use more bandwidth than others. She asked whether it was fair for light users to in effect subsidize their usage. The Consumer Groups reiterated that it was appropriate to charge for usage, but expressed concern that prices would go too high too quickly since ISPs remain an unregulated industry. Further, Lamarre pointed out that it is difficult for users to know how much bandwidth they are actually using, and the Consumer Groups agreed that such information would be helpful for users.

Finally, Lamarre went on to address their three part test, comparing it to the Oakes test. She asked whether s. 36 can be considered a "fundamental right" that deserves a high standard of Oakes protection. The Consumer Groups argued that s. 36 - the right for content to pass without it being observed or changed - is a fundamental right that deserves a high standard of protection.

Katz opened his questioning by pointing out that operators strive to make a profit. He criticized the Consumer Groups for hindering their ability to make money. He argued that without the ability to preserve the integrity of the network, carriers will face higher costs, and consumers will have to pay more. In response, the Consumer Groups claimed they have heard statements from Canadians saying that they would be willing to pay more for unhindered Internet access. However, they doubted that prices would significantly increase in the near future.

Katz pressed the Consumer Groups to recognize that if the carriers’ costs go up, so will the price of Internet usage for consumers.  As a result, demand will decrease and Canada will fall further behind the rest of the world. The Consumer Group responded that they were not trying to create a blanket rule against carriers. They pointed out that they were arguing against unjust discrimination, not no discrimination at all. They said there should be a reason why a provider has to discriminate - such as to avoid prohibitive costs.

The Consumer Groups expressed concern with regards to what DPI practices were doing and the effects they were having. They argued that the reason the burden of proof was so important was because it should fall on the provider to justify their actions. They pointed out that one of the problems with consumption models was the lack of disclosure beforehand to give the consumer the choice to alter their behaviour. The Consumer Groups expressed concern that providers are acting unilaterally and that the public lacks information on what is and is not necessary to protect the integrity of the network.

Timothy Denton’s main concern was the notion that the CRTC should investigate whether or not carriers have made reasonable investments in preventing congestion. He wondered whether the Consumer Groups were taking congestion seriously enough, and he expressed reluctance at second-guessing carriers with regards to the congestion issue. In response, the Consumer Groups argued that DPI is not the only technology available for controlling congestion. They pointed out that Telus is not using DPI and is doing fine. Further, they argued carriers have a requirement to meet the needs of Canadians and to provide a reliable and affordable service. Consequently, the CRTC has a responsibility to look at whether there is some shred of evidence that carriers are addressing their problems. Denton finished his questions by admitting that the Consumer Groups made good points on both issues.

crtc network management hearings, day one

The first day of the CRTC's network management hearing featured some interesting discussion from deep packet inspection providers Sandvine and Juniper as well as Canadian consumer groups.  A summary of the day, thanks to University of Ottawa student Frances Munn, is posted below.  There is additional coverage from the National Post liveblog, CBC.ca, and lots of posts on Twitter [update: CRTC transcript].

While the Sandvine comment that an unmanaged network is not a neutral network captured the headline, I thought the more important part of the DPI provider discussion was Juniper's focus on consumer-controlled prioritization.  This is not currently available in Canada, but the notion that consumers should choose how to prioritize the bandwidth they pay for would address many concerns.

It was the consumer presentation that did the most to link network management to the law and it also highlighted reason for great concern.  I think that the consumer groups rightly focused on who should bear the burden of demonstrating that DPI and other Internet traffic controls are consistent with current Canadian law.  The groups argued that these are prima facie violations of Section 36 of the Telecommunications Act and that the onus therefore should fall on the carriers to show that there is a serious problem, the solution minimally impairs users' rights, and is proportional to the harm.

Unfortunately, the questions that followed suggest that the CRTC Commissioners start these hearings having accepted the carriers' claims that congestion is a problem and that inhibiting the use of deep packet inspection could result in increased consumer costs for Internet access.  This suggests that there is a steep mountain to climb in these hearings, leading me to believe that the issue will ultimately be a political one with pressure on the Conservatives to join with the Liberals and NDP in supporting net neutrality.

Syndicate content