Last Call Review of draft-ietf-dhc-v6only-03

Request Review of draft-ietf-dhc-v6only
Requested rev. no specific revision (document currently at 06)
Type Last Call Review
Team Security Area Directorate (secdir)
Deadline 2020-07-02
Requested 2020-06-18
Authors Lorenzo Colitti, Jen Linkova, Michael Richardson, Tomek Mrugalski
Draft last updated 2020-06-18
Completed reviews Secdir Last Call review of -03 by Russ Housley (diff)
Iotdir Last Call review of -03 by Pascal Thubert (diff)
Opsdir Last Call review of -03 by Sheng Jiang (diff)
Assignment Reviewer Russ Housley
State Completed
Review review-ietf-dhc-v6only-03-secdir-lc-housley-2020-06-18
Posted at
Reviewed rev. 03 (document currently at 06)
Review result Has Nits
Review completed: 2020-06-18


I 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 authors, document editors, and WG chairs should
treat these comments just like any other IETF Last Call comments.

Document: draft-ietf-dhc-v6only-03
Reviewer: Russ Housley
Review Date: 2020-06-18
IETF LC End Date: 2020-07-02
IESG Telechat date: unknown

Summary: Has Nits

Major Concerns:


Minor Concerns:

Section 3.4 includes:

    V6ONLY_WAIT     The minimum time the client SHOULD stop the DHCPv4
                    configuration process for. MUST be no less than
                    MIN_V6ONLY_WAIT seconds. Default: 1800 seconds

The second sentence should include a subject; and "MUST NOT" seems like
a better wording to me.  I suggest:

    V6ONLY_WAIT     The minimum time for which the client SHOULD stop
                    the DHCPv4 configuration process. The value MUST NOT
                    be less than MIN_V6ONLY_WAIT seconds.
                    Default: 1800 seconds.


Section 2: s/seems only natural/seems natural/

Section 3.3.1: s/for V6ONLY_WAIT second/for V6ONLY_WAIT seconds/