Telechat Review of draft-ietf-opsawg-mud-20
review-ietf-opsawg-mud-20-opsdir-telechat-bradner-2018-04-10-00
| Request | Review of | draft-ietf-opsawg-mud |
|---|---|---|
| Requested revision | No specific revision (document currently at 25) | |
| Type | Telechat Review | |
| Team | Ops Directorate (opsdir) | |
| Deadline | 2018-04-17 | |
| Requested | 2018-03-13 | |
| Authors | Eliot Lear , Ralph Droms , Dan Romascanu | |
| I-D last updated | 2018-04-10 | |
| Completed reviews |
Secdir Early review of -08
by Adam W. Montville
(diff)
Genart Early review of -08 by Robert Sparks (diff) Iotdir Early review of -08 by Henk Birkholz (diff) Yangdoctors Early review of -08 by Martin Björklund (diff) Rtgdir Last Call review of -13 by Adrian Farrel (diff) Secdir Last Call review of -13 by Adam W. Montville (diff) Genart Telechat review of -20 by Robert Sparks (diff) Opsdir Telechat review of -20 by Scott O. Bradner (diff) |
|
| Assignment | Reviewer | Scott O. Bradner |
| State | Completed | |
| Request | Telechat review on draft-ietf-opsawg-mud by Ops Directorate Assigned | |
| Reviewed revision | 20 (document currently at 25) | |
| Result | Has nits | |
| Completed | 2018-04-10 |
review-ietf-opsawg-mud-20-opsdir-telechat-bradner-2018-04-10-00
I did an OPS-DIR review of Manufacturer Usage Description Specification < draft-ietf-opsawg-mud > The specification is well written and clear (I also agree with Robert Spark's nits). One suggestion about document organization: I would either move the discussion of what should be done if the MUD controller can not retrieve the MUD file for some reason or another out of the security considerations section to after section 1.9 or at least include a forward pointer to the discussion.