Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove aspa cargo feature from docs, ref #990 #1010

Merged
merged 1 commit into from
Feb 7, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 0 additions & 7 deletions doc/manual/source/advanced-features.rst
Original file line number Diff line number Diff line change
Expand Up @@ -21,13 +21,6 @@ object through which the holder of an Autonomous System (AS) can authorise
one or more other ASes as its upstream providers. When validated, an ASPA's
content can be used for detection and mitigation of route leaks.

.. note::

ASPA support is temporarily behind a feature flag while the draft is under
discussion in the IETF. This way operators can gain operational experience
without unintended side effects. See
:ref:`building:Enabling or Disabling Features` for more information.

You can let Routinator process ASPA objects and include them in the published
dataset, as well as the metrics, using the :option:`--enable-aspa` option
or by setting ``enable-aspa`` to True in the :doc:`configuration
Expand Down
8 changes: 0 additions & 8 deletions doc/manual/source/building.rst
Original file line number Diff line number Diff line change
Expand Up @@ -154,14 +154,6 @@ Routinator currently has the following features:
``rta`` — *Disabled* by default
Let Routinator validate :ref:`advanced-features:Resource Tagged
Attestations`.
``aspa`` — *Disabled* by default
Let Routinator validate :ref:`advanced-features:ASPA` objects.

.. note::

ASPA support is temporarily behind a feature flag while the draft is under
discussion in the IETF. This way operators can gain operational experience
without unintended side effects.

To disable the features that are enabled by default, use the
``--no-default-features`` option. You can then choose which features you want
Expand Down