Opsdir last call review of draft-ietf-6man-rfc6434-bis-08
Scott Bradner <sob@sobco.com> Tue, 19 June 2018 10:35 UTC
Return-Path: <sob@sobco.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B0255130E60; Tue, 19 Jun 2018 03:35:58 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Scott Bradner <sob@sobco.com>
To: ops-dir@ietf.org
Cc: draft-ietf-6man-rfc6434-bis.all@ietf.org, ipv6@ietf.org, ietf@ietf.org
Subject: Opsdir last call review of draft-ietf-6man-rfc6434-bis-08
X-Test-IDTracker: no
X-IETF-IDTracker: 6.81.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152940455863.13546.13553834320913116631@ietfa.amsl.com>
Date: Tue, 19 Jun 2018 03:35:58 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/o0D-1vgNJhMI2NTujXSHQHym_hI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.26
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jun 2018 10:35:59 -0000
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.
- Opsdir last call review of draft-ietf-6man-rfc643… Scott Bradner
- Re: Opsdir last call review of draft-ietf-6man-rf… Timothy Winters
- Re: Opsdir last call review of draft-ietf-6man-rf… Scott O. Bradner