[bess] Mahesh Jethanandani's No Objection on draft-ietf-bess-evpn-fast-df-recovery-10: (with COMMENT)

[Mahesh Jethanandani via Datatracker <[e-mail]>]

Mahesh Jethanandani has entered the following ballot position for
draft-ietf-bess-evpn-fast-df-recovery-10: 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/about/groups/iesg/statements/handling-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-bess-evpn-fast-df-recovery/



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

Thanks to Dave Thaler for the INTDIR, to Elwyn Davies for the GENART, and
Toerless for the IOTDIR review, the last of which surprised me also. But thanks
to Toerless for his review all the same.

Several others have provided COMMENTs that I had, so I am not going to repeat
them here. Some of the following NITS may also be duplicates.

-------------------------------------------------------------------------------
NIT
-------------------------------------------------------------------------------

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 1.2, paragraph 7
> nchronization among PE devices within a Ethernet Segment redundancy group. T
>                                       ^
Use "an" instead of "a" if the following word starts with a vowel sound, e.g.
"an article", "an hour".

Section 2.2, paragraph 2
>  8.5 of [RFC7432] with the default 3 second timer in step 2: 1. Initial stat
>                                    ^^^^^^^^
When "3-second" is used as a modifier, it is usually spelled with a hyphen.

Section 2.2, paragraph 3
> E1. 4. Timer Start: PE2 starts a 3 second timer to allow the reception of RT
>                                  ^^^^^^^^
When a number forms part of an adjectival compound, use a hyphen.

Section 2.2, paragraph 9
> imer Start: PE2 starts at t=100 a 3 second timer to allow the reception of RT
>                                   ^^^^^^^^
When a number forms part of an adjectival compound, use a hyphen.

Section 3, paragraph 9
> se of the SCT approach presented in this documents encourages the use of lar
>                                     ^^^^
The singular determiner "this" may not agree with the plural noun "documents".
Did you mean "these"?

Section 3, paragraph 20
> r Initiation by PE2: PE2 starts a 3 second timer to allow the reception of RT
>                                   ^^^^^^^^
When a number forms part of an adjectival compound, use a hyphen.

Section 3, paragraph 22
> r Initiation by PE3: PE3 starts a 3 second timer to allow the reception of RT
>                                   ^^^^^^^^
When a number forms part of an adjectival compound, use a hyphen.

Section 4, paragraph 2
> NA is requested to confirm the First Come First Served assignment as follows:
>                                      ^^^^
It seems that a comma is missing.