IETF Logo Mail Archive

Re: [netmod] Common etag, timestamp on all interfaces (draft-lindblad-netconf-transaction-id)

Kent Watsen <kent@watsen.net> Wed, 23 March 2022 23:05 UTC

Return-Path: <0100017fb906d433-172359f0-01a8-4a82-8e25-8079bdafef76-000000@amazonses.watsen.net>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D0823A0E04 for <netmod@ietfa.amsl.com>; Wed, 23 Mar 2022 16:05:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cU659bFJ7kmE for <netmod@ietfa.amsl.com>; Wed, 23 Mar 2022 16:05:09 -0700 (PDT)
Received: from a48-92.smtp-out.amazonses.com (a48-92.smtp-out.amazonses.com [54.240.48.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 053903A0E00 for <netmod@ietf.org>; Wed, 23 Mar 2022 16:05:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1648076707; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:In-Reply-To:Cc:To:References:Feedback-ID; bh=S5lKp6AqERGrEygL2KBoREZGiOljx+bU8Ylb8BDK2G0=; b=i4EIDNC3aiv+eGdqwFxdGjQrtjZJt2fhEeXVLtZwfaIMp6caCwFd1+r7cmBWmo/r bNqBzNpQTYCGxakdF3rGmueIxMx/mRnVC7D3DVqnskEE+oDpFfWtq2YOkuJADqqepaD LoKniQrDSSdoNqvGASGe8P1aUf4ycsJJaUwWtIro=
From: Kent Watsen <kent@watsen.net>
Message-ID: <0100017fb906d433-172359f0-01a8-4a82-8e25-8079bdafef76-000000@email.amazonses.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_A38D2FB1-448A-43BA-BB28-A39864D3560A"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.60.0.1.1\))
Date: Wed, 23 Mar 2022 23:05:07 +0000
In-Reply-To: <VI1PR0701MB2351D399AB78445A66E16DD1F0189@VI1PR0701MB2351.eurprd07.prod.outlook.com>
Cc: "netmod@ietf.org" <netmod@ietf.org>
To: =?utf-8?Q?Bal=C3=A1zs_Lengyel?= <balazs.lengyel=40ericsson.com@dmarc.ietf.org>
References: <VI1PR0701MB2351D399AB78445A66E16DD1F0189@VI1PR0701MB2351.eurprd07.prod.outlook.com>
X-Mailer: Apple Mail (2.3693.60.0.1.1)
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
X-SES-Outgoing: 2022.03.23-54.240.48.92
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/_IQSml5V_4b3sOuVOo0GlCH8ZEs>
Subject: Re: [netmod] Common etag, timestamp on all interfaces (draft-lindblad-netconf-transaction-id)
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Mar 2022 23:05:12 -0000


> I assume that the etag defined in your I-D is the same as the one defined in Restconf. Does or should your draft include a statement like:
> “The etag values maintained by the server are protocol/interface independent. If requested the same etag values will be visible on all interface including Restconf, Netconf, CLI etc.”

While it makes sense that a server would use the same values across protocols, I'm unsure if it's needed and, if we do, if we could state it in a NETCONF-specific draft.


> Restconf also includes timestamps. What was your reason to exclude them from your I-D ? IMHO if the server maintains timestamps they would be protocol/interface independent just as etags, so the task is to make them available on Netconf too (and maybe the CLI).

I agree and have mentioned before.  LastModified either needs to be added, or justified why not added, to get my adoption support.


> Regards Balazs

Kent // contributor

v2.8.7 | Report a Bug | By Email