Last Call Review of draft-ietf-rtcweb-jsep-21
review-ietf-rtcweb-jsep-21-opsdir-lc-martinez-2017-08-16-00
| Request | Review of | draft-ietf-rtcweb-jsep |
|---|---|---|
| Requested rev. | no specific revision (document currently at 26) | |
| Type | Last Call Review | |
| Team | Ops Directorate (opsdir) | |
| Deadline | 2017-08-11 | |
| Requested | 2017-07-28 | |
| Draft last updated | 2017-08-16 | |
| Completed reviews |
Secdir Last Call review of -23 by Phillip Hallam-Baker
(diff)
Opsdir Last Call review of -21 by Carlos MartÃnez (diff) Genart Last Call review of -21 by Robert Sparks (diff) |
|
| Assignment | Reviewer | Carlos MartÃnez |
| State | Completed | |
| Review | review-ietf-rtcweb-jsep-21-opsdir-lc-martinez-2017-08-16 | |
| Reviewed rev. | 21 (document currently at 26) | |
| Review result | Ready | |
| Review completed: | 2017-08-16 |
Review
review-ietf-rtcweb-jsep-21-opsdir-lc-martinez-2017-08-16
I have reviewed this document as part of the Operational directorate's ongoing effort to review all IETF documents being processed by the IESG. These comments were written with the intent of improving the operational aspects of the IETF drafts. Comments that are not addressed in last call may be included in AD reviews during the IESG review. Document editors and WG chairs should treat these comments just like any other last call comments. Noting that I'm certainly not an expert on the subject matter, I've found this document to be READY. I found it well-written, it contains plenty of detailed examples (which I believe are really important for API and programming-heavy documents), and includes plenty of references as well. Please do not forget to remove "Appendix B. Change log". A minor observation, not even a nit, is that the text in the Security Considerations "While formally the JSEP interface is an API, it is better to think of it is an Internet protocol, with the JS being untrustworthy from the perspective of the endpoint. " could be more clear. thanks! /Carlos