docs(spec): record the rate-limit ban async-gap as an accepted residual (#1703 item 3) - #45
Merged
Merged
Conversation
…residual (#1703 item 3) Salvage anchor for the #1703 item 3 decide-first (DOCUMENT-AS-ACCEPTED): add a SPEC CON-007 note + DEVELOPMENT_LOG entry recording that the rate-limit ban charge->enforce async gap is not a dodge (mTLS handshake cost >> the gap). Doc-only; closes #1703 item 3 and the whole ticket. Co-Authored-By: Claude <noreply@anthropic.com>
Add normative note in SPEC.md §5.4.1 explaining why the rate-limit ban recording's charge→enforce async gap is not exploitable (mTLS handshake latency prevents same-peer_id reconnect inside the microsecond gap). Also prepend DEVELOPMENT_LOG.md entry clarifying the design rationale: the async gap is defended by cost asymmetry, not synchronous recording, to avoid banned-but-still-Live slot inconsistencies on superseding reconnects. Co-Authored-By: Claude <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.
Closes dig_ecosystem#1703 (item 3 — the final item; closes the whole ticket).
Task
#1703 item 3 (ban-persistence across the async gap) was resolved by a decide-first as DOCUMENT-AS-ACCEPTED: the rate-limit ban charge→enforce async gap is not an exploitable dodge (a same-
peer_idreconnect requires a full SPKI-pinned mTLS handshake in ms — 3+ orders of magnitude larger than the µs spawn→lock gap; thebannedtable is identity-scoped/durable; the synchronous-record "fix" would introduce a banned-but-still-Live map inconsistency). Record it as a conscious accepted residual, with the synchronous-record option noted for if identity-scoped ban persistence is ever wanted.Change (doc-only, no behaviour change)
docs/resources/SPEC.md— a normative note in the CON-007 / §5.2.1 security-properties area.DEVELOPMENT_LOG.md— a durable entry on why the gap isn't a dodge (the mTLS handshake is the lock).Bump
0.17.15 → 0.17.16 (patch — docs, no code/API/wire/format change) — already set in the anchor.
WIP — draft anchor; doc edits applied per the #1703 item-3 decider verdict.
Generated by Claude Code