Skip to Content

copyright

  • 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/pathauto/pathauto.module on line 84.
  • warning: require_once() [function.require-once]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/sites/all/modules/pathauto/pathauto.module on line 85.
  • warning: require_once() [function.require-once]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/sites/all/modules/pathauto/pathauto.module on line 86.
  • warning: require_once() [function.require-once]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/sites/all/modules/pathauto/pathauto.module on line 87.
  • warning: require_once() [function.require-once]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/includes/module.inc on line 273.
  • warning: require_once() [function.require-once]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/sites/all/modules/date/date/date.module on line 529.
  • warning: require_once() [function.require-once]: Unable to allocate memory for pool. in /mnt/www/html/wkaram/docroot/sites/all/modules/date/date_api.module on line 1711.
  • 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.
  • 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.
Monday October 3, 2011
The Daily Digital Lock Dissenter, Day 1: The Provincial Resource Centre for the Visually Impaired
With the introduction of Bill C-11 last week, the government plans to move swiftly to pass its copyright reform bill, including restrictive digital lock rules that have been roundly criticized by many consumer, education, and business groups from across the country. As the bill winds its way through the legislative process, I thought it would be useful to provide a daily reminder of what Canadians have told the government about the digital lock issue. Over the next few months, I plan a daily digital lock post that quotes from a submission to the Bill C-32 legislative committee or the 2009 national copyright consultation. The posts will begin with group submissions but I'll feature individual submissions later in the series as well. The series begins with the Provincial Resource Centre for the Visually Impaired (PRCVI) British Columbia, which works to assist blind and visually impaired students: The exception that permits circumvention of technological protection measures (TPMs) and the means to circumvent these measures for the purpose of producing alternate formats (Section 41.16(1)) may be largely nullified by the condition “to not unduly impair the technological protection measure.” According to the Canadian Library Association there is no effective technical way to remove the TPMs and to restore them after an alternate format has been created. The TPMs would in all likelihood, interfere with the use of some, if not all, of the adaptive technologies used by students with perceptual disabilities to access educational materials.
daily digital lock
Content Country: 
Canada

With the introduction of Bill C-11 last week, the government plans to move swiftly to pass its copyright reform bill, including restrictive digital lock rules that have been roundly criticized by many consumer, education, and business groups from across the country. As the bill winds its way through the legislative process, I thought it would be useful to provide a daily reminder of what Canadians have told the government about the digital lock issue. Over the next few months, I plan a daily digital lock post that quotes from a submission to the Bill C-32 legislative committee or the 2009 national copyright consultation. The posts will begin with group submissions but I'll feature individual submissions later in the series as well.

The series begins with the Provincial Resource Centre for the Visually Impaired (PRCVI) British Columbia, which works to assist blind and visually impaired students:

The exception that permits circumvention of technological protection measures (TPMs) and the means to circumvent these measures for the purpose of producing alternate formats (Section 41.16(1)) may be largely nullified by the condition “to not unduly impair the technological protection measure.” According to the Canadian Library Association there is no effective technical way to remove the TPMs and to restore them after an alternate format has been created. The TPMs would in all likelihood, interfere with the use of some, if not all, of the adaptive technologies used by students with perceptual disabilities to access educational materials.

Wednesday June 23, 2010
NDP MP Charlie Angus Responds to Moore's Attacks
The House of Commons is shut down due to today's earthquake, but I have received a copy of a release from the office of NDP MP Charlie Angus which responds to Canadian Heritage Minister James Moore's attack on fair copyright.  The NDP planned to issue the release today, but cannot due to the office closure.  I was given permission to post the release in its entirety. FOR IMMEDIATE RELEASEJUNE 23, 2010 NEW DEMOCRATS CALL MOORE OFFSIDE FOR ATTACKING FAIR COPYRIGHT ADVOCATESMinister’s description of ‘radical extremists’ shows he’s in need of a time-out  
TIMMINS – Speaking at a G20 Chamber of Commerce event, Heritage Minister James Moore inexplicably lashed out at those who have raised concerns with his new copyright bill, C-32. Moore characterised fair copyright advocates as “babyish” and enemies of any copyright reform whatsoever. He called them “radical extremists” who must be “confronted every step of the way until they are defeated.” New Democrat Digital Affairs Critic Charlie Angus (Timmins-James Bay) said Moore’s comments are reminiscent of a war-time call-to-arms and are way out of line.

