IETF Logo Mail Archive

[Netconf] 4741bis: issue 13, confirmed-commit (new capability)

Andy Bierman <andy@netconfcentral.com> Tue, 08 December 2009 22:10 UTC

Return-Path: <andy@netconfcentral.com>
X-Original-To: netconf@core3.amsl.com
Delivered-To: netconf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 35C333A6831 for <netconf@core3.amsl.com>; Tue, 8 Dec 2009 14:10:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.136
X-Spam-Level:
X-Spam-Status: No, score=-2.136 tagged_above=-999 required=5 tests=[AWL=0.128, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8ZNay0fegVQN for <netconf@core3.amsl.com>; Tue, 8 Dec 2009 14:10:52 -0800 (PST)
Received: from smtp127.sbc.mail.sp1.yahoo.com (smtp127.sbc.mail.sp1.yahoo.com [69.147.65.186]) by core3.amsl.com (Postfix) with SMTP id 14EA83A67C0 for <netconf@ietf.org>; Tue, 8 Dec 2009 14:10:52 -0800 (PST)
Received: (qmail 21098 invoked from network); 8 Dec 2009 22:10:39 -0000
Received: from adsl-67-125-158-117.dsl.irvnca.pacbell.net (andy@67.125.158.117 with plain) by smtp127.sbc.mail.sp1.yahoo.com with SMTP; 08 Dec 2009 14:10:39 -0800 PST
X-Yahoo-SMTP: Z6xhxCCswBAlhcxjVNwaQtp4EKpLdTUUf5Nx_pGy81o-
X-YMail-OSG: KT9ME4MVM1lleFidb6XXwDj4v4QOLrzBLWElvz2UdOW1d6tNYRTtckWtwkIwL4CVYAqWeKjxWp8jR313cCb9o1zecDOYH61vY887ffHZ0DIqmVRpKfY8BlwptUt3JN2VlfzH5VnGkusiXe7C7xwaKUpxcDJS4oPjJUeSAwa0SDCFgcbCNRc9WWtgY6JgiTvHxRdVPnuYQ1t2eGd0k.WZMbQFDCJAsY4ui0OrwKZCPlrD4XhiVa2d5y9ABvMwU70W
X-Yahoo-Newman-Property: ymail-3
Message-ID: <4B1ECEC7.5080604@netconfcentral.com>
Date: Tue, 08 Dec 2009 14:10:15 -0800
From: Andy Bierman <andy@netconfcentral.com>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: NETCONF <netconf@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Subject: [Netconf] 4741bis: issue 13, confirmed-commit (new capability)
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Network Configuration WG mailing list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 08 Dec 2009 22:10:53 -0000

Hi,

First there was the Robust Configuration draft, which proposed
a verified-commit procedure.  Then there was some consensus
towards decoupling the verify and commit procedures.  Then there
was a suggestion to improve the commit procedure with a new
capability.  Old clients would still work because there would
be 1 or more new parameters that must be present to select the
new behavior.  The new confirmed-commit-1.1
capability would add a <persist> parameter to the
<commit> operation.

There are no proposed edits at this time.
The WG needs to decide on a basic solution approach first:

  A) add a new capability which changes the commit procedure
     to allow the original server to terminate without
     canceling the confirmed commit;  detailed proposal
     from Martin is still needed, and WG consensus on
     all the details is needed

 B) start a new draft for this work (now or later), instead of starting
    this new work now as part of the 4741bis 'cleanup' charter

 C) do nothing; do not change the commit procedure


Andy

v2.23.0 | Report a Bug | By Email