[netconf] data-export-capabilities: insert hint into the error response

Qin Wu <bill.wu@huawei.com> Tue, 09 March 2021 03:42 UTC

Return-Path: <bill.wu@huawei.com>
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 C96493A0D4A for <netconf@ietfa.amsl.com>; Mon, 8 Mar 2021 19:42:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 AvnOoJOTV37M for <netconf@ietfa.amsl.com>; Mon, 8 Mar 2021 19:42:49 -0800 (PST)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5BAD13A0D48 for <netconf@ietf.org>; Mon, 8 Mar 2021 19:42:49 -0800 (PST)
Received: from fraeml715-chm.china.huawei.com (unknown [172.18.147.206]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4DvgsX3gtrz67tSq for <netconf@ietf.org>; Tue, 9 Mar 2021 11:38:24 +0800 (CST)
Received: from fraeml715-chm.china.huawei.com (10.206.15.34) by fraeml715-chm.china.huawei.com (10.206.15.34) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Tue, 9 Mar 2021 04:42:46 +0100
Received: from DGGEML422-HUB.china.huawei.com (10.1.199.39) by fraeml715-chm.china.huawei.com (10.206.15.34) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.2106.2 via Frontend Transport; Tue, 9 Mar 2021 04:42:46 +0100
Received: from DGGEML511-MBS.china.huawei.com ([169.254.4.181]) by dggeml422-hub.china.huawei.com ([10.1.199.39]) with mapi id 14.03.0513.000; Tue, 9 Mar 2021 11:42:43 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: data-export-capabilities: insert hint into the error response
Thread-Index: AdcUlYCPLLNtnrcqTBCpZxYAtbbRww==
Date: Tue, 9 Mar 2021 03:42:43 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABAADE4CAC9@dggeml511-mbs.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.136.123.117]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/qVIwRZNSF-KFuCo2UOfE9bYLeG8>
Subject: [netconf] data-export-capabilities: insert hint into the error response
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.29
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, 09 Mar 2021 03:42:52 -0000

Hi, 
One of open issues we discuss in the netconf session is related to necessity of data export capability in the draft-tao-netconf-data-export-capabilities
Is there any alternative way?
One of alternative way we investigate is one proposed in RFC8639, i.e., insert hint into the error response
Pro: Accept the failure the first RPC request attempt, but increases the likelihood of success for subsequent RPC requests
Con: Such likelihood of success for subsequent RPC requests is not guaranteed since hint needs to be specified every time we have new hint, otherwise the client who initiate the RPC request may not understand what hint means.

With data export capability advertisement,
Pro: increase likelihood of success for the first RPC request, doesn’t need to wait for the second round RPC exchange
The cost is to introduce new parameter in the notification capability message in the draft-ietf-netconf-notification-capabilities-14.
Given the notification capability has been well accepted and stable for publication, 
I think it layer foundation for new capability definitions.

-Qin (on behalf of authors)
-----邮件原件-----
发件人: netconf [mailto:netconf-bounces@ietf.org] 代表 maqiufang (A)
发送时间: 2021年1月20日 21:01
收件人: netconf@ietf.org
主题: [netconf] New Version Notification for draft-tao-netconf-data-export-capabilities-03.txt

Hi, all:
 We have updated the draft, https://www.ietf.org/archive/id/draft-tao-netconf-data-export-capabilities-03.txt  .
 
The main changes are following :
   o  Change 'data-export-capabilities' into list type to support
      multiple transport protocol, encoding on the server.
   o  Add Usage Example of interaction with UDP based Transport for
      Configured Subscription.
   o  Add Thomas Graf as a contributor;
   o  Update motivation in the introduction to clarify why this work is
      needed.
   o  Support udp notif and http notif as two optional transport in the
      YANG data model.

Any suggestions and comments would be greatly appreciated!

Qiufang Ma(On behalf of authors)


-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: Wednesday, January 20, 2021 8:46 PM
To: Peng Liu <liupengyjy@chinamobile.com>om>; Qin Wu <bill.wu@huawei.com>om>; Qin Wu <bill.wu@huawei.com>om>; maqiufang (A) <maqiufang1@huawei.com>
Subject: New Version Notification for draft-tao-netconf-data-export-capabilities-03.txt


A new version of I-D, draft-tao-netconf-data-export-capabilities-03.txt
has been successfully submitted by Qiufang Ma and posted to the IETF repository.

Name:		draft-tao-netconf-data-export-capabilities
Revision:	03
Title:		Telemetry Data Export capability
Document date:	2021-01-20
Group:		Individual Submission
Pages:		18
URL:            https://www.ietf.org/archive/id/draft-tao-netconf-data-export-capabilities-03.txt
Status:         https://datatracker.ietf.org/doc/draft-tao-netconf-data-export-capabilities/
Htmlized:       https://datatracker.ietf.org/doc/html/draft-tao-netconf-data-export-capabilities
Htmlized:       https://tools.ietf.org/html/draft-tao-netconf-data-export-capabilities-03
Diff:           https://www.ietf.org/rfcdiff?url2=draft-tao-netconf-data-export-capabilities-03

Abstract:
   This document proposes a YANG module for telemetry data export
   capabilities which augments system Capabilities model and provides
   additional telemetry data export attributes associated with system
   capabilities for transport dependent capability advertisement.

                                                                                  


Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat


_______________________________________________
netconf mailing list
netconf@ietf.org
https://www.ietf.org/mailman/listinfo/netconf