Skip to content

spec: add TEA discovery, protobuf, and JSON schema drafts#235

Closed
MChorfa wants to merge 3 commits intoCycloneDX:mainfrom
MChorfa:spec-only-split
Closed

spec: add TEA discovery, protobuf, and JSON schema drafts#235
MChorfa wants to merge 3 commits intoCycloneDX:mainfrom
MChorfa:spec-only-split

Conversation

@MChorfa
Copy link
Copy Markdown

@MChorfa MChorfa commented Mar 29, 2026

Summary

This PR carries forward only the specification-facing parts of the previous ref-impl branch.

Included here:

  • discovery and API flow documentation
  • TEA protobuf definitions under proto/tea/v1
  • JSON schemas under schemas/json
  • supporting spec-oriented diagrams and reference docs

Explicitly excluded from this PR:

  • Rust server implementation
  • Dagger/build automation
  • CI/release/supply-chain workflows
  • generated integration/reference-implementation material

Implementation split

The implementation work has been moved into a separate repository:

Notes

This is intended to align with the repository boundary discussed in the previous review and keep this PR limited to spec/schema/doc content.

@MChorfa MChorfa requested review from madpah and oej as code owners March 29, 2026 22:59
Signed-off-by: Mohamed Chorfa <mohamed.chorfa@thalesgroup.com>
Mohamed Chorfa added 2 commits March 29, 2026 19:11
Signed-off-by: Mohamed Chorfa <mohamed.chorfa@thalesgroup.com>
Signed-off-by: Mohamed Chorfa <mohamed.chorfa@thalesgroup.com>
@MChorfa
Copy link
Copy Markdown
Author

MChorfa commented Mar 29, 2026

Implementation work has been moved to a separate repository for review here:

This PR is now limited to specification-facing documentation, protobuf definitions, and JSON schemas. CI is currently green (DCO and GitGuardian both passing).

If a smaller review unit is preferred, I can split the remaining content further into separate docs/diagrams and proto/schema PRs.

@oej
Copy link
Copy Markdown
Collaborator

oej commented Mar 30, 2026

Please split this up into more focused PRs so we can discuss each separately. Thank you.

@oej
Copy link
Copy Markdown
Collaborator

oej commented Mar 30, 2026

A pull request this large requires a lot of time for the peers in the working group. We are getting close to 1.0 and are very resistant to add new things before the release. Splitting it up in smaller pieces, more focused, makes it easier to handle and accept small changes - like formatting - and take larger changes later.

The TLS requirements - are they written by you or an AI? It doesn't seem based on experience.

@MChorfa
Copy link
Copy Markdown
Author

MChorfa commented Mar 30, 2026

Following the request to split this into smaller review units, I have opened focused replacement PRs:

I am closing this broader PR to reduce review load. If the remaining narrative docs and diagrams are still useful, I can reintroduce them later as separate focused PRs.

@MChorfa MChorfa closed this Mar 30, 2026
@MChorfa
Copy link
Copy Markdown
Author

MChorfa commented Mar 30, 2026

Following the request to split this into smaller review units, I have opened focused replacement PRs:

I am closing this broader PR to reduce review load. If the remaining narrative docs and diagrams are still useful, I can reintroduce them later as separate focused PRs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants