Last Call Review of draft-ietf-6man-rfc6434-bis-08
review-ietf-6man-rfc6434-bis-08-opsdir-lc-bradner-2018-06-19-00

Request Review of draft-ietf-6man-rfc6434-bis
Requested rev. no specific revision (document currently at 09)
Type Last Call Review
Team Ops Directorate (opsdir)
Deadline 2018-06-25
Requested 2018-06-11
Draft last updated 2018-06-19
Completed reviews Opsdir Last Call review of -08 by Scott Bradner (diff)
Rtgdir Last Call review of -08 by Russ White (diff)
Genart Last Call review of -09 by Vijay Gurbani
Secdir Last Call review of -09 by Tobias Gondrom
Tsvart Telechat review of -08 by Magnus Westerlund (diff)
Assignment Reviewer Scott Bradner
State Completed
Review review-ietf-6man-rfc6434-bis-08-opsdir-lc-bradner-2018-06-19
Reviewed rev. 08 (document currently at 09)
Review result Ready
Review completed: 2018-06-19

Review
review-ietf-6man-rfc6434-bis-08-opsdir-lc-bradner-2018-06-19

This is an OPS-DIR review of IPv6 Node Requirements (draft-ietf-6man-rfc6434-bis-08).

This document is a compendium of what RFCs need to be implemented or paid attention to if someone wants to make a fully operational IPv6 node.  The document shows quite clearly that making such a node is a lot of work - i.e., there are a lot of RFCs listed - gone are the days when implementing an Internet node involved less documentation than implementing an OSI GOSSIP node. 

All of the changes listed in the two "changes from" sections seem very reasonable.

Relative to the OPS area, there is a "Network Management" section that does a good job of listing the possible management technologies to implement.  I do not know why the section is called "network management" since the document is about nodes not networks (it would be better called "IPv6 Node Management")

I'm also not sure why management is a MAY - seems to me that it should be a SHOULD (a MUST unless you have a good reason not to) - deploying new IPv6 nodes that are immune to management does not seem like a good idea these days.