Re: [RTG-DIR] RtgDir Last Call Review: draft-ietf-idr-bgp-ls-flex-algo-09

[Ketan Talaulikar <[e-mail]>]

Hi Donald,

The recent update below includes changes to address your comments.

https://datatracker.ietf.org/doc/html/draft-ietf-idr-bgp-ls-flex-algo-10

Thanks,
Ketan


On Thu, Aug 18, 2022 at 11:02 AM Ketan Talaulikar <[e-mail]>
wrote:

> Hi Donald,
>
> Thanks for your review and agree with all your suggested edits for the
> nits.
>
> These changes will reflect in the upcoming update of the draft.
>
> Thanks,
> Ketan
>
>
> On Thu, Aug 18, 2022 at 12:40 AM Donald Eastlake <[e-mail]> wrote:
>
>> Hello,
>>
>> I have been selected as the Routing Directorate reviewer for this draft.
>> The Routing Directorate seeks to review all routing or routing-related
>> drafts as they pass through IETF last call and IESG review, and sometimes
>> on special request. The purpose of the review is to provide assistance to
>> the Routing ADs. For more information about the Routing Directorate, please
>> see http://trac.tools.ietf.org/area/rtg/trac/wiki/RtgDir
>>
>> Although these comments are primarily for the use of the Routing ADs, it
>> would be helpful if you could consider them along with any other IETF Last
>> Call comments that you receive, and strive to resolve them through
>> discussion or by updating the draft.
>>
>> Document: draft-ietf-idr-bgp-ls-flex-algo-09
>> Reviewer: Donald E. Eastlake III
>> Review Date: 2022-08-16
>> IETF LC End Date: 2022-08-17
>> Intended Status: Proposed Standard
>>
>> *Summary:*
>>
>> This document is basically ready for publication but has nits that should
>> be considered prior to publication.
>>
>> *Comments:*
>>
>> This is a straightforward and relatively easy to read document. The
>> inclusion of the Flexible Algorithm Unknown sub-TLV is an interesting and
>> useful detail. I found a number of nits.
>>
>> *Major Issues:*
>>
>> No major issues found.
>>
>> *Minor Issues:*
>>
>> No minor issues found.
>>
>> *Nits:*
>>
>> In Flexible Algorithm D/definition, the capitalization of "definition"
>> should be consistent. I suggest it be capitalized.
>>
>> In abstract, suggest "propagated (viz. OSPF and IS-IS flooding) through
>> the network" -> "propagated through the network by OSPF and IS-IS
>> flooding"
>>
>> Section 1, top of page 3: "Flexible Algorithm is called so as" ->
>> "Flexible Algorithm is so called because"
>>
>> Maybe it's just me but "leverage" seems to be an overly complicated word
>> with a faint whiff of marketing about it. Suggest, in Section 1,
>> "leverated" -> "used", "leveraging" -> "using"
>>
>> Section 2: Expand SRLG on first use.
>>
>> Reference to draft-ietf-spring-segment-routing-policy should be to RFC
>> 9256.
>>
>> Global: "e.g. " -> "e.g.," (replace space after "e.g." with a comma) In
>> some cases it might read better to replace "e.g. " with "for example,"
>>
>> Global: "ISIS" -> "IS-IS"
>>
>> Donald
>> ===============================
>>  Donald E. Eastlake 3rd   [phone] (cell)
>>  2386 Panoramic Circle, Apopka, FL 32703 USA
>>  [e-mail]
>>
>