“Attacking teachers, students, artists and consumers who have legitimate questions about this legislation is ridiculous,” said Angus. “Instead of understanding and appreciating the nuances of balanced copyright, the Minister is appearing hyper-defensive and bombastic. I think he needs a time out.”

In his speech to the conference, Moore claimed the government’s attack on consumer rights are necessitated by Canada’s international obligations under the World Intellectual Property Organization (WIPO) treaties.  Angus says Moore simply has his facts wrong.

“James Moore shouldn’t hide behind international treaties to excuse the significant stumbling blocks he has put into the bill. All the experts, including those civil servants who drafted the bill, agree that it could be WIPO-compliant without his push for American-style protection for digital locks,” said Angus. “The Tories are pushing this failed agenda that will criminalize perfectly reasonable behaviour and deny educators legal access to works which they should logically have.”

Angus says Moore needs to tone down the rhetoric and get down to the serious business of working with all stakeholders on amendments that will improve the legislation.

“A Minister shouldn’t resort to name calling or start a war with fair-copyright advocates just because he doesn’t like the feedback he’s getting on Twitter,” said Angus.  “If Moore spent more time listening to the educators, experts, academics and artists who have serious issues with this bill, maybe his public statements wouldn’t be so out of line with everyday Canadians who simply want balanced legislation.”

-30-

For more information please contact:

George Soule, Caucus Press Secretary: 613-850-3448 or souleg@parl.gc.ca

The House of Commons is shut down due to today's earthquake, but I have received a copy of a release from the office of NDP MP Charlie Angus which responds to Canadian Heritage Minister James Moore's attack on fair copyright.  The NDP planned to issue the release today, but cannot due to the office closure.  I was given permission to post the release in its entirety.

FOR IMMEDIATE RELEASE
JUNE 23, 2010

NEW DEMOCRATS CALL MOORE OFFSIDE FOR ATTACKING FAIR COPYRIGHT ADVOCATES
Minister’s description of ‘radical extremists’ shows he’s in need of a time-out


 

Friday June 11, 2010
Setting the Record Straight: 32 Questions and Answers on C-32's Digital Lock Provisions, Part Four
The first three posts on the 32 Questions and Answers on Bill C-32's digital lock provisions focused first on general issues in the bill, second on C-32's circumvention exceptions, and third on the missing exceptions.  Today's post discusses the consumer-focused provisions in the bill. For those that want it all in a single package, I've posted the full series as PDF download. The Consumer Provisions This section features answers to the following questions: Bill C-32 purports to allow consumer to legally shift music from CDs to their iPods or other devices.  Do they lose that right if there are digital locks on their CD? Does Bill C-32 allow consumers to make legal backup copies of most commercial DVDs? Does Bill C-32 allow consumers to shift content from a DVD to a portable video player such as an iPad? C-32 purports to allow consumer to legally record television shows, yet cable companies are increasingly inserting anti-copying technologies into some broadcasts?  Does C-32 allow for those programs to be recorded? C-32 includes an exception for unlocking cellphones.  Isn't that a positive new development? Does C-32 require businesses to notify consumers about the presence of digital locks? Isn't there an "analog hole" that would allow someone to record a DVD without circumventing the digital lock?
Bill C-32 purports to allow consumer to legally shift music from CDs to their iPods or other devices.  Do they lose that right if there are digital locks on their CD?

Yes. The new right to legally shift music is subject to an anti-circumvention limitation.  In other words, the right to shift music to your iPod is not a right that you control.  It is a right that is effectively dictated by the record label who can easily remove the right by including copy-controls on the CD release (there are thousands of these kinds of CDs owned by Canadians).  In fact, the anti-circumvention limitation even applies to private copies onto blank CDs.  This means that consumers pay for the CD and pay the levy on a blank CD that nominally gives them the right to make a personal copy, yet violate the law if they circumvent a copy-control in order to do so. 

Does Bill C-32 allow consumers to make legal backup copies of most commercial DVDs?

No.  The new backup copy provision are subject to an anti-circumvention limitation.  Since most commercial DVDs currently contain several TPMs, consumers would not be able to legally make a backup copy of their own personal DVDs.

Does Bill C-32 allow consumers to shift content from a DVD to a portable video player such as an iPad?

No. The format shifting provision is subject to an anti-circumvention limitation.  Since most commercial DVDs currently contain several TPMs, consumers would not be able to legally make a backup copy of their own personal DVDs.

C-32 purports to allow consumer to legally record television shows, yet cable companies are increasingly inserting anti-copying technologies into some broadcasts?  Does C-32 allow for those programs to be recorded?


