Argus 2.0 User Payload Data

[Peter Van Epp]

<snip>> 
> Is there an opinion?  I'm leaning toward strategy
> two, as I see it handling privacy concerns better
> than strategy one.  The basic Argus record is
> designed to minimize privacy intrusion, and the
> supplemental records that could possibly intrude
> could be filtered out, encrypted, tossed etc...
> 
> Suggestions comments opinions are definitely welcome!
> 
> 
> Carter
>

	I'd lean towards option 2 as well. It provides the most flexability
for being able to do things like capture the entire packet when a flag 
oddity (as a for instance) shows up or fragments that have different / 
overlapping offsets appear in the input stream without necessarily always
keeping the entire packet. The down side is that it requires more horsepower
to keep up with the data stream, but power is getting cheaper by the day.

Peter Van Epp / Operations and Technical Support 
Simon Fraser University, Burnaby, B.C. Canada