Re: Opsdir last call review of draft-ietf-6man-rfc6434-bis-08

Timothy Winters <twinters@iol.unh.edu> Wed, 11 July 2018 19:59 UTC

Return-Path: <twinters@iol.unh.edu>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16C021277BB for <ipv6@ietfa.amsl.com>; Wed, 11 Jul 2018 12:59:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=iol.unh.edu
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lFnZk5TMSxZG for <ipv6@ietfa.amsl.com>; Wed, 11 Jul 2018 12:59:07 -0700 (PDT)
Received: from mail-wm0-x22a.google.com (mail-wm0-x22a.google.com [IPv6:2a00:1450:400c:c09::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E7796124C04 for <ipv6@ietf.org>; Wed, 11 Jul 2018 12:59:06 -0700 (PDT)
Received: by mail-wm0-x22a.google.com with SMTP id b188-v6so3509392wme.3 for <ipv6@ietf.org>; Wed, 11 Jul 2018 12:59:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=mHWlJtwZIdCXe42Jd294SFE3L3Dd1xCon29lI+tv5g0=; b=exC4NVB49z7ED6NXfcKpqdEeRxn9IPvvGdu8l21G43SXcfCNH7IGL/st7qBHlzqhK2 hS1i0TriHJaxYVEp0npboD9/C9d6KfjcX5IXzheJFegsjDlFH0Qj1SHizmijfQuO8jMT dyDZWg0jW2FDcSDMiiytwvVtXiTdwLco0mD2Q=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=mHWlJtwZIdCXe42Jd294SFE3L3Dd1xCon29lI+tv5g0=; b=bt7ws/14fXbVUvW5bcB9KNWJAUux3/4mX93XY+yXayBM+8DTvmOD1T74DHDaa+6ztu ib4VsB/6No2+SmqWm/Szo8azvEkoA4M8lcRmCjoRlm/vvJKb+jwAfx559lsaB+z0AJmq 1hdWun5OxzqQZ2E4hftP9JjP6jkFN4l7G8znGSExg3rVOgSmB6I456eaHYIs0dWpQ4vq IxkUlYieoALbgOoxi7nsc3Bq2gyPAu+n/vgL/Urv90ZuFWRn7Ap+3wxX3jChLGBfZH7U 2cGqLqxAQhJJ/D5Qva3IOb00P0Rb0k/Y5ZEVCRG+ZNs1YCTSEDWl1wZWGgnxaOPMU8Gd OcpA==
X-Gm-Message-State: AOUpUlHRyJ5NRdh38lMZdHorxNv2vEGmj5JhxhCMVnjUDumHFcFynvbk eEZEyod1SfrVVhfzn/uC8/ZbanFdTDukML+A8RSaSQ==
X-Google-Smtp-Source: AAOMgpccBvDwC3zXCpPu/OkAL1vbGrv2HWRPEsnps17Z8AIe8mfIdE81MffrkMkd75WGnQ4o8l4w2wPYIrIJy+MFf2c=
X-Received: by 2002:a1c:e708:: with SMTP id e8-v6mr25162wmh.134.1531339145286; Wed, 11 Jul 2018 12:59:05 -0700 (PDT)
MIME-Version: 1.0
References: <152940455863.13546.13553834320913116631@ietfa.amsl.com>
In-Reply-To: <152940455863.13546.13553834320913116631@ietfa.amsl.com>
From: Timothy Winters <twinters@iol.unh.edu>
Date: Wed, 11 Jul 2018 15:58:53 -0400
Message-ID: <CAOSSMjXnYcsRH6LkY+Acb2Oj7ppi1R0SRBD+QNtAK0nu5-EjyQ@mail.gmail.com>
Subject: Re: Opsdir last call review of draft-ietf-6man-rfc6434-bis-08
To: sob@sobco.com
Cc: ops-dir@ietf.org, draft-ietf-6man-rfc6434-bis.all@ietf.org, 6man WG <ipv6@ietf.org>, ietf@ietf.org
Content-Type: multipart/alternative; boundary="000000000000c933230570bead0c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/WfzGAjz1uNrGL92ZY--GZvIjk_k>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jul 2018 19:59:10 -0000

Hi Scott,

Thanks for the review.  The name of the network management section has been
updated, I think that's technically a better name.

The working group discussed the SHOULD and based on feedback thought that
this should be a MAY.

Regards,
Tim

On Tue, Jun 19, 2018 at 6:36 AM Scott Bradner <sob@sobco.com> wrote:

> 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
> --------------------------------------------------------------------
>