Telechat Review of draft-ietf-kitten-rfc5653bis-06
review-ietf-kitten-rfc5653bis-06-genart-telechat-halpern-2018-01-02-00

Request Review of draft-ietf-kitten-rfc5653bis
Requested revision No specific revision (document currently at 07)
Type Telechat Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2018-01-23
Requested 2017-12-27
Authors Mayank D. Upadhyay , Seema Malkani , Wang Weijun
I-D last updated 2018-01-02
Completed reviews Opsdir Last Call review of -05 by Joe Clarke (diff)
Genart Last Call review of -05 by Joel M. Halpern (diff)
Secdir Last Call review of -05 by Tim Polk (diff)
Genart Telechat review of -06 by Joel M. Halpern (diff)
Assignment Reviewer Joel M. Halpern
State Completed
Request Telechat review on draft-ietf-kitten-rfc5653bis by General Area Review Team (Gen-ART) Assigned
Reviewed revision 06 (document currently at 07)
Result Ready w/issues
Completed 2018-01-02
review-ietf-kitten-rfc5653bis-06-genart-telechat-halpern-2018-01-02-00
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.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-kitten-rfc5653bis-06
Reviewer: Joel Halpern
Review Date: 2018-01-02
IETF LC End Date: 2017-09-11
IESG Telechat date: 2018-01-25

Summary: This document is ready for publication as a Proposed Standard RFC

Major issues: None

Minor issues:
    Although ID-Nits does not complain about it, I can find no reference to
    RFCs 2119 or 8174.  Some of the uses of "must" int he document are along
    the lines of "inherently follows", which is not normative language.  But
    other uses are clearly normative in structure.   It is unclear why the
    reference to RFC 2119 was removed as part of this update.

Nits/editorial comments: