IETF Logo Mail Archive

Re: [netconf] Zaheduzzaman Sarker's No Objection on draft-ietf-netconf-http-client-server-17: (with COMMENT)

Kent Watsen <kent+ietf@watsen.net> Tue, 13 February 2024 19:40 UTC

Return-Path: <0100018da3fc9016-6a7badfa-4976-4e20-9b50-14e1ad6c59b5-000000@amazonses.watsen.net>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13023C15107F; Tue, 13 Feb 2024 11:40:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.904
X-Spam-Level:
X-Spam-Status: No, score=-1.904 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=amazonses.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5-Sr0Dh8girf; Tue, 13 Feb 2024 11:40:56 -0800 (PST)
Received: from a8-96.smtp-out.amazonses.com (a8-96.smtp-out.amazonses.com [54.240.8.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 13212C14F693; Tue, 13 Feb 2024 11:40:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=224i4yxa5dv7c2xz3womw6peuasteono; d=amazonses.com; t=1707853254; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:Feedback-ID; bh=crW80hgwPPRKIXUjqkWyorOGdsU5AEU71v34lLW/Cdg=; b=FZmQgA+KJgrGRngtH0XUol9DEzUm6rhqUYRY6hpsGyQlEKXPvUBGZwkp+hMAFJ1A xkjgwM2mcFmDlBpDz+gxs1r7AMXSnPOcJDCJeSjqx+W0ntHeYftMhop2N3HwXFJibKj 5y67PrurAR/RJDyevyjQVe3g6j1zcw5jyfvIwW1E=
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.600.7\))
From: Kent Watsen <kent+ietf@watsen.net>
In-Reply-To: <170782253886.57439.15429040729678382151@ietfa.amsl.com>
Date: Tue, 13 Feb 2024 19:40:54 +0000
Cc: The IESG <iesg@ietf.org>, draft-ietf-netconf-http-client-server@ietf.org, "netconf-chairs@ietf.org" <netconf-chairs@ietf.org>, "netconf@ietf.org" <netconf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-ID: <0100018da3fc9016-6a7badfa-4976-4e20-9b50-14e1ad6c59b5-000000@email.amazonses.com>
References: <170782253886.57439.15429040729678382151@ietfa.amsl.com>
To: Zaheduzzaman Sarker <zahed.sarker.ietf@gmail.com>
X-Mailer: Apple Mail (2.3731.600.7)
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
X-SES-Outgoing: 2024.02.13-54.240.8.96
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/srdkMpPaGczRg0Jko07cHijEurw>
Subject: Re: [netconf] Zaheduzzaman Sarker's No Objection on draft-ietf-netconf-http-client-server-17: (with COMMENT)
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
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: Tue, 13 Feb 2024 19:40:57 -0000

Hi Zaheduzzaman,

Thank you for your valuable comment.  
Please find my response below.

Kent

> On Feb 13, 2024, at 6:08 AM, Zaheduzzaman Sarker via Datatracker <noreply@ietf.org> wrote:
> 
> Zaheduzzaman Sarker has entered the following ballot position for
> draft-ietf-netconf-http-client-server-17: 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-http-client-server/
> 
> 
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> Thanks for working on this specification. This looks good to me from transport
> protocol point of view.
> 
> I have following comment and I believe if addressed properly, it will improve
> the document quality -
> 
> # Section 1 says -
> 
>     It is intended that these groupings will be used to help define the
>     configuration for simple HTTP-based protocols (not for complete web
>     servers or browsers).
> 
>  I would like to see some examples of the "simple HTTP-based protocols" - the
>  words in parenthesis does not help the distinction. The motivation and usage
>  of this protocol should be specified clearly.

I see your point.  First, we should probably s/protocols/applications/.  Next, the word “simple” can be removed.  

For concrete examples, two come to mind: RESTCONF (see the “restconf-client-server” draft) and HTTPS Notifications (see the “https-notif” draft) - both drafts currently being reviewed (or soon to be reviewed) by the IESG.  Both are examples of RESTful APIs.

So with that said, how about this?

NEW:
    It is intended that these groupings will be used to help define
    the configuration for HTTP-based applications, such as those
    implementing RESTful APIs.

Better?
Kent

v2.23.0 | Report a Bug | By Email