Skip to Content

caip

  • warning: require_once() [function.require-once]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/sites/all/modules/views/includes/handlers.inc on line 77.
  • warning: require_once() [function.require-once]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/sites/all/modules/views/includes/handlers.inc on line 77.
  • warning: require_once() [function.require-once]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/sites/all/modules/views/includes/handlers.inc on line 77.
  • warning: require_once() [function.require-once]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/sites/all/modules/views/includes/handlers.inc on line 77.
  • warning: require_once() [function.require-once]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/sites/all/modules/views/includes/handlers.inc on line 77.
  • warning: require_once() [function.require-once]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/sites/all/modules/views/includes/handlers.inc on line 77.
  • warning: require_once() [function.require-once]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/sites/all/modules/views/includes/handlers.inc on line 77.
  • warning: require_once() [function.require-once]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/sites/all/modules/ctools 3/includes/plugins.inc on line 757.
  • warning: require_once() [function.require-once]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/sites/all/modules/ctools 3/includes/plugins.inc on line 341.
  • warning: require_once() [function.require-once]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/sites/all/modules/ctools 3/includes/plugins.inc on line 757.
  • warning: require_once() [function.require-once]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/sites/all/modules/ctools 3/ctools.module on line 108.
  • warning: require_once() [function.require-once]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/sites/all/modules/views/includes/handlers.inc on line 77.
  • warning: require_once() [function.require-once]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/sites/all/modules/views/includes/handlers.inc on line 77.
  • warning: require_once() [function.require-once]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/sites/all/modules/views/includes/handlers.inc on line 77.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: require_once() [function.require-once]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/sites/all/modules/token/token.module on line 158.
  • warning: require_once() [function.require-once]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/sites/all/modules/token/token.module on line 159.
  • warning: require_once() [function.require-once]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/sites/all/modules/token/token.module on line 161.
  • warning: require_once() [function.require-once]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/sites/all/modules/token/token.module on line 164.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: require_once() [function.require-once]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/sites/all/modules/location/location.module on line 1408.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
  • warning: include() [function.include]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/theme.inc on line 1078.
Wednesday July 7, 2010
Federal Court of Appeal Rules ISPs Not Broadcasters: May Be End of ISP Levy Proposal
The Federal Court of Appeal issued is decision today [not online yet] on whether Internet providers can be considered broadcasters within the context of the Broadcasting Act.  The case is the result of last year's CRTC New Media decision in which many cultural groups called on the Commission to establish an ISP levy to fund Canadian content.  The ISPs argued that such a levy was illegal since they fell under the Telecommunications Act, not the Broadcasting Act.  The cultural groups argued that ISPs should be considered broadcasters in the case of the transmission of video programs.  The CRTC punted the issue to the Federal Court of Appeal. The Federal Court of Appeal sided with the ISPs, ruling that providing access to broadcasting is not the same as broadcasting.  So long as ISPs maintain a content-neutral approach, they fall outside of the Broadcasting Act and should not be expected to play a role in promoting the policies found in the legislation.  The case is a huge win for the ISPs and - subject to an appeal to the Supreme Court of Canada or a legislative change - puts an end to the ISP levy proposal.  The case is also noteworthy from a net neutrality perspective, since the court emphasized that ISPs fall outside the Broadcasting Act so long as they remain content-neutral.  Should ISPs play a more active role, their ability to rely on the broadcast/transmission distinction would be lost.

The court set out the issue as follows:

the issue to be decided is whether, when providing access to the "transmission of programs ...", ISPs are broadcasting. The answer to this question hinges on a consideration of the findings of the CRTC as to how programs are transmitted on the Internet on the one hand, and the exact purport of the definition of the word "broadcasting", on the other.

The conclusion, which relied heavily on the Supreme Court of Canada Tariff 22 decision between SOCAN and the Canadian Association of Internet Providers:

Relying on the logic adopted by Binnie J. in CAIP in construing the word "communicate" under the Copyright Act, I am of the view that the definition of "broadcasting" is also directed at the person who transmits a program and that a person whose sole involvement is to provide the mode of transmission is not transmitting the program and hence, is not "broadcasting".