No.  If there is a digital lock (often referred to as a broadcast flag) included with the broadcast, you can't legally circumvent it in order to record the program.  Note that the U.S. has established limits on the use of the broadcast flag, but no such limits exist in Canada.  As Canada transitions to digital, it is possible that broadcasters will increasingly institute anti-copying notices to stop the very recording rights that C-32 purports to provide. 
 
C-32 includes an exception for unlocking cellphones.  Isn't that a positive new development?


The inclusion of a circumvention exception for unlocking cellphones is certainly a good thing, yet the net effect is merely to retain the status quo.  It is currently legal in Canada to unlock a cellphone, with the primary barriers being carrier contracts and technical inability to do so.  The new exception does not create any new rights to unlock the cellphone, but rather merely retains the current right to do so.

Does C-32 require businesses to notify consumers about the presence of digital locks?

No.  Bill C-32 does not contain any notice requirement regarding the limitations imposed by DRM on a consumer product. Most consumers know little if anything about DRMs and the limitations that may be placed on consumer entertainment products such as CDs, DVDs, video games, or digital download services.  While there may some limited disclosures - DVDs indicate the region code, if your eyesight is good enough you might notice that some copy-controlled CDs warn on the back corner that they may not play on all computers, and digital download services all feature lengthy user agreements that few consumers will ever read - they are plainly insufficient and the government should not support the legal fiction that "informed" consumers are knowingly purchasing products that contain a host of limitations.

For many consumers, these DRM products are simply not fit for purpose - they often won't play on your DVD player, on your iPod, or permit usage that most would expect is permissible.  Moreover, consumers frequently can't obtain a refund for their purchases as many retailers won't accept returns on opened CDs and DVDs and digital download services do not offer refunds to disgruntled downloaders.

The federal government might argue that this is provincial problem, since consumer protection issues typically fall under provincial jurisdiction.  The reality, however, is that the federal government can and should play its part to address the issue given the manner it which it is supporting the use of DRM through Bill C-32.  It should consider establishing DRM labeling requirements (an approach also advocated by the Society for Law and Computers in the UK) so that consumers will be able to quickly identify capabilities, compatibilities, and limitations.  The Competition Bureau is currently responsible for two labelling statutes - the Consumer Packaging and Labelling Act and the Textile Labelling Act.  If labelling is required for upholstered furniture, surely it can be added for consumer entertainment products.

Isn't there an "analog hole" that would allow someone to record a DVD without circumventing the digital lock?

Yes.  It is true that rather than picking a digital lock on DVD, a person could try to camcord an analog version of a film.  In fact, this is precisely what the MPAA argued last year, claiming that there was no need for a film studies exemption in the DMCA since there is an analog way to create film clips.  Rather than break the encryption on a DVD, teachers could camcord the same film clips.  In fact, the organization showed a video demonstrating how to effectively camcord clips of DVDs without breaking the encryption on the DVD. 

Leaving aside how surreal it is to see the same organization that travels the world demanding anti-camcording legislation now citing it as a solution, the analog hole is not a solution for making backup copies of DVD or format shifting.  It might only be used for a very brief clip, but given the government's stated goal of modernizing Canadian copyright law, it is worth asking whether a law that proposed using camcording films to preserve basic copyright rights has struck the right balance.  Note that the Film Studies Association of Canada was outspoken on C-61.
The first three posts on the 32 Questions and Answers on Bill C-32's digital lock provisions focused first on general issues in the bill, second on C-32's circumvention exceptions, and third on the missing exceptions.  Today's post discusses the consumer-focused provisions in the bill. For those that want it all in a single package, I've posted the full series as PDF download.

The Consumer Provisions

This section features answers to the following questions:
  • Bill C-32 purports to allow consumer to legally shift music from CDs to their iPods or other devices.  Do they lose that right if there are digital locks on their CD?
  • Does Bill C-32 allow consumers to make legal backup copies of most commercial DVDs?
  • Does Bill C-32 allow consumers to shift content from a DVD to a portable video player such as an iPad?
  • C-32 purports to allow consumer to legally record television shows, yet cable companies are increasingly inserting anti-copying technologies into some broadcasts?  Does C-32 allow for those programs to be recorded?
  • C-32 includes an exception for unlocking cellphones.  Isn't that a positive new development?
  • Does C-32 require businesses to notify consumers about the presence of digital locks?
  • Isn't there an "analog hole" that would allow someone to record a DVD without circumventing the digital lock?
