Last Call Review of draft-ietf-opsawg-sdi-08
review-ietf-opsawg-sdi-08-tsvart-lc-kuehlewind-2020-05-05-00

This document has been reviewed as part of the transport area review team's
ongoing effort to review key IETF documents. These comments were written
primarily for the transport area directors, but are copied to the document's
authors and WG to allow them to address any issues raised and also to the IETF
discussion list for information.

When done at the time of IETF Last Call, the authors should consider this
review as part of the last-call comments they receive. Please always CC
tsv-art@ietf.org if you reply to or forward this review.

This document specifies a process to encrypt an initial configuration file. The
process of fetching the config file is not altered and as such there are no new
transport related issue.

However, one quick question/comment regarding the following sentence in section
4.3.: "if parsing the
   configurations fails, the device will either abort the auto-install
   process, or will repeat this process until it succeeds."
Is this supposed to indicate that the whole process, including fetching the
file should be repeated? If so, there needs to be guidance that one should not
immediately fetch again but wait for a period of maybe seconds (or minutes?)
and a limit for maximum number of retries must be implemented. Yes, this is not
necessarily part of the process that is altered in this document but if this
guidance is given it should be correct. If similar guidance is already provides
in other documents, a pointer to those docs might work as well.

Editorial comment:
I would recommend to use more generic company names than Sirius Cybernetics
Corp and Acme Network Widgets to avoid that these names can be mistaken as real
companies. I know it's boring but Vendor A and Operator B would probably work
just fine.