[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ipng
Subject:    Opsdir last call review of draft-ietf-6man-rfc6434-bis-08
From:       Scott Bradner <sob () sobco ! com>
Date:       2018-06-19 10:35:58
Message-ID: 152940455863.13546.13553834320913116631 () ietfa ! amsl ! com
[Download RAW message or body]

Reviewer: Scott Bradner
Review result: Ready

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.


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
[prev in list] [next in list] [prev in thread] [next in thread]