Russ Housley's comments on draft-12

[dthaler]

5. Section 3.3 talks about the Internet of Things. It does not talk about the billions of devices being used to mount DDoS attacks. Can it cover that too? Without putting the network interface inside the TEE, I'm skeptical there is a solution.

6. Section 3.4 talks about Confidential Cloud Computing. Can something be said in Section 4.4.1 to make this less abstract?

Regarding 6), the original Section 4.4.1 gone, and Section 1 does not seem like a good place to resolve this comment. In the current document structure, I think a sentence or two needs to appear in Section 3.4.

In addition, I have a few new comments based on the revised document.

Section 2: Since my last review, Raw Public Key was added. Please add [RFC5280] as the reference for a "PKIX certificate".

Section 4.1: now says:

  ...  A TA Signer or
  Device Administrator may run their own TAM, but the devices they
  wish to manage must include this TAM's public key/certificate
  [RFC5280], or a certificate it chains up to, in the Trust Anchor
  Store.

The meaning of "/" is unclear. I think it means "or", Please spell it out.

Section 5: s/content encryption key/content-encryption key/

Section 9.2: s/provides protection/provide protection/

Section 9.2 says: "... user/tenant ...". Again, I think the slash means "or".

Section 9.2 uses the term "payload security". For alignment with Section 5.5, I think it should say "payload encryption".

Section 9.4 talks about compromise and expiration. I do not think about expiration as a form of compromise, so I think the title of the section should be expanded.

[dthaler]

Fixed in draft-13