As for promoting the Broadcasting Act objectives, the court stated:

Because ISPs' sole involvement is to provide the mode of transmission, they have no control or input over the content made available to Internet users by content producers and as a result, they are unable to take any steps to promote the policy described in the Broadcasting Act or its supporting provisions. Only those who "transmit" the "program" can contribute to the policy objectives.

Finally, the comment that puts net neutrality back on the table:

In providing access to "broadcasting", ISPs do not transmit programs. As such, they are not "broadcasting" and therefore they do not come within the definition of "broadcasting undertaking". In so holding, I wish to reiterate as was done in CAIP that this conclusion is based on the content-neutral role of ISPs and would have to be reassessed if this role should change (CAIP, para. 92).

The court set out the issue as follows:

the issue to be decided is whether, when providing access to the "transmission of programs ...", ISPs are broadcasting. The answer to this question hinges on a consideration of the findings of the CRTC as to how programs are transmitted on the Internet on the one hand, and the exact purport of the definition of the word "broadcasting", on the other.

The conclusion, which relied heavily on the Supreme Court of Canada Tariff 22 decision between SOCAN and the Canadian Association of Internet Providers:

Relying on the logic adopted by Binnie J. in CAIP in construing the word "communicate" under the Copyright Act, I am of the view that the definition of "broadcasting" is also directed at the person who transmits a program and that a person whose sole involvement is to provide the mode of transmission is not transmitting the program and hence, is not "broadcasting".

As for promoting the Broadcasting Act objectives, the court stated:

Because ISPs' sole involvement is to provide the mode of transmission, they have no control or input over the content made available to Internet users by content producers and as a result, they are unable to take any steps to promote the policy described in the Broadcasting Act or its supporting provisions. Only those who "transmit" the "program" can contribute to the policy objectives.

Finally, the comment that puts net neutrality back on the table:

In providing access to "broadcasting", ISPs do not transmit programs. As such, they are not "broadcasting" and therefore they do not come within the definition of "broadcasting undertaking". In so holding, I wish to reiterate as was done in CAIP that this conclusion is based on the content-neutral role of ISPs and would have to be reassessed if this role should change (CAIP, para. 92).

federal court on isp as broadcasters

The Federal Court of Appeal issued is decision today [not online yet] on whether Internet providers can be considered broadcasters within the context of the Broadcasting Act.  The case is the result of last year's CRTC New Media decision in which many cultural groups called on the Commission to establish an ISP levy to fund Canadian content.  The ISPs argued that such a levy was illegal since they fell under the Telecommunications Act, not the Broadcasting Act.  The cultural groups argued that ISPs should be considered broadcasters in the case of the transmission of video programs.  The CRTC punted the issue to the Federal Court of Appeal.

The Federal Court of Appeal sided with the ISPs, ruling that providing access to broadcasting is not the same as broadcasting.  So long as ISPs maintain a content-neutral approach, they fall outside of the Broadcasting Act and should not be expected to play a role in promoting the policies found in the legislation.  The case is a huge win for the ISPs and - subject to an appeal to the Supreme Court of Canada or a legislative change - puts an end to the ISP levy proposal.  The case is also noteworthy from a net neutrality perspective, since the court emphasized that ISPs fall outside the Broadcasting Act so long as they remain content-neutral.  Should ISPs play a more active role, their ability to rely on the broadcast/transmission distinction would be lost.

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).

