Summary: Has enough positions to pass.
I found myself wishing that Section 3.8 was a bit clearer about the advantages of sequential versus parallel forking. I can imagine some of the advantages because I have a SIP background, and I can dig some of what I was expecting to see in 3.8.2, but I'm imagining and digging, and I'm betting that the document could be more explicit about the tradeoffs - just saying "if you're communicating with a SIP endpoint, most of them can only exchange media with one endpoint at a time" is already helping.
I think that this is a well-written document -- while reading through the Directorate reviews the last line of PHB's SecDir comment made me laugh.
I have read the whole document, but I didn't check references or correctness of section numbers ;-).
I'm sure the RFC editor would have caught this nit: 2nd paragraph of security considerations section: While formally the JSEP interface is an API, it is better to think of it is an Internet protocol s/is an Internet/as an Internet/
I am an author on this document.