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 Usage in v2.1.0 #259

Closed
PhilPNguy opened this issue Aug 1, 2023 · 1 comment · Fixed by #260
Closed

Terminology Usage in v2.1.0 #259

PhilPNguy opened this issue Aug 1, 2023 · 1 comment · Fixed by #260

Comments

@PhilPNguy
Copy link
Contributor

As of v2.1.0,

  • There is no usage of "MAY" or "OPTIONAL" at all when there are many parts of the standard that should have them to be clearer.

  • "CONDITIONALLY REQUIRED" is used once and not defined. Either we define the entire phrase, define just the "CONDITIONALLY" word, or decide to rephrase the sentence to follow RFC2119 (and not add additional key words).

From "5.2.3.1.1. Custom metadata about images"

The following information is CONDITIONALLY REQUIRED for each image on the Director repository IF that image is encrypted:
- Information about filenames, hashes, and file size of the encrypted image.
- Information about the encryption method, and other relevant information–for example, a symmetric encryption key encrypted by the ECU’s asymmetric key could be included in the Director repository metadata.
@PhilPNguy
Copy link
Contributor Author

PhilPNguy commented Aug 15, 2023

Based on Ira's comments during 2023/08/01 meeting, uptane no longer uses "MAY" and "OPTIONAL" keywords.
Any optional requirements will just not contain the other keywords (SHALL & REQUIRED).

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 a pull request may close this issue.

1 participant