search

uptane / POUFs

Interoperability profiles for Uptane implementations
Other
3 stars 1 forks source link

[WIP] Add POUF template #3

Open mnm678 opened 4 years ago

mnm678 commented 4 years ago

To address some discussion during the 5/22 Uptane workshop about the usability of POUFs, I added a POUF template that lists all of the MAYs and SHOULDs from the standard that should be addressed by a POUF. I would appreciate any feedback on this approach.

cwaldren commented 4 years ago

This is really quite helpful, thank you for putting it together.

Is there a standard way to indicate that a POUF does not implement Uptane yet? Would that mean leaving Uptane Version Implemented: blank, or using a particular string to indicate non-compliance?

mnm678 commented 4 years ago

Is there a standard way to indicate that a POUF does not implement Uptane yet? Would that mean leaving Uptane Version Implemented: blank, or using a particular string to indicate non-compliance?

We don't have an official way to support this, but leaving the Uptane Version Implemented blank would be a good way to indicate that the POUF hasn't yet implemented all the features in Uptane. It might also be good to include a note in the abstract.

JustinCappos commented 4 years ago

Is there a standard way to indicate that a POUF does not implement Uptane yet? Would that mean leaving Uptane Version Implemented: blank, or using a particular string to indicate non-compliance?

We don't have an official way to support this, but leaving the Uptane Version Implemented blank would be a good way to indicate that the POUF hasn't yet implemented all the features in Uptane. It might also be good to include a note in the abstract.

I agree that some note (as obvious as possible) is a great idea.

But we also really don't do much but just assign the POUF number, right? We could hold off from actually assigning the number until a POUF is compliant.