asif: Library for creating and querying segmented feeds

[ library, mit, program, services ] [ Propose Tags ]
Versions [RSS] 1.0.0, 2.0.0, 3.0.0, 3.1.0, 3.2.0, 3.3.4, 3.4.0, 4.0.0, 4.0.1, 4.1.0, 5.0.0, 5.0.1, 5.0.2, 6.0.0, 6.0.1, 6.0.3, 6.0.4
Change log
Dependencies asif, attoparsec, base (>=4.7 && <5), binary, bytestring, conduit, conduit-combinators, conduit-extra, containers, cpu, directory, either, exceptions, foldl, generic-lens, hw-bits, hw-ip, lens, network, old-locale, optparse-applicative, profunctors, resourcet, temporary-resourcet, text, thyme, transformers, vector [details]
License MIT
Copyright Arbor Networks
Author Arbor Networks
Category Services
Home page
Bug tracker
Source repo head: git clone
Uploaded by arbornetworks at 2019-03-28T05:22:02Z
Executables asif
Downloads 7666 total (22 in the last 30 days)
Rating 2.0 (votes: 1) [estimated by Bayesian average]
Your Rating
  • λ
  • λ
  • λ
Status Docs available [build log]
Last success reported on 2019-03-28 [all 1 reports]

Readme for asif-5.0.1

[back to package description]

Arbor Safe Intelligence Format (asif)


Library for creating and querying segmented feeds.

File Format Specification

Layer 0: Segments

|Segmented OSI Model |

 magic, where XXXX is a feed type
| "seg:XXXX" [char:8] | ver: uint64 |

c -- countries
a -- asns
n -- naics

| seg_num: uint64 |

| segment_offset: int32 | segment_length: int32 |

 segment vector
| key: X, ... |

 segment vector
| val: Y, ... |

Vector keys are fixed-length values such as 4-byte IPv4 addresses, 2-byte country codes, or 4-byte NAIC IDs.

All values are little-endian.

Values are other ints or can be null-terminated strings.

Layer 1: Segment filenames

Segment 0 must contain a concatenated list of null terminated filenames.

The first filename must be .asif/filenames.

The n-th filename in the segment 0 describes the n-th segment in the file.

Layer 2: Additional metadata

The asif file may contain contain a named segment .asif/createtime. If it does, this segment concatenated Word64 numbers representing the create time of each file in microseconds since epoch. If the segment does not have a create time, it's create time entry will be 0 instead.

The asif file may contain contain a named segment .asif/formats. If it does, this segment concatenated null terminated strings representing the format of the data in the respective segments. The dump command will use this information to choose the most appropriate way to print the data in each segment.


CLI documentation