Clarification regarding Data Protection about architecture HOT 4 CLOSED

What is the issue? The text says "might be implemented outside a TEE" so it already implies it's a design choice.
Hence to me it's already clear enough and agnostic to it.

Also, as an aside, that paragraph is transport protocol agnostic, so if there were a binding over something other than TLS (e.g., DTLS or OPC UA's security protocol) it would still be correct.

I'd propose resolving this as wont fix.

from architecture.

Here is my proposal: #229

from architecture.

The issue is that I see others coming with different solutions that fit the same architectural description and problem statement.

Reading through the draft I noticed that there are a few places where we go the step from the architecture to the solution details. This is not really necessary and hence I wanted to make it a bit more generic

from architecture.

Fixed in draft -15

from architecture.