docs: remove false RPKI enforcement callout from CLI reference#14
Merged
Merged
Conversation
The gateway attempts ensure_roa() before revocation but logs failures as warnings and proceeds regardless — there is no enforced constraint. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The callout claimed "RPKI must be re-enabled before revoking a prefix. The platform enforces this for routing stability."
Checked
peerlab-gateway/src/lib.rs(revoke_prefix, ~line 359): the gateway callsensure_roa()as a best-effort before deletion, but the error is onlywarn!-logged — execution always continues to thedelete_prefix_leasecall. No enforcement exists.🤖 Generated with Claude Code