Re: [secdir] secdir review of draft-ietf-spring-segment-routing-13

[Benjamin Kaduk <[e-mail]>]

Hi Tero,

On Thu, Mar 29, 2018 at 12:38:34AM +0300, Tero Kivinen wrote:
> 
> "Correct review" is meant to be used when you want to correct some
> mistke in your review. For example link points to wrong location or
> version does not match.
> 
> You can also use it to fix the "review summary" if it is incorrect for
> some reason, but it is not really meant to be used to mark whether the
> discussion triggered by the review caused the issues to be fixed.
> I.e., if the issues found in review are fixed, you do not edit the
> review, but simply reply to the review thread in mailing lists saying
> that "Yes, this solves my issues" or similar, so when ADs check the
> thread they will see that as final email in the thread and know that
> issues have been solved.

Thanks for the clarification!

> Perhaps we should make #2217 higher priority, so reviewers could enter
> unsolicited reviews themselves. 
> 
> [1] https://trac.tools.ietf.org/tools/ietfdb/ticket/2217

It's not entirely clear how often the situation comes up, so I'll
not try to influence the tools team's prioritization.  It will
probably be fine to just tell document authors who want to see a
"clean secdir review" that the system is set up to work differently.

-Ben