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.

Sign up for GitHub

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

Jump to bottom

Quantitative or qualitative guidance on what "small" or "large" means #101

Closed
hannestschofenig opened this issue Jul 6, 2023 · 0 comments · Fixed by #124
Closed

Quantitative or qualitative guidance on what "small" or "large" means #101

hannestschofenig opened this issue Jul 6, 2023 · 0 comments · Fixed by #124

Comments

@hannestschofenig
Copy link
Collaborator

** Section 8.4.8.9
If data is encoded this way, it should be small. Large payloads
written via this method will prevent the manifest from being held in
memory during validation. Typical applications include small
configuration parameters.

Is it possible to provide quantitative or qualitative guidance on what "small" or "large" means?
bremoran added a commit that referenced this issue Oct 16, 2023
@bremoran
guidance on what "small" and "large" mean in suit-parameter-content
2095ba6 
Fixes #101
@bremoran bremoran mentioned this issue Oct 16, 2023
Merged
bremoran added a commit that referenced this issue Oct 23, 2023
@bremoran
guidance on what "small" and "large" mean in suit-parameter-content (#…
79dbf5b 
…124)

* guidance on what "small" and "large" mean in suit-parameter-content

Fixes #101

* Update draft-ietf-suit-manifest.md

* Update draft-ietf-suit-manifest.md
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

guidance on what "small" and "large" mean in suit-parameter-content suit-wg/manifest-spec
1 participant
@hannestschofenig