[dns-operations] DNS Traffic Archive Protocol

[Tony Finch]

On Thu, 2 Dec 2010, Bedrich Kosata wrote:
>
> - save only relevant data, remove details of lower network layers (store
> all data in the same way regardless of IP version or transport protocol).
> - store data as efficiently as possible (use single bits or portions of
> a byte where possible, such as for IP version, transport protocol, etc.).
> - combine DNS queries and responses together to remove redundancy.
> - store repetitive data only when they change (server IP address, server
> port and RR class are good candidates for this)
> - store only data important for the task at hand, i.e., make certain
> data only an optional part of the output. This way each user could
> fine-tune the format to suit his needs. A good candidate for this is the
> content of responses, which makes for the largest part of the data
> (especially with the introduction of DNSSEC).

How does this compare to a general purpose compression algorithm?

Tony.
-- 
f.anthony.n.finch  <dot at dotat.at>  http://dotat.at/
HUMBER THAMES DOVER WIGHT PORTLAND: NORTH BACKING WEST OR NORTHWEST, 5 TO 7,
DECREASING 4 OR 5, OCCASIONALLY 6 LATER IN HUMBER AND THAMES. MODERATE OR
ROUGH. RAIN THEN FAIR. GOOD.