Hi Mike, Authors,

I agree with Mike's comment. 

> On Jan 5, 2026, at 4:03 PM, Mike Bishop via Datatracker <[email protected]> 
> wrote:
> 
> Mike Bishop has entered the following ballot position for
> draft-ietf-lsr-anycast-flag-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-lsr-anycast-flag/
> 
> 
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> # IESG review of draft-ietf-lsr-anycast-flag-10
> 
> CC @MikeBishop
> 
> ## Comments
> 
> ### Section 6.1, paragraph 2
> 
> This doesn't need 2119 keywords; just highlight the requirement for receivers.

I agree. A flag is, by definition, either set or clear. 

> 
> ## Nits
> 
> 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.
> 
> ### Typos
> 
> #### Section 5.1, paragraph 1
> ```
> -    This document requests the allocation of new value in the "OSPFv2
> +    This document requests the allocation of a new value in the "OSPFv2

Agree - replace "new" with "a new". 

> +                                             ++
> ```
> 
> ### Grammar/style
> 
> #### Section 2, paragraph 3
> ```
> OULD be logged as an operational error (subject to rate-limiting). The AC-fla

Agree - replace "error(" with "error (". 

>                                      ^
> ```
> It appears that a space is missing.
> 
> #### Section 2, paragraph 10
> ```
> eted according to OSPFv2 [RFC7684]. Thus the Flags field of the BGP-LS Prefix
>                                    ^^^^
> ```
> A comma may be missing after the conjunctive/linking adverb "Thus".

Sure. 

Thanks,
Acee


> 
> 
> 

_______________________________________________
Lsr mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to