Wednesday July 8, 2009
Did the CRTC Misunderstand the CAIP Throttling Case Against Bell?
Today's CRTC network management hearing featured some stunning discussion on the throttling of wholesale services that undoubtedly left many observers wondering whether the Commission actually understood what it was doing in the CAIP throttling complaint against Bell (CAIP has asked the Commission to reconsider the decision).  The discussion started when MTS Allstream adopted the position that dominant carriers should not be permitted to throttle or traffic shape at the wholesale level.  In other words, any traffic management practices should be limited to the ISP that interacts directly with a customer at the retail level.  MTS argued that the wholesale service (known as GAS or Gateway Access Service) is more like a private virtual network, where the ISP is purchasing capacity.  The GAS is not strictly an Internet service and MTS assured the Commission that the use of the wholesale services should not have a congestion impact on the carrier's retail Internet services. This is relevant since the CAIP complaint involved GAS.  CAIP was concerned that Bell's throttling was being done not to relieve congestion, but rather for competitive reasons.  It believed that Bell was concerned that independent ISPs would offer retail customers non-throttled services (which ISPs like TekSavvy did), which might lead some to consumers to leave Bell (which they began to do).  Of course, this is an illustration of why competition would address many net neutrality concerns (assuming consumers can choose an alternate provider).  Yet Bell's approach was to throttle everyone's service at the retail and wholesale level, so that this form of competition would be eliminated.  And the CRTC, perhaps not even understanding the specifics of the services at issue, let them get away with it.
crtc net neutrality

Today's CRTC network management hearing featured some stunning discussion on the throttling of wholesale services that undoubtedly left many observers wondering whether the Commission actually understood what it was doing in the CAIP throttling complaint against Bell (CAIP has asked the Commission to reconsider the decision).  The discussion started when MTS Allstream adopted the position that dominant carriers should not be permitted to throttle or traffic shape at the wholesale level.  In other words, any traffic management practices should be limited to the ISP that interacts directly with a customer at the retail level.  MTS argued that the wholesale service (known as GAS or Gateway Access Service) is more like a private virtual network, where the ISP is purchasing capacity.  The GAS is not strictly an Internet service and MTS assured the Commission that the use of the wholesale services should not have a congestion impact on the carrier's retail Internet services.

This is relevant since the CAIP complaint involved GAS.  CAIP was concerned that Bell's throttling was being done not to relieve congestion, but rather for competitive reasons.  It believed that Bell was concerned that independent ISPs would offer retail customers non-throttled services (which ISPs like TekSavvy did), which might lead some to consumers to leave Bell (which they began to do).  Of course, this is an illustration of why competition would address many net neutrality concerns (assuming consumers can choose an alternate provider).  Yet Bell's approach was to throttle everyone's service at the retail and wholesale level, so that this form of competition would be eliminated.  And the CRTC, perhaps not even understanding the specifics of the services at issue, let them get away with it.

Thursday May 21, 2009
CAIP Calls on CRTC To Reverse Bell Throttling Decision
The Canadian Association of Internet Providers has filed an application with the CRTC that calls on the Commission to rescind its November 2008 Bell throttling decision. The application alleges multiple errors of fact and law in the decision and points specifically to the CRTC's lack of a full understanding of the issues raised in the proceeding. CAIP argues that the CRTC specifically launched the larger net neutrality proceeding this summer in order to gain that fuller understanding, but argues that A broader proceeding in order to understand the complex issues raised in the CAIP application is a perfectly acceptable and responsible means of developing a thoughtful policy approach and decision on network management. What is entirely unfair and unacceptable, however, is the fact that the Commission rendered Decision 2008-108 without the benefit of a comprehensive understanding of the factual, legal and policy issues at play. In particular, if the Commission did not believe that it had an adequate evidentiary record or did not have a full understanding of the factual and legal issues raised by Bell's throttling of wholesale GAS services to be able to determine in an unqualified and final manner the issues raised in the CAIP proceeding, then it was procedurally unfair for the Commission to have rendered a decision on CAIP's application. Moreover, CAIP highlights a concern raised by many in the net neutrality world - that the CRTC has already decided many of the bigger issues even before the July hearings begin. CAIP notes that:

in effect, the Commission has pre-judged certain factual and legal issues raised in the PN 2008-19 proceeding, thereby narrowing the scope of the Commission's decision in the PN 2008-19 proceeding even before it is made. As long as Decision 2008-108 stands, the perception that the Commission has pre-judged the outcome of PN 2008-19 on the key issue of the legality of CAP-based throttling pursuant to subsection 27(2) and section 36 of the Act will persist.

