Expand security considerations

[bremoran]

Resolves comments from IETF115:

DT: How might you carry a SUIT report in an EAT?
Brendan: We need to define a new EAT claim for this for a SUIT report.

DT: Do you encrypt the SUIT report or use an EAT encrypted EAT?
HB: We should not assume that EAT will always have responsibility for encryption
Brendan: What do we do when the SUIT report is not sent in an EAT?
DT: In security consideration, we should discuss individually encrypting multiple items, or encrypting all the items as an encrypted EAT. This should be documented in EAT.

MR: What about privacy considerations? How do we handle a status tracker that needs this information? Is there a need to recharter for this?
Brendan: Alternative: TEEP doesn’t restrict use to only a TEE. A status tracker could use this information.

DT: What do supported identifiers mean for a non-constrained device?
Brendan: Wildcards can be used for this.