Roadmap

Roadmap

This page summarizes the current implemented baseline and planned work. It is synchronized with the main repository roadmap without copying it verbatim and does not promise dates.

Implemented

The current codebase implements:

• plain UDP ingress;
• direct !AIVDM and !AIVDO extraction and forwarding;
• authenticated encrypted UDPSEC ingress through nmea_sproxy;
• physical serial and USB virtual COM receiver input through nmea_sproxy;
• explicit trusted-network plain UDP output through nmea_sproxy;
• static logical routing loaded from configuration;
• runtime routing status, replacement, and disable operations;
• logical source zones with include, union, intersection, and difference;
• internal source_id and target_id routing identities;
• named UDP egress targets;
• target-scoped deduplication in routing mode;
• legacy global deduplication and broadcast forwarding;
• endpoint ACLs with allow_from;
• outbound source-address binding with source_ip and output.source_ip;
• immutable routing snapshots and process-local generations;
• versioned JSON routing-control protocol;
• opt-in POSIX Unix-domain control server and client;
• repository-managed systemd unit;
• RuntimeDirectory=aismixer provisioning;
• global /usr/local/bin/aismixerctl wrapper in lifecycle scripts;
• privilege-aware install, update, and uninstall scripts;
• install/update flows that preserve existing operator configuration and keys.

Current confirmed nmea_sproxy relation modes are local UDP or serial input to UDPSEC or explicit plain UDP output, with !AIVDM and !AIVDO extraction in those paths.

Planned Or Not Implemented

The following remain planned work:

• dedicated AISMixer service user/group;
• explicit control-socket group policy;
• persistent runtime routing state;
• configuration watching or reload;
• dynamic ingress and egress adapter lifecycle;
• coordinator process;
• ingress workers;
• egress workers;
• IPC routing synchronization;
• P2P routing exchange;
• Docker support;
• additional egress adapters beyond UDP;
• spoof and anomaly detection;
• geographic, MMSI, vessel, or payload-aware filtering;
• long-term AIS storage and analytics.

Non-Goals For Current Documentation

Do not describe Docker, multiprocessing, non-UDP egress adapters, persistent runtime routing, dynamic adapter lifecycle, or spoof detection as available features until they are implemented and tested.