Update: CRTC PN 2008-19 ISP Filing Summary Document

200902132334.jpgI’ve updated my initial ISP Filing Summary document with the information that ISPs provided on February 9, 2008 per the CRTC’s February 4, 2009 request. Updates to the document are made in blue. The updates to not include Videotron’s response to 1 (c).

I would maintain that the most interesting parts of was was released have been summarized in a post from two days ago, which was entitled “Update: CRTC PN 2008-19 Filings“. Tomorrow, I should be posting a document that correlates data the CRTC aggregated and anonymized with the ISPs who were required to release anonymized data. My hope is that this will make it a bit clearer who data might be associated with.

Update: ‘More Secure’ (non-EDL) Drivers Licenses Coming to BC Soon!

200902131709.jpgAs I’ve written about before, Enhanced Drivers Licenses (EDLs) are coming to British Columbia, as well as many other provinces around the country (I have a wiki page set up to collate information on EDLs). It seems that, at the same time the BC is rolling out EDLs, they are updating their ‘regular’ licenses.

The Canadian Press is reporting that these new licenses will be available in March, and include:

holographic overlays and laser-engraving or raised elements such as the cardholder’s image and signature…The B.C. government said the cards will incorporate technology that analyzes characteristics that do not change, such as the size and location of cheekbones and the distance between the eyes. This “facial recognition technology … will enable ICBC to compare a cardholder’s image with their existing image on file and with the corporation’s entire database of millions of images.” (Source)

Continue reading

Update: CRTC PN 2008-19 Filings

200902122343.jpgI’ve only just now had a chance to start to summarize my thoughts on documents related to CRTC Public Notice (PN) 2008-19; Review of the Internet traffic management practices of Internet service providers that have been filed since January 26th, 2009. Below are points of interest that come up – my hope is in the next few days to integrate and update the initial summary document that I prepared for ISP filings, so that a more complete picture of what has been filed exists.

January 26, 2009 ISP Filings

These filings, by major Canadian ISPs, were in response to the earlier inquiries made by non-ISP interrogatories for the public notice. I put together a summary document concerning those inquiries, and wrote a post that pulled together interesting comments that emerged from them.

Cogeco noted hat it was well known that there was a growth in Internet data traffic, though was not willing to disclose their actual growth numbers. Bell and MTS Allstream both supported the suggestion that the CRTC aggregate raw data traffic information that was provided by ISPs, so long as the information was anonymized and thus kept trade secrets relatively secret. Bell suggested that such aggregations could be divided according to ‘HTTP/streaming’, ‘P2P’, ‘UDP’, and ‘Other’ categories. MTS Allstream suggested that aggregated numbers be divided by ‘Telcos’ and ‘Cable providers’, or by ‘ISPs that throttle’ and ‘ISPs that don’t throttle traffic’.

Continue reading

Update: Network Management, Packet Inspection, and Stimulus Dollars?

200902122010.jpgIain Thomson notes that the stimulus bill that recently cleared the American Congress might work to legitimize ISP packet inspection practices under the guise of ‘network management’. Specifically, the amendment in question reads:

In establishing obligations under paragraph (8), the assistant secretary shall allow for reasonable network management practices such as deterring unlawful activity, including child pornography and copyright infringement.

While Thomson takes this to (potentially) mean that ISPs and major content producers/rights holders might use this language to justify the use of packet inspection technologies, it’s possible that alternate management methods could be envisioned. This said, given that copyright infringement is explicitly noted, there is a very real worry that this might legitimize this clause to push for ISP ‘policing’. Any such effect, I suspect, would further escalate the war between P2P and Media; encryption would become more common and effective, and result in a greater sophistication in avoiding inspection devices. This is a real loss for any and all groups who rely on non-encrypted traffic for intelligence purposes; any drive that will get ‘common folk’ thinking about encrypting more and more of their traffic, accompanied with relatively easy ways of doing so, will substantially hinder the capture of actual content. How you read the implications of this depends on your perspective on privacy and surveillance, but it seems to me that it threatens to further escalate a ‘war’ that criminalizes huge swathes of the population for actions that are relatively harmless.

Comment: Google Latitude

200902121734.jpgIn the past week or so, Google has receive an enormous amount of attention because of their Latitude program. Latitude, once installed and enabled, will alert specified friends to your geographic location very specifically (i.e. street address) or more broadly (i.e. city). Google has developed this system so that users can turn off the system, can alter how precise it locates users, and has (really) just caught up to the technologies that their competitors have already been playing with (I wrote a little about Yahoo!’s Fire Eagle software, which is similar to Latitude, a few months ago).

While many people have already written and spoken about Latitude, I’ve found myself on a fence. On the one hand, I think that some of the criticisms towards the ‘privacy’ features of the program have been innane – at least one privacy advocate’s core ‘contribution’ to has been a worry that individuals might be given a phone with Latitude installed and active, without knowing about its presence or activation. As a result, they would be tracked without having consented to the program, or the geo-surveillance.

Continue reading

Update: Ontario EDL Suppliers Named

200902042317.jpgDr. Ann Cavoukian, the Ontario Information and Privacy Commissioner, announced yesterday that GND (located in Munich) would be responsible for producing Ontario EDLs. Further, she is working with the company Peratech to develop an on/off switch that would enable or disable the EDL RFIDs. As of yet, Peratech only has their technology working with contactless smart cards (i.e. cards with a 10 cm range), but they expect to overcome this. Ann is presently in talks with DHS to let them build the Peratech solution into the EDLs – this ‘privacy protective’ feature is not currently in the EDL spec. This is part of her ‘PETs Plus’, or ‘positive sum’ approach to security and privacy.