ietf-rats / charter Goto Github PK

This is a small nit, but why would someone want to profile DTLS or CoAP? Is there an example how this could be useful? I am under the impression that profiling probably applies to application protocols and not to the layers DTLS or CoAP operate on - but I might be missing something obvious. This definitely is not a blocker on the charter text - I am just wondering.

ietf-teep/architecture#52

To accommodate Roman's suggestion to make use of what we've learned from the architecture, I think this may come in handy.

Concretely, we could replace this bit:

"Remote attestation procedures (RATS) enable relying parties to establish a level of confidence in the trustworthiness of remote system components through the creation of attestation evidence by remote system components and a processing chain towards the relying party. A relying party can then decide whether to consider a remote system component trustworthy or not."

with something similar to the "objectives and mechanisms" I linked above.