The application continues with specific examples of error in fact and law.  These include errors in fact on P2P activities and the use of deep packet inspection as well as numerous errors in law, particularly in the way the CRTC interpreted sections 27(2) and 36 of the Telecommunications Act.  The CAIP application comes as a surprise given that most of the attention had moved to this summer's net neutrality hearings and places the CRTC on the defensive just weeks before those hearings are scheduled to take place.

crtc caip appeal

The Canadian Association of Internet Providers has filed an application with the CRTC that calls on the Commission to rescind its November 2008 Bell throttling decision. The application alleges multiple errors of fact and law in the decision and points specifically to the CRTC's lack of a full understanding of the issues raised in the proceeding. CAIP argues that the CRTC specifically launched the larger net neutrality proceeding this summer in order to gain that fuller understanding, but argues that

A broader proceeding in order to understand the complex issues raised in the CAIP application is a perfectly acceptable and responsible means of developing a thoughtful policy approach and decision on network management. What is entirely unfair and unacceptable, however, is the fact that the Commission rendered Decision 2008-108 without the benefit of a comprehensive understanding of the factual, legal and policy issues at play. In particular, if the Commission did not believe that it had an adequate evidentiary record or did not have a full understanding of the factual and legal issues raised by Bell's throttling of wholesale GAS services to be able to determine in an unqualified and final manner the issues raised in the CAIP proceeding, then it was procedurally unfair for the Commission to have rendered a decision on CAIP's application.

Moreover, CAIP highlights a concern raised by many in the net neutrality world - that the CRTC has already decided many of the bigger issues even before the July hearings begin. CAIP notes that:

Monday November 24, 2008
CRTC Decision Not the Final Word On Net Neutrality
My weekly technology law column (Toronto Star version, homepage version) discusses last week's CRTC decision in the CAIP v. Bell case.  Echoing my remarks immediately after the decision, I argue in the column that the decision is not the final word on net neutrality in Canada, but rather the first word on it.
crtc net neutrality decision

My weekly technology law column (Toronto Star version, homepage version) discusses last week's CRTC decision in the CAIP v. Bell case.  Echoing my remarks immediately after the decision, I argue in the column that the decision is not the final word on net neutrality in Canada, but rather the first word on it.

Thursday November 20, 2008
CRTC Denies CAIP Application on Throttling, But Sets Net Neutrality Hearing
This morning, the CRTC issued its much-anticipated ruling in the CAIP v. Bell case, the first major case to test the legality of Internet throttling.  The Commission denied CAIP's application, ruling that Bell treated all of its customers (retail and wholesale) in the same throttled manner.  This points to the challenge in this case - it was not about discriminatory network practices per se, but rather about wholesale shaping in a specific context.  Bell comes out a winner in this round. The Commission found that there was network congestion due to P2P usage and that some network management is required to address it.  Moreover, it rejected the competition concerns noting that there was no evidence that Bell's action had lessened competition and it concluded that reducing speeds does not rise to the level of controlling content. While the CRTC's decision to permit Bell's throttling practices is disappointing in the short term - and seems to place Canada on a different track from the U.S. - the decision is not a total loss for net neutrality supporters as the Commission made a clear commitment to addressing the issue of net neutrality and network management in a formal proceeding in July 2009.  Indeed, it is important not to lose sight of how much has changed in the past year.  Just over one year, I wrote a column noting the need for greater ISP transparency in the wake of Rogers' admission that it engaged in traffic shaping.  At the time, net neutrality was viewed as a fringe issue in Canada without much political traction.  In the span of 13 months, there has been a major CRTC case, a private member's bill on net neutrality, a rally on Parliament Hill, the emergence of BitTorrent as distribution tool for broadcast content, a more vocal business community supporting net neutrality, and a gradual shift of this issue into the political mainstream.  In the United States, the change has been even more dramatic - an FCC ruling on the throttling activities, proposed legislation, the shift of net neutrality to wireless, and a President-elect who has been outspoken on the need to preserve net neutrality. In other words, today's CRTC decision is not the final word on net neutrality in Canada, but rather the first word on it.  The Commission itself has opened the door to broader hearings on the issue next year, which may come alongside the new media hearings that also offer the opportunity to raise net neutrality concerns.  Moreover, if the Commission comes to the conclusion that these practices are consistent with current Canadian law, there is the likelihood of growing calls from within Parliament to change the law. A year ago, the net neutrality debate focused on whether rules were needed. Today, the debate is changing from whether there should rules on network management to what those rules should be.  In fact, the Commission notes that as part of the hearing it "will try to establish the criteria to be used in the event that specific traffic management practices need to be authorized."  There is an emerging consensus on the easy issues -  no content blocking and better transparency of network management practices (the CRTC today required Bell to provide its wholesale customers with advanced notice of its plans).  We are in the early stages of the more difficult questions of what constitutes reasonable network management practices and the opening of a formal proceeding puts those tougher questions squarely on the table. Update: The NDP's Charlie Angus responds.  Coverage from the CBC, Globe, Toronto Star, and Ars Technica.
net neutrality decision

