Last Call Review of draft-hardie-privsec-metadata-insertion-05
review-hardie-privsec-metadata-insertion-05-tsvart-lc-tuexen-2017-02-16-00
Request | Review of | draft-hardie-privsec-metadata-insertion |
---|---|---|
Requested revision | No specific revision (document currently at 08) | |
Type | Last Call Review | |
Team | Transport Area Review Team (tsvart) | |
Deadline | 2017-02-21 | |
Requested | 2017-01-24 | |
Authors | Ted Hardie | |
I-D last updated | 2017-02-16 | |
Completed reviews |
Opsdir Last Call review of -05
by Ron Bonica
(diff)
Genart Last Call review of -06 by Stewart Bryant (diff) Secdir Last Call review of -05 by Yoav Nir (diff) Tsvart Last Call review of -05 by Michael Tüxen (diff) Genart Telechat review of -06 by Stewart Bryant (diff) Genart Telechat review of -07 by Stewart Bryant (diff) |
|
Assignment | Reviewer | Michael Tüxen |
State | Completed | |
Request | Last Call review on draft-hardie-privsec-metadata-insertion by Transport Area Review Team Assigned | |
Reviewed revision | 05 (document currently at 08) | |
Result | Ready w/nits | |
Completed | 2017-02-16 |
review-hardie-privsec-metadata-insertion-05-tsvart-lc-tuexen-2017-02-16-00
I've reviewed this document as part of the transport area directorate's ongoing effort to review key IETF documents. These comments were written primarily for the transport area directors, but are copied to the document's authors for their information and to allow them to address any issues raised. When done at the time of IETF Last Call, the authors should consider this review together with any other last-call comments they receive. Please always CC tsv-art@ietf.org if you reply to or forward this review. This draft is basically ready for publication, but has nits that should be fixed before publication. Running https://tools.ietf.org/tools/idnits/idnits.pyht reports * The abstract seems to contain references ([RFC7624]), which it shouldn't. * Unused Reference: 'RFC4301' The discussion of RFC 7871 in section 4 could be improved to allow readers not knowing the EDNS0 option to get the point. Either provide an abstract description or refer to RFC 6891.