<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">On Jun 10, 2015, at 9:28 AM, Joseph Goldman <<a href="mailto:joe@apcs.com.au" class="">joe@apcs.com.au</a>> wrote:<br class=""><div><blockquote type="cite" class=""><br class="Apple-interchange-newline"><div class="">
<meta content="text/html; charset=windows-1252" http-equiv="Content-Type" class="">
<div bgcolor="#FFFFFF" text="#000000" class="">
I wonder how much realistically that $131.3 mill will be split and
provided - but ultimately it looks like for the most part, Netflow
data married with IP history to a subscriber will cover the broad
strokes. </div></div></blockquote><div><br class=""></div><div>Why would you gather netflow data?</div><div><br class=""></div><div>IP history comes from Radius. Other service history comes from logfiles associated with those services.</div><div><br class=""></div><div>If you’re retaining my netflow data, you’re retaining information about things I’m communicating with which are outside AGD’s specified data set. I’m going to get pretty upset and annoyed about that unlawful snooping, and I’ll wonder how insane an ISP would have to be to want to get involved in that level of detail.</div><div><br class=""></div><div><i class="">You people need to get legal advice. </i>If geeks are making decision about which data gets retained, you’re comprehensively stuffing this up.</div><div><br class=""></div><div>Get it together, you people. You’ve already squibbed on the campaign against it, and now you’re paying the price. For god’s sake, don’t squib the implementation too.</div><div><br class=""></div><div> - mark</div><div><br class=""></div><div><br class=""></div></div></body></html>