We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Recently the key labels are changed, and now it defines suit-validate = 7 (see https://github.com/suit-wg/manifest-spec/blob/master/draft-ietf-suit-manifest.cddl#L213). However, the label value 7 was originally used by suit-dependency-resolution = 7 and now it is located in the Multiple Trust Domains document (see https://datatracker.ietf.org/doc/html/draft-ietf-suit-trust-domains-00#appendix-A).
suit-validate = 7
7
suit-dependency-resolution = 7
@bremoran How about updating the Multiple Trust Domains document like below.
- suit-dependency-resolution = 7 + suit-dependency-resolution = 15
If there is a github repo that hosts the document, I will send a Pull Request to it.
The text was updated successfully, but these errors were encountered:
Exactly, that's what it should be. That was missed unfortunately.
Sorry, something went wrong.
https://github.com/bremoran/suit-multiple-trust-domains
Thanks!
I've changed my mind because you know the appropriate value to be assigned. Do it on your side, please.
No branches or pull requests
Recently the key labels are changed,
and now it defines
suit-validate = 7
(see https://github.com/suit-wg/manifest-spec/blob/master/draft-ietf-suit-manifest.cddl#L213).However, the label value
7
was originally used bysuit-dependency-resolution = 7
and now it is located in the Multiple Trust Domains document (see https://datatracker.ietf.org/doc/html/draft-ietf-suit-trust-domains-00#appendix-A).@bremoran
How about updating the Multiple Trust Domains document like below.
If there is a github repo that hosts the document, I will send a Pull Request to it.
The text was updated successfully, but these errors were encountered: