Last Call Review of draft-hardy-pdf-mime-02
review-hardy-pdf-mime-02-genart-lc-romascanu-2016-07-15-00

Request Review of draft-hardy-pdf-mime
Requested rev. no specific revision (document currently at 05)
Type Last Call Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2016-07-21
Requested 2016-06-23
Other Reviews Genart Telechat review of -02 by Dan Romascanu (diff)
Secdir Last Call review of -02 by Phillip Hallam-Baker (diff)
Opsdir Last Call review of -00 by Rick Casarez (diff)
Review State Completed
Reviewer Dan Romascanu
Review review-hardy-pdf-mime-02-genart-lc-romascanu-2016-07-15
Posted at https://www.ietf.org/mail-archive/web/gen-art/current/msg13464.html
Reviewed rev. 02 (document currently at 05)
Review result Ready
Draft last updated 2016-07-15
Review closed: 2016-07-15

Review
review-hardy-pdf-mime-02-genart-lc-romascanu-2016-07-15






I am the assigned Gen-ART reviewer for this draft. The General Area Review Team (Gen-ART) reviews all IETF documents being processed by the IESG for the IETF Chair. Please wait for direction from your document shepherd or AD before posting
 a new version of the draft.




 




For more information, please see the FAQ at




                                                                                                                                                                                                                                                        





<https://trac.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.




 




Document: draft-hardy-pdf-mime-02




Reviewer: Dan Romascanu




Review Date: 07/07/16




IETF LC End Date: 07/21/16




IESG Telechat date: 




 




Summary: Ready. 




 




This informational document which obsoletes RFC 3778 provides an overview of the PDF format and updates the media type registration of “application/pdf” by aligning it with RFC 6838. I am no expert in application formats, but the document
 seems to be well informed and clearly written. A couple of nits generate id-nits warnings (updating RFC 3778 is not mentioned in the Abstract, one unused reference) that can be easily fixed during the RFC Editor processing.





 




Major issues:




 




Minor issues:




 




Nits/editorial comments: