<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Barry Sookman &#187; spam</title>
	<atom:link href="http://www.barrysookman.com/tag/spam/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.barrysookman.com</link>
	<description>Copyright, Intellectual Property, Computer, Internet, e-Commerce Law.</description>
	<lastBuildDate>Sat, 04 Feb 2012 13:30:00 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Will it be illegal to recommend a dentist under Canada’s new anti-spam law (CASL)?</title>
		<link>http://www.barrysookman.com/2012/01/03/will-it-be-illegal-to-recommend-a-dentist-under-canada%e2%80%99s-new-anti-spam-law-casl/</link>
		<comments>http://www.barrysookman.com/2012/01/03/will-it-be-illegal-to-recommend-a-dentist-under-canada%e2%80%99s-new-anti-spam-law-casl/#comments</comments>
		<pubDate>Tue, 03 Jan 2012 13:45:06 +0000</pubDate>
		<dc:creator>Barry Sookman</dc:creator>
				<category><![CDATA[Bill C-28]]></category>
		<category><![CDATA[CASL]]></category>
		<category><![CDATA[E-commerce]]></category>
		<category><![CDATA[ECPA]]></category>
		<category><![CDATA[FISA]]></category>
		<category><![CDATA[FIWSA]]></category>
		<category><![CDATA[Free Speech]]></category>
		<category><![CDATA[electronic records production]]></category>
		<category><![CDATA[malware]]></category>
		<category><![CDATA[spam]]></category>
		<category><![CDATA[spyware]]></category>
		<category><![CDATA[anti-spam law]]></category>
		<category><![CDATA[canada]]></category>

		<guid isPermaLink="false">http://www.barrysookman.com/?p=3970</guid>
		<description><![CDATA[Over the holidays I got an email from one of my relatives visiting Toronto. She asked me to recommend a dental surgeon for an unexpected tooth extraction. She also asked me to refer her to other dentists to get additional recommendations. I sent her an email with a recommendation to get treatment from a dental [...]]]></description>
			<content:encoded><![CDATA[<p>Over the holidays I got an email from one of my relatives visiting Toronto. She asked me to recommend a dental surgeon for an unexpected tooth extraction. She also asked me to refer her to other dentists to get additional recommendations. I sent her an email with a recommendation to get treatment from a dental surgeon who I encouraged her to see and also provided the name of a family dentist who could make other recommendations. My email included a link to a website of the clinic operated by the dental surgeon. My wife sent a similar email when I told her my relative was looking for a dentist. Later that day I started wondering whether responding to this type of inquiry would be legal or illegal under Canada’s anti-spam law (<a href="http://lois-laws.justice.gc.ca/eng/AnnualStatutes/2010_23/FullText.html">CASL</a>), once it is proclaimed into force.</p>
<p>The legality of recommending a dental surgeon to someone with a toothache should be a no-brainer. But under CASL sending anyone an email, IM, or other electronic message that encourages participation in a commercial activity may be illegal. Even recommending a dentist to a person with a toothache could be illegal under CASL. In fact, in many instances it would be impossible for the average Canadian to comply with all of CASL’s strictures even if all they wanted to do was recommend a dentist to someone with a toothache.</p>
<p>To determine whether a person will be able to legally email a recommendation for a dentist to someone asking for one without worrying about violating CASL, the average Canadian will have to make a number of legal determinations.</p>
<p>The first is whether the email or other electronic message is a “commercial electronic message” (a “CEM”).  An email would be an electronic message. To be a CEM the message including any links in the message need only encourage participation in a commercial activity. It is not limited to encouraging participation in a commercial activity with the sender of the message.</p>
<p>My email to my relative may well have been a CEM because it contained a recommendation and encouragement to purchase services from a dental surgeon and because the link to the clinic would display the clinic’s website which contains a description of clinic’s services, hours of operation, contact details, and other information about the clinic designed to solicit patients and new business. The referral to another dentist to recommend a dental surgeon would not likely have been enough to make the email a CEM on its own. However, since an email is a CEM if any part of it encourages participation in a commercial activity, the email as a whole would still likely be a CEM.</p>
<p>The next question is whether CASL contains any exceptions that make its internationally unprecedented onerous requirements inapplicable. There is an exception that permits a CEM to be sent to a person who has a personal or family relationship with the sender, as defined in the regulations. Since only draft regulations are available, we don’t know for sure whether sending a CEM to one’s relatives, friends or others will be illegal or not if CASL is not complied with. However, if we assume that the regulations that are ultimately finalized will be at least as broad as the <a href="http://www.barrysookman.com/2011/07/18/draft-fisa-regulations-published-by-crtc/">draft CRTC and Industry Canada regulations</a>, we can make some preliminary conclusions.</p>
<p>Under the draft Industry Canada regulations family relationship and personal relationship are defined as follows:</p>
<blockquote><p><em>(a) </em><em> </em>“family relationship” means the relationship between individuals who are connected by</p>
<p>(i) a blood relationship, if one individual is the child or other descendant of the other individual, the parent or grandparent of the other individual, the brother or sister of the other individual or of collateral descent from the other individual’s grandparent,</p>
<p>(ii) marriage, if one individual is married to the other individual or to an individual connected by a blood relationship to that other individual,</p>
<p>(iii) a common-law partnership, if one individual is in a common-law partnership with the other individual or with an individual who is connected by a blood relationship to that other individual; and</p>
<p>(iv) adoption, if one individual has been adopted, either legally or in fact, as the child of the other individual or as the child of an individual who is connected by a blood relationship to that other individual; and</p>
<p><em>(b) </em>“personal relationship” means the relationship, other than in relation to a commercial activity, between an individual who sends the message and the individual to whom the message is sent, if they have had an in-person meeting and, within the previous two years, a two-way communication.</p></blockquote>
<p>Under these definitions some of my relatives and I would have a “family relationship”. For example, CASL exempts sending CEMs to parents, siblings, children, and other lineal descendants. I could also respond to an email with an email recommending a dentist to my aunts and uncles and first and second cousins as they are of “collateral descent” to my grandparents without violating CASL.<a href="file:///C:/MyFiles/blogs/DOCS-%2311044671-v8-Sookman_CASL_Blog_Dentist%20DOC.doc#_ftn1">[1]</a></p>
<p>Once you get past the obvious close “family” relationships, however, the average Canadian would need to have the knowledge of an estates, family, tax or immigration lawyer to know whether their family member is someone to whom they can recommend a dentist without being subject to CASL’s strictures.<a href="file:///C:/MyFiles/blogs/DOCS-%2311044671-v8-Sookman_CASL_Blog_Dentist%20DOC.doc#_ftn2">[2]</a> Recommending a dentist would likely be illegal if sent by email, for example, to a great uncle or aunt or someone more removed than a second cousin, or members of their immediate families, unless CASL’s strictures are complied with.</p>
<p>CASL exempts certain friends where they fit into the “personal relationship” class, as defined in the regulations. However, CASL and its prohibitions against sending emails and other electronic messages that are CEMs would apply to a variety of other situations the average Canadian would never expect. It would apply to sending a recommendation to a friend you went to high school or university with, played a sport or went to camp with, were members of the same club, or simply had lost touch with, and hadn’t spoken or “had a two-way communication” within the last two years. It would apply to a friend who had moved away for a few years and was moving back and needed a dentist. You couldn’t email a friend of a friend to recommend a dentist, without violating CASL. You couldn’t recommend one to your brother or sister’s friend, or the parents of your child’s friend. You couldn’t reply to an email to recommend a dentist by email to a person you met at a party from out of town, but that you didn’t have a chance to directly speak to.</p>
<p>You also couldn’t send an instant message to someone recommending a dentist you had been conversing with over Facebook, even though you may have shared family pictures and videos with the person as well as had real time live video chats with the person continuously over the course of years. CASL does not recognize virtual friends as “friends”, even though many people would, at least in some circumstances.</p>
<p>Trying to help others by recommending a dentist to remedy a toothache could also be illegal in many other circumstances. If the person asking for help is not within the definition of “family relationship” or “personal relationship”, making a recommendation using email could be illegal. For example, if you are a lawyer negotiating a deal with out of town lawyers and are asked by email for a recommendation to a dentist to address a sudden toothache, none of the CASL exceptions would apply. They would also not apply to helping out a person you had just met related to a commercial activity e.g. a sales meeting with an out of town potential customer or supplier.</p>
<p>Unless the person asking for help is totally excluded from CASL by virtue of being in the “family relationship” or “personal relationship” classes, the next question the average Canadian will need to know before responding to a request for help is whether the person has the consent of the recipient to respond to the email. Again, one would have thought that it was a no-brainer that a person could reply to an email asking for a dental recommendation since one could easily imply or infer consent from the request. However, unlike New Zealand and Australia, Canada has chosen not to recognize inferred consents as valid under CASL. CASL also excludes all implied consents unless the relationship between the parties falls into the tightly defined categories of “existing business relationship” or “existing non-business relationship”, or several other limited classes in Section 10(9). In the case of a request for a dental referral, none of them are necessarily going to be applicable. Neither would any of the exceptions in Section 6(6) which sets out specific circumstances in which the requirement for an express consent is waived.</p>
<p>In these circumstances, a person could only respond to the email request if the request itself can be construed as an “express consent” to respond with a recommendation. CASL does not define the term “express consent”. It likely means an affirmative consent &#8211; something more than the type of consent that can be implied under paragraph 4.3.7 of Schedule 1 to PIPEDA,<a href="file:///C:/MyFiles/blogs/DOCS-%2311044671-v8-Sookman_CASL_Blog_Dentist%20DOC.doc#_ftn3">[3]</a> or inferred from the circumstances. From a form perspective, it may also require that the consent be in a verifiable form including in writing or in an electronic format.<a href="file:///C:/MyFiles/blogs/DOCS-%2311044671-v8-Sookman_CASL_Blog_Dentist%20DOC.doc#_ftn4">[4]</a> If so construed, an oral consent would not be recognized as a valid consent.</p>
<p>It is unclear whether a person asking for a recommendation gives an express consent (as contrasted with an implied or inferred consent) to reply with a recommendation. It is even more unclear whether a request for help includes an express consent for a third party, such as in my case, my wife, to give her recommendations. In the circumstances, there would be little doubt that my wife would have had implied or inferred consent. But, that would not have been enough to make her reply legal under CASL. CASL even makes it illegal to ask someone for consent to send him or her a CEM. Calling to ask permission wouldn’t help either since CASL’s draft regulations require all requests for consent to be in writing. So as absurd as it seems, it would not be clear that my wife or I would have had consent under CASL needed to make recommendations to the person in need of dental services &#8211;  even in reply to the person’s own email asking for help. Even more incredibly, there would be no legally recognized way to even ask for the consent.</p>
<p>Even assuming my wife and I had express consent to send the email replies, the emails would still need to comply with CASL (and its regulations’) formalities. In particular, our emails, to be legal, would need to</p>
<blockquote><p>(a) set out prescribed information that identifies the person who sent the message;</p>
<p>(b) set out information enabling the person to whom the message is sent to readily contact the sender (the contact information must be valid for 60 days; and</p>
<p>(c) set out the prescribed unsubscribe mechanism.</p></blockquote>
<p>Under the draft CRTC regulations, our email replies would have been illegal unless they contained our names and our “physical and mailing address, a telephone number providing access to an agent or a voice messaging system, an email address and a web address”.</p>
<p>It seems absurd that my wife and I would be forced to disclose our personal information – information protected by PIPEDA – simply to reply to an email requesting a recommendation for a dental surgeon. However, CASL compels every individual who sends a CEM on their own account to disclose this personal information. In fact, CASL makes all anonymous commercial speech in the form of CEMs illegal in Canada, regardless of the circumstances.</p>
<p>Moreover, it would be illegal to send the recommendations unless the other CASL requirements including having a web address and a voice mail system are met. My wife doesn’t have a web site. While I have this blog, it is not set up to receive communications under CASL. Accordingly, when CASL is proclaimed into force, we would not be able to reply to requests for recommendations in a manner that meets CASL’s identification requirements.</p>
<p>It doesn’t end there. CASL also sets out extremely onerous requirements for an unsubscribe mechanism which must be included with all CEMs. Under CASL, the unsubscribe mechanism must</p>
<blockquote><p>(a) enable the recipient to indicate, at no cost to them, the wish to no longer receive any CEMs, or any specified class of such messages, from the sender, using (i) the same electronic means by which the message was sent, or (ii) if using those means is not practicable, any other electronic means that will enable the person to indicate the wish; and</p>
<p>(b) specify an electronic address, or link to a page on the World Wide Web that can be accessed through a web browser, to which the indication may be sent.</p></blockquote>
<p>Under the draft CRTC regulations, the unsubscribe mechanism must also be able to be performed in no more than two clicks or another method of equivalent efficiency.</p>
<p>So, incredibly, under CASL, unless one of the “family” or “personal” relationship exemptions applies, neither my wife nor I could legally respond to a request for a recommendation for a dentist unless we also included in our emails the above unsubscribe options to the hapless requestor. CASL would require the average Canadian to license the same kind of “unsubscribe” tools that have become common place with commercial newsletters and mailouts – just to be able to recommend a dentist to a person with a toothache.</p>
<p>It is also interesting to consider the position of the dentists who were asked for email recommendations for dental surgeons. Their recommendations would likely also be CEMs. If they responded directly to my wife or me, they may, depending on our relationship with them, have an existing business relationship which would permit them to reply to us without an express consent. However, they would likely not have had express consent to send recommendations directly to my relative, nor would any consent to send these CEMs be implied under CASL. The dentists wouldn’t even have been able to pick up a phone to call to get permission to send recommendations electronically or send an email asking for permission. Accordingly, it would likely be illegal for the dentists to reach out electronically to my relative with recommendations for an oral surgeon. It also seems unlikely they would even think to comply with CASL’s identification and unsubscribe requirements. Their best legal course of action would be to refuse to help – and leave my relative without important information needed to assess what dental surgeon to retain. Ironically, they could communicate with my relative through conventional mail or by phone, methods usually seen as more intrusive forms of communications.</p>
<p>The strictures of CASL will also apply to other electronic formats including messages sent using instant messaging systems like BlackBerry Messenger (BBM) and other social networks, and SMS messages. They would also likely apply to recommendations forwarded using services such as Groupon or Livingsocial. However, it is virtually impossible to practically comply with all of CASL’s formalities using these messaging types – even assuming it is desirable to have these formalities apply in the circumstances.<a href="file:///C:/MyFiles/blogs/DOCS-%2311044671-v8-Sookman_CASL_Blog_Dentist%20DOC.doc#_ftn5">[5]</a></p>
<p>Consider for example if the request for the recommendation for the dental surgeon had been received via an SMS message. It would likely be impossible for the average Canadian to respond to the message via an SMS message. As noted above, CASL requires each CEM to include detailed identification information as well as an unsubscribe mechanism. It is impossible to include all of this information in the 140 character space limits that this messaging format permits.</p>
<p>The draft CRTC regulations provide an alternative that is equally unworkable. They provide that:</p>
<blockquote><p>If it is not practicable to include the information referred to in subsection (1) and the unsubscribe mechanism referred to in paragraph 6(2)(c) of the Act in a commercial electronic message, that information may be provided by a link to a web page on the World Wide Web that is clearly and prominently set out and that can be accessed by a single click or another method of equivalent efficiency at no cost to the person to whom the message is sent.</p></blockquote>
<p>The CRTC draft regulations would require individual Canadians, young and old, to do the following merely to reply to a request for a dental recommendation using SMS:</p>
<ul>
<li>Have or establish a web site.</li>
<li>Publically post on the web site the individual’s PIPEDA protected      personal information including physical      and mailing address, telephone number and email address.</li>
<li>Establish a mechanism to receive unsubscribe requests and disclose      this on the individual’s web site.</li>
<li>Include in the reply SMS message the dental recommendation and in      the same 140 character space limit “clearly and prominently set out” the      web link. Some links can be more than 140 characters. So this would force      individuals to find link shortening tools that work on the person’s mobile      phone and to copy the results into the SMS message. Even then, it is hard      to see how the recommendation and the links could be included in only 140      characters.</li>
<li>Find a way to make the individual’s web site accessible in a      single click from the SMS message. (On my phone it takes at least two      clicks. One to select the link, the other to engage it.)</li>
</ul>
<p>Consider next if the request for the recommendation for the dental surgeon had been received via an instant message from a BBM user. Again, it would likely be impossible for the average Canadian to respond to the message via BBM. Since it would not be practical to include all of the identification and unsubscribe information in a BBM message, individual Canadians would need to do the same things as a person replying using SMS. This is as unworkable for BBM and other IM messaging systems as it is for SMS messaging.</p>
<p>CASL is touted as being technologically neutral. But only part of it is. A CEM is defined, essentially, to include email, IM, telephone and similar messaging systems. However, the message form, prescribed requirements, and unsubscribe mechanisms are firmly rooted in a PC based email architecture, with work around add-ons that permit, without necessarily enabling, compliance using another specific technology – the web.  This asymmetrical approach to technological neutrality makes it a problem today – even before CASL is proclaimed into force. One can well imagine that as the technologies of communication evolve, CASL will increasingly hinder the innovation and deployment of new technologies and business models in Canada. This will undoubtedly disadvantage Canadians, who alone will be subject to laws as stringent and prescriptive as CASL.</p>
<p>It is obvious that the strictures of CASL are not limited to requests for dental surgeons. They would apply to requests that ordinary Canadians routinely get. They would apply ubiquitously to recommendations for any product or service including recommendations for doctors, lawyers and other professionals, restaurants, financial planners, stockbrokers, bankers, real estate agents, car dealers, bakers, plumbers, electricians and other contractors, retail stores, movers, babysitters, school tutors, and so forth – you name it. They would also apply to prevent individuals whose business life blood relies on third party recommendations from reaching out electronically to prospective new clients. For example, a real estate agent could not email a friend of a satisfied customer for a potential listing at the suggestion of the customer. Nor could a stockbroker make a “cold email call” to a friend of a customer at the suggestion of the customer.</p>
<p>It is also obvious that CASL could apply also to a myriad of other situations in which email or other electronic means are used in relation to a commercial activity. For example it could apply to a kid trying to buy or sell a baseball or hockey card; a student trying to buy or sell high school, college or university used textbooks; a mother trying to hire a new babysitter; or a kid soliciting a parent of a friend to shovel snow or mow a lawn for some extra cash. It goes on and on – you can only imagine.</p>
<p>CASL also makes it illegal for anyone to &#8220;aid, induce, procure or cause to be procured&#8221; breaching the anti-spam and its other provisions. Accordingly, it would also be illegal for a parent to help his or her child buy or sell the baseball or hockey card or the school textbooks or to solicit customers for snow shoveling by electronic means. Conceivably, providing access to a home computer with permission to use it for these purposes could be enough to create liability.</p>
<p>CASL and its strictures could apply to an unlimited and unpredictable set of activities engaged in by individuals, professionals, and large and small businesses including start-up businesses. Yet, its list of exceptions is narrow and can only change through a slow reactive regulatory process. Meanwhile, kids selling baseball cards or trying to make some needed money cutting grass, students trying to buy a used textbook to save money, mothers trying to hire babysitters for a needed night out, and others would have to set up websites, establish unsubscribe mechanisms and publically disclose their personal information on the web to try and comply with CASL just to do those basic things.</p>
<p>While on vacation I also thought about the occasional emails I get from my local cottage street association asking for a financial donation to help fund issues of importance to our neighborhood (my cottage is close to the riding of Minister Clement, who was originally the Minister responsible for CASL). Sending these emails will become illegal under CASL. No one has expressly consented to receiving them. But, it is implied, or at least inferred, by most everyone that such emails are wanted. In some cases the individuals receiving the emails would have “personal relationships” (as defined in the draft Industry Canada regulations) with the street volunteer who sends out the emails. In some cases they would not. None of the other exceptions in CASL would apply to dispense with obtaining express consents to send out the  emails. The local street volunteer is also unlikely to want to disclose his or her PIPEDA protected personal information merely to send emails to members of the street “association”. The street volunteer is also unlikely to be able to comply with CASL’s formality requirements which include having a web address and a formal unsubscribe mechanism.  (So will many unregistered charities which will also be very significantly impacted by the restrictions in CASL.) So, when CASL comes into force, the street volunteer will either likely continue as before illegally, or stop because CASL stifles using electronic means of communication.</p>
<p>The volunteer may need think long and hard before violating CASL, however, because the penalties for violation can be severe. Every person who contravenes any of anti-spam provisions can be liable for a fine (an administrative monetary penalty or AMP). The maximum penalty per violation is a $1,000,000 in the case of an individual, and $10,000,000 in the case of any other person. A person who merely aids in the violation &#8211; for example, the parent who helps a child get a snow shoveling job &#8211; can be liable for a fine of up to the same $1 million dollar maximum per violation. CASL also subjects individuals to damages and penalties under the private right of action provisions. The penalties can reach a maximum of $200 for each contravention not to exceed $1,000,000 for each day on which it occurred.</p>
<p>It is highly unlikely that the CRTC would seek the maximum penalties against individuals for some of the activities described here, assuming it even decided to prosecute individuals for some of these kinds of transgressions. However, individuals who know about these potential fines – such as the dentist who is asked for a recommendation or the street volunteer- might well decide that the risks associated with CASL to them outweigh the socially beneficial activities they were inclined to engage in.</p>
<p>It is ironic that under the <a href="http://www.barrysookman.com/2011/10/03/some-observations-on-bill-c-11-the-copyright-modernization-act/">Bill-C-11</a> (<em>The Copyright Modernization Act</em>) , the Government plans to lower the current cap on statutory damages from a maximum of $20,000 for each work infringed in the proceeding to a maximum $5,000 for all works infringed where the infringement is for a non-commercial purpose. Yet, when it comes to CEMs, CASL would make individuals liable for up to $1 million dollars per violation.</p>
<p>It is hard to imagine that Parliament could have intended to make electronic communications responding to requests for recommendations for needed information illegal. Nor is it conceivable that Parliament intended to make it illegal for local neighborhood associations to communicate electronically. Nor is it likely that many of the other problems described here could have been intended by Parliament. I very much doubt, for example, that Parliament intended to make kids buying or selling baseball cards or mothers trying to hire babysitters, or people trying to help them with these things, worry about CASL. But, CASL potentially affects everyone.</p>
<p>My colleague Lorne Salzman and I have pointed out elsewhere, that CASL will have many more unintended consequences including:</p>
<blockquote><p>1)      FISA will impede start-up businesses from launching in Canada.</p>
<p>2)      FISA will impede Canadian businesses from developing new marketing models over the Internet.</p>
<p>3)      FISA will deter suppliers of service providers, including outsourcing and cloud service providers, from operating with or maintaining facilities in Canada.</p>
<p>4)      FISA will deter foreign businesses from offering their products to Canadians via the Internet, mobile and other communications networks.</p>
<p>5)      FISA will impose costs and restrictions on Canadian businesses that their competitors outside Canada will not have to bear.</p>
<p>6)      FISA contains very strong incentives for Canadian businesses to confess wrong-doing, even in cases of questionable or trivial conduct, thereby tarnishing the reputation of legitimate businesses in circumstances<em> </em>where the offending conduct is not significant.<a href="file:///C:/MyFiles/blogs/DOCS-%2311044671-v8-Sookman_CASL_Blog_Dentist%20DOC.doc#_ftn6">[6]</a><em> </em></p></blockquote>
<p>Numerous organizations filed detailed submissions with <a href="http://fightspam.gc.ca/eic/site/030.nsf/eng/00210.html">Industry Canada</a> and the <a href="https://services.crtc.gc.ca/pub/ListeInterventionList/Default-Defaut.aspx?en=2011-400&amp;dt=c&amp;Lang=e">CRTC</a> in response to the draft regulations. They pointed out a multitude of unintended consequences with CASL that would make doing business in Canada electronically difficult, expensive, and in some cases impossible. The submissions pointed out how CASL could stifle innovation and put Canada at a competitive disadvantage relative to our trading partners, none of which have taken such an onerous or prescriptive approach to regulating electronic commerce. A summary of the comments can be found <a href="http://www.barrysookman.com/2011/09/20/electronic-commerce-protection-regulations-%E2%80%93-much-work-remains/">here</a>. The Government is currently reviewing these submissions to determine if changes to the regulations, or additional regulations, are required to address these problems.</p>
<p>The problems identified above can be somewhat alleviated by adding new exceptions to CASL by regulation. However, regulations which merely incrementally add more narrow exceptions to address newly identified problems will not solve the fundamental structural problem with CASL. CASL bans all commercial speech in the form of commercial electronic messages – whether wanted or unwanted – unless the specific class of the message falls into an identified exception, and unless its strictures are also met. This approach inevitably will ban some – probably a lot of – desirable and constitutionally protected speech. Incrementally creating new exemptions to address newly recognized impingements on commercial speech will not solve the structural problems with CASL. It would be playing wac-a-mole with basic freedoms of Canadians. (CASL takes the same “ban-all” approach to computer programs, making illegal the installation of any program –good or bad- without express consent and compliance with other requirements.)</p>
<p>The approach CASL takes to commercial speech is akin to trying to prevent crime by making it an offense for citizens to leave their homes except for purposes that are listed as exemptions in the Criminal Code or in regulations – regulations that incrementally grow in number as new non-criminal activities are identified. It would be easy to name obvious initially exempt purposes such as work, school, and sports. But, with the myriad of diverse human activities, an unforeseeable plethora of legitimate activities that individuals expect can be legally engaged in in a free and democratic society would be criminalized. For example, if going camping, bird watching, or attending the annual Santa Claus parade were not in the class of exempted activities, it would be illegal to do them until the Government enacts new regulations to exempt them. The same is true with CASL.</p>
<p>One of the greatest problems with CASL is that it will chill and make legitimate commercial speech illegal. It will undermine fundamental freedoms protected by the <em>Charter of Rights and Freedoms</em>. My colleague Lorne Salzman and I raised this issue previously. So did a number of entities who made submissions to Industry Canada and the CRTC on the draft regulations.<a href="file:///C:/MyFiles/blogs/DOCS-%2311044671-v8-Sookman_CASL_Blog_Dentist%20DOC.doc#_ftn7">[7]</a></p>
<p>Following the Supreme Court of Canada’s decision in the <em>Reference re Securities Act</em>, <a href="http://canlii.ca/t/fpdw">2011 SCC 66</a> case, questions might also be asked about the Federal Parliament’s constitutional jurisdiction to enact major portions of CASL including the anti-spam, anti-spyware, and address harvesting provisions. It may be that CASL would do better than the proposed national security regulator proposal as it does not interfere with property and establishes rules to address threats to commerce. However, it does regulate matters of a contractual nature such as consents and disclosures related to contractual activities and has similarities to provincial consumer protection legislation.</p>
<p>In light of the very substantial questions about, and problems with, CASL, once its regulations are finalized, the Government should consider referring the constitutionality of CASL including its compliance with the <em>Charter</em> <em>of Rights and Freedoms</em> to the Supreme Court of Canada.</p>
<p>Of course, steps could be taken to fix CASL before it is proclaimed into force. These measures could also help CASL survive the inevitable <em>Charter</em> challenge once it becomes law. But, merely tinkering with CASL through the regulatory process will not be enough. And it certainly won&#8217;t help you if you need a dentist when out of town.</p>
<hr size="1" /><a href="file:///C:/MyFiles/blogs/DOCS-%2311044671-v8-Sookman_CASL_Blog_Dentist%20DOC.doc#_ftnref1">[1]</a> Descent are of two sorts, <em>lineal and collateral</em>.  Lineal descent is descent in a direct or right line, as from father to grandfather to son or grandson. Collateral descent is descent in a collateral or oblique line, that is, up to the common ancestor and then down from him, as from brother to brother, or between cousins. <em>Num v. Canada (Citizenship and Immigration)</em>, <a href="http://canlii.ca/t/1zh4z">2005 CanLII 62936</a>, <em>Burnaby Lake Greenhouses v. Her Majesty The Queen In Right Of The Province Of British Columbia</em>, <a href="http://canlii.ca/t/1m4r1">2005 BCSC 1682</a>.</p>
<p><a href="file:///C:/MyFiles/blogs/DOCS-%2311044671-v8-Sookman_CASL_Blog_Dentist%20DOC.doc#_ftnref2">[2]</a> See Wikipedia “Cousins” http://en.wikipedia.org/wiki/Cousin</p>
<p><a href="file:///C:/MyFiles/blogs/DOCS-%2311044671-v8-Sookman_CASL_Blog_Dentist%20DOC.doc#_ftnref3">[3]</a> Individuals can give express consent under PIPEDA in several ways. For example:</p>
<p>(a) an application form may be used to seek consent, collect information, and inform the individual of the use that will be made of the information. By completing and signing the form, the individual is giving consent to the collection and the specified uses;</p>
<p>(b) a checkoff box may be used to allow individuals to request that their names and addresses not be given to other organizations. Individuals who do not check the box are assumed to consent to the transfer of this information to third parties;</p>
<p><a href="file:///C:/MyFiles/blogs/DOCS-%2311044671-v8-Sookman_CASL_Blog_Dentist%20DOC.doc#_ftnref4">[4]</a> See, Collection and Debt Repayment Practices Regulation, Alta Reg 194/1999, (Fair Trading Act) Consolidated Regulations of Alberta; Regulation respecting the Taxation Act, RRQ, c I-3, r 1; Income Tax Regulations, CRC, c 945, (Income Tax Act) Consolidated Regulations of Canada</p>
<p><a href="file:///C:/MyFiles/blogs/DOCS-%2311044671-v8-Sookman_CASL_Blog_Dentist%20DOC.doc#_ftnref5">[5]</a> See, <a href="http://www.barrysookman.com/2011/09/07/fixing-casl-comments-on-the-draft-crtc-and-industry-canada-regulations/">Fixing CASL: comments on the draft CRTC and Industry Canada regulations</a><strong>; </strong><a href="http://www.barrysookman.com/2011/09/20/electronic-commerce-protection-regulations-%E2%80%93-much-work-remains/">Electronic Commerce Protection Regulations – Much Work Remains</a>; <a href="http://www.barrysookman.com/2011/05/25/rethinking-fisa/">Rethinking FISA</a></p>
<p><a href="file:///C:/MyFiles/blogs/DOCS-%2311044671-v8-Sookman_CASL_Blog_Dentist%20DOC.doc#_ftnref6">[6]</a> See, <a href="http://www.barrysookman.com/2011/09/07/fixing-casl-comments-on-the-draft-crtc-and-industry-canada-regulations/">Fixing CASL: comments on the draft CRTC and Industry Canada regulations</a><strong>; </strong><a href="http://www.barrysookman.com/2011/09/20/electronic-commerce-protection-regulations-%E2%80%93-much-work-remains/">Electronic Commerce Protection Regulations – Much Work Remains</a>; <a href="http://www.barrysookman.com/2011/05/25/rethinking-fisa/">Rethinking FISA</a></p>
<p><a href="file:///C:/MyFiles/blogs/DOCS-%2311044671-v8-Sookman_CASL_Blog_Dentist%20DOC.doc#_ftnref7">[7]</a> <a href="http://www.barrysookman.com/2011/05/25/rethinking-fisa/">Rethinking FISA</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.barrysookman.com/2012/01/03/will-it-be-illegal-to-recommend-a-dentist-under-canada%e2%80%99s-new-anti-spam-law-casl/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Canada’s new anti-spam Law: too much of a good thing?</title>
		<link>http://www.barrysookman.com/2011/10/17/canada%e2%80%99s-new-anti-spam-law-too-much-of-a-good-thing/</link>
		<comments>http://www.barrysookman.com/2011/10/17/canada%e2%80%99s-new-anti-spam-law-too-much-of-a-good-thing/#comments</comments>
		<pubDate>Mon, 17 Oct 2011 14:55:38 +0000</pubDate>
		<dc:creator>Lorne Salzman and Barry Sookman</dc:creator>
				<category><![CDATA[Bill C-28]]></category>
		<category><![CDATA[CASL]]></category>
		<category><![CDATA[FISA]]></category>
		<category><![CDATA[FIWSA]]></category>
		<category><![CDATA[spam]]></category>
		<category><![CDATA[spyware]]></category>
		<category><![CDATA[canada's anti-spam law]]></category>

		<guid isPermaLink="false">http://www.barrysookman.com/?p=3759</guid>
		<description><![CDATA[Here is a copy of the op-ed published by The Hill Times today on CASL.
Most people would agree that unwanted commercial emails – commonly called spam – are awful. Spam wastes our time. It clogs our inboxes and can be full of scams, malware and fraudulent, false and misleading messages. So who wouldn’t have cheered [...]]]></description>
			<content:encoded><![CDATA[<p>Here is a copy of the op-ed published by <a href="http://hilltimes.com/opinion-piece/2011/10/17/canada%E2%80%99s-new-anti-spam-law-too-much-of-a-good-thing/28468">The Hill Times </a>today on CASL.</p>
<p>Most people would agree that unwanted commercial emails – commonly called spam – are awful. Spam wastes our time. It clogs our inboxes and can be full of scams, malware and fraudulent, false and misleading messages. So who wouldn’t have cheered when Canada finally decided to outlaw spam and related afflictions?</p>
<p>With the September 7 conclusion of the public comment period on the new anti-spam law, known as CASL (for Canada’s anti-spam law), Canada has taken a major step toward finalizing legislation designed to outlaw practices such as sending commercial electronic messages without recipients’ consent or using misleading information in the online promotion of products. Reason to celebrate, one would think.</p>
<p>But those who have studied the bill and its consequences more closely have concluded that there might not be as much to cheer about after all, with CASL potentially having a number of negative effects on the Canadian businesses and consumers it seeks to protect.</p>
<p>In its current guise, CASL will provide Canadians with the toughest anti-spam law in the world. Some of the restrictions that will be imposed by CASL include requirements related to messaging consents, message formalities, working with third parties, technical compliance and the updating of messaging systems.</p>
<p>However, while this may seem all well and good, its implementation could lead to potentially substantial costs for Canadian businesses because our anti-spam law will be much more onerous than similar legislation in any other country, including any other G20 country.</p>
<p>So what are the costs of CASL and the draft regulations as currently drafted? In addition to the dollar outlays that Canadian businesses will have to bear to comply with CASL, the new law will have a number of other unwelcome consequences.</p>
<p>These include impeding start-up businesses from launching in Canada. Start-ups do not have ready-to-use email lists and the new legislation will greatly hinder the ability to develop these from scratch or source them from a third party. Canada, which already suffers from insufficient entrepreneurial activity, should not be placing new hurdles in the way of budding entrepreneurs, but this is precisely what CASL will do.</p>
<p>There will also be issues for Canadian business looking to develop new Internet-based marketing models. CASL was designed to address email spam, and its requirements do not easily fit with social networks such as Twitter, referral marketing and other more modern vehicles for transmitting commercial electronic messages. Sadly, it appears CASL is already in danger of becoming antiquated thanks to social networking.</p>
<p>CASL will likely also discourage some server operators, including outsourcing and cloud service providers, from operating facilities in Canada. Any business that sends commercial electronic messages from a server in Canada will be caught by CASL, even where the recipient is outside the country. Accordingly, companies that wish to send messages to non-Canadians, but avoid restrictions, will want to do so from servers outside Canada. This cannot be a good thing.</p>
<p>CASL will deter some foreign businesses, notably social network companies, from offering their products to Canadians, as they may find it too onerous to comply with the new law. Canadian consumers will lose out while foreign competitors with less stringent anti-spam legislation will pick up the pieces.</p>
<p>Perhaps worst of all, it is also likely that some legitimate and even useful online communication will be prohibited due to the wide scope of the bill. This means CASL could be challenged as presenting an infringement of the protection of free expression in the <em>Canadian Charter of Rights and Freedoms</em>. If proven, CASL would be undermined, leading to inevitable amendments and further compliance costs for Canadian businesses.</p>
<p>Many of these shortcomings have been addressed in the public comments recently submitted to the Canadian Radio-television and Telecommunications Commission and Industry Canada. Unfortunately, it appears that CASL could succeed in partially stemming the deluge of spam, but at the same time create a series of much greater problems for Canadian businesses and consumers.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.barrysookman.com/2011/10/17/canada%e2%80%99s-new-anti-spam-law-too-much-of-a-good-thing/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Electronic Commerce Protection Regulations – Much Work Remains</title>
		<link>http://www.barrysookman.com/2011/09/20/electronic-commerce-protection-regulations-%e2%80%93-much-work-remains/</link>
		<comments>http://www.barrysookman.com/2011/09/20/electronic-commerce-protection-regulations-%e2%80%93-much-work-remains/#comments</comments>
		<pubDate>Tue, 20 Sep 2011 13:13:19 +0000</pubDate>
		<dc:creator>Lorne Salzman and Barry Sookman</dc:creator>
				<category><![CDATA[Bill C-28]]></category>
		<category><![CDATA[CASL]]></category>
		<category><![CDATA[Electronic Commerce Protection Act (ECPA)]]></category>
		<category><![CDATA[FISA]]></category>
		<category><![CDATA[FIWSA]]></category>
		<category><![CDATA[cloud computing]]></category>
		<category><![CDATA[spam]]></category>
		<category><![CDATA[spyware]]></category>
		<category><![CDATA[c-28]]></category>
		<category><![CDATA[crtc regulations]]></category>

		<guid isPermaLink="false">http://www.barrysookman.com/?p=3624</guid>
		<description><![CDATA[Canada’s new anti-SPAM/anti-malware law, or CASL, was passed by Parliament in late 2010.  The draft Electronic Commerce Protection Regulations, which were intended to clarify and flesh out the law, were published for public consultation earlier this summer.  Fifty-seven organizations and individuals filed comments by the September 7, 2011 deadline.  The message from these commentators is [...]]]></description>
			<content:encoded><![CDATA[<p>Canada’s new anti-SPAM/anti-malware law, or <a href="http://lois-laws.justice.gc.ca/eng/AnnualStatutes/2010_23/FullText.html">CASL</a>, was passed by Parliament in late 2010.  The draft Electronic Commerce Protection Regulations, which were intended to clarify and flesh out the law, were published for public consultation earlier this summer.  Fifty-seven organizations and individuals filed comments by the September 7, 2011 deadline.  The message from these commentators is clear: while all support the goal of reducing unwanted commercial electronic messages (CEMs) and malware, the draft regulations miss the mark, and much work remains before CASL can be proclaimed into law.</p>
<p>The CRTC and Industry Canada initiated the public consultation process by issuing the draft regulations in June and July 2011 respectively. Each organization published their own draft regulations as each has distinct regulation-making powers under CASL. The CRTC promptly <a href="https://services.crtc.gc.ca/pub/ListeInterventionList/Default-Defaut.aspx?en=2011-400&amp;dt=c&amp;Lang=e">published</a> on its website all the comments that it received. Industry Canada indicated it will follow suit shortly. That said, most of the commentators submitted combined comments on the two sets of draft regulations, and thus the CRTC filings give a good picture of what has been submitted to Industry Canada as well.</p>
<p>Fifty-seven trade and public interest organizations, businesses, and individuals filed comments with the CRTC. Most of the commentators represented Canadian businesses, large and small. Many industry associations filed comments, including: Association of Canadian Advertisers (ACA), Association of International Automobile Manufactuers of Canada (AIAM), Canadian Bankers Association, Canadian Bar Association (CBA), Canadian Chamber of Commerce, (The Chamber), Canadian Federation of Independent Business (CFIB), Canadian Life and Health Insurance Association (CLHIA), Canadian Manufacturers &amp; Exporters (CME), Canadian Marketing Association (CMA), Canadian Real Estate Association (CREA), Canadian Vehicle Manufacturers&#8217; Association (CVMA), Canadian Wireless Telecommunications Association CWTA), Direct Sellers Association of Canada (DSAC),  Entertainment Software Association of Canada (ESAC), The Financial Advisors Association of Canada (FAAC), Information Technology Association of Canada (ITAC),  Insurance Bureau of Canada (IBC), Investment Industry Association of Canada (IIAC), Magazines Canada, Ontario Telecommunications Association (OTA), Retail Council of Canada (RCA), and The Investment Funds of Canada (IFC). A number of individual businesses also submitted comments, including: AVLA Audio-Video Licensing Agency Inc. (AVLA), Bell Canada, Johnson &amp; Johnson Family of Companies in Canada (J&amp;J), Microsoft Canada Inc. (Microsoft),  Primerica Financial Services, Re:Sound, Research In Motion Limited (RIM),  Rogers Communications Partnership (Rogers), Shaw Cablesystems G.P. (Shaw), Tbaytel, TELUS Communications Company (Telus),  and Wells Fargo &amp; Company. Together these organizations represent hundreds of thousands of Canadian businesses.</p>
<p>Two consumer organizations filed comments: Public Interest Advocacy Centre/ Option consummateurs (PIAC) and Union des consummateurs.</p>
<p>Some individuals also filed comments. Among them, we personally<strong> </strong><a href="http://www.barrysookman.com/2011/09/07/fixing-casl-comments-on-the-draft-crtc-and-industry-canada-regulations/">filed</a><strong> </strong>detailed comments with the CRTC and Industry Canada. These comments followed on from an<strong> </strong><a href="http://www.barrysookman.com/2011/05/25/rethinking-fisa/">earlier paper</a><strong> </strong>that we published suggesting that CASL needed rethinking.<strong> </strong></p>
<p>Canadian businesses all agreed with the goal of reducing unwanted CEMs, or “SPAM”, and malware, but most expressed concern that the proposed regulations contain significant problems that need to be addressed. In some cases, the problems are those of omission, namely failure to set out needed exemptions or needed clarifications. In other cases, the regulations impose requirements that are unworkable or unduly cumbersome and expensive to operate.</p>
<p>The purpose of this paper is to briefly describe and summarize the key positions parties submitted in their filings with the CRTC, with a particular focus on the concerns expressed by Canadian businesses and their representative associations. Distilled to the essence, their comments identify the following concerns:</p>
<p>1. Although all parties support the goal of reducing SPAM and malware, most considered that the draft regulations fail to address the overreach inherent in CASL. Consequently, CASL plus its regulations are a disproportionate response to the acknowledged problems of SPAM and malware.</p>
<p>2. Although many commentators had expected that the proposed regulations would target truly offensive conduct under CASL and, as well, clarify ambiguities, thereby enabling the law to better meet the Government’s objectives, this has not occurred. The proposed regulations fail to set out worthwhile classes of exempt conduct, and they impose extra compliance costs that many businesses found troubling.</p>
<p>3. Under CASL and the proposed regulations, some inoffensive communications will become illegal, an overreach that will invite challenges under the freedom of speech provisions of the Canadian Charter of Rights and Freedom, with unpredictable results.</p>
<p>4. The proposed regulations do not remedy the concerns that CASL will hinder the start up and growth of small business.</p>
<p>5. The proposed regulations do not look beyond CASL’s “email-focused” model and consequently they fail to fit well with other messaging systems. As a result, CASL is not technologically neutral in its regulatory approach.</p>
<p>6. The proposed regulations fail to address messaging systems where SPAM is not a problem, such as Common Short Code Messaging, Opt-in Instant Messaging and similar systems, and where the additional regulation would impose costs, be impractical or impossible to comply with.</p>
<p>7. The proposed regulations fail to address CASL&#8217;s territorial overreach, and the consequent risk to investment and innovation in cloud computing and outsourcing in Canada.</p>
<p>8. The proposed regulations fail to properly clarify what is included under the definition of a CEM, thereby subjecting non-CEMs to CASL’s unsubscribe and formality requirements.</p>
<p>9. The proposed regulations fail to recognize the value of other, reasonable, approaches to obtaining consent to send CEMs, such as under existing PIPEDA rules.</p>
<p>10.The proposed regulations fail to clear the confusion in CASL between holders of message accounts and recipients of messages.</p>
<p>11.The proposed regulations stipulate that requests for consent be in writing, a requirement that is both limiting and, in some cases, impractical.</p>
<p>12.Most commentators criticized as unworkable the CRTC’s proposed regulation which requires that each CEM and each request for consent to send a CEM include the physical and mailing address, a telephone number providing access to an agent or a voice messaging system, an email address and a web address of the sender and any other electronic address used by the sender.</p>
<p>13.The CRTC’s proposed regulation requiring that each request for consent include a statement that a consent can be withdrawn using any of the mandatory contact information is contrary to CASL and is unworkable. It would require organizations to monitor physical and mailing addresses, a telephone number, an email address and a web address and any other electronic address used by those persons.</p>
<p>14.The CRTC’s proposed regulation is unworkable where it requires that request for consent must be sought separately for each act described in sections 6 to 8 of CASL.</p>
<p>15.The CRTC’s proposed regulation permitting prescribed information to be made available on the web is not a practical or technologically neutral solution to the disclosure requirement problems created by CASL and the proposed regulations.</p>
<p>16.The proposed regulations fail to accommodate a business that does not maintain a web site from receiving unsubscribe requests. Further, the CRTC’s proposed regulation requiring the unsubscribe mechanism be performed in no more than two clicks is not technologically neutral or workable in many circumstances.</p>
<p>17.The heightened consent requirements in Section 5 of the draft CRTC regulations for computer programs that perform one of the functions listed in Section 10(5) is unworkable. It is impractical to require that such consents be in writing or to require the ser provide an acknowledgement. Further, there are many circumstances in which meeting these requirements would be either technically or commercially unfeasible.</p>
<p>18.Certain of the CRTC’s proposed regulations may be beyond the CRTC’s authority under CASL.</p>
<p>In the following, we expand on the concerns with the proposed regulations that have been identified by Canadian businesses and their representatives.</p>
<p>1. <span style="text-decoration: underline;">Although all parties support the goal of reducing SPAM and malware, most considered that the draft regulations fail to address the overreach inherent in CASL. Consequently, CASL plus its regulations are a disproportionate response to the acknowledged problems of SPAM and malwar</span><span style="text-decoration: underline;">e</span>.</p>
<p>Although commentators agreed that containing the flood of SPAM and malware is desirable, CASL and the proposed regulations will impose costs and inefficiencies on Canadians that exceed the benefits. These costs and inefficiencies are significant. They are not just the substantial compliance costs that Canadian businesses must bear.  They extend to impeding the use of electronic means of communicating, putting Canadian businesses at competitive disadvantages to their foreign competitors, retarding the growth of small and start-up businesses, and potentially limiting the use by Canadian businesses of modern messaging platforms.</p>
<p>A key source of the problem is the design of CASL. Its approach is to forbid practically all commercial electronic messages, and then prescribe certain exemptions in both the law and the regulations. Thus, rather than targeting truly offensive conduct in the first place, the law and proposed regulations are based on the sweeping proposition that, in effect, nothing is permitted except that which is specifically allowed.  CASL takes the same prohibitory approach to regulating the installation of computer programs on computers, mobile phones, tablets and other devices.</p>
<p>The Chamber, which represents over 192,000 Canadian businesses, had this to say:</p>
<blockquote><p>“The Act and proposed Regulations do not adequately balance the objective of preventing unwanted, or harmful behaviour with the objectives of ensuring that perfectly legitimate acts are not made illegal, and preserving the vitality of the Internet for electronic commerce. Furthermore, they introduce conflicting or unnecessary regulatory regimes that needlessly impose significant costs on legitimate business.”</p></blockquote>
<blockquote><p>”The overly broad language in both the Act and the proposed regulations could circumscribe legitimate business-to-business activities and inadvertently impact businesses ability to deliver products and services to consumers.”</p></blockquote>
<blockquote><p>“The over-broad scope of the Act and proposed Regulations, the lack of exceptions for socially valuable activities, unwieldy consent requirements, administrative monetary penalties and statutory damage provisions that have little relation to actual harm suffered may collectively have the opposite effect: rather than promoting Canada&#8217;s digital economy, the Act and proposed Regulations may actually create significant impediments to electronic commerce and the development of the digital sector.”</p></blockquote>
<p>The Canadian Federation of Independent Business (CFIB) which represents over 108,000 small business owners from coast-to-coast commented as follows:</p>
<blockquote><p>“This new level of regulation and oversight on industry seems contrary to the government&#8217;s stated objectives to encourage entrepreneurial growth and reduce the regulatory burden”, based on their announcements earlier this year designating 2011 the Year of the Entrepreneur, and the creation of the Red Tape Reduction Commission to tackle red tape”.</p></blockquote>
<p>The Canadian Wireless Telecommunications Association (CWTA) is the authority on wireless issues, developments and trends in Canada.  It represents cellular, PCS, messaging, mobile radio, fixed wireless and mobile satellite carriers as well as companies that develop and produce products and services for the industry. It had this to say:</p>
<blockquote><p>“The Act and the proposed Regulations are highly prescriptive and create a high degree of regulation for legitimate commercial messages.  This will result in significant compliance costs for businesses that communicate with their customers electronically”.</p></blockquote>
<blockquote><p>“No one wants to permit true spammers to continue operating unfettered, but it would be antithetical if the result of the Regulations were to dampen bona fide electronic business activities”.</p></blockquote>
<p>The Entertainment Software Association of Canada (ESAC) represents Canada’s leading interactive entertainment software publishers and distributors, which collectively accounted for more than 90 per cent of the $2 billion in entertainment software and hardware sales in Canada in 2009. It stated as follows:</p>
<blockquote><p>“We are deeply concerned that the extremely broad application of the Act to all forms of electronic messaging and software, the often onerous and inflexible requirements and the potential for massive, multi-million dollar liability for inconsequential breaches, will have a negative impact on the growth of electronic commerce in Canada that outweighs the benefits.”</p></blockquote>
<p>2. <span style="text-decoration: underline;">Although many commentators had expected that the proposed regulations would target truly offensive conduct under CASL and, as well, clarify ambiguities, thereby enabling the law to better meet the Government’s objectives, this has not occurred. The proposed regulations fail to set out worthwhile classes of exempt conduct, and they impose extra compliance costs that many businesses found troubling</span>.</p>
<p>In introducing CASL at <a href="http://openparliament.ca/hansards/2290/187/only/">second reading</a>, Minister Clement stated that CASL’s purpose “is not to limit legitimate online business. It is to promote electronic commerce by increasing confidence in the use of the Internet to carry out business transactions”. CASL was passed to “deter the most damaging and deceptive forms of SPAM from occurring in Canada and help drive spammers out of Canada”<a href="http://www.barrysookman.com/wp-includes/js/tinymce/plugins/paste/pasteword.htm?ver=327-1235#_ftn3"><strong><strong>[3]</strong></strong></a> and to encourage the use of electronic means to carry of commercial activities.<a href="http://www.barrysookman.com/wp-includes/js/tinymce/plugins/paste/pasteword.htm?ver=327-1235#_ftn4"><strong><strong>[4]</strong></strong></a> These goals were intended to be accomplished without negatively impacting legitimate businesses that use electronic means to market their products and services to Canadians.<a href="http://www.barrysookman.com/wp-includes/js/tinymce/plugins/paste/pasteword.htm?ver=327-1235#_ftn5"><strong><strong>[5]</strong></strong></a></p>
<p>With appropriate regulations, CASL could go a long distance to achieving its goal of deterring the most damaging and deceptive forms of SPAM and help drive spammers out of Canada. However, virtually all business commentators contended that the proposed regulations miss the mark. They do not address the issue of overreach by establishing categories of exempt conduct. Moreover, the proposed regulations add to the difficulty and cost of compliance with CASL.</p>
<p>The costs and inefficiencies are significant. They are not just the substantial compliance costs that Canadian businesses must bear.  They extend to impeding the use of electronic means of communicating, putting Canadian businesses at competitive disadvantages to their foreign competitors, retarding the growth of small and start-up businesses, and potentially limiting the innovation and use by Canadian businesses of modern messaging platforms.</p>
<p>The Canadian Marketing Association (CMA) is the national voice for Canada’s marketing community. It stated the following about the regulations:</p>
<blockquote><p>“The proposed rules, as well as those published by Industry Canada, are problematic, cumbersome and ultimately serve to negatively impact legitimate marketing practices in Canada with consequent negative economic impact.”</p></blockquote>
<p>The Canadian Bankers Association represents over 50 banks and lending institutions in Canada. The association was critical of the proposed regulations, stating as follows:</p>
<blockquote><p>“The stated goal of the CRTC Draft Regulations is to clarify the required content and form of commercial electronic messages (&#8220;CEM&#8221;) and the request for consent under the Act. It is disappointing, however, and a cause for concern, that the CRTC Draft Regulations do not address some of the operational challenges created by the requirements of the Act”.</p></blockquote>
<blockquote><p>“Several additional requirements and a number of undefined terms have been introduced in the CRTC Draft Regulations that we believe are problematic for business, exceed best marketing practices, do little to protect customers from SPAM or malicious software and, therefore, should be reconsidered”.</p></blockquote>
<blockquote><p>“Our members anticipate significant planning and resource implications with respect to the implementation of the Anti-SPAM Act and the related Regulations (particularly with respect to technology systems and processes).”</p></blockquote>
<p>Commentators strongly proposed that Industry Canada use the broad regulatory powers conferred on the Governor in Council by Section 64(1) to fix CASL to enable it to a achieve its objectives. The Chamber stated as follows:</p>
<blockquote><p>“Several of the most problematic and unwieldy requirements imposed by the Act can be addressed by the introduction of judicious regulation that provides &#8216;greater flexibility and exempts legitimate forms of electronic communications.”</p></blockquote>
<blockquote><p>“The more details that the CRTC can provide, through regulations or interpretation guidelines, and the more flexibility that is added to the regime, the less the impact on legitimate businesses and the smoother the transition to the new regime will be, especially for small businesses across Canada.”</p></blockquote>
<blockquote><p>“Using the regulations to achieve a reasonable balance of costs and benefits will be critical if unintended impacts, such as deterring suppliers of services, impeding businesses from developing new marketing strategies involving electronic communications and creating material costs and restrictions on enterprises carrying on business in Canada, are to be avoided.”</p></blockquote>
<p>3. <span style="text-decoration: underline;">Under CASL and the proposed regulations, some inoffensive communications will become illegal, an overreach that will invite challenges under the freedom of speech provisions of the Canadian Charter of Rights and Freedom, with unpredictable results</span>.</p>
<p>CASL prescriptive approach to regulating commercial speech will see the banning of all commercial electronic messages unless they are sent with express consent, or a consent which falls into an exclusive list of exceptions for which consent is deemed to be implied or not to be required and unless they comply with onerous, and sometimes impossible to meet, form, disclosure, and unsubscribe requirements. This wide regulatory sweep is bound to impinge on legitimate and beneficial commercial speech  thereby raising concerns as to compliance with the Canadian Charter of Rights and Freedoms.</p>
<p>RIM, one of Canada’s leading telecommunications companies, articulated this concern as follows in a brief that thoroughly commented on the proposed regulations:</p>
<blockquote><p>“RIM notes that CASL’s approach to SPAM is to broadly prohibit the sending of all CEMs unless the messages are sent with express consent or fall into an excluded category.  It does not prohibit just the sending of only unwanted, false, fraudulent, misleading or otherwise harmful messages. Its “ban all unless allowed” structure guarantees that some legitimate and useful commercial speech will be become illegal. This restriction on legitimate CEMs, ultimately when challenged, will have to pass the scrutiny of the Canadian Charter of Rights and Freedoms. The limits on commercial speech imposed by CASL must be reasonable and justified, with minimal impairment of the free speech right and with the limits on free speech being in proportion to the harm that is being targeted.”</p></blockquote>
<blockquote><p>“In order to be consistent with the Charter and the intent of Parliament, the government must take steps in the regulations to ensure that legitimate online commercial activities are not unnecessarily hindered by CASL, while at the same time curtailing real and harmful SPAM. Unchanged, CASL will not achieve, and would undermine, some of its most important objectives.”</p></blockquote>
<p>4. <span style="text-decoration: underline;">The proposed regulations do not remedy the concerns that CASL will hinder the start up and growth of small business</span>.</p>
<p>Under CASL, it will be illegal to send a commercial electronic message unless the individual or business sending the message establishes and maintains a web site to receive unsubscribe requests.<a href="http://www.barrysookman.com/wp-includes/js/tinymce/plugins/paste/pasteword.htm?ver=327-1235#_ftn6"><sup><sup>[6]</sup></sup></a><sup> </sup>Under the proposed CRTC regulations, the individual or business would have to have a physical and mailing address, a telephone number, an email address and a web address if it wants to obtain consents to send out CEMs or to send out a CEM. Not every individual or small business can meet these requirements.</p>
<p>Unlike established companies, start-up companies also do not have a ready list of electronic contacts they can approach to market their products and services.  Rather, they have to develop electronic lists from a variety of sources and use them to launch their products. Although few would find these activities offensive, they will all be potentially problematic under CASL.  Rather than using electronic communications, business start-ups will be forced to send their messages using the post or other more expensive and less convenient and efficient mechanisms, or limit the persons to whom they can send messages to the limited exception that permits use of conspicuously published e-mail addresses.</p>
<p>CFIB expressed its concern as to the impact of CASL and the proposed regulations on small businesses as follows:</p>
<blockquote><p>“The proposed regulatory regime “may make it more difficult for smaller businesses to start up and grow and may even hinder some small-and medium-sized enterprise (SME) members from providing better and more customized products for their clients”.</p></blockquote>
<blockquote><p>“The Draft Regulations propose that all communications must contain the following: the names of every party involved, physical and mailing address, a telephone number, an email address and a web address.</p></blockquote>
<p>The assumption is that every single business in Canada has a website, however only about half of small businesses have a website yet two-thirds use the web as part of their business.</p>
<p>Newer businesses trying to increase their customer base and garner revenue might not be able to initially spend money on a new website, but this requirement will force them to take time and money away from their priorities to comply with the rules”.</p>
<p>The Canadian Real Estate Association (CREA) is one of Canada&#8217;s largest single-industry trade associations, representing more than 100,000 real estate Brokers/agents and salespeople working through more than 100 real estate Boards and Associations. It stated the following:</p>
<blockquote><p>“The Draft Regulations raise compliance to impractical levels for small businesses and their clients, and they go beyond the scope and jurisdiction provided by the government to the CRTC.”</p></blockquote>
<blockquote><p>“The CRTC regulations are “putting up unreasonable barriers to legitimate commerce and eliminating legitimate business tools and communications practices for small business.   As a result, small business will be impeded and opportunities will be lost.””</p></blockquote>
<blockquote><p>“The requirement for senders of requests for consent and CEMs to include a web address effectively excludes persons unless they have a website.”</p></blockquote>
<blockquote><p>“Not all businesses that use email have websites – particularly small businesses – and to require a website is unnecessary, unfair, and costly.   In addition, consumers wishing to seek consent on behalf of another person would be prevented from doing so unless they had a web address.’</p></blockquote>
<p>5. <span style="text-decoration: underline;">The proposed regulations do not look beyond CASL’s “email-focused” model and consequently they fail to fit well with other messaging systems. As a result, CASL is not technologically neutral in its regulatory approach</span>.</p>
<p>Although CASL is supposed to be technologically neutral, applying broadly to all electronic means of sending electronic messages, the CASL regulatory regime is modelled on regulating electronic messages that are sent as emails. This focus on emails means that other forms of electronic messaging, such as instant messaging and those through social networks, do not easily fit within the CASL framework. As a result, Canadian businesses that wish to exploit new and developing alternative electronic messaging systems will be impeded by CASL.</p>
<p>The CMA noted this problem as follows:</p>
<blockquote><p>“In addition, there seems to be an underlying assumption that email communication is the sole or primary form of electronic communication covered by the Anti-SPAM Act.</p></blockquote>
<p>Notwithstanding the additional detail included in the CRTC Draft Regulations, we believe they fall short of properly accommodating other forms of electronic communication (e.g. SMS communications, instant messaging, text messaging).</p>
<p>Digital communications continue to evolve.  To be relevant, the statutory framework needs to &#8220;fit&#8221; with new and emerging digital constructs including SMS messages and social media based communications, and be flexible enough to accommodate future technologies.</p>
<p>The technologically specific regulatory requirements of CASL are also discussed below.</p>
<p>6. <span style="text-decoration: underline;">The proposed regulations fail to address messaging systems where SPAM is not a problem, such as Common Short Code Messaging, Opt-in Instant Messaging and </span><span style="text-decoration: underline;">s</span><span style="text-decoration: underline;">imilar </span><span style="text-decoration: underline;">s</span><span style="text-decoration: underline;">ystems, and where the additional regulation would impose costs, be impractical or impossible to comply with</span>.</p>
<p>The CASL regulatory regime is modelled on regulating electronic messages that are sent as emails. This focus on emails means that other forms of electronic messaging, such as those sent using opt-in messaging systems like RIM’s BBM, other social networks, and short form messaging systems like Short Code Messages social networks, do not easily fit within the CASL framework. Users who use opt-in messaging networks will face risks of offending CASL, and operators could face risks of aiding conduct that is contrary to CASL.</p>
<p>Social networks often operate under rules enforced by contract and by an administration that monitors and enforces compliance. As such, there are mechanisms in place to control unwanted commercial electronic messages. Where such protections are in place, CASL&#8217;s requirements are not needed, and can be counter-productive.  Faced with the risks of offending CASL, Canadian businesses will be wary of developing (or continuing to offer) innovative business models or implementing similar models that are legal in other countries such as the United States.</p>
<p>Numerous commentators asked for new classes of exceptions for these messaging systems. The CWTA stated the following on this point:</p>
<blockquote><p>“The Act, and therefore the Regulations have been framed on the basis that every Commercial Electronic Message will be an email.  For CWTA&#8217;s membership, this drafting bias causes a considerable challenge for compliance.”</p></blockquote>
<blockquote><p>“Compliances with the form requirements in the Act in the context of CSC messages could be exceedingly challenging in light of the severe constraints on message size (typically 136 or 140 characters )”.</p></blockquote>
<p>Telus which filed a very comprehensive brief to both sets of regulations, for example, stated the following:</p>
<blockquote><p>“By imposing an additional layer of regulation on top of existing governance regimes, CASL threatens to reduce the utility of certain modem messaging platforms, without having a material impact on the volume of SPAM experienced on those platforms (which is typically none).  These platforms, such as BlackBerry Messenger (BBM) and Common Short Code (CSC) SMS text messaging, are inherently opt-in environments with existing anti-abuse rules and tools that empower users to protect themselves from unwanted messages (in the unlikely event that they should receive any).”</p></blockquote>
<blockquote><p>“Application of CASL in these circumstances [where Canadians are already protected by other regimes, such as through contractual arrangements] would add an unnecessary and inefficient layer of regulation that would have little to no effect on actual SPAM or malware, and, to the contrary, could actually reduce the utility (and/or increase the cost) of electronic messaging and software installation for legitimate purposes.”</p></blockquote>
<p>RIM made the following submission on this point:</p>
<blockquote><p>“Some messaging platforms are “closed” such that users can only receive messages from others in an opt-in contact list.  For example, BlackBerry Messenger (BBM) is a strictly opt-in system. That is, users specifically invite contacts, or accept requests from contacts, before any messages can be sent between them.  As these messaging systems will not allow messages from senders that the user has not pre-approved, these types of “closed” platforms should be exempted from the requirements of CASL.</p></blockquote>
<blockquote><p>“RIM recommends such an exemption for at least three reasons.  First, the user has already consented to receiving messages.  Second, the user has the ability to “unsubscribe” using system tools.  Third, users would find it a burden and unnecessary to comply with the consent, form, disclosure and unsubscribe requirements, especially given the short message format and the informality associated with this type of messaging system.  Section 2(2) of the CRTC Regulations does not provide a practical solution to complying with the form requirements of Section 6(2) of CASL over social networks such as BBM.  We also note that there is no equivalent to Section 2(2) of the CRTC Regulations in Section 4 of the CRTC Regulations to help address obtaining consents under Section 10(1) or 10(3) of CASL in similar circumstances.”</p></blockquote>
<p>7. <span style="text-decoration: underline;">The proposed regulations fail to address CASL&#8217;s territorial overreach, and the consequent risk to investment and innovation in cloud computing and outsourcing in Canada</span>.</p>
<p>CASL applies to commercial electronic messages that are sent from computer systems in Canada to recipients outside of Canada.  As such CASL imposes the Canadian standards of disclosure, consent and unsubscribe on non-Canadians. This will inevitably discourage the use of Canadian facilities for activities that are perfectly lawful in other countries.</p>
<p>The problem is particularly troubling where companies rely on cloud computing. Under cloud computing, a company can use a variety of servers in a variety of locations to perform computing work, including the sending of messages.  The location of the server sending particular messages may vary, depending on demand and other factors. Under CASL, however, cloud computing activities that are undertaken in Canada must comply with the CASL requirements, even where the recipients of the messages are located outside Canada. Faced with this regulatory imposition, companies will be discouraged from operating in Canada.  As such, those computer activities, and the jobs and other economic spin-offs that result, will be lost to Canada.</p>
<p>The Information Technology Association of Canada (ITAC) is the voice of the Canadian information and communications technologies (ICT) industry. Its member companies account for more than 70 per cent of the 572,000 jobs, $140.5 billion in revenue, $6.0 billion in R&amp;D investment, $31.4 billion in exports and $11.4 billion in capital expenditures that the ICT industry contributes annually to the Canadian economy.  ITAC is a prominent advocate for the expansion of Canada&#8217;s innovative capacity and for stronger productivity across all sectors through the strategic use of technology. ITAC had the following to say about this problem.</p>
<blockquote><p>“Given that section 6 of CASL will apply when a computer system located in Canada is used to send or access a CEM, CASL will impact a range of business decisions that could have unintended negative effects on the competitiveness of a wide range of Canadian technology companies.  At least three scenarios can be contemplated.</p></blockquote>
<blockquote><p>First, Canadian multi-national companies sending messages to non-Canadian customers are incented to use vendors located outside Canada to send those messages, because otherwise the messages will have to comply with CASL.  This would result in service jobs leaving the country.  ITAC understands that some Canadian organisations that are already contemplating moving their foreign market-related messaging operations outside Canada.</p></blockquote>
<blockquote><p>Second, foreign companies deciding where to locate server farms and other facilities related to cloud computing that could be used to send messages or provide services on behalf of vendors located anywhere in the world, to customers located anywhere in the world, may choose against Canada because of the extra cost of complying with CASL.  That would have significant unintended negative consequences for the growth of cloud computing in Canada.</p></blockquote>
<blockquote><p>Third, Canadian providers of outsourced services to non-Canadian businesses will be at a major disadvantage compared to competitors in other countries.  By selecting foreign service providers, the foreign entities can avoid the costs and complications of complying with CASL.”</p></blockquote>
<p>8. <span style="text-decoration: underline;">The proposed regulations fail to properly clarify what is included under the definition of a CEM, thereby subjecting non-CEMs to CASL’s unsubscribe and formality requirements</span>.</p>
<p>Many organizations expressed concerns that CASL deems service, transactional, informational and other messages to be CEMs, even when they do not by any reasonable interpretation encourage participation in a commercial activity.  This expansion of CASL is due to paragraph 6(6) of CASL which describes a range of messages which it exempts from the consent requirements without also exempting them from CASL’s unsubscribe and formality requirements. The problem is that these messaging types would, in many cases, not be considered CEMS in the first place, but the wording of section 6(6) appears to deem them to be so. Not only does this confuse what is or is not a CEM, but message recipients will be enabled to unsubscribe from receiving non-CEMs, a requirement that would create considerable operational problems for organizations wanting to do business electronically including those that have contracted with their customers to do business that way. Organizations will need to develop and operate, at additional cost and expense, non-electronic ways of communicating with third parties.  In some cases, it could even make it illegal for organizations to deliver messages electronically, even though they are required to do so under other legislation.</p>
<p>The CMA stated the following in this regard:</p>
<blockquote><p>“A fundamental issue with CASL is that of its scope.  The definition of commercial electronic message (CEM) is sufficiently wide that it is conceivable to argue that any and all electronic communication is commercial in nature.  This thereby imposes strict, and costly if not followed correctly, rules on the delivery of all electronic messages. CASL further confuses the issue by clearly defining CEM In Section 1(2), exempting certain messaging from consent requirements In Section 6(6), but still requiring that they meet the unsubscribe requirements laid out in Section 11(1).”</p></blockquote>
<p>The Canadian Bankers Association addressed this point as follows:</p>
<blockquote><p>“We note that, while the categories of messages listed in subsections 6 (6) (a) through (f) are exempt from the consent requirements in subsection 6 (1) (a), it seems that some non-marketing messages may still be subject to the form and content requirements listed in subsection 6 (2) of the Anti-SPAM Act and further detailed in the CRTC Draft Regulations.”</p></blockquote>
<blockquote><p>“We believe that this is a serious problem with the Anti-SPAM Act, and one which we had hoped would be addressed through the Regulations.  We are concerned, in particular, that subsection 6(6) of the Anti-SPAM Act implies that customers have the ability to opt-out of receiving essential service messages (e.g. messages that confirm transactions, or that provide warranty, product recall, safety or security information). We do not believe this was the intent of the legislation”.</p></blockquote>
<blockquote><p>“Under a variety of legislation, including the Bank Act, and provincial securities legislation, financial institutions are largely required to send specific information to their customers and these types of messages, if sent electronically, should not be regarded as CEMs covered by the Act”.</p></blockquote>
<p>Telus, which along with the Canadian Bankers Association dealt with this issue in depth, added a further concern as follows:</p>
<blockquote><p>“There may be circumstances in which a business might be mandated by law to send certain information or a certain type of message to its customers and/or the public.  This might have to do with public safety, consumer protection, or some other form of regulation.  As it stands now, given that section 6(6) deems a wide range of messages to be CEMs, there is a risk that compliance with a legal regime that mandates the sending of certain messages which the CRTC might consider to be CEMs would put the sender in violation of CASL.”</p></blockquote>
<p>9. <span style="text-decoration: underline;">The proposed regulations fail to recognize the value of other, reasonable, approaches to obtaining consent to send CEMs, such as under existing PIPEDA rules</span>.</p>
<p>Many companies have previously determined that they had consent to send commercial electronic messages, either because express consent had been given or because it was a reasonable expectation of the recipients. Indeed, making such determinations would have been part of their compliance with PIPEDA.<a href="http://www.barrysookman.com/wp-includes/js/tinymce/plugins/paste/pasteword.htm?ver=327-1235#_ftn7"><sup><sup>[7]</sup></sup></a> These companies now face the need to check that the names on their list of consenting recipients all either comply with the express consent requirements of CASL, or fit under one of the few implied consent categories. This can be a daunting and expensive task, given that these lists were assembled over time and they may be quite extensive. Many commentators questioned the obligation to comply on an ongoing basis with two overlapping regulatory regimes with the attendant expense of doing so.</p>
<p>The CMA made the following submission on this point:</p>
<blockquote><p>“As a result of potential contradictions with existing privacy law, the new regime may disqualify entire databases of personal contact data obtained using responsible consent processes which meet, and in some cases exceed, the requirements of the Personal Information and Protection of Electronic Documents Act (PIPEDA).  The failure to grandfather existing databases that meet the requirements of PIPEDA will not reduce the amount of SPAM messages Canadians receive, but will in turn create a massive financial burden on Canadian organizations.”</p></blockquote>
<p>The ESAC stated the following:</p>
<blockquote><p>“The exception for implied consent in the Act is quite narrow and specific, and in light of the diversity and rapidly changing nature of business communications there is a very significant risk that a CEM could violate the provision and subject the sender to considerable liability even if consent could reasonably be inferred from the circumstances simply because it did not happen to fall within the narrow definition of &#8220;existing business relationship&#8221;.  Furthermore, this inflexible approach is not only inconsistent with the approach adopted in other jurisdictions, where implied consent can generally be inferred from the conduct, the nature of the business, and the other relationships of the intended recipients without limiting it to prescribed circumstances/ but also with the Personal Information Protection and Electronic Documents Act (PIPEDA), which deems that consent can be implied where consent may reasonably be inferred from the action or inaction of the individual.&#8221;  This creates a significant inconsistency between federal legal regimes intended to govern relationships with end users.  Recognizing implied consents that would be valid under PIPED would resolve this issue and further render the implied consent regime under the Act consistent with PIPEDA and other jurisdictions.”</p></blockquote>
<p>Some commentators are concerned that the closed categories of implied consents are too narrow and would impede legitimate, recognized and desirable ways of doing business. For example, Re:Sound, a copyright collective that represents performers and makers of sound recordings, noted that the definition of the term “existing business relationship” does not include organizations that collectively license copyright materials under tariffs certified by the Copyright Board. Canada’s copyright collectives which administer rights on behalf of hundreds of thousands of Canadian artists, composers, performers or other rights holders would not be able to use many of the publically available materials PIPEDA excludes from its consent requirements because these exclusions are not carried forward into CASL.</p>
<p>Other commentators noted the failure by the proposed regulations to exempt referral relationships which are the life blood of many business and professional opportunities.</p>
<p>CREA noted this omission saying the following:</p>
<blockquote><p>“Canada’s anti SPAM legislation already places an onerous burden on a person making a referral to act as an intermediary beyond the initial referral, requiring them to obtain consent on behalf of the professional.  However, when combined the requirement for consent to be in writing, as set out in the draft CRTC regulations, the regime places an “unreasonable and impractical responsibility on the intermediary and adds insurmountable barriers to the referral process”.</p></blockquote>
<blockquote><p>“In practice, it is highly unlikely that a client would be willing to seek consent from the person they are referring once they become aware of their obligations to provide the information proposed in the CRTC Regulations, including: the need for the intermediary to identify in writing the professional’s name, business name, mailing address, telephone number, web address and all electronic addresses belonging to the professional”.</p></blockquote>
<p>The CFIB made a similar criticism of the lack of an exception for referrals:</p>
<blockquote><p>“The requirement to have any referral in writing could cause a small business to choose between non-compliance and a much more difficult, and time-consuming process, thereby putting small-and medium-sized enterprises in a difficult position and making them less competitive.”</p></blockquote>
<blockquote><p>“The process as described in the proposed regulations is not realistic for today&#8217;s rapidly changing business.”</p></blockquote>
<p>10.<span style="text-decoration: underline;">The proposed regulations fail to clear the confusion in CASL between holders of message accounts and recipients of messages</span>.</p>
<p>CASL prohibits sending CEMs unless the person to whom the message is sent has consented to receiving it, whether the consent is express or implied.<a href="http://www.barrysookman.com/wp-includes/js/tinymce/plugins/paste/pasteword.htm?ver=327-1235#_ftn8"><strong><strong>[8]</strong></strong></a> CASL states that “a reference to the person to whom an electronic message is sent means the holder of the account associated with the electronic address to which the message is sent, as well as any person who it is reasonable to believe is or might be authorized by the account holder to use the electronic address.”<a href="http://www.barrysookman.com/wp-includes/js/tinymce/plugins/paste/pasteword.htm?ver=327-1235#_ftn9"><strong><strong>[9]</strong></strong></a></p>
<p>CASL imposes an unworkable burden in determining who must consent to receiving a CEM in circumstances in which the holder of an account is different from the person to whom the message is sent.  For example, in business to business communications in which organizations operate, or outsource the operation of, accounts, consents could conceivably be required both from someone in authority in a business as well as the intended recipient.</p>
<p>This double requirement poses additional challenges in considering whether a person has an implied consent to send a CEM. The existing and non-business relationship exception, for example, requires the person who sends the message to have an existing business relationship or an existing non-business relationship with the person to whom it is sent.<a href="http://www.barrysookman.com/wp-includes/js/tinymce/plugins/paste/pasteword.htm?ver=327-1235#_ftn10"><strong><strong>[10]</strong></strong></a> This could potentially require existing relationships with both the organization and employees of the organization. This double standard is unlikely to be made out in most cases, unless an inference can be made that a transaction such as a sale to an organization is sale to its employees.</p>
<p>A similar problem exists with respect to the “conspicuously published” exemption.<a href="http://www.barrysookman.com/wp-includes/js/tinymce/plugins/paste/pasteword.htm?ver=327-1235#_ftn11"><strong><strong>[11]</strong></strong></a> It cannot necessarily be assumed that a conspicuously published electronic address has been published by both the account holder and the person whose electronic address is published.</p>
<p>11.<span style="text-decoration: underline;">The proposed regulations stipulate that requests for consent be in writing, a requirement that is both limiting and, in some cases, impractical</span>.</p>
<p>Section 4 of the CRTC proposed regulations requires that a request for consent be in writing, a requirement that many commentators considered to be unworkable for many organizations and frustrating for consumers.</p>
<p>The CWTA stated the following:</p>
<blockquote><p>“The requirement that all requests for consent must be in writing is an onerous obligation for legitimate marketers with questionable additional benefit to consumers.  The requirement is also inconsistent with requirements for express consent in other contexts.”</p></blockquote>
<blockquote><p>“In Telecom Decision CRTC 2003-33, the Commission found it appropriate to permit Canadian carriers to use other forms of express consent as alternatives to written consent.  The Privacy Commissioner of Canada does not prescribe a method of obtaining express consent required under the Personal Information Protection and Electronic Documents Act (PIPEDA).  In fact, guidance documents from the Office of the Privacy Commission clearly state that consent can be obtained in person, by phone, by mail, via the Internet, etc, provided the person seeking consent considers the reasonable expectations of the individual and the circumstances surrounding the consent”.</p></blockquote>
<p>CREA stated the following:</p>
<blockquote><p>“The regulations, when combined with the general prohibition from the Act against obtaining consent by email in situations where the sender does not have implied consent, results in a prohibition against obtaining consent orally.  This result, combined with the reality that professionals often use electronic messages to follow up with consumers on earlier telephone or in-person discussions, create restrictions that do not reflect the realities of business communication.”</p></blockquote>
<p>These restrictions would require professionals to write a letter or have consumers sign a document in person to obtain consent.  “This will slow the speed of business and result in lost opportunities while the professional waits for a response in order to send an electronic message”.</p>
<p>HB Global Advisors Corp explained the impracticality of the “in writing” standard for consents as follows:</p>
<blockquote><p>“In our view, the writing requirement will effectively preclude organizations from obtaining express consent for the sending of Commercial Electronic Messages (&#8220;CEMs&#8221;) in person or over the phone.  By way of example, it is a common practice in the retail sector for express consents to be obtained verbally at points of sale, at customer service desks or on the phone through customer service agents.  Once the regulations come into force, retailers and other organizations will practically no longer be able to use these entirely legitimate means of obtaining express consent of consumers, thus adversely impacting both business and consumers.  Valid express consent can be obtained orally under the Personal Information Protection and Electronic Documents Act (&#8220;PIPEDA&#8221;) and provincial private sector privacy legislation, under the CRTC Unsolicited Telecommunications Rules and at common law.  In our view, there is no policy rationale for imposing the burden of a writing requirement on organizations in the course of obtaining express consent.  Such a requirement, in and of itself, will not serve to advance the purposes of the Act in any re In our view, the requirements of Section 4 of the Draft Regulations are unnecessarily onerous and restrictive and will pose significant challenges for organizations seeking to obtain express consent in compliance with the Act.”</p></blockquote>
<p>12.<span style="text-decoration: underline;">Most commentators criticized as unworkable the CRTC’s proposed regulation which requires that each CEM and each request for consent to send a CEM include </span><span style="text-decoration: underline;">the physical and mailing address, a telephone number providing access to an agent or a voice messaging system, an email address and a web address of the sender and any other electronic address used by the sender</span>.</p>
<p>Numerous commentators objected to the CRTC’s proposed regulation that requires each request for consent and each CEM to include “the physical and mailing address, a telephone number providing access to an agent or a voice messaging system, an email address and a web address of the person seeking consent and, if different, the person on whose behalf consent is sought and any other electronic address used by those persons”.<a href="http://www.barrysookman.com/wp-includes/js/tinymce/plugins/paste/pasteword.htm?ver=327-1235#_ftn12">[12]</a> Businesses considered that this inflexible approach requiring detailed contact information would be inconsistent with CASL, would impose additional costs for Canadian businesses and would cause confusion and frustration among consumers.</p>
<p>According to ITAC</p>
<blockquote><p>“Meeting all of these requirements will be challenging for organisations, particularly when the message is being sent on behalf of multiple third parties (such as dealers, resellers, franchisees or affiliates).”</p></blockquote>
<blockquote><p>“Including each category of contact information is unnecessary, as section 6(2) of CASL already requires the disclosure of information that would enable the recipient of a message to &#8220;readily contact&#8221; the sender.”</p></blockquote>
<blockquote><p>“Including each category of contact information will discourage the use of electronic means to conduct business, as many internet companies do not maintain a mailing address and telephone number to receive written and oral communications from consumers, relying instead on electronic communications.</p></blockquote>
<p>The ESAC said the following:</p>
<blockquote><p>“The wide range of contact information that must be provided under subsection 2(1)(d) is impractical and excessive, and may not be applicable in some cases.  The subsection assumes that all businesses sending CEMs have both physical and mailing addresses, and telephone numbers with voice messaging, and email addresses, and web addresses where they may be contacted. While this will generally be true of large companies, many internet start-ups and independent game developers operate entirely online and do not have physical addresses or telephone numbers with voicemail. In order to comply with the Regulations, such legitimate e-commerce businesses will be required to establish all these forms of contact, including a formal address, which represents an unnecessary and burdensome cost to small early stage technology companies and game development studios.”</p></blockquote>
<p>PIAC was one of the few commentators to approve of requiring several modes of contact, although it too questioned the need for the “any other electronic address” stipulation in Section 2(1)(d).</p>
<p>Numerous commentators were also critical of the requirement to provide “any other electronic address used by those persons. This requirement was viewed as excessive. ESAC noted that the “requirement to include all electronic addresses is excessive and will present a massive burden for all but the smallest companies.” CREA made a similar comment stating: “strictly interpreted, a sender could be required to list dozens of electronic addresses, which is clearly burdensome, unnecessary, and confusing to consumers.”</p>
<p>13.<span style="text-decoration: underline;">The CRTC’s proposed regulation requiring that each request for consent include a statement that a consent can be withdrawn using any of the mandatory contact information is contrary to CASL and is unworkable. It would require organizations to monitor physical and mailing addresses, a telephone number, an email address and a web address and any other electronic address used by those persons</span>.</p>
<p>The Canadian Bankers Association described the problems with the proposed regulation as follows:</p>
<blockquote><p>“Requiring the sender to include a list of &#8220;other electronic address[es]&#8221; is onerous and, in any case, will be of limited use to recipients of CEMs since most Canadian financial institutions operate thousands of electronic addresses, as the term is defined in the Act (e.g., individual e-mail and telephone accounts assigned to employees), and these addresses change frequently.</p></blockquote>
<blockquote><p>“Requiring the sender to continuously monitor every one of these electronic addresses and other Channels (e.g. mail. telephone, physical address) for withdrawals of consent for an extensive time period, would be extremely difficult, if not impossible, to implement operationally”.</p></blockquote>
<p>RIM summarized the problems as follows:</p>
<blockquote><p>“Subsection 4(e) requires the sender to include a statement telling recipients that they can withdraw consents using any of this contact information.  This regulation is also beyond the power of the Commission. As noted above, the unsubscribe mechanism is set out in subsection 11(1) of CASL.  The Commission does not have the power under that subsection to prescribe the particular way in which businesses must permit individuals to unsubscribe to receiving CEMs.  But, requiring a statement telling recipients that they can withdraw consents using any of this contact information would be an attempt to do indirectly what the Commission cannot do directly&#8230;   Lastly, this requirement will mandate that companies and their agents maintain multiple mechanisms to collect these indications, making it inefficient and costly.</p></blockquote>
<p>14.<span style="text-decoration: underline;">The CRTC’s proposed regulation is unworkable where it requires that request for consent must be sought separately for each act described in sections 6 to 8 of CASL</span>.</p>
<p>Section 4 of the proposed regulation requires that consent “must be sought separately for each act described in sections 6 to 8 of the Act.”<a href="http://www.barrysookman.com/wp-includes/js/tinymce/plugins/paste/pasteword.htm?ver=327-1235#_ftn13">[13]</a> Organizations such as the CLHIA pointed out that it is not clear what is intended by “sought separately for each act.”  Further, it points out that “It does not seem unreasonable that a single request for consent could expressly identify more than one activity for which the consent is being sought”.</p>
<p>The ESAC noted that the draft language suggests that consent must be obtained separately for each and every occasion a message is sent or re-directed or software is installed.  “This would effectively negate the ability to obtain consent for future actions, and create an overwhelming burden for businesses (due to the vast number of consents) and consumers (who would have to consent before receiving each and every message).”</p>
<p>15.<span style="text-decoration: underline;">The CRTC’s proposed regulation permitting prescribed information to be made available on the web is not a practical or technologically neutral solution to the disclosure requirement problems created by CASL and the proposed regulations</span>.</p>
<p>The draft CRTC regulations recognize the impracticality for many message types to comply with the form and disclosure requirements of CASL. The short nature of many message types, such as instant or SMS messages and those used over social networks could not accommodate the legal formalities mandated by CASL.</p>
<p>The draft CRTC regulations purport to make it easier for short message types to comply with CASL&#8217;s message form requirements by enabling users to provide prescribed information by using a link to a web page on the World Wide Web that is clearly and prominently set out and that can be accessed by a single click or another method of equivalent efficiency at no cost to the person to whom the message is sent.<a href="http://www.barrysookman.com/wp-includes/js/tinymce/plugins/paste/pasteword.htm?ver=327-1235#_ftn14">[14]</a></p>
<p>There are significant limitations with the approach taken. For example, there is no equivalent mechanism in Section 4 of the draft CRTC regulations to enable users of instant messaging, SMS, or social networks or similar networks to use a link to a web page to make the necessary disclosures to obtain consents under Section 10(1) or 10(3) of CASL.  Accordingly, given the limitations of those networks, it would be problematic to seek consent to send a CEM using many modern messaging systems.  Further, it requires anyone seeking to use modern messaging systems to have and maintain a website.  This will be especially burdensome on individuals and small businesses. The solution will often not be practically implementable because the character limitations on short messages cannot even accommodate even the solution proposed. Nor can the link always be accessed in just “one click”. Moreover, the “one click” proposal is not technologically neutral.  As well, users of mobile devices would often have to pay data charges and thus cannot be provided at no charge, thereby making the solution unworkable for one of the fastest growing sectors of the communications marketplace. In any event, there are questions as to whether it is realistic to impose the disclosure requirements on users of social networks.</p>
<p>The CFIB had the following to say about this solution to the disclosure problems created by CASL</p>
<blockquote><p>“The assumption is that every single business in Canada has a website, however only about half of small businesses have a website yet two-thirds use the web as part of their business.”</p></blockquote>
<blockquote><p>“Newer businesses trying to increase their customer base and garner revenue might not be able to initially spend money on a new website, but this requirement will force them to take time and money away from their priorities to comply with the rules”.</p></blockquote>
<blockquote><p>“The reference to a &#8220;single Click&#8221; in Subsection 2(2) implies that the &#8220;link to a web page on the World Wide Web&#8221; is accessed using an Internet connection, but this is unclear, as is the meaning of &#8220;another method of equivalent efficiency.&#8221;</p></blockquote>
<blockquote><p>“For example, is the provision of a toll-free telephone number which the text message recipient may use to access the information a ‘method of equivalent efficiency’?”</p></blockquote>
<p>ITAC said the following:</p>
<blockquote><p>“Including all of the mandatory information on a single web page is impractical and unnecessarily restrictive, particularly where a message is being sent on behalf of multiple third parties (such as dealers, franchisees or affiliates) or using short messaging platforms. Links to additional information should be permitted.”</p></blockquote>
<p>The Canadian Bankers Association made the following comments on this point:</p>
<blockquote><p>“We assume that the underlying purpose of the inclusion of the phrase &#8220;at no cost to the person to whom the message is sent&#8221;, is to ensure that consumers are not charged by the sender to access contact information of the sender or unsubscribe from a CEM.”</p></blockquote>
<blockquote><p>“However…there are data costs associated with many forms of digital communication (e.g. as levied by ISP and mobile telephony service providers) over which a sender of a CEM has limited knowledge and no control.  The recipient of a CEM may subscribe to a &#8216;pay as you go&#8217; mobile plan that offers a bundle of minutes for a set fee, so every use of the mobile device results in a cost to the user, even to dial a toll-free telephone number.  Many data plans with Internet services for mobile devices have a limit over which the user is charged fees to send additional messages or for additional Internet access.”</p></blockquote>
<p>ESAC made the following statement:</p>
<blockquote><p>“Subsection (2) specifically requires that the information must be on a &#8220;web page&#8221; on the &#8220;World Wide Web&#8221; that can be accessed by a &#8220;single click&#8221;.  This is not a technologically neutral solution, and effectively precludes the use of any non-web-based interfaces.  The section essentially dictates the form of communications technology companies are permitted to use. While subsection (2) does permit information to be accessed by &#8220;another method of equivalent efficiency&#8221;, the scope of this provision is unclear.  It immediately follows the requirement that the information be accessed in a &#8220;single click&#8221;, suggesting that the&#8221; method of equivalent efficiency&#8221; only applies to the equivalent of a &#8220;click&#8221;.  If it is intended to be applied more broadly, this must be clarified.”</p></blockquote>
<blockquote><p>“The imposition of a &#8220;single click&#8221; limit is also problematic.  There may be situations where it would take 2 or more &#8220;clicks&#8221; to access the complete range of information that the Regulations require.  The fact that all of the prescribed information must be accessible at a &#8220;single click&#8221; is very restrictive and inflexible, especially as a single extra &#8220;click&#8221; may result in significant punitive measures against the sender.”</p></blockquote>
<p>16.<span style="text-decoration: underline;">The proposed regulations fail to accommodate a business that does not maintain a web site from receiving unsubscribe requests. Further, the CRTC’s proposed regulation requiring the unsubscribe mechanism be performed in no more than two clicks is not technologically neutral or workable in many circumstances</span>.</p>
<p>Individuals and organizations cannot send CEMs or request a consent to send a CEM unless they have a website to disclose the prescribed information and receive unsubscribe requests.<a href="http://www.barrysookman.com/wp-includes/js/tinymce/plugins/paste/pasteword.htm?ver=327-1235#_ftn15">[15]</a> This will be onerous for individuals and small businesses as well as users of social networks.</p>
<p>The requirements also cannot be met for all messaging systems including for messaging systems in which the subscribe and unsubscribe mechanisms are under the control of a third party. It is also not a technologically neutral solution.</p>
<p>The ESAC made the following comments on this draft regulation.</p>
<blockquote><p>“While the Act and proposed Regulations appear to assume that only the sender controls the transmission of a message, there are many circumstances in which the subscribe and unsubscribe are actually under the control of a third party (often a messaging platform), and where it is the user who determines the messages he or she wishes to receive.  For instance, in the case of CEMs sent via social networking sites such as FaceBook or Twitter, it is the social networking site that establishes the unsubscribe process, and recipients themselves may unsubscribe without any action required by the sender by simply &#8220;un-friending&#8221; or &#8220;un-following&#8221; or adjusting their settings.  Similarly, most mobile &#8220;apps&#8221; including mobile games include a setting that permits users to switch notifications that could be construed as CEMs off.”</p></blockquote>
<blockquote><p>“The requirement that the recipient be able to unsubscribe in &#8220;two clicks&#8221; is not a technologically neutral requirement and appears designed for email messages.  Moreover, requiring that the recipient be able to unsubscribe in &#8220;two clicks&#8221; is arbitrary.  There may be situations where it would take 3 or more &#8220;clicks&#8221; to complete the unsubscribe process.  Given the potential penalties associated with the Act, such a limit is punitive.”</p></blockquote>
<blockquote><p>“Not every communication device or medium to which messages are sent will be web-enabled. Given the broad application of CASL to all digital technologies, this exception needs greater flexibility to ensure technologically neutral application.”</p></blockquote>
<p>The CMA stated the following:</p>
<blockquote><p>“The restrictive form of the unsubscribe mechanism will effectively prevent the practice of allowing recipients to select within a preference centre the types of messages to which recipients wish to unsubscribe, as multiple clicks are typically necessary to allow for the narrowing of a subscription.  This valid practice should not be discouraged as it provides recipients with greater control over the type of information they receive.”</p></blockquote>
<blockquote><p>“The use of the term &#8220;click&#8221; itself creates problems as it is not technologically neutral. The term does not allow for the use of platforms such as mobile and tablet.”</p></blockquote>
<blockquote><p>“The number of permitted clicks is arbitrary and will result in existing senders of commercial electronic messages that have otherwise legitimate unsubscribe mechanisms (i.e. that do not require the recipient to provide a reason, or other types of information, to unsubscribe) having to alter, at a cost, these mechanisms unnecessarily.”</p></blockquote>
<p>The Canadian Bankers Association stated:</p>
<blockquote><p>“The requirement that the unsubscribe mechanism be performed in no more than two &#8220;clicks&#8221; does not reflect current industry standard.</p></blockquote>
<blockquote><p>At minimum, one click is needed to click on the link to move from the GEM to access the web page which houses the unsubscribe mechanism, A second click is then needed to select unsubscribe.  A third click is often needed to &#8220;confirm&#8221; or &#8220;submit&#8221; the unsubscribe request”.</p></blockquote>
<blockquote><p>“A two click requirement may impact current industry practice where the recipient of a CEM is directed to a web page to select his or her electronic communication preferences…”</p></blockquote>
<blockquote><p>The requirement “also appears to directly conflict with the requirement in subsection 11(1) (a) of the Anti-SPAM Act to enable the recipient of a CEM to indicate his or her wish to no longer receive &#8220;any specified class&#8221; of such messages.  Depending on the scope of specified classes offered by the sender of the CEM in the unsubscribe mechanism, it is likely that more than two clicks would often be required in order to properly perform an unsubscribe mechanism”.</p></blockquote>
<p>The comments also had considerable criticisms of CASL and the draft regulatory approaches to regulating “spyware” and other malware.  These include the following problems.</p>
<p>17.<span style="text-decoration: underline;">The heightened consent requirements in Section 5 of the draft CRTC regulations for computer programs that perform one of the functions listed in Section 10(5) is unworkable. It is impractical to require that such consents be in writing or to require the user provide an acknowledgement. Further, there are many circumstances in which meeting these requirements would be either technically or commercially unfeasible</span>.</p>
<p>The ESAC provided extensive comments on this point.</p>
<blockquote><p>“The requirement that any description of the specified functions listed in subsection 10(5) of the Act be brought to the attention of the person from whom consent is being sought &#8220;separately from any other information&#8221; is unclear.  It suggests that this information must be included in a separate notice. Section 10(4) of the Act already requires that consent for the installation of a computer program that performs a specified function be separate and apart from the licence agreement, so requiring an additional, separate notice is excessive, confusing and creates unnecessary records.”</p></blockquote>
<blockquote><p>“The requirement that the consent be obtained, in writing, and include a specific acknowledgement from the user that they understand and agree that the computer program will perform the specified functions is deeply problematic.  The only way to obtain the acknowledgement of consent to a specific function will be to generate an electronic message to be sent to the company.  However, this would constitute installing a computer program that causes an electronic message to be sent, which is also prohibited and for which a separate consent will be required.  This will multiply the number of consents that must be obtained, which will be extremely onerous for business and overwhelming to the consumer.  Further, in the event that a consumer declines to consent to the transmission of the acknowledgement, the company will be unable to comply with the requirement and thus be penalized for not obtaining the required acknowledgement in writing, when the reason for doing so was outside their control.”</p></blockquote>
<blockquote><p>“There are many circumstances beyond the permitted exceptions where express consent cannot be obtained, and attempting to obtain consent (including the prescribed information) would not only be not technically feasible but disruptive to the end user&#8217;s experience.  For instance, many software, mobile &#8220;app&#8221; and game developers provide frequent updates and upgrades for their programs, but do so as a courtesy rather than pursuant to formal terms and consequently would not benefit from the &#8220;updates and upgrades&#8221; exception.  Under these circumstances, consent will need to be obtained for each separate update, and will need to include all the required information.  This applies even if the user has requested automatic updates, or the developer has no control over the information that can be provided with an update.  This will similarly occur if an update or upgrade could alter settings or data on a device, as these &#8220;functions&#8221; trigger enhanced disclosure obligations and requiring obtaining separate consent regardless of the circumstances or actual impact on the end user.”</p></blockquote>
<blockquote><p>“Many electronic devices are not designed in a manner that would enable them to display a request for consent or accompanying prescribed information (e.g. some MP3 players, printers, scanners, appliances, etc.), and are incapable of satisfying the consent requirements (especially in circumstances where enhanced disclosure would be required).”</p></blockquote>
<p>Telus also had very extensive comments on this issue:</p>
<blockquote><p>“However, due to the way section 10(5) is drafted, this provision has the potential to interfere with common, accepted business practices that are adequately governed by contracts.  The concern arises from the definition of the types of functionalities that trigger the heightened disclosure and consent requirements.  Section 10(10) refers to “any of the following functions that the person who seeks express consent knows and intends will cause the computer system to operate in a manner that is contrary to the reasonable expectations of the owner or an authorized user of the computer system.”  One of those functions – the only one that causes TELUS concern at present – is (c), “changing or interfering with settings, preferences or commands already installed or stored on the computer system without the knowledge of the owner or an authorized user of the computer system.”</p></blockquote>
<blockquote><p>The reality is that within many kinds of client/service provider relationships, there are times when functionalities and settings are changed in a way that may cause a device to operate in a manner that the user does not expect.  These changes typically take the form of updates, upgrades, or program installations which, while they might make a device work differently, are technical in nature and fall within the scope of contractual consents.</p></blockquote>
<blockquote><p>Programs may also be installed from time to time for the purposes of network management, security, diagnostics, technical support or repair, or the detection or prevention of unauthorized or fraudulent use of a service or system.  Installations for these purposes are also typically within the scope of applicable contracts.”</p></blockquote>
<blockquote><p>“…the &#8220;alteration of transmission data&#8221; provisions include an exception for network management. Section 7(2) specifies that that rule &#8220;does not apply if the alteration is made by a telecommunications service provider for the purposes of network management.&#8221;  A telecommunications service provider may need to install programs from time to time for the purposes of network management, security, diagnostics, technical support or repair, or the detection or prevention of unauthorized or fraudulent use of a service or system.  In some cases, particularly anti-fraud measures, it would defeat the purpose to disclose the action to the user and seek his or her consent.”</p></blockquote>
<p>18.<span style="text-decoration: underline;">Certain of the CRTC’s proposed regulations may be beyond the CRTC’s authority under CASL</span>.</p>
<p>Several commentators argue that the CRTC does not have the authority to promulgate the regulations in the form proposed. Comments filed by the CBA, The Chamber, ITAC and RIM, among others, deal with these points. Conversely, PIAC maintains that the CRTC indeed has the requisite jurisdiction.</p>
<p><span style="text-decoration: underline;">Conclusion</span></p>
<p>Canadian businesses have identified a number of important concerns with the proposed regulations under CASL. Unless the proposed regulations are reformulated, many worry that CASL will impede rather than facilitate e-commerce. It will hurt small and large businesses, cause significant economic harm and stifle innovation in the use of electronic messaging systems. It will hinder investment and job creation and drive new and emerging businesses to locate outside of Canada. Its red tape will be costly and inefficient to comply with.</p>
<p>As a last point, many commentators made suggestions related to the go forward process. For example, several organizations, such as the Chamber, endorsed the need for a second round of consultations once revised draft regulations are issued.  Many organizations also asked for sufficient lead time from when the regulations are finalized until the date that CASL comes into legal force. Finally, many comments contained thoughtful solutions to the problems summarized above. These might well form the basis for reformulating the existing regulations and for drafting additional regulations.</p>
<hr size="1" /><a href="http://www.barrysookman.com/wp-includes/js/tinymce/plugins/paste/pasteword.htm?ver=327-1235#_ftnref1">[1]</a> lsalzman@mccarthy.ca</p>
<p><a href="http://www.barrysookman.com/wp-includes/js/tinymce/plugins/paste/pasteword.htm?ver=327-1235#_ftnref2">[2]</a> bsookman@mccarthy.ca</p>
<p><a href="http://www.barrysookman.com/wp-includes/js/tinymce/plugins/paste/pasteword.htm?ver=327-1235#_ftnref3">[3]</a> See <span style="text-decoration: underline;">http://www.ic.gc.ca/eic/site/ecic-ceac.nsf/eng/gv00521.html</span></p>
<p><a href="http://www.barrysookman.com/wp-includes/js/tinymce/plugins/paste/pasteword.htm?ver=327-1235#_ftnref4">[4]</a> See section 3 of CASL.</p>
<p><a href="http://www.barrysookman.com/wp-includes/js/tinymce/plugins/paste/pasteword.htm?ver=327-1235#_ftnref5">[5]</a> For additional information on the history, goals and objectives of CASL, see Government of Canada, <em>Backgrounder, </em>Questions<em> and Answers, and Online Threats, </em><a href="http://www.ic.gc.ca/eic/site/ecic-ceac.nsf/eng/h_gv00567.html">http://www.ic.gc.ca/eic/site/ecic-ceac.nsf/eng/h_gv00567.html</a>),  <em>Government of Canada Moves to Enhance Safety and Security in the Online Marketplace</em> <a href="http://www.ic.gc.ca/eic/site/ic1.nsf/eng/05596.html">http://www.ic.gc.ca/eic/site/ic1.nsf/eng/05596.html</a></p>
<p><a href="http://www.barrysookman.com/wp-includes/js/tinymce/plugins/paste/pasteword.htm?ver=327-1235#_ftnref6">[6]</a> CRTC draft regulation Section 2(1), 2(2), 4.</p>
<p><a href="http://www.barrysookman.com/wp-includes/js/tinymce/plugins/paste/pasteword.htm?ver=327-1235#_ftnref7">[7]</a> <em>Personal Information Protection and Electronic Documents Act</em></p>
<p><a href="http://www.barrysookman.com/wp-includes/js/tinymce/plugins/paste/pasteword.htm?ver=327-1235#_ftnref8">[8]</a> CASL Section 6(1)</p>
<p><a href="http://www.barrysookman.com/wp-includes/js/tinymce/plugins/paste/pasteword.htm?ver=327-1235#_ftnref9">[9]</a> CASL Section 1(1)(5)</p>
<p><a href="http://www.barrysookman.com/wp-includes/js/tinymce/plugins/paste/pasteword.htm?ver=327-1235#_ftnref10">[10]</a> CASL Section 10(10)(a)</p>
<p><a href="http://www.barrysookman.com/wp-includes/js/tinymce/plugins/paste/pasteword.htm?ver=327-1235#_ftnref11">[11]</a> CASL Section 10(10)(b)</p>
<p><a href="http://www.barrysookman.com/wp-includes/js/tinymce/plugins/paste/pasteword.htm?ver=327-1235#_ftnref12">[12]</a> CRTC draft regulation, Sections 2(d) and 4(d)</p>
<p><a href="http://www.barrysookman.com/wp-includes/js/tinymce/plugins/paste/pasteword.htm?ver=327-1235#_ftnref13">[13]</a> CRTC draft regulation, Section 4.</p>
<p><a href="http://www.barrysookman.com/wp-includes/js/tinymce/plugins/paste/pasteword.htm?ver=327-1235#_ftnref14">[14]</a> CRTC draft regulation, Section 2(2)</p>
<p><a href="http://www.barrysookman.com/wp-includes/js/tinymce/plugins/paste/pasteword.htm?ver=327-1235#_ftnref15">[15]</a> CRTC draft regulation Section 2(1), 2(2), 4.</p>
<p>* Updated Sept 21.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.barrysookman.com/2011/09/20/electronic-commerce-protection-regulations-%e2%80%93-much-work-remains/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Draft FISA (Anti-SPAM) regulations published by CRTC and Industry Canada (updated)</title>
		<link>http://www.barrysookman.com/2011/07/18/draft-fisa-regulations-published-by-crtc/</link>
		<comments>http://www.barrysookman.com/2011/07/18/draft-fisa-regulations-published-by-crtc/#comments</comments>
		<pubDate>Mon, 18 Jul 2011 15:30:21 +0000</pubDate>
		<dc:creator>Barry Sookman</dc:creator>
				<category><![CDATA[E-commerce]]></category>
		<category><![CDATA[FISA]]></category>
		<category><![CDATA[CASL]]></category>
		<category><![CDATA[crtc reglations]]></category>
		<category><![CDATA[ECPA]]></category>
		<category><![CDATA[spam]]></category>
		<category><![CDATA[spam regulations]]></category>

		<guid isPermaLink="false">http://www.barrysookman.com/?p=3282</guid>
		<description><![CDATA[The Canadian Anti-SPAM law (CASL or FISA) contemplated that regulations would need to be promulgated before the Act is proclaimed into force. CASL contemplated two sets of regulations: one from Industry Canada and the other from the CRTC.  The CRTC published draft regulations for comment purposes on June 30, 2011. The Commission will accept comments [...]]]></description>
			<content:encoded><![CDATA[<p>The <a href="http://laws-lois.justice.gc.ca/eng/acts/E-1.6/page-1.html">Canadian Anti-SPAM law </a>(CASL or FISA) contemplated that regulations would need to be promulgated before the Act is proclaimed into force. CASL contemplated two sets of regulations: one from Industry Canada and the other from the CRTC.  The CRTC published <a href="http://crtc.gc.ca/eng/archive/2011/2011-400.htm" target="_blank">draft regulations</a> for comment purposes on June 30, 2011. The Commission will accept comments from interested persons that it receives on or before September 7, 2011, a date <a href="http://www.crtc.gc.ca/eng/archive/2011/2011-400-1.htm">extended by the CRTC</a> from the original date of 29 August 2011.</p>
<p>The CRTC draft regulations are as follows:</p>
<blockquote><p><strong>1. </strong> In these Regulations, “Act” means <em>An Act to promote the efficiency and adaptability of the Canadian economy by regulating certain activities that discourage reliance on electronic means of carrying out commercial activities, and to amend the Canadian Radio-television and Telecommunications Commission Act, the Competition Act, the Personal Information Protection and Electronic Documents Act and the Telecommunications Act</em>.</p>
<p>INFORMATION TO BE INCLUDED IN COMMERCIAL ELECTRONIC MESSAGES</p>
<p><strong>2. </strong> (1)   For the purposes of subsection 6(2) of the Act, the following information must be set out in any commercial electronic message:</p>
<p>(<em>a</em>)   the name of the person sending the message and the person, if different, on whose behalf it is sent;</p>
<p>(<em>b</em>)   if the message is sent on behalf of another person, a statement indicating which person is sending the message and which person on whose behalf the message is sent;</p>
<p>(<em>c</em>)   if the person who sends the message and the person, if different, on behalf of whom it is sent carry on business by different names, the name by which those persons carry on business; and</p>
<p>(<em>d</em>)   the physical and mailing address, a telephone number providing access to an agent or a voice messaging system, an email address and a web address of the person sending the message and, if different, the person on whose behalf the message is sent and any other electronic address used by those persons.</p>
<p>(2)   If it is not practicable to include the information referred to in subsection (1) and the unsubscribe mechanism referred to in paragraph 6(2)(<em>c</em>) of the Act in a commercial electronic message, that information may be provided by a link to a web page on the World Wide Web that is clearly and prominently set out and that can be accessed by a single click or another method of equivalent efficiency at no cost to the person to whom the message is sent.</p>
<p>FORM OF COMMERCIAL ELECTRONIC MESSAGES</p>
<p><strong>3.</strong> (1)   The information referred to in section 2 and the unsubscribe mechanism referred to in paragraph 6(2)(<em>c</em>) of the Act must be set out clearly and prominently.</p>
<p>(2)   The unsubscribe mechanism referred to in paragraph 6(2)(<em>c</em>) of the Act must be able to be performed in no more than two clicks or another method of equivalent efficiency.</p>
<p>INFORMATION TO BE INCLUDED IN A REQUEST FOR CONSENT</p>
<p><strong>4. </strong> For the purposes of subsections 10(1) and (3) of the Act, a request for consent must be in writing and must be sought separately for each act described in sections 6 to 8 of the Act and must include</p>
<p>(<em>a</em>)   the name of the person seeking consent and the person, if different, on whose behalf consent is sought;</p>
<p>(<em>b</em>)   if the consent is sought on behalf of another person, a statement indicating which person is seeking consent and which person on whose behalf consent is sought;</p>
<p>(<em>c</em>)   if the person seeking consent and the person, if different, on whose behalf consent is sought carry on business by different names, the name by which those persons carry on business;</p>
<p>(<em>d</em>)   the physical and mailing address, a telephone number providing access to an agent or a voice messaging system, an email address and a web address of the person seeking consent and, if different, the person on whose behalf consent is sought and any other electronic address used by those persons; and</p>
<p>(<em>e</em>)   a statement indicating that the person whose consent is sought can withdraw their consent by using any contact information referred to in paragraph (<em>d</em>).</p>
<p>SPECIFIED FUNCTIONS OF COMPUTER PROGRAMS</p>
<p><strong>5. </strong> A computer program’s material elements that perform one or more of the functions listed in subsection 10(5) of the Act must be brought to the attention of the person from whom consent is being sought separately from any other information provided in a request for consent and the person seeking consent must obtain an acknowledgement in writing from the person from whom consent is being sought that they understand and agree that the program performs the specified functions.</p></blockquote>
<p>Industry Canada published additional <a href="http://canadagazette.gc.ca/rp-pr/p1/2011/2011-07-09/html/reg1-eng.html">draft regulations</a> on July 8, 2011. There is also a 60 day period for commenting on these regulations. These draft regulatons read as follows:</p>
<blockquote><p>PERSONAL RELATIONSHIP AND FAMILY RELATIONSHIP</p>
<p><strong>2.</strong> For the purposes of paragraph 6(5)(<em>a</em>) of the Act</p>
<ol>
<li>(<em>a</em>) “family relationship” means the relationship between individuals who are connected by
<ol>
<li>(i) a blood relationship, if one individual is the child or other descendant of the other individual, the parent or grandparent of the other individual, the brother or sister of the other individual or of collateral descent from the other individual’s grandparent,</li>
<li>(ii) marriage, if one individual is married to the other individual or to an individual connected by a blood relationship to that other individual,</li>
<li>(iii) a common-law partnership, if one individual is in a common-law partnership with the other individual or with an individual who is connected by a blood relationship to that other individual; and</li>
<li>(iv) adoption, if one individual has been adopted, either legally or in fact, as the child of the other individual or as the child of an individual who is connected by a blood relationship to that other individual; and</li>
</ol>
</li>
<li>(<em>b</em>) “personal relationship” means the relationship, other than in relation to a commercial activity, between an individual who sends the message and the individual to whom the message is sent, if they have had an in-person meeting and, within the previous two years, a two-way communication.</li>
</ol>
<p>CONDITIONS FOR USE OF CONSENT</p>
<p><strong>3.</strong> (1) For the purposes of paragraph 10(2)(<em>b</em>) of the Act, a person who obtained express consent on behalf of a person whose identity was unknown may authorize any person to use the consent on the condition that the person who obtained consent ensures that, in any commercial electronic message sent to the person from whom consent was obtained,</p>
<ol>
<li>(<em>a</em>) the person who obtained consent is identified; and</li>
</ol>
<ol>
<li>(<em>b</em>) the authorized person provides an unsubscribe mechanism that, in addition to meeting the requirements set out in section 11 of the Act, allows the person from whom consent was obtained to withdraw their consent from the person who obtained consent or any other person who is authorized to use the consent.</li>
</ol>
<p>(2) The person who obtained consent must ensure that, on receipt of an indication of withdrawal of consent by the authorized person who sent the commercial electronic message, that authorized person notifies the person who obtained consent that consent has been withdrawn from, as the case may be,</p>
<ol>
<li>(<em>a</em>) the person who obtained consent;</li>
<li>(<em>b</em>) the authorized person who sent the commercial electronic message; or</li>
<li>(<em>c</em>) any other person who is authorized to use the consent.</li>
</ol>
<p>(3) The person who obtained consent must inform, without delay, a person referred to in paragraph 2(<em>c</em>) of the withdrawal of consent on receipt of notification of withdrawal of consent from that person.</p>
<p>(4) The person who obtained consent must give effect to a withdrawal of consent and, if applicable, ensure that a person referred to in paragraph 2(<em>c</em>) gives effect to the withdrawal of consent, in accordance with subsection 11(3) of the Act.</p>
<p>MEMBERSHIP, CLUB, ASSOCIATION AND VOLUNTARY ORGANIZATION</p>
<p><strong>4.</strong> (1) For the purposes of paragraph 10(13)(<em>c</em>) of the Act, membership is the status of having been accepted as a member of a club, association or voluntary organization in accordance with the membership requirements of the club, association or organization.</p>
<p>(2) For the purposes of paragraph 10(13)(<em>c</em>) of the Act, a club, association or voluntary organization is a non-profit organization that is organized and operated exclusively for social welfare, civic improvement, pleasure or recreation or for any purpose other than profit, if no part of its income is payable to, or otherwise available for the personal benefit of any proprietor, member or shareholder of that organization unless the proprietor, member or shareholder is an organization the primary purpose of which is the promotion of amateur athletics in Canada.</p></blockquote>
<p>*Updated after the Industry Canada draft regulations were published.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.barrysookman.com/2011/07/18/draft-fisa-regulations-published-by-crtc/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Naming Canada’s Anti-Spam/Anti-Spyware Law</title>
		<link>http://www.barrysookman.com/2011/02/14/naming-canada%e2%80%99s-anti-spamanti-spyware-law/</link>
		<comments>http://www.barrysookman.com/2011/02/14/naming-canada%e2%80%99s-anti-spamanti-spyware-law/#comments</comments>
		<pubDate>Mon, 14 Feb 2011 13:50:24 +0000</pubDate>
		<dc:creator>Barry Sookman</dc:creator>
				<category><![CDATA[Bill C-28]]></category>
		<category><![CDATA[E-commerce]]></category>
		<category><![CDATA[Electronic Commerce Protection Act (ECPA)]]></category>
		<category><![CDATA[FISA]]></category>
		<category><![CDATA[FIWSA]]></category>
		<category><![CDATA[spam]]></category>
		<category><![CDATA[spyware]]></category>
		<category><![CDATA[malware]]></category>
		<category><![CDATA[spam bill]]></category>

		<guid isPermaLink="false">http://www.barrysookman.com/?p=2671</guid>
		<description><![CDATA[Last week in a blog post I asked for suggestions to help name Canada’s new anti-SPAM and anti-spyware law, Bill –C-28. The Bill has no short title and needs one.
You clearly had fun trying to come up with a name. Some of you suggested a few names. Some suggestions were serious (more or less). Others [...]]]></description>
			<content:encoded><![CDATA[<p>Last week in a <a href="http://www.barrysookman.com/2011/02/06/name-canada%E2%80%99s-anti-spamanti-spyware-law/">blog</a> post I asked for suggestions to help name Canada’s new anti-SPAM and anti-spyware law, <a href="http://www2.parl.gc.ca/HousePublications/Publication.aspx?Language=E&amp;Parl=40&amp;Ses=3&amp;Mode=1&amp;Pub=Bill&amp;Doc=C-28_4">Bill –C-28</a>. The Bill has no short title and needs one.</p>
<p>You clearly had fun trying to come up with a name. Some of you suggested a few names. Some suggestions were serious (more or less). Others were hysterical, many reflecting your thoughts about the Bill, or about SPAM. Here are your proposals to name the Bill.</p>
<p>Please read them and let me know which ones you like or would choose. You can email me (bsookman@mccarthy.ca) or post comments on my blog with your recommended name and short name, if applicable. My partner Lorne Salzman and I will select the winning name (and the winner of the McCarthy’s gift) after getting your input.</p>
<p><strong>Eyjafjallajökul</strong>l – the name of the volcano in Iceland that disrupted so much flight travel in Europe last year. No one (outside of Iceland) could pronounce the name and like this Bill, no one will be able to remember the full name so let’s give it a label we will at least remember – to see, if not say. (John Leblanc)</p>
<p><strong>Canada Risible Anti-spam Propoundment</strong> or <strong>CRAP</strong> for short. (Richard Owens)</p>
<p><strong>Spam<sup>24</sup> Act. </strong>Surely relying on the Wisdom of The Hitchhikers Guide to the Universe, the name then should be:  <strong>Spam<sup>42</sup></strong> Act. BUT since spam is transmitted over the Internet and Google is a very important term in relation to the Internet and the number Googol sounds very close to Google, we could call it: <strong>Spam<sup>googol</sup></strong> <strong>Act</strong> (David Bilinsky)</p>
<p>One is reminded of that Python bit profiling an otherwise forgotten composer, Johann Gambolputty de von Ausfern- schplenden- schlitter- crasscrenbon- fried- digger- dingle- dangle- dongle- dungle- burstein- von- knacker- thrasher- apple- banger- horowitz- ticolensic- grander- knotty- spelltinkle- grandlich- grumblemeyer- spelterwasser- kurstlich- himbleeisen- bahnwagen- gutenabend- bitte- ein- nürnburger- bratwustle- gerspurten- mitz- weimache- luber- hundsfut- gumberaber- shönedanker- kalbsfleisch- mittler- aucher von Hautkopft of Ulm.Given the Pythonic origin of the term &#8220;Spam&#8221;, the best short name for the new Act would have to be similarly surreal, irrelevant and disrespectful. Hence my vote for the &#8220;<strong>Fish-Slapping Dance Act</strong>, <strong>2011</strong>&#8220;. (David Basskin)</p>
<p>Given some of the potential concerns Barry <a href="http://www.barrysookman.com/2011/01/26/impacts-of-bill-c-28-the-new-anti-spam-and-anti-spyware-legislation/">identifies</a> due to overbreadth or sloppy drafting, how about the <strong>Law of Unintended Consequences</strong>? (Richard Pfohl)</p>
<p>How about:  “<strong>An Act to Amend other Acts and do some other things</strong>.” The government could use the same name for all future legislation. And they could advertise it as the <strong>A++ Act</strong>. Very efficient and no less informative… (Michael Erdle)</p>
<p>I&#8217;m fond of the <strong>Spam Spam Spam Spam Spam Spam Spam Spam Spam Spam Spam Spam  Spam Spam Spam Spam Spam Spam Spam Spam Spam Spam Spam Spam Act</strong>.(It&#8217;s even shorter the current name.) (Eric Boehm)</p>
<p><strong>P.P.P.S</strong>. At least no one has (yet) suggested naming the Act for someone, especially a child, who has died in painful circumstances. (Wallace Mclean)</p>
<p><strong>The eCommerce Holy Grail Act</strong>. (Get it? Spam &#8211; Monty Python- Holy Grail)  (Peter Ruby)</p>
<p><strong>Green Eggs and Spam</strong>? (Bernice Karn)</p>
<p>I call dibs on the “<strong>Canada Spam-a-Lot Act</strong>”. (Bernice Karn)</p>
<p><strong>ASS Law</strong> (<strong>Anti Spam and Spyware Law</strong>)? (Bradley Freedman)</p>
<p>Oh heck let’s mix French and English. <strong>Sans-Spam Act</strong> (David Bilinsky)</p>
<p><strong>Spam-a-Little</strong> (Mary Hemmings)</p>
<p><strong>Internet Wish Act</strong> – as in I wish that the anti-spam provisions by the government in this act could actually be enforced without bankrupting the public service. By the way, my Visa has limited internet purchase capacity…an email from germany told me so! WISH could stand for Wise Interneters Suspect Havoc (so they read the screen to delete spam) ((Shaunna Mireau)</p>
<p>How about <strong>Anti-Malware Act</strong>? Short and bilingual&#8230; (Michel Racicot)</p>
<p>Since the statute deals with spam and spyware, and various other nasty practices, perhaps the generic “<strong>Anti-malware Act</strong>” would be appropriate. I expect that most people who do not live and breathe computers may not recognize the term, but it’s still a good one, and a title can be educational as well as convenient. I learn that the recognized Canadian French equivalent is ‘maliciel’, a formation from the very elegant ‘logiciel’ for software (in France that tends to be called ‘le soft’, but we should prefer the elegance of the Canadian formation). So: “Loi contre le maliciel”.  The ‘original’ title was, I believe, the ‘Electronic Commerce Protection Act’, which is fine except that it gives no hint as to the contents. The ‘Fight Internet Spam Act’ is OK, though a little tendentious – better than a lot of political titles. (John Gregory)</p>
<p><strong>Canadian Anti-Spam Act</strong>, which can be further shortened to <strong>CASPA</strong>. (Lorne Salzman)</p>
<p><strong>Can-Can Spam Act</strong> since I’ve been telling people it is sort of the Canadian version of the US Can-Spam Act! (Joel Guralnick)</p>
<p>Using the logic of the DaVinci&#8217;s Code (or the &#8220;USA PATRIOT ACT&#8221;), we should refer to the law as the <strong>PEACE Act</strong> (or perhaps the <strong>e-PEACE Act</strong>). “An Act to <strong>P</strong>romote the <strong>E</strong>fficiency and <strong>A</strong>daptability of the <strong>C</strong>anadian <strong>E</strong>conomy [...] (Charles Morgan)</p>
<p>I&#8217;d like to suggest &#8220;<strong>The CORE</strong><strong> </strong><strong>Discourse Act</strong>&#8221; . I am most certainly not a lawyer, but what I understand of C-28 suggests to me an attempt to describe and moderate Corporate Responsibility in Electronic Discourse.  (Scott Elcomb)</p>
<p>And don&#8217;t forget &#8220;<strong>Canada&#8217;s Anti-Spam Legislation</strong>&#8221; (<strong>CASL</strong>) which is how the legislation is now described (without the acronym) on the <a href="http://www.ic.gc.ca/eic/site/ecic-ceac.nsf/eng/h_gv00567.html">Industry Canada site</a>. CASL gets my vote, but the ultimate decision might be made <a href="http://laws.justice.gc.ca/en/index.html">by Justice Laws</a>.  (Bruce Tattrie)</p>
<p><strong>Canadian Legislation Against Spam &amp; Spyware Act</strong> (or <strong>CLASS Act</strong>, because it’s a CLASS Act that invites a lot of CLASS Action…)  (James Gannon)</p>
<p><strong>Canadian Anti-Spam, Anti-Spyware Act</strong> (<strong>CASASA</strong>, pronounced “Que c’est ça?” in French) (James Gannon)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.barrysookman.com/2011/02/14/naming-canada%e2%80%99s-anti-spamanti-spyware-law/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Name Canada’s Anti-Spam/Anti-Spyware Law</title>
		<link>http://www.barrysookman.com/2011/02/06/name-canada%e2%80%99s-anti-spamanti-spyware-law/</link>
		<comments>http://www.barrysookman.com/2011/02/06/name-canada%e2%80%99s-anti-spamanti-spyware-law/#comments</comments>
		<pubDate>Mon, 07 Feb 2011 01:35:01 +0000</pubDate>
		<dc:creator>Barry Sookman</dc:creator>
				<category><![CDATA[Bill C-28]]></category>
		<category><![CDATA[Bill C-58]]></category>
		<category><![CDATA[E-commerce]]></category>
		<category><![CDATA[Electronic Commerce Protection Act (ECPA)]]></category>
		<category><![CDATA[FISA]]></category>
		<category><![CDATA[FIWSA]]></category>
		<category><![CDATA[misleading advertising]]></category>
		<category><![CDATA[spam]]></category>
		<category><![CDATA[spyware]]></category>
		<category><![CDATA[ECPA]]></category>
		<category><![CDATA[Electronic Commerce Protection Act]]></category>
		<category><![CDATA[spam bill]]></category>

		<guid isPermaLink="false">http://www.barrysookman.com/?p=2644</guid>
		<description><![CDATA[Canada has a new anti-SPAM and anti-spyware law, Bill –C-28. It is a law with an inordinately long name: “An Act to promote the efficiency and adaptability of the Canadian economy by regulating certain activities that discourage reliance on electronic means of carrying out commercial activities, and to amend the Canadian Radio-television and Telecommunications Commission [...]]]></description>
			<content:encoded><![CDATA[<p><span style="font-size: 13.3333px;">Canada has a new anti-SPAM and anti-spyware law, <a href="http://www2.parl.gc.ca/HousePublications/Publication.aspx?Language=E&amp;Parl=40&amp;Ses=3&amp;Mode=1&amp;Pub=Bill&amp;Doc=C-28_4">Bill –C-28</a>. It is a law with an inordinately long name: “An Act to promote the efficiency and adaptability of the Canadian economy by regulating certain activities that discourage reliance on electronic means of carrying out commercial activities, and to amend the Canadian Radio-television and Telecommunications Commission Act, the Competition Act, the Personal Information Protection and Electronic Documents Act and the Telecommunications Act”.</span></p>
<p>The Bill has no short title. As a result different terms and acronyms are being used to refer to it including the ECPA, FISA, FIWSA, the SPAM Bill, the Anti-SPAM Legislation, and the Anti-SPAM and Anti-Spyware Bill.</p>
<p>The Bill needs a short title we can all agree on. I am asking you to help decide what we call it.</p>
<p><strong>Some Background</strong></p>
<p>On April 24, 2009, the Government introduced <a href="http://www2.parl.gc.ca/HousePublications/Publication.aspx?DocId=3832885&amp;Language=e&amp;Mode=1">Bill C-27</a>. It had a short title called <em>the Electronic Commerce Protection Act</em>. Its acronym was the ECPA. It received second reading in the House of Commons. The ECPA died on the Order Paper, however, when it reached the stage of second reading in the Senate, due to the prorogation of Parliament on December 30, 2009.</p>
<p>On 25 May 2010, the Government introduced Bill C-28. This bill was based substantially on Bill C-27. At <a href="http://www2.parl.gc.ca/HousePublications/Publication.aspx?Language=E&amp;Parl=40&amp;Ses=3&amp;Mode=1&amp;Pub=Bill&amp;Doc=C-28_1&amp;File=32%22%20%5Cl%20%221">first reading</a> in the House of Commons, the short title of the Bill was <em>Fighting Internet and Wireless Spam Act</em>. It was also known by the acronyms <a href="http://www.canadiantechnologyiplaw.com/2010/06/articles/privacy/canadian-government-reintroduces-antispam-legislation/">FIWSA</a> or <a href="http://www2.parl.gc.ca/Sites/LOP/LegislativeSummaries/Bills_ls.asp?lang=E&amp;ls=c28&amp;source=library_prb&amp;Parl=40&amp;Ses=3">FISA</a>.<span style="font-size: 13.3333px;"> </span></p>
<p>Bill C-28 was reviewed by the <a href="http://www2.parl.gc.ca/HousePublications/Publication.aspx?DocId=4754401&amp;Language=E&amp;Mode=1&amp;Parl=40&amp;Ses=3">Standing Committee on Industry, Science and Technology</a>. On Tuesday, November 2, 2010, the Committee voted to amend the Bill to remove the short title. The amendment was initiated by NDP MP Brian Masse during the following exchange in the Committee hearings over the short title:</p>
<blockquote><p><span style="text-decoration: underline;">Mr. Brian Masse</span>:</p>
<p>I have just one last quick question. I noticed that the short title of the bill has been amended. We&#8217;ve had some things around that. Who suggested that the short title be changed?</p>
<p><span style="text-decoration: underline;">Mrs. Janet DiFrancesco: </span></p>
<p><span style="font-size: 13.3333px;">The short title of the bill was provided to us.</span></p>
<p>I also can&#8217;t tell you why they dropped a letter out of it. I don&#8217;t what happened to the “W” to go with the initials FISA, but that was the acronym they also gave us when it was tabled.<span style="font-size: 13.3333px;"> </span></p>
<p><span style="text-decoration: underline;">Mr. Brian Masse:</span></p>
<p>I suspected as much.</p>
<p>Thank you very much for your answers. I appreciate them.</p>
<p>Thank you, Mr. Chair. I&#8217;m all done.</p>
<p><span style="text-decoration: underline;">The Chair:</span></p>
<p>There are 92 clauses, so we&#8217;ll postpone the short title, as is the practice per Standing Order 75(1).</p>
<p>(Clauses 2 to 92 inclusive agreed to)</p>
<p>(On clause 1—Short title)…</p>
<p><span style="text-decoration: underline;">The Chair:</span></p>
<p>Shall the short title carry?</p>
<p><span style="text-decoration: underline;">Mr. Brian Masse:</span></p>
<p>No, I&#8217;m not going to agree to the short title. First of all, it wasn&#8217;t from the department. We got into these silly games of naming bills with these little titles here and there. I&#8217;m not going to give them this; it&#8217;s just ridiculous to do this type of stuff. I haven&#8217;t seen this in the years I&#8217;ve been here, so I&#8217;m not supporting this nonsense.</p>
<p><span style="text-decoration: underline;">The Chair:</span></p>
<p>Okay.</p>
<p><span style="text-decoration: underline;">Mr. Anthony Rota:</span></p>
<p>Mr. Chair, just for clarification, if we vote in favour of the title, then it has a title. If we vote against the short title, then it has no title. Am I correct?</p>
<p><span style="text-decoration: underline;">The Chair:</span></p>
<p><span style="font-size: 13.1944px;">That&#8217;s right. We&#8217;ll report it back that way. We&#8217;ll still have the long title.</span></p>
<p><span style="text-decoration: underline;">Mr. Anthony Rota:</span></p>
<p>I just wanted to clarify that. Thank you.</p>
<p><span style="text-decoration: underline;">The Chair:</span></p>
<p>Shall the short title carry? Can I see a show of hands?</p>
<p>(Clause 1 negatived)</p>
<p><span style="text-decoration: underline;">The Chair</span>: It&#8217;s defeated.</p>
<p>Shall the title carry?</p>
<p>Some hon. members: Agreed.</p>
<p><span style="text-decoration: underline;">The Chair:</span> Shall the bill as amended carry?</p>
<p>Some hon. members: Agreed.</p>
<p><span style="text-decoration: underline;">The Chair:</span> Shall I report the bill, as amended to the House?</p>
<p>Some hon. members: Agreed.</p>
<p><span style="text-decoration: underline;">The Chair</span>: Shall the committee order a reprint of the bill?</p>
<p>Some hon. members: Agreed.</p>
<p>The Chair: Gentlemen, that&#8217;s very good work. We have no meeting on Thursday.</p>
<p>The meeting&#8217;s adjourned.</p></blockquote>
<p>The Bill eventually passed the House of Commons and the Senate before being given <a href="http://www2.parl.gc.ca/sites/lop/legisinfo/index.asp?Language=E&amp;Chamber=N&amp;StartList=A&amp;EndList=Z&amp;Session=23&amp;Type=0&amp;Scope=I&amp;query=7019&amp;List=stat">Royal Assent</a> on December 15, 2010. It awaits publication of the regulations and then proclamation, which is expected to occur in the fall of this year.<span style="font-size: 13.1944px;"> </span></p>
<p><strong>You Name the Bill</strong></p>
<p>Bill C-28 is going to be with us for a long time. It is legislation that is very complex and will undoubtedly result in considerable study, litigation (including class action proceedings) and enforcement proceedings before the CRTC. (The Bill is summarized <a href="http://www.ic.gc.ca/eic/site/ecic-ceac.nsf/eng/gv00568.html">here</a>, <a href="http://www.barrysookman.com/2011/01/26/impacts-of-bill-c-28-the-new-anti-spam-and-anti-spyware-legislation/">here</a>, <a href="http://www.barrysookman.com/2011/01/06/canada-passes-anti-spam-and-anti-spyware-law/">here</a>, and <a href="http://www.lexology.com/library/detail.aspx?g=f5266525-0a55-47c5-803a-abdf4bad5a22">here</a>.)</p>
<p>We need a common way of referring to it. We need a short title. What do you think it should be?</p>
<p>I encourage you to email me (bsookman@mccarthy.ca) or post comments on my blog with your recommended short name (and/or acronym) and the reasons for choosing it. I will list the top few suggested names along with some of the main reasons for suggesting it and ask people to let me know their preferences.*</p>
<p>What do you recommend we call the Bill and why?</p>
<p>One of the people to recommend the winning name will be given a McCarthy Tétrault branded gift as a reward for his/her skill.</p>
<p>* By participating, you confirm you are okay with me attributing (or not attributing) suggestions to you, unless you let me know otherwise.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.barrysookman.com/2011/02/06/name-canada%e2%80%99s-anti-spamanti-spyware-law/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Impacts of Bill C-28 (the new anti-SPAM and anti-spyware legislation)</title>
		<link>http://www.barrysookman.com/2011/01/26/impacts-of-bill-c-28-the-new-anti-spam-and-anti-spyware-legislation/</link>
		<comments>http://www.barrysookman.com/2011/01/26/impacts-of-bill-c-28-the-new-anti-spam-and-anti-spyware-legislation/#comments</comments>
		<pubDate>Wed, 26 Jan 2011 20:11:31 +0000</pubDate>
		<dc:creator>Barry Sookman</dc:creator>
				<category><![CDATA[Bill C-28]]></category>
		<category><![CDATA[E-commerce]]></category>
		<category><![CDATA[Electronic Commerce Protection Act (ECPA)]]></category>
		<category><![CDATA[Presentations]]></category>
		<category><![CDATA[address harvesting]]></category>
		<category><![CDATA[ECPA]]></category>
		<category><![CDATA[FIWSA]]></category>
		<category><![CDATA[spam]]></category>
		<category><![CDATA[spyware]]></category>

		<guid isPermaLink="false">http://www.barrysookman.com/?p=2588</guid>
		<description><![CDATA[The new anti-SPAM and anti-spyware legislation (Bill C-28) will have significant implications for entities carrying on business in Canada and for entities doing business with Canadians. Its scope is very broad. Its approach to tacking the challenges posed by SPAM, malware, spyware, false and misleading representations associated with electronic messages, and harvesting of electronic address and personal information, is comprehensive.
The legislation creates [...]]]></description>
			<content:encoded><![CDATA[<p>The new anti-SPAM and anti-spyware legislation (Bill C-28) will have significant implications for entities carrying on business in Canada and for entities doing business with Canadians. Its scope is very broad. Its approach to tacking the challenges posed by SPAM, malware, spyware, false and misleading representations associated with electronic messages, and harvesting of electronic address and personal information, is comprehensive.</p>
<p>The legislation creates significant vicarious and accessorial liability for companies and for their officers and directors with the potential for administrative penalties of up to $10 million and damages awards which can reach $1 million per day or per breach.</p>
<p>Accordingly, you will want to learn about this new legislation and how to comply with its many provisions. To help you do so, I am posting slides prepared by Lorne Salzman and I for the  IT Can Roundtable presentation we gave earlier today on the impacts of Bill C-28.</p>
<p><a style="margin: 12px auto 6px auto; font-family: Helvetica,Arial,Sans-serif; font-style: normal; font-variant: normal; font-weight: normal; font-size: 14px; line-height: normal; font-size-adjust: none; font-stretch: normal; -x-system-font: none; display: block; text-decoration: underline;" title="View Sookman Salzman ITCAN Spam Slides on Scribd" href="http://www.scribd.com/doc/47617311/Sookman-Salzman-ITCAN-Spam-Slides">Sookman Salzman ITCAN Spam Slides</a> <object id="doc_83134370867928" style="outline: none;" classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" width="100%" height="600" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,40,0"><param name="name" value="doc_83134370867928" /><param name="data" value="http://d1.scribdassets.com/ScribdViewer.swf" /><param name="wmode" value="opaque" /><param name="bgcolor" value="#ffffff" /><param name="allowFullScreen" value="true" /><param name="allowScriptAccess" value="always" /><param name="FlashVars" value="document_id=47617311&amp;access_key=key-t03tuyz2zjj2ky3gqlk&amp;page=1&amp;viewMode=list" /><param name="src" value="http://d1.scribdassets.com/ScribdViewer.swf" /><param name="allowfullscreen" value="true" /><param name="flashvars" value="document_id=47617311&amp;access_key=key-t03tuyz2zjj2ky3gqlk&amp;page=1&amp;viewMode=list" /><embed id="doc_83134370867928" style="outline: none;" type="application/x-shockwave-flash" width="100%" height="600" src="http://d1.scribdassets.com/ScribdViewer.swf" flashvars="document_id=47617311&amp;access_key=key-t03tuyz2zjj2ky3gqlk&amp;page=1&amp;viewMode=list" allowscriptaccess="always" allowfullscreen="true" wmode="opaque" bgcolor="#ffffff" name="doc_83134370867928" data="http://d1.scribdassets.com/ScribdViewer.swf"></embed></object></p>
]]></content:encoded>
			<wfw:commentRss>http://www.barrysookman.com/2011/01/26/impacts-of-bill-c-28-the-new-anti-spam-and-anti-spyware-legislation/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Canada Passes Anti-Spam and Anti-Spyware Law</title>
		<link>http://www.barrysookman.com/2011/01/06/canada-passes-anti-spam-and-anti-spyware-law/</link>
		<comments>http://www.barrysookman.com/2011/01/06/canada-passes-anti-spam-and-anti-spyware-law/#comments</comments>
		<pubDate>Thu, 06 Jan 2011 17:16:46 +0000</pubDate>
		<dc:creator>James Gannon Charles S. Morgan Lorne P. Salzman</dc:creator>
				<category><![CDATA[E-commerce]]></category>
		<category><![CDATA[Electronic Commerce Protection Act (ECPA)]]></category>
		<category><![CDATA[anti-spam]]></category>
		<category><![CDATA[ECPA]]></category>
		<category><![CDATA[spam]]></category>
		<category><![CDATA[spam bill]]></category>
		<category><![CDATA[spyware]]></category>

		<guid isPermaLink="false">http://www.barrysookman.com/?p=2484</guid>
		<description><![CDATA[Organizations that conduct business online should start preparing for Canada’s new anti-spam and anti-spyware legislation, which was passed in mid-December and is expected to come into force later this year.1 As the Act is complex and the penalties for violating the new law can be severe, organizations should review and modify their online practices, where [...]]]></description>
			<content:encoded><![CDATA[<p>Organizations that conduct business online should start preparing for Canada’s new anti-spam and anti-spyware legislation, which was passed in mid-December and is expected to come into force later this year.<sup>1</sup> As the Act is complex and the penalties for violating the new law can be severe, organizations should review and modify their online practices, where necessary, at an early opportunity.</p>
<div><strong>Anti-Spam Provisions</strong></div>
<p>The Act prohibits organizations from sending commercial electronic messages unless the recipient has given express or implied consent. A &#8220;commercial&#8221; electronic message is an electronic message where one of its purposes is to encourage participation in commercial activity. An &#8220;electronic message&#8221; is defined broadly to include any &#8220;message sent by any means of telecommunication, including a text, sound, voice or image message.&#8221; This covers e-mails, text messages, instant messages, &#8220;tweets&#8221; or Facebook® postings, but excludes two-way voice communication, faxing to a telephone account or accessing a voice mailbox.</p>
<p>When requesting express consent to send a commercial electronic message, an organization must &#8220;clearly and simply&#8221; set out the purpose(s) for which consent is being sought and identify the organization seeking the consent. However, consent is not required to send a commercial electronic message where the purpose is to:</p>
<ul>
<li>provide a quote or estimate in response to a request;</li>
<li>facilitate, complete or confirm a pre-agreed commercial transaction;</li>
<li>provide warranty, product recall or safety information to a purchaser of goods;</li>
<li>provide information related to an ongoing subscription, membership, account or loan;</li>
<li>provide information related to an employment relationship; or</li>
<li>deliver a pre-authorized product, goods or service, including product updates and upgrades<strong>.</strong></li>
</ul>
<p>Consent to receive messages can also be implied, most notably where:</p>
<ul>
<li>the sender and the recipient have an existing business relationship or non-business relationship (<em>e.g.</em>, membership in a club), where the relationship arose within the past two years or is pursuant to a contract in effect in the past two years;</li>
<li>the recipient has &#8220;conspicuously published&#8221; its electronic address and has not indicated a desire to not receive unsolicited commercial electronic messages, <em>and</em> the message is relevant to the recipient’s business role; or</li>
<li>the recipient has provided its electronic address to the sender without indicating a wish not to receive unsolicited commercial electronic messages, <em>and</em> the message is relevant to the recipient’s business role.</li>
</ul>
<p>The Act also requires that all commercial electronic messages must identify the sender, include the sender’s contact information, and provide an &#8220;unsubscribe&#8221; mechanism so that recipient can opt out of receiving future communications.</p>
<div><strong>Anti-Spyware Provisions</strong></div>
<div><strong> </strong></div>
<div>To combat spyware, malware and other malicious software, the Act prohibits the installation of computer programs without the consent of the computer’s user or owner. When consent to install the program is requested, it must &#8220;describe clearly and simply the function and purpose of every computer program that is to be installed.&#8221;</div>
<p>In addition, if a program performs certain potentially undesirable functions, it must bring its &#8220;foreseeable impacts&#8221; to the attention of the user. The prescribed list of undesirable functions includes:</p>
<ul>
<li>collecting personal information stored on the computer system;</li>
<li>interfering with the user’s control of the computer system;</li>
<li>changing or interfering with settings or preferences on the computer system without the user’s knowledge;</li>
<li>interfering with access to or use of that data on the computer system;</li>
<li>causing the computer system to communicate with another computer system without the authorization of the user; or</li>
<li>installing a computer program that may be activated by a third party without the knowledge of the user.</li>
</ul>
<p>These requirements apply not only to personal computers and computer servers, but also to any electronic device that allows for the installation of third-party programs — such as smartphones and tablets. Programs are exempted from these requirements only if it is reasonable to conclude from the recipient’s conduct that the recipient consented to the installation of the programs (<em>e.g</em>., HTML code, Web cookies, javascript code, operating systems, patches and add-ons). Program upgrades and updates are also exempt if the recipient consented to the initial installation and is entitled to receive upgrades or updates<strong>.</strong></p>
<p><strong>Amendments to the <em>Competition Act </em>and <em>PIPEDA</em><sup>2</sup></strong></p>
<p>The Act amends the <em>Competition Act</em> to prohibit false or misleading representations in the sender description, subject matter field or message field of an electronic message, or in the URL or other locater on a webpage. Senders will have to be particularly wary of making overly boastful statements in subject matter lines in an attempt to catch readers’ attention.</p>
<p>The Act also amends <em>PIPEDA, </em>to prohibit the collection of personal information by means of unauthorized access to computer systems, and the unauthorized compiling of lists of electronic addresses (sometimes called &#8220;address harvesting&#8221;).</p>
<div><strong>Enforcement and Penalties</strong></div>
<div>Violators of the anti-spam and anti-spyware provisions of the Act could face fines of up to $1 million for individuals and $10 million for organizations per violation. Officers and directors can also be penalized if they directed, authorized, acquiesced in or participated in the offending conduct. The Act is enforced by the Canadian Radio-television and Telecommunications Commission.</div>
<p>The Act also creates a private right of action that allows any business or consumer to take civil action directly against anyone who violates the Act, or the new false or misleading representations provisions of the <em>Competition Act</em>. The Act contemplates that a litigant will be able to recover its actual damages <em>and </em>additional amounts that could amount to as much as $1 million per day. These latter provisions will undoubtedly excite the plaintiff class action bar.</p>
<div><strong>McCarthy Tétrault Notes</strong></div>
<div>While aimed at preventing spam and spyware, the Act imposes strict requirements on all businesses that use electronic communication. Any company conducting business online (including through e-mails) should be aware of these new requirements and may need to adapt their business practices. In order to prepare for the Act coming into force, which is expected in the next six to nine months, organizations should consider taking the following steps:</div>
<ul>
<li>review and update website privacy policies and terms and conditions to ensure proper consents for the collection of personal information and/or the installation of computer programs on dynamic websites;</li>
<li>review and update their forms for obtaining express consent to send commercial electronic messages (including e-mail or newsletters), or install software programs to ensure that the forms satisfy the prescribed requirements;</li>
<li>re-examine their procedures for documenting the receipt of consent, as the onus will rest on senders and software developers to prove they obtained consent;</li>
<li>ensure that any commercial electronic message contains the prescribed information and an unsubscribe mechanism that is operational for the specified period;</li>
<li>deal with unsubscribe requests within the requisite time frame;</li>
<li>ensure that any process that involves online collection of e-mail addresses or other personal information complies with the amendments to the <em>PIPEDA</em>;</li>
<li>generally review and revise marketing, advertising and external communication practices to comply with the requirements of the Act and the new provision of the <em>Competition Act</em>; and</li>
<li>in the case of software developers:
<ul>
<li>examine their program-installation procedures to ensure that information about the function and purpose of the program is provided prior to installation;</li>
<li>if the program performs one of the prescribed undesirable functions, the disclosure mechanism will also need to describe the foreseeable impacts of these functions; and</li>
<li>revise end-user licence agreements (EULAs) to ensure that consent to install patches and upgrades is expressly obtained before installation of computer programs.</li>
</ul>
</li>
</ul>
<div><strong></strong></div>
<p><strong><br />
<hr /></strong> <sup><strong>1</strong></sup> The full name of the Act is long, and quite unmemorable: &#8220;An Act to promote the efficiency and adaptability of the Canadian economy by regulating certain activities that discourage reliance on electronic means of carrying out commercial activities, and to amend the <em>Canadian Radio-television and Telecommunications Commission Act</em>, the <em>Competition Act</em>, the <em>Personal Information Protection and Electronic Documents Act</em> and the<em> Telecommunications Act.</em>&#8221; The Act will come into force upon proclamation.</p>
<p><sup>2</sup><em> Personal Information Protection and Electronic Documents Act</em>, which is the primary federal statute that addresses privacy matters.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.barrysookman.com/2011/01/06/canada-passes-anti-spam-and-anti-spyware-law/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Developments in Computer, Internet and E-Commerce Law (2009-2010)</title>
		<link>http://www.barrysookman.com/2010/05/26/developments-in-computer-internet-and-e-commerce-law-2009-2010/</link>
		<comments>http://www.barrysookman.com/2010/05/26/developments-in-computer-internet-and-e-commerce-law-2009-2010/#comments</comments>
		<pubDate>Wed, 26 May 2010 18:00:40 +0000</pubDate>
		<dc:creator>Barry Sookman</dc:creator>
				<category><![CDATA[Copyright]]></category>
		<category><![CDATA[Criminal Law]]></category>
		<category><![CDATA[E-commerce]]></category>
		<category><![CDATA[Electronic Commerce Protection Act (ECPA)]]></category>
		<category><![CDATA[Fair Dealing]]></category>
		<category><![CDATA[Fair Use]]></category>
		<category><![CDATA[Fundamental breach]]></category>
		<category><![CDATA[Google Book Scanning]]></category>
		<category><![CDATA[Graduated Response]]></category>
		<category><![CDATA[ISP Liability]]></category>
		<category><![CDATA[IT Contracts]]></category>
		<category><![CDATA[Limitations of liability]]></category>
		<category><![CDATA[Patents]]></category>
		<category><![CDATA[Piracy]]></category>
		<category><![CDATA[Presentations]]></category>
		<category><![CDATA[Privacy]]></category>
		<category><![CDATA[Trade Marks]]></category>
		<category><![CDATA[data protection]]></category>
		<category><![CDATA[human rights]]></category>
		<category><![CDATA[intellectual property]]></category>
		<category><![CDATA[isohunt]]></category>
		<category><![CDATA[p2p piracy]]></category>
		<category><![CDATA[computer law]]></category>
		<category><![CDATA[ecommerce law]]></category>
		<category><![CDATA[internet law]]></category>
		<category><![CDATA[spam]]></category>
		<category><![CDATA[spyware]]></category>
		<category><![CDATA[toronto computer lawyers group presentation]]></category>
		<category><![CDATA[trademarks]]></category>

		<guid isPermaLink="false">http://www.barrysookman.com/?p=1464</guid>
		<description><![CDATA[Here are the slides used in my presentation to the Toronto Computer Lawyers Group earlier today,  The Year in Review: Developments in Computer, Internet and E-Commerce Law (2009-2010). It covers significant developements since my talk last spring.
The slides include a summary of the following cases and statutory references:
Tercon Contractors Ltd. v. British Columbia, 2010 SCC 4
Internet Broadcasting [...]]]></description>
			<content:encoded><![CDATA[<p>Here are the slides used in my presentation to the Toronto Computer Lawyers Group earlier today,  <em>The Year in Review: Developments in Computer, Internet and E-Commerce Law (2009-2010)</em>. It covers significant developements since my talk last spring.</p>
<p>The slides include a summary of the following cases and statutory references:</p>
<p><em>Tercon Contractors Ltd. v. British Columbia</em>, 2010 SCC 4</p>
<p><em>Internet Broadcasting Corporation Ltd. v Mar LLC</em> [2009] EWHC 844 (Ch)</p>
<p><em>Gammasonics Institute for Medical Research Pty Ltd v Comrad Medical Sysytems Pty Ltd </em>[2010] NSWSC 267 (9 April 2010)</p>
<p><em>Kingsway Hall Hotel Ltd. v Red Sky IT (Hounslow) Ltd.</em> [2010] EWHC 965</p>
<p><em>BSkyb Ltd v HP Enterprise Services UK Ltd</em> [2010] EWHC 86 (TCC) (26 January 2010)</p>
<p><em>Griffin v. Dell Canada Inc.</em>, 2010 ONCA 29</p>
<p><em>Tracfone Wireless, Inc. v Anadisk LLC</em> 2010 WL 565392 (S.D.Fla. Feb 18, 2010)</p>
<p><em>Defrontes v Dell Inc.</em> 984 A.2d 106<em>1</em> (Sup.Ct.RH.Isld.2009)</p>
<p><em>Major v McCallister</em> (Miss.CT.App. Dec 23, 2009)</p>
<p><em>DC Laboratories, Inc. v. Hach Co.</em>, 2009 WL 2605270 (C.D.Ill.,Aug 25, 2009)</p>
<p><em>Hines v. Overstock.com, Inc.</em> 668 F.Supp.2d 362 (E.D.N.Y. 2009)</p>
<p><em>Tradecomet.com LLC v Google, Inc.</em> 2010 WL 779325 (S.D.N.Y. Mar. 5, 2010)</p>
<p><em>Scherillo v. Dun &amp; Bradstreet, Inc.</em> 684 F.Supp.2d 313 (E.D.N.Y.2010.)</p>
<p><em>LTVN Holdings LLC v. Odeh</em> 2009 WL 3736526 (D.Md.2009)</p>
<p><em>Brodsky v. Match.com LLC</em>  2009 WL 3490277 (S.D.N.Y. Oct. 28, 2009)</p>
<p><em>Miller v. Facebook, Inc.</em>, No. 09-02810 (N.D. Ga. Jan. 15, 2010)</p>
<p><em>National Auto Lenders, Inc. v. SysLOCATE, Inc.</em> 2010 WL 527866 (S.D.Fla.Feb. 10, 2010)</p>
<p><em>Carimate v. Ginsglobal Index Funds</em> 2009 WL 3233538 (C.D.Cal.Sept.30, 2009)</p>
<p><em>Thomas &amp; Anor v BPE Solicitors</em> (A Firm) [2010] EWHC 306 (Ch) (19 February 2010)</p>
<p><em>Grant v. Torstar Corp.</em>, 2009 SCC 61</p>
<p><em>Crookes v. Newton</em>, 2009 BCCA 392, (leave to SCC granted)</p>
<p><em>Metropolitan International Schools Ltd. v Designtechnica Corp</em> [2009] EWHC 1765 (QB) (16 July 2009)</p>
<p><em>R. v. Morelli</em>, 2010 SCC 8</p>
<p>Review of the Internet traffic management practices of Internet service providers, Telecom Regulatory Policy CRTC 2009-657, Oct. 21, 2009)</p>
<p>Bill C-22 An Act respecting the mandatory reporting of Internet child pornography by persons who provide an Internet service</p>
<p>Notice Paper, May 25, 2010 &#8211; INTRODUCTION OF GOVERNMENT BILLS http://ow.ly/1OatI</p>
<p><em>Lucasfilm Ltd &amp; Ors v Ainsworth &amp; Anor</em> [2009] EWCA Civ 1328 (16 December 2009)</p>
<p><em>Editions du Seuil v Google Inc</em>, Tribunal de Grande Instance de Paris 3ème chambre, 2ème section Ruling of December 18, 2009</p>
<p><em>Columbia Pictures Industries Inc v Fung</em>  2:06-cv-05578-SVW-JC (C.D. Cal. May 20, 2010)</p>
<p><em>Banyan Tree Holding (P) Limited v Reddy</em> CS (OS) No. 894/2008 (H.C.Delhi. Nov. 23, 2009)</p>
<p>Sheppard &amp; Anor, R v [2010] EWCA Crim 65 (29 January 2010)</p>
<p>PIPEDA Case Summary #2009-010 Report of Findings &#8211; Assistant Commissioner recommends Bell Canada inform customers about Deep Packet Inspection</p>
<p><em>Johnson et al. v. Microsoft Corp.</em> (W.D. Wash., June 2009)</p>
<p><em>EMI Records &amp; Ors -v- Eircom Ltd</em>,  [2010] IEHC 108</p>
<p>PIPEDA Case Summary #2009-013 Publisher collected and used e-mail addresses for marketing without consent</p>
<p><em>R. v. Cuttell</em>, 2009 ONCJ 471</p>
<p><em>Carter v. Connors</em>, 2009 NBQB 317</p>
<p><em>Warman v. Fournier et al</em>, 2010 ONSC 2126</p>
<p><em>Boring v Google Inc.</em> 2010 WL 318281 (3rd.Cir.Jan 28, 2010)</p>
<p>PIPEDA Case Summary #2009-008 Report of Findings into the Complaint Filed by CIPPIC against Facebook Inc (July 22, 2009)</p>
<p><em>Poliquin v. Devon Canada Corporation</em>, 2009 ABCA 216 (Alta.C.A.)</p>
<p>Bill S-4: An Act to amend the Criminal Code (identity theft and related misconduct) (in force Jan 8, 2010)</p>
<p>Bill C-28 Fighting Internet and Wireless Spam Act</p>
<p>BILL C-29 An Act to amend PIPEDA</p>
<p><em>SOCAN v. Bell Canada</em>, 2010 FCA 123</p>
<p><em>Telstra Corporation Limited v. Phone Directories Company Pty Ltd.</em> [2010] FCA 44 (8 February 2010)</p>
<p><em>RecordTV Pte Ltd v MediaCorp TV Singapore Pte Ltd</em> [2009] SGHC 287</p>
<p><em>Roadshow Films Pty Ltd v  iiNet  Limited</em> (No. 3) [2010] FCA 24 (4 February 2010)</p>
<p><em>Twentieth Century Fox Film Corporation v. Newzbin Ltd.</em>, [2010] EWHC 601 (Ch) (29 March 2010)</p>
<p><em>Arista Records LLC v Usenet.com Inc.</em> 91 USPQ2d 1744 (S.D.N.Y.2009)</p>
<p>EMI Records &amp; Ors -v- Eircom Ltd<em>, [2010] IEHC 108</em></p>
<p><em>Columbia Pictures Industries Inc v Fung</em>  2:06-cv-05578-SVW-JC (C.D. Cal. Dec. 21, 2009)</p>
<p><em>Arista Records, LLC v Lime Wire Group</em>  2010 WL 1914816 (S.D.N.Y.2010)</p>
<p><em>Sony BMG  Music Entertainment v Tenenbaum</em>, 2009 WL 4547019 (D.Mass. Dec 7, 2009).</p>
<p><em>Brein v Mininova. B.V.</em>, District Court of Utrecht, 26 August 2009</p>
<p><em>Louis Vuitton Malletier, S.A. v. Akanoc Solutions, Inc.</em> (N.D. Cal. March 19, 2010)</p>
<p><em>Autodesk, Inc v Dassault Systems Solidworks Corp.</em> 2009 WL 5218009 (N.D.Cal. Dec. 31, 2009)</p>
<p><em>Tiffany (NJ) Inc. v eBay Inc.</em> 600 F.3d 93 (2nd.Cir.2010)</p>
<p><em>Google France v Louis Vuitton Malletier</em>, Official Journal of the European Union 22.5.2010</p>
<p><em>Silvaco Data Systems v. Intel Corp.</em> 2010 WL 1713241 (Cal.App. 6 Dist.2010)</p>
<p><a style="margin: 12px auto 6px auto; font-family: Helvetica,Arial,Sans-serif; font-style: normal; font-variant: normal; font-weight: normal; font-size: 14px; line-height: normal; font-size-adjust: none; font-stretch: normal; -x-system-font: none; display: block; text-decoration: underline;" title="View DOCS-#1270489-V10-Sookman TCLG 2010 Year in Review on Scribd" href="http://www.scribd.com/doc/31988256/DOCS-1270489-V10-Sookman-TCLG-2010-Year-in-Review">DOCS-#1270489-V10-Sookman TCLG 2010 Year in Review</a> <object id="doc_524881847889674" style="outline: none;" classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" width="100%" height="600" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,40,0"><param name="name" value="doc_524881847889674" /><param name="data" value="http://d1.scribdassets.com/ScribdViewer.swf" /><param name="wmode" value="opaque" /><param name="bgcolor" value="#ffffff" /><param name="allowFullScreen" value="true" /><param name="allowScriptAccess" value="always" /><param name="FlashVars" value="document_id=31988256&amp;access_key=key-1zouh0qlrf9x2nwm9sqk&amp;page=1&amp;viewMode=slideshow" /><param name="src" value="http://d1.scribdassets.com/ScribdViewer.swf" /><param name="allowfullscreen" value="true" /><param name="flashvars" value="document_id=31988256&amp;access_key=key-1zouh0qlrf9x2nwm9sqk&amp;page=1&amp;viewMode=slideshow" /><embed id="doc_524881847889674" style="outline: none;" type="application/x-shockwave-flash" width="100%" height="600" src="http://d1.scribdassets.com/ScribdViewer.swf" flashvars="document_id=31988256&amp;access_key=key-1zouh0qlrf9x2nwm9sqk&amp;page=1&amp;viewMode=slideshow" allowscriptaccess="always" allowfullscreen="true" wmode="opaque" bgcolor="#ffffff" name="doc_524881847889674" data="http://d1.scribdassets.com/ScribdViewer.swf"></embed></object></p>
]]></content:encoded>
			<wfw:commentRss>http://www.barrysookman.com/2010/05/26/developments-in-computer-internet-and-e-commerce-law-2009-2010/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Government introduces bills to fight SPAM and spyware and to amend PIPEDA</title>
		<link>http://www.barrysookman.com/2010/05/25/government-introduces-bills-to-fight-spam-and-spyware-and-to-amend-pipeda/</link>
		<comments>http://www.barrysookman.com/2010/05/25/government-introduces-bills-to-fight-spam-and-spyware-and-to-amend-pipeda/#comments</comments>
		<pubDate>Wed, 26 May 2010 01:42:30 +0000</pubDate>
		<dc:creator>Barry Sookman</dc:creator>
				<category><![CDATA[Electronic Commerce Protection Act (ECPA)]]></category>
		<category><![CDATA[Privacy]]></category>
		<category><![CDATA[address harvesting]]></category>
		<category><![CDATA[PIPEDA]]></category>
		<category><![CDATA[spam]]></category>
		<category><![CDATA[spyware]]></category>

		<guid isPermaLink="false">http://www.barrysookman.com/?p=1448</guid>
		<description><![CDATA[Earlier today the Government introduced two important Bills &#8211; Bills C-28 and C-29.
Bill C-28, Fighting Internet and Wireless Spam Act, is the re-introduction of the Electronic Commerce Protection Act (ECPA). It is essentially the Bill as passed by the House of Commons just before the olympics with a few changes. Most of the changes are [...]]]></description>
			<content:encoded><![CDATA[<p>Earlier today the Government introduced two important Bills &#8211; Bills C-28 and C-29.</p>
<p>Bill C-28, <em>Fighting Internet and Wireless Spam Act,</em> is the re-introduction of the <em>Electronic Commerce Protection Act</em> (ECPA). It is essentially the Bill as passed by the House of Commons just before the olympics with a few changes. Most of the changes are to harmonize the language to drafting conventions or to clarify the legislative intent.</p>
<p>The Bill is a major improvement over the initial version of the ECPA which was significantly improved during the Industry Committee review.</p>
<p>The Bill would do the following:</p>
<p>•	Prohibit the sending of commercial electronic messages without prior consent.</p>
<p>•	Prohibit alteration of transmission data to route the message to an unintended destination.</p>
<p>•	Prohibit installation or use of spyware in the course of commercial activities (there are exceptions for cookies, html code, java scripts and operating systems).</p>
<p>•	Amend the <em>Competition Act</em> to prohibit false or misleading commercial representations made electronically.</p>
<p>•	Amend PIPEDA to prohibit the collection of personal information by means of unauthorized access to computer systems in violation of federal laws, and the unauthorized automated compiling of lists of electronic addresses.</p>
<p>Bill C-29 is a new piece of legislation that will amend PIPEDA. It would do the following:</p>
<p>•	Exclude business contact information from being personal information.</p>
<p>.•	Specify the elements of valid consent (“the consent of an individual is only valid if it is reasonable to expect that the individual understands the nature, purpose and consequences of the collection, use or disclosure of personal information to which they are consenting”).</p>
<p>•	Require organizations to report material data breaches of personal information to the Privacy Commissioner of Canada, and to notify affected individuals when the breach poses a real risk of significant harm, such as identity theft or fraud, or damage to reputation.</p>
<p>•	Create exceptions for prospective and completed business transactions such as the purchase of an organization or assets, M&#038;A transactions, financings and loans, taking security, lease or license transactions, other arrangements to conduct a business activity.</p>
<p>•	Permit organizations to collaborate with government institutions, such as law enforcement and security agencies that have requested personal information, in the absence of a warrant, subpoena, or order.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.barrysookman.com/2010/05/25/government-introduces-bills-to-fight-spam-and-spyware-and-to-amend-pipeda/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