This morning, the CRTC issued its much-anticipated ruling in the CAIP v. Bell case, the first major case to test the legality of Internet throttling.  The Commission denied CAIP's application, ruling that Bell treated all of its customers (retail and wholesale) in the same throttled manner.  This points to the challenge in this case - it was not about discriminatory network practices per se, but rather about wholesale shaping in a specific context. 

Bell comes out a winner in this round. The Commission found that there was network congestion due to P2P usage and that some network management is required to address it.  Moreover, it rejected the competition concerns noting that there was no evidence that Bell's action had lessened competition and it concluded that reducing speeds does not rise to the level of controlling content.

While the CRTC's decision to permit Bell's throttling practices is disappointing in the short term - and seems to place Canada on a different track from the U.S. - the decision is not a total loss for net neutrality supporters as the Commission made a clear commitment to addressing the issue of net neutrality and network management in a formal proceeding in July 2009.  Indeed, it is important not to lose sight of how much has changed in the past year. 

Just over one year, I wrote a column noting the need for greater ISP transparency in the wake of Rogers' admission that it engaged in traffic shaping.  At the time, net neutrality was viewed as a fringe issue in Canada without much political traction.  In the span of 13 months, there has been a major CRTC case, a private member's bill on net neutrality, a rally on Parliament Hill, the emergence of BitTorrent as distribution tool for broadcast content, a more vocal business community supporting net neutrality, and a gradual shift of this issue into the political mainstream.  In the United States, the change has been even more dramatic - an FCC ruling on the throttling activities, proposed legislation, the shift of net neutrality to wireless, and a President-elect who has been outspoken on the need to preserve net neutrality.

In other words, today's CRTC decision is not the final word on net neutrality in Canada, but rather the first word on it.  The Commission itself has opened the door to broader hearings on the issue next year, which may come alongside the new media hearings that also offer the opportunity to raise net neutrality concerns.  Moreover, if the Commission comes to the conclusion that these practices are consistent with current Canadian law, there is the likelihood of growing calls from within Parliament to change the law.

A year ago, the net neutrality debate focused on whether rules were needed. Today, the debate is changing from whether there should rules on network management to what those rules should be.  In fact, the Commission notes that as part of the hearing it "will try to establish the criteria to be used in the event that specific traffic management practices need to be authorized."  There is an emerging consensus on the easy issues -  no content blocking and better transparency of network management practices (the CRTC today required Bell to provide its wholesale customers with advanced notice of its plans).  We are in the early stages of the more difficult questions of what constitutes reasonable network management practices and the opening of a formal proceeding puts those tougher questions squarely on the table.

Update: The NDP's Charlie Angus responds.  Coverage from the CBC, Globe, Toronto Star, and Ars Technica.

CRTC Bell - CAIP Throttling Decision Tomorrow

The CBC reports that the CRTC will release its much anticipated decision on Bell's throttling practices on Thursday morning.

CRTC Delays CAIP v. Bell Decision

The CBC reports that the CRTC has announced that its decision in the Bell v. CAIP decision has been delayed until November.

CRTC To Rule on CAIP v. Bell Case By October 31st

The CBC reports that the CRTC has advised CAIP and Bell that it will issue its decision in the throttling case by October 31st.

Syndicate content