Regulating content on the Internet: A new technological perspective

Spectrum Management and Telecommunications

Appendix A — Author Bios

Dr. Gerri Sinclair is currently the Executive Director of the Masters of Digital Media Program at Great Northern Way Campus, a collaborative partnership between the University of B.C., Simon Fraser University, Emily Carr Institute of Art + Design, and the B.C. Institute of Technology. Most recently she was the Chair of the Canadian Federal Government's Telecom Policy Review Panel, advising the Federal Government on the future policy and regulatory environment required to support an advanced telecommunications framework. She was also the General Manager of MSN Canada and a senior member of the Microsoft executive team, as well as the founder and CEO of NCompass Labs, an Internet content management company acquired by Microsoft in 2001. A former visiting scientist at IBM Research, Dr. Sinclair was also the president of the British Columbia Government Premier's Technology Council, and the founding director of the ExCITE lab at Simon Fraser University, the first multimedia educational technology centre in Canada. She has served on several government and corporate boards including Telus Corporation and BC Telecom, and is currently a director of the Toronto Stock Exchange, Ballard Power, Genome B.C., the Canadian Foundation for Innovation and the Canadian Communications Research Council.

Julie Zilber is Co-Director of 7th Floor Media at Simon Fraser University, Canada's seminal new media development, prototyping and consulting centre. A former lawyer specializing in intellectual property law, Julie Zilber joined 7th Floor Media (then ExCITE) in 1990. She has a long history of working with governmental and non-governmental organizations to answer important questions combining human, technical and policy issues. She has led research teams investigating issues ranging from human factors, interface, and technological design for on-line educational delivery systems to government policy on broadband connectivity for remote and rural communities. Julie was co-author of the 1999 report Regulation of the Internet: A Technological Perspective. In addition, she has led many new media product development teams, provided consulting services related to interface and Web site design, and conducted evaluations of internet-based on-line learning platforms. She is a Research Leader for the Mobile MUSE Research Network, a member of the Board of the Virtual School Society of British Columbia, and Vice-Chair of Lions Gate Learning Alliance. She is also the Founding Director of LinguaComm Enterprises Inc., which develops engaging and intuitive voice-driven learning applications for network connected mobile devices.

Ed Hargrave is one of Western Canada's most experienced network strategists. For over 20 years, he has acted as a technical architect and consultant for a wide range of public and private sector organizations in Canada including Simon Fraser University, various school districts and community colleges in B.C., the Province of British Columbia, the Government of the Northwest Territories, Shaw Communications, BC Lottery Corporation, MacDonald Detweiller, Siebel Systems and Hewlett Packard. Ed Hargrave was a member of the original research team for Regulation of the Internet: A Technology Perspective, and has collaborated on a number of technology research projects, including Sustainable Broadband Networks in British Columbia's Remote and Rural Communities, a report and recommendations for the BC Premier's Technology Council. He currently heads the Network Management Practice for Steeves and Associates.

Appendix B — List of Interviewees

The following individuals were interviewed by the researchers during the course of the research.

List of Interviewees
Organization	Interviewee
Audible Magic	Jeremy Stern, Vice President of Business Development.
Bell Canada	William Crago, Senior Scientist Technology. Michael Tanglao, Vice-President Corporate Affair. Yvonne Stienberg, Executive Assistant to Michael Tanglao.
University of Ottawa	Michael Geist, Canada Research Chair in Internet and ECommerce Law, Faculty of Law.
Canoe/MSN	Stephen Evans, Vice-President, Portal & Emerging Products.
Carleton University	Thom Whalen, Professor of New Media.
comScore Canada Inc.	Brent Bernie, President.
Consultant	Claude Gallipeau
CRTC	Namir Anani, Executive Director, Policy Development & Research Sector. Chris Seidl, Director, New Media and Technology. Steve Harroun, Manager, New Media Research.
Google	Vinton Cerf, Vice-President and Chief Internet Evangelist.
Industry Canada	Len St-Aubin, Director General of Industry Canada Telecommunications Policy Branch.
ISOC	Leslie Daigle, Chief Internet Technology Officer.
McCarthy Tetrault	Peter Grant, Senior Counsel.
Narus, Incorporated	Greg Oslan, Chief Executive Officer and President.
Quebecor/Vidéotron	Edouard Trepanier, Vice-President, Regulatory Affairs.
Rogers	Michael Lee, Vice-President and Chief Strategy Officer.
Shaw Cablesystems	Ken Stein, Senior Vice-President, Corporate and Regulatory Affairs.
Telus	Tim Fell, Director, Technology Strategy. Mike Hennessey, Vice-President-Wireless, Broadband and Content Policy. Craig McTaggart, Director of Regulatory Affairs. David Neale, Senior VP — Consumer Products & Services. Kevin Salvadori, Executive Vice President Transformation and CIO.
University of Toronto	Ronald Deibert, Assoc. Prof. Political Science; Director of the Munk Centre for International Studies.
Vancouver Police Dept	Kevin McQuiggan & members of VPD cybercrime team.
Videotron	Charles Boyer, Director, Government Relations, Videotron Pierre Roy, Vice-President, IP Technologies

