<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
I suppose this is again where the legalese confuses - as the
documents
(<a class="moz-txt-link-freetext" href="http://www.ag.gov.au/NationalSecurity/DataRetention/Documents/Dataset.pdf">http://www.ag.gov.au/NationalSecurity/DataRetention/Documents/Dataset.pdf</a>
specifically) mention things like even if the communication is
social media, chat etc (See 5a in that document).<br>
<br>
Once we get clarification from groups such as SIG (mentioned earlier
in this thread) then a lot of this confusion may come to pass - but
if what your saying is correct then that is a much better situation
then storing netflow data - Billing info along with CDR's should
cover most things, just need archive systems to sort, store and
ensure the retention of that data.<br>
<br>
<div class="moz-cite-prefix">On 10/06/15 10:16, Noel Butler wrote:<br>
</div>
<blockquote cite="mid:db751a1222d9fe9ba7d63e15cb23b903@ausics.net"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<p>On 10/06/2015 10:10, Joseph Goldman wrote:</p>
<blockquote type="cite" style="padding: 0 0.4em; border-left:
#1010ff 2px solid; margin: 0">From reading those pages it seems
to indicated source, destination, time and type of the
communication. Perfect job for this appears to be netflow data -
netflow itself holds a lot more information that may not be
necessary but it seems to be the best way to pull that
information at a quick glance, no?</blockquote>
<p> </p>
<p>That is for voice, read it carefully. Yes for voice they want
to know from and to, but for internet, only who has what IP at
what time and their life story including payment history and a
total, I guess monthly, of that users used quota, a one line per
month total entry in a DB, which one assumes is in your billing
system already anyway, they certainly do not want to know how
many times you logged onto twitter or youtube or if you ever
visited watchingthegrassgrow.com</p>
<p> </p>
<p> </p>
<blockquote type="cite" style="padding: 0 0.4em; border-left:
#1010ff 2px solid; margin: 0"><br>
<div class="moz-cite-prefix">On 10/06/15 10:06, Noel Butler
wrote:</div>
<blockquote type="cite" style="padding: 0 0.4em; border-left:
#1010ff 2px solid; margin: 0">
<p>Why would you keep netflow for DR, they don't want to know
where your customers go or what they d/l from, only who your
customer is.</p>
<p>It's rather scary some of you people have no idea, despite
it being plastered all over the frickin place for months
now, including in the Bill itself and even a short FAQ as to
what you need to keep (which is a direct copy from the Bill
thats been floating around for ages) on the AG's website.</p>
<p>On 10/06/2015 09:28, Joseph Goldman wrote:</p>
<blockquote style="padding: 0 0.4em; border-left: #1010ff 2px
solid; margin: 0;">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. To
cover a recent discussion, would sFlow be applicable with
its sampling rate unless set to N=1?<br>
2 Years of that could be quite a lot of disk space filled
up. I'll also be keen to know what kind of penalties or
reporting there may be in the instance an outage on
collecting this data occurs (say server freezes and it takes
10 minutes to fix, 10 minute gap in data etc)<br>
<br>
</blockquote>
<br>
<br>
<pre>_______________________________________________
AusNOG mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a><a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.ausnog.net/mailman/listinfo/ausnog">http://lists.ausnog.net/mailman/listinfo/ausnog</a></pre>
</blockquote>
<br>
<br>
<div class="pre" style="margin: 0; padding: 0; font-family:
monospace">_______________________________________________<br>
AusNOG mailing list<br>
<a moz-do-not-send="true"
href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a><br>
<a moz-do-not-send="true"
href="http://lists.ausnog.net/mailman/listinfo/ausnog">http://lists.ausnog.net/mailman/listinfo/ausnog</a></div>
</blockquote>
<p> </p>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
AusNOG mailing list
<a class="moz-txt-link-abbreviated" href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a>
<a class="moz-txt-link-freetext" href="http://lists.ausnog.net/mailman/listinfo/ausnog">http://lists.ausnog.net/mailman/listinfo/ausnog</a>
</pre>
</blockquote>
<br>
</body>
</html>