[netconf] Opsdir last call review of draft-ietf-netconf-restconf-notif-13
Dan Romascanu via Datatracker <noreply@ietf.org> Fri, 12 April 2019 06:54 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: netconf@ietf.org
Delivered-To: netconf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C8BB012015B; Thu, 11 Apr 2019 23:54:04 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Dan Romascanu via Datatracker <noreply@ietf.org>
To: ops-dir@ietf.org
Cc: netconf@ietf.org, ietf@ietf.org, draft-ietf-netconf-restconf-notif.all@ietf.org, dromasca@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 6.95.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Dan Romascanu <dromasca@gmail.com>
Message-ID: <155505204479.14152.7199403462087388546@ietfa.amsl.com>
Date: Thu, 11 Apr 2019 23:54:04 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/3nANLhr7x2FCdmg6eS5PJUPMJLA>
Subject: [netconf] Opsdir last call review of draft-ietf-netconf-restconf-notif-13
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.29
List-Id: NETCONF WG list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Apr 2019 06:54:05 -0000
Reviewer: Dan Romascanu Review result: Ready This document describes the RESTCONF binding to the dynamic subscription capability of both subscribed notifications and YANG-Push. It's a useful and important addition to the RESTCONF protocol mechanisms, and operators should pay attention. The document is not easy reading, as it relies on several other documents, but the references in the text help. It would have helped if some notes were added concerning the possible actions that the operators need to take in order to ensure optimal behavior (initial configuration for example) or indications about when to use one or the other of the notifications mechanisms. This is not blocking, however, and the document is READY for publication.
- [netconf] Opsdir last call review of draft-ietf-n… Dan Romascanu via Datatracker
- Re: [netconf] Opsdir last call review of draft-ie… Reshad Rahman (rrahman)
- Re: [netconf] Opsdir last call review of draft-ie… Alexander Clemm