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

Ensure TAP references do not have TUF specific content #86

Closed
mnm678 opened this issue Mar 13, 2019 · 1 comment
Closed

Ensure TAP references do not have TUF specific content #86

mnm678 opened this issue Mar 13, 2019 · 1 comment
Assignees
Milestone

Comments

@mnm678
Copy link
Collaborator

mnm678 commented Mar 13, 2019

As discussed in the 3/13 standards meeting, we need to ensure that any referenced TAPs have consistent TUF/Uptane terminology.

@mnm678 mnm678 self-assigned this Mar 13, 2019
@mnm678
Copy link
Collaborator Author

mnm678 commented Mar 20, 2019

I went through TAP 3, 4, and 5 to look for inconsistencies with Uptane terminology. Other than a couple of TUF examples, I think these TAPs are consistent with Uptane. There are a couple of very minor TUF/Uptane differences that come up in the TAPs (for example whether to verify custom metadata), but the terminology all seems to be consistent.

Overall I would say the references to these TAPs make sense in the context of Uptane, and I don’t see a reason to duplicate them.

I am going to close this issue, but if anyone has objections I’m happy to reopen it for more discussion.

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

No branches or pull requests

2 participants