Wednesday June 9, 2010
If C-32 Becomes Law: Redline Version of the Copyright Act
Thanks once again to the hard work of my research assistant Keith Rose, posted below is a redline version of the Copyright Act with Bill C-32 incorporated into the law. 

Thanks once again to the hard work of my research assistant Keith Rose, posted below is a redline version of the Copyright Act with Bill C-32 incorporated into the law. 

Thanks once again to the hard work of my research assistant Keith Rose, posted below is a redline version of the Copyright Act with Bill C-32 incorporated into the law. 

Monday June 7, 2010
Setting the Record Straight: 32 Questions and Answers on C-32's Digital Lock Provisions, Part One
The digital lock provisions have quickly emerged as the most contentious part of Bill C-32, the new copyright bill.  This comes as little surprise, given the decision to bring back the digital lock approach from C-61 virtually unchanged. The mounting public concern with the digital lock provisions (many supporters of the bill have expressed serious misgivings about the digital lock component) has led to many questions as well as attempts to characterize public concerns as myths.  In effort to set the record straight, I have compiled 32 questions and answers about the digital lock provisions found in C-32.  The result is quite lengthy, so I will divide the issues into five separate posts over the next five days: (1) general questions about the C-32 approach; (2) the exceptions in C-32; (3) the missing exceptions; (4) the consumer provisions; and (5) the business provisions.  For those that want it all in a single package, I've posted the full series as PDF download. Before getting into the 32 questions, it is worth answering the most basic question - what are anti-circumvention or digital lock provisions?  The short answer is that they are provisions that grant legal protection to technological protection measures (TPMs).  In plainer English, traditional copyright law grants creators a basket of exclusive rights in their work.  TPMs or digital locks (such as copy-controls on CDs, DVDs, or e-books) effectively provide a second layer of protection by making it difficult for most people to copy or sometimes access works in digital format.  Anti-circumvention legislation creates a third layer of protection by making it an infringement to simply pick or break the digital lock (in fact, it even goes further by making it an infringement to make available tools or devices that can be used to pick the digital lock).  Under the Bill C-32, it would be an infringement to circumvent a TPM even if the intended use of the underlying work would not constitute traditional copyright infringement. The C-32 Approach This section features answers to the following questions: Isn't the C-32 digital lock approach simply the required implementation to comply with the WIPO Internet treaties? Penalties are reduced for individuals who circumvent for personal purposes.  Doesn't this solve the problem? The digital lock provisions in C-32 appear to distinguish between copy controls and access controls.  Isn't that enough to address concerns about the bill's impact on fair dealing? Are the digital lock provisions in C-32 constitutional? Is it true that C-32 requires teachers and students to destroy some digital lessons 30 days after the course concludes? Is it true that C-32 requires librarians to ensure that inter-library digital loans self-destruct within five days of first use? The U.S. has a regular review of new exceptions every three years.  Does Canada plan the same?
Isn't the C-32 digital lock approach simply the required implementation to comply with the WIPO Internet treaties?

No.  The WIPO Internet treaties require that countries provide legal protection for digital locks, but leave considerable flexiblity in how this requirement is implemented.  The U.S. has promoted its particular approach (as found in the DMCA and now in C-32) since before the treaty was even concluded, yet consensus in establishing the treaty was only achieved by adopting far more flexible language.

On the issue of legal protection for digital locks, the treaties require countries to provide "adequate legal protection and effective legal remedies" for technological protection measures.  The U.S. initially proposed:

(1) Contracting Parties shall make unlawful the importation, manufacture or distribution of protection-defeating devices, or the offer or performance of any service having the same effect, by any person knowing or having reasonable grounds to know that the device or service will be used for, or in the course of, the exercise of rights provided under this Treaty that is not authorized by the rightholder or the law.

(2) Contracting Parties shall provide for appropriate and effective remedies against the unlawful acts referred to in paragraph (1).

This language did not achieve consensus support with many proposed changes.  A compromise position was ultimately reached using the "to provide adequate legal protection and effective legal remedies" standard.  Not only does this language not explicitly require a ban on the distribution or manufacture of circumvention devices (ie. software programs used to circumvent digital locks), it is quite obvious that the intent of the negotiating parties was to provide flexibility to avoid such an outcome.

U.S. law professor Pam Samuelson chronicles precisely what happened in her 1997 law review article, The U.S. Digital Agenda at the World Intellectual Property Organization:

At the diplomatic conference, there was little support for the Committee's proposed language on circumvention technologies. Some countries opposed inclusion of any anti-circumvention provision in the treaty.  Others proposed a "sole purpose" or "sole intended purpose" standard for regulating circumvention technologies. Some wanted an explicit statement that carved out circumvention for fair use and public domain materials.  The E.U. offered a proposal that would have required contracting parties to adopt adequate and effective legal measures to regulate devices and services intended for technology-defeating purposes.

Facing the prospect of little support for its proposal or the Committee's draft anti-circumvention provision, the U.S. delegation was in the uncomfortable position of trying to find a national delegation to introduce a compromise provision brokered by U.S. industry groups that would simply have required contracting parties to have adequate and effective legal protection against circumvention technologies and services.  In the end, such a delegation was found, and the final treaty embodied this sort of provision as Article 11.

This was, of course, a far cry from the provision that the U.S. had initially promoted. Still, it was an accomplishment to get any provision in the final treaty on this issue. The inclusion of terms like "adequate" and "effective" protection in the treaty will mean that U.S. firms will be able to challenge national regulations that they deem deficient.

In the years since the treaty was concluded, the U.S. and a handful of supporters have argued strenuously that countries should ignore the compromise language and adopt the U.S. approach. Yet some countries have rejected that advice - Canada's own bill C-60 adopted a flexible approach, as does the most recent copyright reform bill from India.  New Zealand's law features many differences from the U.S. model and dozens of countries have added exceptions and changes to the basic U.S. approach.  In fact, the reality is that of the 88 states that have ratified the WIPO Internet treaties, fewer than half that have adopted the U.S. model. 

When the U.S. was in the process of implementing the WIPO Internet treaties into what became the DMCA, officials acknowledged the flexibility that exists in the treaty.  Marybeth Peters, the U.S. Register of Copyrights, said in testimony before the House Judiciary Committee on 16 Sept. 1997:

"Some have urged that the legislation not address the provision of products or services, but focus solely on acts of circumvention. They state that the treaties do not require such coverage, and argue that devices themselves are neutral, and can be used for either legitimate or illegitimate purposes. It is true that the treaties do not specifically refer to the provision of products or services, but merely require adequate protection and effective remedies against circumvention. As discussed above, however, the treaty language gives leeway to member countries to determine what protection is appropriate, with the question being whether it is adequate and effective."

And, later in the same testimony, the clearest statement: "the treaties do not specifically require protection for access controls in themselves."

Applied to C-32, the current bill goes far beyond what is strictly required to be compliant with the WIPO Internet treaties.  A more flexible, balanced implementation would still be WIPO compliant, provide protection for businesses seeking to use DRM, and maintain the copyright balance.

Penalties are reduced for individuals who circumvent for personal purposes.  Doesn't this solve the problem?

No.  First, claims that reduced penalties removes the impediment to Canadians circumventing digital locks for personal purposes assumes that concern for statutory damages is the primary motivator for a particular action.  I disagree. In the education world, teachers and students will not break the lock because academic guidelines will make it clear that they can't.  Similarly, research will also be stifled in the same way since researchers sign ethics documents when they apply for grants that their research plan is compliant with all laws.  They can't sign the document in this situation, regardless of the likelihood of damages.

Second, C-32 also makes the distribution and marketing of devices (ie. software) used to circumvent illegal.  This suggests it will be more difficult to get those tools (and perhaps risky), so the notion that people will circumvent in light of lower penalties is undermined by the underground nature of being able to do so.

Third, from a bigger picture perspective, rights holders have been complaining for years that the public does not respect copyright.  This bill is an attempt to revive respect for copyright by having the law better reflect current norms (and therefore make it more respectable).  However, you do not build respect for copyright by creating provisions that outlaw something but have the government indirectly say it is acceptable to violate its new rule.  C-32 should craft rules that generate support and acceptance in the public and thereby build support and acceptance for copyright more broadly.

The digital lock provisions in C-32 appear to distinguish between copy controls and access controls.  Isn't that enough to address concerns about the bill's impact on fair dealing?

No.  The distinction in one section of Bill C-32, which was also contained in C-61, does not address the fair dealing concerns in the bill.  First, the distinction between access controls (access to the work itself) and copy controls (copying the work) is a distinction without a difference for many of today's TPMs.  The digital locks used by Amazon or Apple on e-books or the TPMs on DVDs are both access and copy controls.  In order to effectively circumvent to be able to copy, you have to circumvent access.  The locks often permit access for some uses, but not others.  In other words, Canadians will often need to circumvent access to get to the copying and therefore will still be infringing under the law.

