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

Defined what we mean by 'Software Update' #223

Closed
wants to merge 3 commits into from

Conversation

@hannestschofenig
Copy link
Collaborator

@hannestschofenig hannestschofenig commented Mar 23, 2021

No description provided.

@dthaler
Copy link
Collaborator

@dthaler dthaler commented Apr 9, 2021

@hannestschofenig why do we need to define this term in the TEEP architecture? The term is used nowhere in the document after the terminology section. It's used once on line 153 of the markdown, but is used in a way that i think is clear in context without needing a definition.

draft-ietf-teep-architecture.md Outdated Show resolved Hide resolved
draft-ietf-teep-architecture.md Outdated Show resolved Hide resolved
@dthaler
Copy link
Collaborator

@dthaler dthaler commented Jul 10, 2021

The term "software update" only appears once in the TEEP architecture draft, and it is in the introduction before the terminology section:

To simplify the life of TA developers interacting with TAs in a TEE, an interoperable protocol for managing TAs running in different TEEs of various devices is needed. This software update protocol needs to make sure that compatible trusted and untrusted components (if any) of an application are installed on the correct device. In this TEE ecosystem, there often arises a need for an external trusted party to verify the identity, claims, and rights of TA developers, devices, and their TEEs. This trusted third party is the Trusted Application Manager (TAM).

Rather than trying to define it formally in a terminology section, I'd rather either remove the use of the term "software update" or make sure it's clear in context. My personal opinion is that the latter is already the case.

Is this PR in response to some specific feedback? No Issue number is referenced.

hannestschofenig and others added 2 commits Jul 11, 2021
Co-authored-by: Dave Thaler <dthaler@microsoft.com>
Co-authored-by: Dave Thaler <dthaler@microsoft.com>
@mingpeiwk
Copy link
Collaborator

@mingpeiwk mingpeiwk commented Jul 12, 2021

The term sounds a common word to me. Do we have to define it?

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

Successfully merging this pull request may close these issues.

None yet

3 participants