Skip to main content

Last Call Review of draft-ietf-detnet-use-cases-19
review-ietf-detnet-use-cases-19-secdir-lc-hallam-baker-2018-10-24-00

Request Review of draft-ietf-detnet-use-cases
Requested revision No specific revision (document currently at 20)
Type Last Call Review
Team Security Area Directorate (secdir)
Deadline 2018-10-03
Requested 2018-09-19
Authors Ethan Grossman
I-D last updated 2018-10-24
Completed reviews Secdir Last Call review of -19 by Phillip Hallam-Baker (diff)
Genart Last Call review of -18 by Pete Resnick (diff)
Genart Telechat review of -19 by Pete Resnick (diff)
Assignment Reviewer Phillip Hallam-Baker
State Completed
Request Last Call review on draft-ietf-detnet-use-cases by Security Area Directorate Assigned
Reviewed revision 19 (document currently at 20)
Result Ready
Completed 2018-10-24
review-ietf-detnet-use-cases-19-secdir-lc-hallam-baker-2018-10-24-00
I have reviewed the document, and it is ready for publication. The document is
an analysis of the use cases and (now) properly refers to a separate security
considerations section.

The use cases document is ready for publication and this should go forward now.
However the security considerations document is still a work in progress, no
document shepherd assigned. Which is of course right and proper for a security
considerations relating to the final proposal. And of course it is useful to
nail down the use cases before looking at the security considerations. But the
use cases having deferred security to the external document risks creating a
deadlock situation.

It is important that the document contain a link to the security considerations
to be supplied but this should not hold up publication as an RFC.

My only comment on the referenced SC document at this stage is that it might be
that the term 'deterministic networking' overstates the requirements evidenced
by the use cases. In many of the cited use cases, what is required is a higher
degree of confidence that the network characteristics meet certain requirements
than an absolute guarantee. It might be that 'predictable networking' provides
a better description of those requirements.