Hi all As the TICSA buzzword has popped up again I just wanted to add a bit to this. OpenLI are currently nearing a product that can meet our requirements as network operators under TICSA. Namely data intercepts and voice intercepts. We are working closely with the police on the compliance side of this. To be clear, the final product will be released as open source code at some stage (on your favourite Microsoft code platform ;) ) Funding for this project is still useful and can be put to good use. Orgs that fund this software get early (beta) access to the software and will have their LI requirements met where possible. You may also get direct access to the OpenLI code monkeys. At the moment we are purely being supported by private industry funding and NZIX (AKL-IX) funding. Other funding applied for was declined. You can find some fools talking about LI here from about 1:02 onwards - https://www.youtube.com/watch?v=pRXdv-CaVjA You will also likely hear more about OpenLI if you attend the NZIX AGM later this month. Cheers Dave On Fri, Jun 1, 2018 at 6:39 PM, Richard Nelson wrote:

Yes, lots.

https://openli.nz

On 1/06/18 6:12 PM, Cameron Beattie wrote:

Has any progress been made on a collaborative effort to address the TICSA requirements?

Regards

Cameron

On 5/06/2018, at 8:42 PM, Tarus BALOG wrote:

On 06/01/2018 02:12 AM, Cameron Beattie wrote:

...

Has any progress been made on a collaborative effort to address the TICSA requirements?

I'm not sure if this will help, but we have a new project for collecting flow data from network devices. The flows are put into an Elasticsearch database and examined using Grafana.

https://wiki.opennms.org/wiki/DevProjects/Drift

This was included in last week's Horizon 22 release. This could be used to track meta-data (who is talking to whom using which protocol and transferring how much data) which I assume would help meet TICSA requirements.

No, TICSA compliance is not the nail for that hammer. Full packets are required, not flow data. -- Nathan Ward

You forgot the important bit 😊 "In ETSI Format" 😊

I'm not sure if this will help, but we have a new project for collecting flow data from network devices. The flows are put into an Elasticsearch database and examined using Grafana.

https://wiki.opennms.org/wiki/DevProjects/Drift

This was included in last week's Horizon 22 release. This could be used to track meta-data (who is talking to whom using which protocol and transferring how much data) which I assume would help meet TICSA requirements.

No, TICSA compliance is not the nail for that hammer. Full packets are required, not flow data. -- Nathan Ward Simon Allard | Development & Operations Manager D: +64 9 550 2790E: Simon.Allard(a)vocusgroup.co.nz M: +64 20 1000 790W: vocusgroup.co.nz A: Level 2, 1-7 The Strand, Takapuna 0622 _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz https://list.waikato.ac.nz/mailman/listinfo/nznog