Last Call Review of draft-ietf-httpbis-rfc5987bis-04
review-ietf-httpbis-rfc5987bis-04-secdir-lc-zhang-2017-02-23-00

Request Review of draft-ietf-httpbis-rfc5987bis
Requested rev. no specific revision (document currently at 05)
Type Last Call Review
Team Security Area Directorate (secdir)
Deadline 2017-02-20
Requested 2017-02-06
Authors Julian Reschke
Draft last updated 2017-02-23
Completed reviews Opsdir Last Call review of -04 by Jouni Korhonen (diff)
Secdir Last Call review of -04 by Dacheng Zhang (diff)
Genart Last Call review of -04 by Stewart Bryant (diff)
Assignment Reviewer Dacheng Zhang 
State Completed
Review review-ietf-httpbis-rfc5987bis-04-secdir-lc-zhang-2017-02-23
Reviewed rev. 04 (document currently at 05)
Review result Ready
Review completed: 2017-02-23

Review
review-ietf-httpbis-rfc5987bis-04-secdir-lc-zhang-2017-02-23

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 specifies an encoding suitable for use in HTTP header fields that is compatible with a simplified profile of the encoding defined in RFC2231, and obsoletes RFC5987.



Compared to RFC 5987, the updates in this document does not introduce any additional security considerations, and the contents in the security considerations section is exactly identical to the counterparts in RFC 5987. So, I agree this document is ready for publication as Proposed Standard.



Cheers



Dacheng