Appendix C — IP Packets

Structure of IP Packet Headers⁷⁴

IP packets are composed of a header and payload. The IPv4 packet header consists of:

4 bits that contain the version, that specifies if it's an IPv4 or IPv6 packet,
4 bits that contain the Internet Header Length which is the length of the header in multiples of 4 bytes. Ex. 5 is equal to 20 bytes.
8 bits that contain the Type of Service, also referred to as Quality of Service (QoS), which describes what priority the packet should have,
16 bits that contain the length of the packet in bytes,
16 bits that contain an identification tag to help reconstruct the packet from several fragments,
3 bits that contain a zero, a flag that says whether the packet is allowed to be fragmented or not (DF: Don't fragment), and a flag to state whether more fragments of a packet follow (MF: More Fragments)
13 bits that contain the fragment offset, a field to identify which fragment this packet is attached to,
8 bits that contain the Time to live (TTL) which is the number of hops (router, computer or device along a network) the packet is allowed to pass before it dies (for example, a packet with a TTL of 16 will be allowed to go across 16 routers to get to its destination before it is discarded),
8 bits that contain the protocol (TCP, UDP, ICMP, etc...)
16 bits that contain the Header Checksum, a number used in error detection,
32 bits that contain the source IP address,
32 bits that contain the destination address.

After those, optional flags can be added of varied length, which can change based on the protocol used, then the data that packet carries is added. An IP packet has no trailer. However, an IP packet is often carried as the payload inside an Ethernet frame, which has its own header and trailer.

Explanation of Packets, Headers, and Payloads

The Internet is a "packet switched" network. This means that the data transferred over the network is broken into small formatted blocks. Packets consist of two types of information: control information and the user data (or "payload"). The control information provides the data the network needs in order to deliver the packet to its destination and to reassemble the packets after they have been received by the client. On networks using the Internet protocol, the control information is contained in the packet "header."

The payload is what you would normally think of as the "content" of the file. However, since IP networks have maximum packet sizes, most files will not fit inside a single packet. Files are therefore broken up into fragments, and reassembled (using the fragment offset information in the packet headers) after the packets have been delivered. An analogy is to think of the header a courier envelope, with the waybill indicating type of service, recipient's address, declared value, etc., and the payload as the contents of the envelope. If we carry the analogy one step further, we can think of someone using small courier envelopes to send a large picture, which has to be cut into small pieces in order to fit into the envelopes. The packages (packets) are picked up by different couriers; go off in different courier trucks; are put on different airplanes; and are delivered by different couriers; whereupon the recipient reassembles the picture.

Appendix D — Bytes & Bits

This report contains frequent references to bytes and bits per second. Bits and bytes refer to units of data storage. Generally, a byte is equal to eight bits, and is the amount of storage required for a single text character. Network speeds are measured in "bits per second" (bps). So, for example, a connection speed of 4 megabits per second (mbps) can transfer 500KB or (½ a megabyte) of data per second. The following table sets out common terms used to refer to quantities of bytes.

Quantities of Bytes
Name	Abbrev.	Number of Bytes (in powers of 10)	Number of Bytes (written in full)	Equivalent to
Kilobyte	KB	10³	1,000	100 typewritten words
Megabyte	MB	10⁶	1,000,000	This report (without the graphics)
Gigabyte	GB	10⁹	1,000,000,000	A pickup truck filled with books
Terabyte	TB	10¹²	1,000,000,000,000	The collection of the Library of Canada
Petabyte	PB	10¹⁵	1,000,000,000,000,000	1000 times the collections of the Library of Canada
Exabyte	EB	10¹⁸	1,000,000,000,000,000,000	More than three times all of the information transferred over the Internet in 2000

Appendix E — A Short List of Web Sites with Links to Proxy Servers

There are hundreds of Web sites with links of anonymizing proxy servers, and many of these sites list well over one hundred servers. Some sites are focused on servers that unblock specific sites (e.g., Facebook, MySpace), while others provide links to more generalized proxy servers. The list below consists simply of the first ten links displayed in a search conducted on google.ca for the term "proxy server" on February 27, 2008.

http://www.tech-faq.com/proxy-sites.shtml

http://www.proxybeat.com/

http://www.bestproxysites.com/

http://www.forproxyusers.com/

http://www.proxy-sites.info/

http://www.allproxysites.com/

http://accesstoblockedsites.com/

http://meoso.com/

http://www.proxysite.org/

http://www.proxytoolbox.com/list

⁷⁴ This explanation is taken from http://en.wikipedia.org/wiki/Data_packet.

First