[dhcwg] Lars Eggert's No Objection on draft-ietf-dhc-dhcpv6-yang-24: (with COMMENT)

Lars Eggert via Datatracker <noreply@ietf.org> Thu, 16 December 2021 12:59 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: dhcwg@ietf.org
Delivered-To: dhcwg@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2716A3A0E75; Thu, 16 Dec 2021 04:59:17 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Lars Eggert via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-dhc-dhcpv6-yang@ietf.org, dhc-chairs@ietf.org, dhcwg@ietf.org, Timothy Winters <tim@qacafe.com>, tim@qacafe.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.41.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Lars Eggert <lars@eggert.org>
Message-ID: <163965955639.4687.2162687908401182501@ietfa.amsl.com>
Date: Thu, 16 Dec 2021 04:59:17 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/fGDW9uQ_Up822b7gfG4BaCRTIRk>
Subject: [dhcwg] Lars Eggert's No Objection on draft-ietf-dhc-dhcpv6-yang-24: (with COMMENT)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Dynamic Host Configuration <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Dec 2021 12:59:17 -0000

Lars Eggert has entered the following ballot position for
draft-ietf-dhc-dhcpv6-yang-24: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/blog/handling-iesg-ballot-positions/
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv6-yang/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

All comments below are about very minor potential issues that you may choose to
address in some way - or ignore - as you see fit. Some were flagged by
automated tools (via https://github.com/larseggert/ietf-reviewtool), so there
will likely be some false positives. There is no need to let me know what you
did with these suggestions.

Section 4.1. , paragraph 10, nit:
-        to the license terms contained in, the Simplified BSD License
-                                               ^ ^^^^^^
+        to the license terms contained in, the Revised BSD License
+                                               ^^^ ^

Also elsewhere, please change them all. (The TLP recently changed.)

Section 3.1. , paragraph 3, nit:
>  than 128-octets) content field. Currently there are four defined types of D
>                                  ^^^^^^^^^
A comma may be missing after the conjunctive/linking adverb "Currently".
[SENT_START_CONJUNCTIVE_LINKING_ADVERB_COMMA]

Section 3.1. , paragraph 5, nit:
> ed when there is a status message for an failure. 3.2. DHCPv6 Relay Tree Dia
>                                       ^^
Use "a" instead of "an" if the following word doesn't start with a vowel sound,
e.g. "a sentence", "a university". [EN_A_VS_AN]

Section 3.3. , paragraph 3, nit:
> th (1-128 octets) content field. Currently there are four defined types of D
>                                  ^^^^^^^^^
A comma may be missing after the conjunctive/linking adverb "Currently".
[SENT_START_CONJUNCTIVE_LINKING_ADVERB_COMMA]

Section 4.1. , paragraph 20, nit:
>  this option to tell the client whether or not to accept Reconfigure messages
>                                 ^^^^^^^^^^^^^^
Consider shortening this phrase to just "whether". It is correct though if you
mean "regardless of whether". [WHETHER]

Section 4.2. , paragraph 38, nit:
> nitions for DHCPv6 options that can be be sent by the client. Additional opti
>                                     ^^^^^
Possible typo: you repeated a word. [ENGLISH_WORD_REPEAT_RULE]

Section 4.4. , paragraph 29, nit:
> tions The following section provides a example of how the DHCPv6 option defi
>                                      ^
Use "an" instead of "a" if the following word starts with a vowel sound, e.g.
"an article", "an hour". [EN_A_VS_AN]

Section 4.4. , paragraph 29, nit:
> escription "SIP server list identifier identifier."; } leaf sip-serv-domain-n
>                             ^^^^^^^^^^^^^^^^^^^^^
Possible typo: you repeated a word. [ENGLISH_WORD_REPEAT_RULE]

Section 4.4. , paragraph 33, nit:
> on "Configures how the server will stores leases."; choice storage-type { de
>                                    ^^^^^^
The modal verb "will" requires the verb's base form. [MD_BASEFORM]

Section 4.4. , paragraph 35, nit:
> rname { type string; description "User name of the account under which the se
>                                   ^^^^^^^^^
It's more common nowadays to write this noun as one word.
[RECOMMENDED_COMPOUNDS]

Section 5. , paragraph 2, nit:
> rname { type string; description "User name of the account under which the se
>                                   ^^^^^^^^^
It's more common nowadays to write this noun as one word.
[RECOMMENDED_COMPOUNDS]