Moreover, even if a consumer could distinguish between access and copy controls, the tools themselves that would be used to circumvent for copy purposes cannot be lawfully marketed or distributed.  The notion that it is permissible to circumvent for copying but that the software needed to do so can't be distributed demonstrates how this distinction really makes no real difference. 

Finally, many of the other new exceptions - format shifting, time shifting, and backup copies - are covered by all digital locks, including both access and copy controls.

Are the digital lock provisions in C-32 constitutional? 

Possibly not.  The constitutionality of digital lock legislation has been examined in two articles by Canadian law professors.  Both conclude that the provisions are constitutionally suspect if they do not contain a clear link to conventional copyright law.  Their reasoning is that the constitution grants jurisdiction over copyright to the federal government, but jurisdiction over property rights is a provincial matter.  Digital lock legislation that is consistent with existing copyright law - ie. one that factors in existing exceptions - is more clearly a matter of copyright.  The C-32 provisions are arguably far more about property rights since the provisions may be contained in the Copyright Act, but they are focused primarily on the rights associated with personal property.

My colleague Jeremy deBeer conducted a detailed analysis of this issue in his article, Constitutional Jurisdiction over Paracopyright Laws.  Many of his arguments were echoed in a 2009 article published in the Journal of Information Law and Technology by Professor Emir Aly Crowne-Mohammed and Yonatan Rozenszajn, both from the University of Windsor, which concluded that the anti-circumvention provisions found in Bill C-61 were unconstitutional.  The authors argue that the DRM provisions were "a poorly veiled attempt by the Government to strengthen the contractual rights available to copyright owners, in the guise of copyright reform and the implementation of Canada’s international obligations. Future iterations of Bill C-61 that do not take the fair dealing provisions of the Copyright Act (and the overall scheme of the Act) into account would also likely to fail constitutional scrutiny."

Is it true that C-32 requires teachers and students to destroy some digital lessons 30 days after the course concludes?

Yes.  Bill C-32 requires teachers that utilize a new educational exemption to destroy the lessons that they have created for their courses with one month of the conclusion of the course.  Teachers must recreate the lessons each year, which obviously establishes a strong incentive to run as far away as possible from these new "rights." 

Is it true that C-32 requires librarians to ensure that inter-library digital loans self-destruct within five days of first use?

Yes.  While moving toward digital interlibrary loans has obvious advantages (speed and cost being at the top of the list), Bill C-32 forces libraries to implement DRM-based solutions.  The requirements for legal digital interlibrary loans include limits on further copying and distribution that go far beyond what is necessary (they are presumably a response to the unlikely scenario that only a single Canadian library will purchase the copy of a work and use digital distribution to cover the rest of the country).  Even worse is the requirement to destroy the digital copy within five days of first use.  There are no similar requirements for paper-based copies of works and it makes no sense to force libraries to install DRM protections on digital copies to create time-limited uses.

The U.S. has a regular review of new exceptions every three years.  Does Canada plan the same?

No.  The U.S. DMCA experience leaves little doubt that the introduction of anti-circumvention legislation will create some unintended consequences.  No matter how long the list of circumvention rights and other precautionary measures, it is impossible to identify all future concerns associated with anti-circumvention legislation.  The U.S. DMCA addresses this by establishing a flawed tri-annual review process.  The system has not worked well, creating a formidable barrier to new exceptions and long delays to address emerging concerns.

As bad as the U.S. system is, the proposed Canadian system under Bill C-32 is worse since there is no mandated review of the exceptions at all.  Instead, Canada gets a flexible process that will allow the government to consider new exceptions if and when it sees fit.  In other words, the same government that brought you the Canadian DMCA will decide if there is a need to add any exceptions. If Canada establishes anti-circumvention legislation, it should also establish an impartial process that will enable concerned parties to raise potential new circumvention rights without excessive delay.  The process must be fast, cheap, and easily accessible to all Canadians.  Bill C-32 establishes the criteria for the introduction of new circumvention rights but fails to implement an administrative structure to conduct the reviews.
The digital lock provisions have quickly emerged as the most contentious part of Bill C-32, the new copyright bill.  This comes as little surprise, given the decision to bring back the digital lock approach from C-61 virtually unchanged. The mounting public concern with the digital lock provisions (many supporters of the bill have expressed serious misgivings about the digital lock component) has led to many questions as well as attempts to characterize public concerns as myths.  In effort to set the record straight, I have compiled 32 questions and answers about the digital lock provisions found in C-32.  The result is quite lengthy, so I will divide the issues into five separate posts over the next five days: (1) general questions about the C-32 approach; (2) the exceptions in C-32; (3) the missing exceptions; (4) the consumer provisions; and (5) the business provisions.  For those that want it all in a single package, I've posted the full series as PDF download.

