Last Call Review of draft-ietf-appsawg-about-uri-scheme-
review-ietf-appsawg-about-uri-scheme-secdir-lc-kumari-2012-05-04-00
Request | Review of | draft-ietf-appsawg-about-uri-scheme |
---|---|---|
Requested revision | No specific revision (document currently at 07) | |
Type | Last Call Review | |
Team | Security Area Directorate (secdir) | |
Deadline | 2012-05-17 | |
Requested | 2012-04-22 | |
Authors | S Moonesamy | |
I-D last updated | 2012-05-04 | |
Completed reviews |
Secdir Last Call review of -??
by Warren "Ace" Kumari
|
|
Assignment | Reviewer | Warren "Ace" Kumari |
State | Completed | |
Request | Last Call review on draft-ietf-appsawg-about-uri-scheme by Security Area Directorate Assigned | |
Result | Ready | |
Completed | 2012-05-04 |
review-ietf-appsawg-about-uri-scheme-secdir-lc-kumari-2012-05-04-00
Hi, Do not be alarmed... I have reviewed this document as part of the security directorate's ongoing effort to review all IETF documents being processed by the IESG. These comments were written primarily for the benefit of the security area directors. Document editors and WG chairs should treat these comments just like any other last call comments. This document codifies an existing mechanism, used by lots of browsers. It creates a registry for specific about:<something> tokens, where the only (currently) defined token is "blank", which, surprisingly enough, brings up a blank page... The "Security Considerations" section exists, and is well written. It punts much of the security to the application -- IMO this is the correct thing to do in this case. W