[Netconf] RFC6241 - Confirmed Commit Capability, <close-session> and <kill-session>

"Jonathan Hansford" <jonathan@hansfords.net> Mon, 18 June 2018 15:33 UTC

Return-Path: <jonathan@hansfords.net>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id B6FA0130E0E for <netconf@ietfa.amsl.com>; Mon, 18 Jun 2018 08:33:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.722
X-Spam-Status: No, score=0.722 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_REMOTE_IMAGE=0.01, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hansfords.net
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id sM2UZqDMZbfQ for <netconf@ietfa.amsl.com>; Mon, 18 Jun 2018 08:33:02 -0700 (PDT)
Received: from server.myfast.site (server.myfast.site []) (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 B8AEC130E2D for <netconf@ietf.org>; Mon, 18 Jun 2018 08:32:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=hansfords.net; s=default; h=Content-Type:Mime-Version:Reply-To:Message-Id: Date:Subject:To:From:Sender:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=BjxF1F1DHiL74RpPy9zNXyPm7iNB0lFt47LNEDx+PDo=; b=njKRH3jnbn9tLiNUmt2tbqiUzr zpxSVq16w5vGBirU6d6PxwNdkPtvNJDIVlLW3rjZHmZBBMg4lixsGPxXADwNTx716pnGamlQwJZ7F FtOmIfC5MZ+KdFURtonrBaFT9XE53NhxBi36w7nztHi+nY5Bh+bKY7OeKtFB/CgpGUyMX02eqI6Jh 3d7z0VumoTQ2n0ykZAW6FlfPOlR1EC+4phCSc1xXy081/Lem6nVFXZtgrIK4yMOLQChtwp2kzI+pi W6OpMpLRroVzjXcUc20pYqO6sctvnczExj5OZLyXpenAn5Th/wqkZkbIde2oizd0NU4PtWX0CsnOF A1YCXKxw==;
Received: from host-87-242-131-102.static.onetel.net.uk ([]:8552 helo=[]) by server.myfast.site with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91) (envelope-from <jonathan@hansfords.net>) id 1fUw97-001jME-QI for netconf@ietf.org; Mon, 18 Jun 2018 16:32:45 +0100
From: "Jonathan Hansford" <jonathan@hansfords.net>
To: netconf@ietf.org
Date: Mon, 18 Jun 2018 15:32:45 +0000
Message-Id: <em915805dc-94c3-4955-8d85-f8931cd4d69b@morpheus>
Reply-To: "Jonathan Hansford" <jonathan@hansfords.net>
User-Agent: eM_Client/7.1.32088.0
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="------=_MB18C3BF16-23D7-4978-BEE8-3B3C540AC020"
X-Antivirus: Avast (VPS 180618-2, 18/06/2018), Outbound message
X-Antivirus-Status: Clean
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server.myfast.site
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - hansfords.net
X-Get-Message-Sender-Via: server.myfast.site: authenticated_id: jonathan@hansfords.net
X-Authenticated-Sender: server.myfast.site: jonathan@hansfords.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/MQwF5lrm9rqvKrPlho8bN7S14uc>
Subject: [Netconf] RFC6241 - Confirmed Commit Capability, <close-session> and <kill-session>
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Network Configuration WG mailing 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, 18 Jun 2018 15:33:16 -0000


RFC6241, Section 7.9 <kill-session> states "If a NETCONF server receives 
a <kill-session> request while processing a confirmed commit (Section 
8.4), it MUST restore the configuration to its state before the 
confirmed commit was issued."

Is it correct to assume that only applies if the session being killed is 
the one for which a confirmed commit is being processed?

Section 8.4.1 states "If the session issuing the confirmed commit is 
terminated for any reason before the confirm timeout expires, the server 
MUST restore the configuration to its state before the confirmed commit 
was issued, unless the confirmed commit also included a <persist> 

Is it correct to assume if a <kill-session> is received for a session 
for which the confirmed commit included a <persist> element, the 
behaviour is still to restore the configuration to its state before the 
confirmed commit was issued since the client owning the session is no 
longer in control and the session is having to be killed using a 
different client?

Section 7.8 <close-session> makes no mention of confirmed commits.

Is it correct to assume the client would be expected to cancel a 
confirmed commit before closing its session unless the client wished to 
continue on a new session (e.g. after a device reboot) in which case the 
confirmed commit would have included a <persist> element?



This email has been checked for viruses by Avast antivirus software.