Before getting into the 32 questions, it is worth answering the most basic question - what are anti-circumvention or digital lock provisions?  The short answer is that they are provisions that grant legal protection to technological protection measures (TPMs).  In plainer English, traditional copyright law grants creators a basket of exclusive rights in their work.  TPMs or digital locks (such as copy-controls on CDs, DVDs, or e-books) effectively provide a second layer of protection by making it difficult for most people to copy or sometimes access works in digital format.  Anti-circumvention legislation creates a third layer of protection by making it an infringement to simply pick or break the digital lock (in fact, it even goes further by making it an infringement to make available tools or devices that can be used to pick the digital lock).  Under the Bill C-32, it would be an infringement to circumvent a TPM even if the intended use of the underlying work would not constitute traditional copyright infringement.

The C-32 Approach

This section features answers to the following questions:
  • Isn't the C-32 digital lock approach simply the required implementation to comply with the WIPO Internet treaties?
  • Penalties are reduced for individuals who circumvent for personal purposes.  Doesn't this solve the problem?
  • The digital lock provisions in C-32 appear to distinguish between copy controls and access controls.  Isn't that enough to address concerns about the bill's impact on fair dealing?
  • Are the digital lock provisions in C-32 constitutional?
  • Is it true that C-32 requires teachers and students to destroy some digital lessons 30 days after the course concludes?
  • Is it true that C-32 requires librarians to ensure that inter-library digital loans self-destruct within five days of first use?
  • The U.S. has a regular review of new exceptions every three years.  Does Canada plan the same?
Wednesday November 11, 2009
Canadian Labour Congress Adopts New Copyright Policy
Earlier this year, I posted on a Canadian Labour Congress IP policy that was scheduled for approval by the CLC Council.  The proposal represented a dramatic shift in approach  that was exceptionally one-sided.  The proposal did not pass, however, and the CLC formed a working group to develop a new policy.  Sources advise that the new policy was approved late last month and the results much better reflect the diversity of interests within Canada's largest labour organization.  In fact, the policy combines both copyright and net neutrality, adopting a broader approach to digital policy. On copyright, the policy statement contains 14 recommendations including expanding fair dealing, limiting the application of statutory damages, eliminating crown copyright, and linking anti-circumvention legislation to actual infringement.  The 14 recommendations:
  • to engage in open and genuine consultation with Canadians before drafting new copyright legislation;
  • in the drafting of any new copyright legislation, to balance the needs of Canadian users, creators and owners of copyrighted works in a manner that reflects and addresses Canadian concerns;
  • to introduce and pass amendments to the Canadian Copyright Act to conform with the World Intellectual Property Organization's (WIPO) Internet Treaties and to implement those treaties;
  • to expand the Fair Dealing provisions of the Copyright Act to achieve an appropriate balance between the rights of users, creators and owners of copyrighted works;
  • to direct enforcement measures at commercial copyright infringement, including the counterfeit and pirated goods that threaten the health, safety and jobs of Canadians;
  • to amend the Statutory Damages provisions of the Copyright Act to remove their application from those who copy a work with a reasonable belief that their actions are justified by Fair Dealing or other statutory rights;
  • to advocate for the establishment of an audio-visual performance rights treaty at the WIPO and establish such rights in domestic legislation to benefit performers and creators for use of their work;
  • to eliminate Crown Copyright so that government materials can be freely used by Canadians;
  • to introduce anti-circumvention provisions (measures that protect digital locks) in the Copyright Act that renders circumvention unlawful if such circumvention is for the purposes of copyright infringement;
  • to ensure that the use of digital locks or other such technological measures for the protection of copyrighted works in Canada will be consistent with the established principles and practices of current copyright legislation in relation to access for “fair dealing” purposes;
  • to amend the Copyright Act to protect the holders of moral rights either by recognizing such rights as non-waivable and inalienable personal rights, or by considering further limitations and conditions on such waivers;
  • to amend the current Canadian copyright ownership formulation in section 13(3) of the Copyright Act where the employer, not the author or creator, is deemed to be the first owner of the copyright so it is less onerous for a wider range of creative workers;
  • to update and expand the Canadian private copying regime to ensure that creators are appropriately compensated for uses of their work in all media while affording users the right to copy works they have obtained legally for personal use; and
  • to enact an effective legal framework in the Copyright Act governing internet service providers that ensures providers play a role in addressing copyright infringement on the internet and that allegations of copyright infringement are dealt with fairly.

