Last Call Review of draft-ietf-rtcweb-security-11
I have been assigned to review this document on behalf of the Ops directorate. In general, I found the document well-written, but the reason I marked it as not ready as I was confused as to its standards track trajectory. I do not see any kind of inter-operable standard being defined here. On my reading -- before I noticed it was standards track -- it felt informational. While it does set out a threat model for the browser, I struggle to see how that needs to be standardized.
On that threat model note, the abstract indicates that the WebRTC threat model will be laid out, but section 3 defines a more general browser threat model.
Other nits are mentioned below on a section-by-section basis.
s/provide a escape hatch/provide an escape hatch/
s/ threats is less severe/threats are less severe/
s/ The calling service is is/The calling service is/
(a) the browser to trusted UI to provide the name and
I don't grok this sentence fragment. There seems to be a verb missing, and I'm not sure what your intent is here.
s/e.g., read aloud over the the voice/e.g., read aloud over the voice/
s/However, it it is well-known/However, it is well-known/