Argus 5.0

[openargus]

We're going to evaluate a transition to Argus 4.0 in June. The rule we've used to bump up the major version number of argus has been based on the need to modify the fundamental flow record format. We've avoided this for a large number of years, using the version support that is in each sub-section of the argus record. We can continue that, but there is a real need to add additional support for the Argus source id, and this maybe the reason to move from Argus 3.0 to Argus 4.0.

There is also a desire to add additional DSRs to the argus flow record. This does not require a change in major numbers, but if we have a critical mass of new DSRs, then a bump maybe justified.

As a part of the discussion, we'd like to talk about new DSRs, and possible modifications to existing DSRs. The kind of changes that are fair game include:

1. Extending the flow DSR to report the key used to generate the flow, or add a new flow key DSR.
2. Modifications to the user data buffer DSR for more variations of user data capture.
3. An encapsulation DSR to better support multiple encapsulation tracking and reporting ...
4. Modifications to the Argus Event structure to report stuff ...

These are just a few possibilities ...
Lets discuss !!!

[openargus]

OK, so we're making some real progress on releasing the next version of argus ... Argus-5.0 has been running in a number of commercial deployments (DHS, Sandia, Stanford) for over 5 years, and started to transition that to the open source project.

I've established both server and client distributions as private repo's in the openargus GitHub site and will start to update the license and copyright's to transition.

If anyone is interesting in what is different / new / fixed ... lets get started !!!

[openargus]

Argus-5.0 available for testing

We've uploaded the release candidates for argus-5.0 and argus-clients-5.0 to GitHub. Please take a look at these repo's as they will be replacing argus-3.x as the current and stable argus, sometime before June.

Argus-5.0 data is not compatible with argus-3.0 data, as we changed the structure of the core ArgusRecordStruct to handle the 128-bit argus Source id.

Argus-clients-5.0 are compatible with argus-3.0 data, and is our means to transition from 3 to 5.

[openargus]

Just to close the discussion, we've fully transitioned the argus and argus-clients distro's to V5, so ... mission accomplished !!