1.7.0-experimental

[ydahhrk]

Improvements since 1.6.8:

• Implement RTRv2 #132: Implement ASPA and RTRv2
• Do a quick temporary offline validation to prevent No Data Available #70: Reuse RTR session if Fort hasn't been down for a long time
  (Time limit: --server.deltas.lifetime * --server.interval.validation)
• reload feature: restart validation on SIGHUP #42: Fire up validation when SIGUSR1 is received while sleeping
• Build failure with OpenSSL 4.0 #183: Add support for OpenSSL 4
• GHSA-4q3q-6gww-wc52: Fix bad RTR response on half-range serial

Thanks to 王鑫 for GHSA-4q3q-6gww-wc52.

There are three new configuration variables:

1. --output.aspa: File where Fort will print the valid ASPAs found after each validation run.
2. --aspa.max-providers: Maximum number of providers each customerASID is allowed to declare across all RPKI trees during each validation cycle.
3. --server.max-rtr-version: Maximum RTR version the server will be willing to negotiate with RTR clients.

Please note that max-rtr-version defaults to zero. This is because Fort's validation currently yields no router keys (defeating the purpose of RTRv1), and the RTRv2 specification is still receiving updates.

The latter is all the ".experimental" suffix refers to. If you raise max-rtr-version to 2, you'll be trying a feature that hasn't been RFC'd yet.

Full Changelog: 1.6.8...1.7.0.experimental

---

This discussion was created from the release 1.7.0-experimental.

[job]

Many thanks for your work on ASPA!