<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 10/15/2015 10:41, Noel Butler wrote:<br>
</div>
<blockquote cite="mid:c58bf71bb1f6785ce29e48b749ceb449@ausics.net"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<p>On 15/10/2015 09:36, Noel Butler wrote:</p>
<blockquote type="cite" style="padding: 0 0.4em; border-left:
#1010ff 2px solid; margin: 0">
<p>On 13/10/2015 10:43, Peter Fern wrote:</p>
<blockquote style="padding: 0 0.4em; border-left: #1010ff 2px
solid; margin: 0;"><br>
<blockquote style="padding: 0 0.4em; border-left: #1010ff 2px
solid; margin: 0;">
<div class="WordSection1">
<p>the destination address is explicitly EXCLUDED..</p>
</div>
</blockquote>
<br>
Only for web traffic - pretty much all the other protocols
(email, VOIP, IM, etc) specifically require that destination
addresses are retained.<br>
<br>
</blockquote>
<p>I dont see how that is possible since you are not req</p>
<p> </p>
</blockquote>
<p>blasted webmail...</p>
<p>...your not required to log DNS, so your not to know who is
using what service, only those running those services will know
who connects to, or are you going to try claim that every
outbound pkt except those destined to ports 80 and 443 are
required to be captured? if your implying that, thanks, i'll add
that to my already large list of DR funnies.<br>
</p>
</blockquote>
<br>
What? No, you need to retain this data only if you *provide* these
as OTT services in addition to your data services. You capture them
however you see fit, generally that's going to be at the application
level (SIP proxy, mail server, etc). Your list may be funny for the
wrong reasons.<br>
</body>
</html>