diff options
Diffstat (limited to 'docs/FOG-SPHINX-PROFILES.md')
| -rw-r--r-- | docs/FOG-SPHINX-PROFILES.md | 12 |
1 files changed, 5 insertions, 7 deletions
diff --git a/docs/FOG-SPHINX-PROFILES.md b/docs/FOG-SPHINX-PROFILES.md index f1d32de..2c4aac8 100644 --- a/docs/FOG-SPHINX-PROFILES.md +++ b/docs/FOG-SPHINX-PROFILES.md @@ -764,12 +764,11 @@ complete-packet benchmarking but does not activate it. The unresolved non-KEM primitives and implementation evidence keep the complete profile non-active. -`FOG-CRYPTO-BENCHMARKS.md` records a first-host benchmark of this exact -geometry. Future implementations MUST preserve its strict integration -finding: the parameterized maintained API is wrapped by a FOG boundary that -rejects every path, packet, payload, SURB, encrypted reply, or reply-key length -that differs from this profile before cryptographic processing. The first-host -result does not change `geometry-only` status or assign a profile ID. +No active FOG implementation benchmark exists for this geometry. Every future +implementation MUST enforce the exact path, packet, payload, SURB, encrypted +reply, and reply-key lengths at the FOG boundary before cryptographic +processing. This requirement follows from the profile contract itself, not +from an archived external implementation experiment. ### 18.2 Candidate primitive inputs @@ -1158,7 +1157,6 @@ These risks must appear in deployment documentation and public claims. <https://www.rfc-editor.org/rfc/rfc7748> - FOG Composer protocol: `FOG-COMPOSER.md` - FOG cryptographic suite evaluation: `FOG-CRYPTO-SUITES.md` -- FOG cryptographic benchmark baseline: `FOG-CRYPTO-BENCHMARKS.md` - FOG traffic and topology simulation: `FOG-SIMULATION.md` ## 31. Completion Checklist |