IETF Logo Mail Archive

[netconf] RPC request Timeout

Jonathan Hansford <jonathan@hansfords.net> Mon, 21 March 2022 08:59 UTC

Return-Path: <jonathan@hansfords.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 D161A3A18FD for <netconf@ietfa.amsl.com>; Mon, 21 Mar 2022 01:59:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.106
X-Spam-Level:
X-Spam-Status: No, score=-7.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hansfords.net
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 jrCxYtPGPjLA for <netconf@ietfa.amsl.com>; Mon, 21 Mar 2022 01:59:51 -0700 (PDT)
Received: from sender11-op-o11.zoho.eu (sender11-op-o11.zoho.eu [31.186.226.225]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 997D13A1905 for <netconf@ietf.org>; Mon, 21 Mar 2022 01:59:50 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1647853185; cv=none; d=zohomail.eu; s=zohoarc; b=H6827MULG+r4CFAQamY17pLhZFXvYBOCHRGN6mAPBUoQfAAJB4A6vPI0/JtNivRPvaMnDZlIiUKVNb1xXBHqX2BrrQcDPz6V4lr8QejB1fASO0RQPlaC6tBVpvzTXvrLECG1Q393idPqKsiErIfOC+lK/5DoEpTbm/UwquBOK6w=
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.eu; s=zohoarc; t=1647853185; h=Content-Type:Date:From:MIME-Version:Message-ID:Reply-To:Subject:To; bh=pcVeJr0p4Cas2curXY7q2b08YD6NHIBeKgJ8Lew50/U=; b=XnAI3YnekXA6VEYyZmpz1FU2Dwr2ISh4mtW/HTcrWAgPK1ao81Ml2aBxjJclJlc+a+NbqrQJNWPy1gOotqwL4eq31Zj279TsHfx0OTnSI/F7uLt1AaTeEc0c5aQxwVuz8JXL1uw2g1d8e9LkFSQuK55Wdt1mEFCRfm+pk1JErzs=
ARC-Authentication-Results: i=1; mx.zohomail.eu; dkim=pass header.i=hansfords.net; spf=pass smtp.mailfrom=jonathan@hansfords.net; dmarc=pass header.from=<jonathan@hansfords.net>
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1647853185; s=hansfordsdefault; d=hansfords.net; i=jonathan@hansfords.net; h=From:To:Subject:Date:Message-Id:Reply-To:Mime-Version:Content-Type; bh=pcVeJr0p4Cas2curXY7q2b08YD6NHIBeKgJ8Lew50/U=; b=BUzFG8WYliMTfIO1telWWDD4YcqBveZuj7NdNVbCoagv0MMsELYNg6Z8fVthJenq WoQIZJ18pqXHpyVfwkqM0yN45AYx7TKwkNXUY+ru7TVEng6c5ZYCg3GGI+gmQxvUYZ/ 93a5QiPbp5hgl6docV+XQ3f0T5uwE2bl2o24F4vk=
Received: from [192.168.54.20] (92.41.60.163.threembb.co.uk [92.41.60.163]) by mx.zoho.eu with SMTPS id 1647853184167251.92160544124545; Mon, 21 Mar 2022 09:59:44 +0100 (CET)
From: Jonathan Hansford <jonathan@hansfords.net>
To: netconf@ietf.org
Date: Mon, 21 Mar 2022 08:59:44 +0000
Message-Id: <em6de2e9d8-75b4-4715-b22b-f0c5c4797a78@vanguard>
Reply-To: Jonathan Hansford <jonathan@hansfords.net>
User-Agent: eM_Client/8.2.1659.0
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="------=_MBCA5106D4-F1A4-4BD1-A71A-619056F8B7D7"
X-ZohoMailClient: External
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/p2lfDVoTfbKEsZg4GVVTeJ5eCbE>
Subject: [netconf] RPC request Timeout
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: Mon, 21 Mar 2022 08:59:56 -0000

Hi,

back in 2004, V. Sarma asked (see Pipelining and Timeout queries 
<https://mailarchive.ietf.org/arch/msg/netconf/h_vSQNr9YY2ewAQQHudNJaTCpns/>):

Once the netconf manager sends a rpc request to the managed device, how 
long should it wait for the rpc-reply?

Can the netconf manager time-out after a specified time interval?

I know this is a basic question, but it doesn't appear it was ever 
answered. So, can anyone advise what the typical strategies are:
When the client doesn't receive an rpc-reply (e.g. time interval to 
retry, number of retries, presumably followed by closing the session if 
it is still open)?
When the server receives a duplicate rpc request (e.g. reply based on 
latest config and state)?

Thanks,

Jonathan

v2.23.0 | Report a Bug | By Email