Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Terminology: Registry & Transparency Service #7

Closed
SteveLasker opened this issue Feb 21, 2023 · 7 comments
Closed

Terminology: Registry & Transparency Service #7

SteveLasker opened this issue Feb 21, 2023 · 7 comments
Milestone

Comments

@SteveLasker
Copy link
Collaborator

Copied over from: ietf-scitt/draft-birkholz-scitt-architecture#38

The architecture I-D, and other docs use Registry and Transparency Service (TS) interchangeably.

This issue is about consistent naming, and what we should use for an implementation that hosts the SCITT standards.
As we've discussed various terms, I'm pasting a "thousand words" to highlight conceptual components.

image

How do we finish this sentence:
The user will submit a signed statement/claim (see issue #34) to the ___

  1. The thing we're trying to name here, which is an implementation of a service.
  2. The eNotary component that evaluates the Registration Policy (3) before proceeding
  3. The Registration Policy, as the gatekeeper for what may be submitted to the ledger.
  4. The eNotary counter signing key/service
  5. The ledger, where statements/claims are persisted
  6. The ledger of a ___ (1) may be implemented through various "ledger databases", such as Azure CCF, QLDB, Trillian

This issue is to discuss what we call (1)
Please "vote" with a comment, representing a number, and any supporting thoughts:

  1. Transparency Service (with no acronym)
  2. Registry
  3. SCITT Implementation
  4. Transparency Service (TS as a acronym)
  5. write in your own
@fournet
Copy link
Collaborator

fournet commented Feb 27, 2023

  1. Transparency Service (TS as a acronym)

Please look at the existing terminology section before proposing global substitutions.

@henkbirkholz
Copy link
Member

henkbirkholz commented Feb 27, 2023

The substitution of TS to Transparency Services was due to comments that highlighted a possible confusion with Timestamp that might be not intuitive to the generic reader.

Maybe let us split that decision out to the list and then fix this with a %s/foo/bar/g?

@rjb4standards
Copy link

rjb4standards commented Feb 27, 2023

IMO a "Transparency Service" operates a SCITT Registry that contains authenticated statements expressing trust in an artifact. A SCITT Registry may employ multiple technologies to provide its services, i.e. blockchain ledger, relational database, evidence locker, REST API to query the Registry for statements, API's to submit new statements and evidence, etc. The operator of a Transparency Service serves as the Registry Gatekeeper to ensure the integrity of the Registry.

@SteveLasker
Copy link
Collaborator Author

Adding a link to a higher level overview @raylutz
assembled: https://docs.google.com/document/d/1qYljgugcraiamGjrhldQ1ZEoa4i_TkM3tzBg8yNzE_E/edit#

@SteveLasker
Copy link
Collaborator Author

#16 mostly converges on Transparency Service. However, #8 is also open as additional discussions commence.
I'm leaving open to keep discussions with all the history, including updates to @raylutz's doc.

@SteveLasker SteveLasker added this to the IETF 117 milestone Mar 10, 2023
@SteveLasker
Copy link
Collaborator Author

Assigning to @raylutz for confirmation and update.

@SteveLasker
Copy link
Collaborator Author

Closing, due to inactivity and #16 and #8 cover open topics.

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

No branches or pull requests

4 participants