<div dir="ltr">I just had a quick read of the act - Would be nice if they actually gave a nice english document explaining who needs to keep data, who they need to keep it on (end users only, or all users?), what services (seems to be any carriage service - adsl/efm/fibre/wifi/3g - and comms services such as voip ? But not things like vpn/webhosting/streaming audio/vds/dedi/etc ?), and exactly what data? <div><br></div><div>Seems like for VOIP, you would be keeping time of call, source, dest, length of call ? And for carriage services, you'd keep time, source IP, dest IP (so a subset of netflow, easiest to keep it in netflow format and just export out what's needed if you ever need it? Though that's still a decent amount of data to need to keep somewhere..<div><br></div><div><br></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 10 June 2015 at 10:10, Joseph Goldman <span dir="ltr"><<a href="mailto:joe@apcs.com.au" target="_blank">joe@apcs.com.au</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
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?<div><div class="h5"><br>
<br>
<div>On 10/06/15 10:06, Noel Butler wrote:<br>
</div>
</div></div><blockquote type="cite"><div><div class="h5">
<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> </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> </p>
<p> </p>
<p>On 10/06/2015 09:28, Joseph Goldman wrote:</p>
<blockquote type="cite" 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>
<div> </div>
</blockquote>
<br>
<fieldset></fieldset>
<br>
</div></div><span class=""><pre>_______________________________________________
AusNOG mailing list
<a href="mailto:AusNOG@lists.ausnog.net" target="_blank">AusNOG@lists.ausnog.net</a>
<a href="http://lists.ausnog.net/mailman/listinfo/ausnog" target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a>
</pre>
</span></blockquote>
<br>
</div>
<br>_______________________________________________<br>
AusNOG mailing list<br>
<a href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a><br>
<a href="http://lists.ausnog.net/mailman/listinfo/ausnog" target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr">
<p>Damien Gardner Jnr<br>VK2TDG. Dip EE. GradIEAust<br><a href="mailto:rendrag@rendrag.net" target="_blank">rendrag@rendrag.net</a> - <span><a href="http://www.rendrag.net/" target="_blank">http://www.rendrag.net/</a><u><br></u></span>--<br>We rode on the winds of the rising storm,<br> We ran to the sounds of thunder.<br>We danced among the lightning bolts,<br> and tore the world asunder</p></div></div>
</div>