<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Nov 22, 2016, at 3:27 PM, David Beveridge <<a href="mailto:dave@bevhost.com" class="">dave@bevhost.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><a href="https://www.ag.gov.au/NationalSecurity/DataRetention/Documents/Dataset.pdf" class="">https://www.ag.gov.au/NationalSecurity/DataRetention/Documents/Dataset.pdf</a><br class=""><div class=""><br class=""></div><div class="">2. The source of a
communication </div><div class="">Identifiers of a related account, service or
device from which a communication has
been sent or attempted to be sent by means
of the relevant service.</div></div></div></blockquote><div><br class=""></div>“Identifiers of a related account” can be a username, or a full name, or a name and an address or somesuch (aka “any other service or device identifier known to the provider that uniquely identifies the source of the communication.”)</div><div><br class=""></div><div>It can’t be “the IP address and port number allocated to the subscriber or device connected to the internet…” because you’re an ISP, you don’t allocate port numbers, that’s the job of the applications running on the users’ devices.</div><div><br class=""></div><div>How on earth are you harvesting port numbers?</div><div><br class=""></div><div> - mark</div><div><br class=""></div><div><br class=""></div></body></html>