This represents a dramatic shift for an organization representing three million Canadian workers that includes groups such as ACTRA.  When I posted on this issue earlier this year, I suggested that people contact the CLC to express their concern with the proposed resolution.  Given this new policy, it would similarly be appropriate to contact the CLC to express support for taking a closer look at the issue and working toward a more balanced policy approach.

  • to engage in open and genuine consultation with Canadians before drafting new copyright legislation;
  • in the drafting of any new copyright legislation, to balance the needs of Canadian users, creators and owners of copyrighted works in a manner that reflects and addresses Canadian concerns;
  • to introduce and pass amendments to the Canadian Copyright Act to conform with the World Intellectual Property Organization's (WIPO) Internet Treaties and to implement those treaties;
  • to expand the Fair Dealing provisions of the Copyright Act to achieve an appropriate balance between the rights of users, creators and owners of copyrighted works;
  • to direct enforcement measures at commercial copyright infringement, including the counterfeit and pirated goods that threaten the health, safety and jobs of Canadians;
  • to amend the Statutory Damages provisions of the Copyright Act to remove their application from those who copy a work with a reasonable belief that their actions are justified by Fair Dealing or other statutory rights;
  • to advocate for the establishment of an audio-visual performance rights treaty at the WIPO and establish such rights in domestic legislation to benefit performers and creators for use of their work;
  • to eliminate Crown Copyright so that government materials can be freely used by Canadians;
  • to introduce anti-circumvention provisions (measures that protect digital locks) in the Copyright Act that renders circumvention unlawful if such circumvention is for the purposes of copyright infringement;
  • to ensure that the use of digital locks or other such technological measures for the protection of copyrighted works in Canada will be consistent with the established principles and practices of current copyright legislation in relation to access for “fair dealing” purposes;
  • to amend the Copyright Act to protect the holders of moral rights either by recognizing such rights as non-waivable and inalienable personal rights, or by considering further limitations and conditions on such waivers;
  • to amend the current Canadian copyright ownership formulation in section 13(3) of the Copyright Act where the employer, not the author or creator, is deemed to be the first owner of the copyright so it is less onerous for a wider range of creative workers;
  • to update and expand the Canadian private copying regime to ensure that creators are appropriately compensated for uses of their work in all media while affording users the right to copy works they have obtained legally for personal use; and
  • to enact an effective legal framework in the Copyright Act governing internet service providers that ensures providers play a role in addressing copyright infringement on the internet and that allegations of copyright infringement are dealt with fairly.

This represents a dramatic shift for an organization representing three million Canadian workers that includes groups such as ACTRA.  When I posted on this issue earlier this year, I suggested that people contact the CLC to express their concern with the proposed resolution.  Given this new policy, it would similarly be appropriate to contact the CLC to express support for taking a closer look at the issue and working toward a more balanced policy approach.

clc copyright policy

Earlier this year, I posted on a Canadian Labour Congress IP policy that was scheduled for approval by the CLC Council.  The proposal represented a dramatic shift in approach  that was exceptionally one-sided.  The proposal did not pass, however, and the CLC formed a working group to develop a new policy.  Sources advise that the new policy was approved late last month and the results much better reflect the diversity of interests within Canada's largest labour organization.  In fact, the policy combines both copyright and net neutrality, adopting a broader approach to digital policy.

On copyright, the policy statement contains 14 recommendations including expanding fair dealing, limiting the application of statutory damages, eliminating crown copyright, and linking anti-circumvention legislation to actual infringement.  The 14 recommendations:

Friday August 14, 2009
CIPPIC Launches DigitalAgenda.ca

CIPPIC has launched an exciting new advocacy site - DigitalAgenda.ca. The site provides information and tools for speaking out on copyright, net neutrality, lawful access, and the ECPA.  The copyright section is the most robust at the moment, complete with a sample letter for the consultation and an Idea Torrent designed to faciliate discussion on copyright reform issues.

ACTRA Posts Position on Copyright Reform

ACTRA has posted its position on the copyright reform consultation ahead of Monday's roundtable in Halifax.

Canada Shedding Reputation as Illegal Camcording Haven

CP reports on declining numbers of illegal camcords being traced to Canada with some claiming that it is a result of new anti-camcording legislation.

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

Syndicate content