Last Call Review of draft-altman-tls-channel-bindings-
review-altman-tls-channel-bindings-secdir-lc-nystrom-2009-11-02-00
| Request | Review of | draft-altman-tls-channel-bindings |
|---|---|---|
| Requested rev. | no specific revision (document currently at 10) | |
| Type | Last Call Review | |
| Team | Security Area Directorate (secdir) | |
| Deadline | 2009-11-02 | |
| Requested | 2009-10-08 | |
| Draft last updated | 2009-11-02 | |
| Completed reviews |
Secdir Last Call review of -?? by Magnus Nystrom
Secdir Last Call review of -?? by Magnus Nystrom |
|
| Assignment | Reviewer | Magnus Nystrom |
| State | Completed | |
| Review | review-altman-tls-channel-bindings-secdir-lc-nystrom-2009-11-02 | |
| Review completed: | 2009-11-02 |
Review
review-altman-tls-channel-bindings-secdir-lc-nystrom-2009-11-02
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 defines channel binding types for Transport Layer Security (TLS), in accordance with RFC 5056. The security considerations section seems adequate to me (especially the discussion about the consequences of sending channel binding data in the authentication mechanism). It would have been nice with an example of an authentication mechanism using one of the channel bindings in this document, perhaps in the form of an illustrative appendix. Nits: -Section 2 should reference RFC 5056, not RFC 5246. -There should be some spell checking, like "descritption" -- Magnus