Ah yes, proctoring malware, because human teachers are just too expensive (but legions of highly-paid administrative staff, mysteriously enough, aren't too expensive).

At least you can confine the malware in a virtual machine right now, but that won't be the case for much longer. I'm glad I don't have any children…

I rechecked the current spec. It does not fully cover what a user agent can ask to the attestor ( "content binding" to be defined). So we can assume this attestation spec is defined at the attestor.

Of course this does not mean attestor can not have different profiles to attest for.

So your comment even though is possible, just not defined yet. Which we can - I believe - rightfully assume will be in the final spec or implementation.