docs(spec): add IC-TDF v1alpha specification suite - #3907
Draft
dmihalcik-virtru wants to merge 1 commit into
Draft
docs(spec): add IC-TDF v1alpha specification suite#3907dmihalcik-virtru wants to merge 1 commit into
dmihalcik-virtru wants to merge 1 commit into
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Contributor
Benchmark results, click to expandBenchmark authorization.GetDecisions Results:
Benchmark authorization.v2.GetMultiResourceDecision Results:
Benchmark Statistics
Bulk Benchmark Results
TDF3 Benchmark Results:
|
Contributor
dmihalcik-virtru
force-pushed
the
ictdf/spec-v1alpha
branch
from
August 20, 2026 21:21
444c636 to
bc14a41
Compare
3 tasks
Contributor
dmihalcik-virtru
force-pushed
the
binarytdf/spec-v1alpha
branch
from
August 21, 2026 01:30
eacb646 to
b25dc4f
Compare
dmihalcik-virtru
force-pushed
the
ictdf/spec-v1alpha
branch
from
August 21, 2026 01:30
bc14a41 to
27527de
Compare
Contributor
X-Test Failure Report |
Contributor
Benchmark results, click to expandBenchmark authorization.GetDecisions Results:
Benchmark authorization.v2.GetMultiResourceDecision Results:
Benchmark Statistics
Bulk Benchmark Results
TDF3 Benchmark Results:
|
Contributor
Benchmark results, click to expandBenchmark authorization.GetDecisions Results:
Benchmark authorization.v2.GetMultiResourceDecision Results:
Benchmark Statistics
Bulk Benchmark Results
TDF3 Benchmark Results:
|
Contributor
dmihalcik-virtru
force-pushed
the
ictdf/spec-v1alpha
branch
from
August 21, 2026 02:16
27527de to
b2c8109
Compare
Contributor
X-Test Failure Report |
Contributor
Benchmark results, click to expandBenchmark authorization.GetDecisions Results:
Benchmark authorization.v2.GetMultiResourceDecision Results:
Benchmark Statistics
Bulk Benchmark Results
TDF3 Benchmark Results:
|
Contributor
Benchmark results, click to expandBenchmark authorization.GetDecisions Results:
Benchmark authorization.v2.GetMultiResourceDecision Results:
Benchmark Statistics
Bulk Benchmark Results
TDF3 Benchmark Results:
|
Contributor
|
Contributor
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
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.
Stacked on #3887.
Proposed Changes
IC-TDF.XML.V2014-DEC-r2017-JUL, into parallel BaseTDF-style components underspec/ictdf/v1alpha.IC-TDF.xsdstructure, all three CVEs, all 49 Schematron constraint rules, the TDO/TDC object model, assertion scope and transitivity, binding coverage, layered encryption, and the multi-pass conformance procedure.ICTDF-SCPfor the assertion scope algebra (scope determines binding coverage in IC-TDF, so it is load-bearing rather than an assertion property) andICTDF-VALfor the four-to-five step validation procedure over foreign-namespace content.spec/README.md, which previously referenced neither.Module layout
ICTDF-BNDcovers the signature half ofBaseTDF-ASN. IC-TDF has noINTcounterpart: it defines no segmentation and no per-segment integrity, so payload integrity comes from the encryption method or from binding coverage. The suite README states these boundaries explicitly.Notes for reviewers
The source specification permits several things a current spec should not bless:
SHA1andSHA1with*in the signature CVE,AttachedKey, and examples using@algorithm="AES"(a family, not a mode) and a literalnormalizationMethod="Normalization Method"placeholder. Those are reproduced faithfully inICTDF-EXand annotated as not production-safe, andICTDF-SEC/ICTDF-ALGmark SHA-1 andAttachedKeyas MUST NOT produce. That security guidance is an addition to the source and is scoped to guidance, not wire format.ICTDF-KASdocuments what IC-TDF actually carries —RemoteStoredKey/@protocoland@uri,WrappedPDPKey/EncryptedPolicyObject— and states explicitly that IC-TDF defines no key-release protocol.Source: DI2E
ICS-Data_Standards, Public Release, available for use without restriction.Checklist
Testing Instructions
Documentation-only change. Verified that all 49 source rule IDs (
00001-00019,00025-00028,00030-00055) appear in theICTDF-SCHcatalog with no gaps or extras, that everyIC-TDF-ID-*cited across the suite is a valid rule, that all relative Markdown links resolve, and that all 17ICTDF-*cross-references name real modules. No Go changes, somake lintandmake fmtdo not apply; the repository has no Markdown linter.