[netconf] Francesca Palombini's No Objection on draft-ietf-netconf-https-notif-14: (with COMMENT)

Francesca Palombini via Datatracker <noreply@ietf.org> Wed, 31 January 2024 10:31 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 0C616C151095; Wed, 31 Jan 2024 02:31:53 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Francesca Palombini via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-netconf-https-notif@ietf.org, netconf-chairs@ietf.org, netconf@ietf.org, maqiufang1@huawei.com, maqiufang1@huawei.com
X-Test-IDTracker: no
X-IETF-IDTracker: 12.4.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Francesca Palombini <francesca.palombini@ericsson.com>
Message-ID: <170669711304.61715.4383969207518582579@ietfa.amsl.com>
Date: Wed, 31 Jan 2024 02:31:53 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/TfcZ3hNn4rCOOajFNQveKndpw48>
Subject: [netconf] Francesca Palombini's No Objection on draft-ietf-netconf-https-notif-14: (with COMMENT)
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.39
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: Wed, 31 Jan 2024 10:31:53 -0000

Francesca Palombini has entered the following ballot position for
draft-ietf-netconf-https-notif-14: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ 
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-netconf-https-notif/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thank you for the work on this document.

I strongly agree with John's DISCUSS. As he says, RFC required is probably what
you want, also given that the "Reference" field specifically ask for "The RFC
that defined the URN.".

In Section 1: Please update the reference to HTTP/1.1: 7230 has been obsoleted
by 9110 and 9112 (you already have the ref to 9110, so here it is enough to
change 7230 to 9112).

Just a note from someone who is not experienced with YANG, so most likely OK to
ignore, especially since IANA will most likely know how to deal with this, but
by quickly scanning for the "YANG Notifications" registry group, I am not
really sure where to find it. 3553 doesn't really point me to it. But again,
happy to be educated.