Filing requests with endpoints leaves a trail, and an agency would have a hard time requesting everyone's total traffic without proper cause.
On the other hand, recording everything through a key bottleneck leaks no information about what is specifically of interest. It also allows retrospective looks at things that might not have seemed interesting enough to request up front. And 'certain ports'? Bah! Get it all. Maybe future breakthroughs (or current undisclosed innovations) can render it all transparent.
This may not be the 'easiest' approach, but it's definitely the 'best', for maximum knowledge, if you can afford/manage it.
The proper spelling is 'Narus', which is also the name of the supplier company, based in Sunnyvale and since 2010 a subsidiary of Boeing. You can read about them and their capabilities at:
Ah, thank you very much. A google for "Naris" (as it is spelled in the RT article) isn't very helpful.
Your logic is definitely sound. It's just mind boggling to me that anyone could possibly be logging everything thrown through every port. Every single day. Just, wow.
On the other hand, recording everything through a key bottleneck leaks no information about what is specifically of interest. It also allows retrospective looks at things that might not have seemed interesting enough to request up front. And 'certain ports'? Bah! Get it all. Maybe future breakthroughs (or current undisclosed innovations) can render it all transparent.
This may not be the 'easiest' approach, but it's definitely the 'best', for maximum knowledge, if you can afford/manage it.
The proper spelling is 'Narus', which is also the name of the supplier company, based in Sunnyvale and since 2010 a subsidiary of Boeing. You can read about them and their capabilities at:
http://en.wikipedia.org/wiki/Narus_%28company%29
http://www.narus.com/