Early Review of draft-ietf-dhc-rfc3315bis-10

Request Review of draft-ietf-dhc-rfc3315bis
Requested rev. no specific revision (document currently at 13)
Type Early Review
Team Internet Area Directorate (intdir)
Deadline 2017-10-30
Requested 2017-10-16
Requested by Suresh Krishnan
Authors Tomek Mrugalski, Marcin Siodelski, Bernie Volz, Andrew Yourtchenko, Michael Richardson, Sheng Jiang, Ted Lemon, Timothy Winters
Draft last updated 2017-11-01
Completed reviews Intdir Early review of -10 by Zhen Cao (diff)
Genart Telechat review of -10 by Elwyn Davies (diff)
Secdir Telechat review of -10 by Kyle Rose (diff)
Opsdir Telechat review of -10 by Dan Romascanu (diff)
Tsvart Telechat review of -10 by Allison Mankin (diff)
Assignment Reviewer Zhen Cao 
State Completed
Review review-ietf-dhc-rfc3315bis-10-intdir-early-cao-2017-11-01
Reviewed rev. 10 (document currently at 13)
Review result Ready with Issues
Review completed: 2017-11-01


I am an assigned INT directorate reviewer for this draft. These
comments were written primarily for the benefit of the Internet Area
Directors. Document editors and shepherds should treat these comments
just like they would treat comments from any other IETF contributors
and resolve them along with any other Last Call comments that have
been received. For more details of the INT directorate, see

This version is quite ready to go, with a small issue that I would like to discussion: 

In Section. 15 (Reliability of Client Initiated Message Exchanges), I strongly recommend that implementation MUST NOT set both MRC or MRD to ZERO, which attaches a possible risk that the client continues to send this message without a stop.    So I would like to propose the following change:

" If both MRC and MRD are zero, the client continues to transmit the
   message until it receives a response."
"The client must be informed with a limit of its retransmission behavior, and MUST NOT set both MRC and MRD to zero"