IETF Logo Mail Archive

Re: [Netconf] Solicit comments on inline action capability for NETCONF

Robert Wilton <rwilton@cisco.com> Tue, 17 July 2018 14:12 UTC

Return-Path: <rwilton@cisco.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 D740812F1A6 for <netconf@ietfa.amsl.com>; Tue, 17 Jul 2018 07:12:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 a4QWO92ThrTp for <netconf@ietfa.amsl.com>; Tue, 17 Jul 2018 07:12:52 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 40D1C130E1B for <netconf@ietf.org>; Tue, 17 Jul 2018 07:12:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1191; q=dns/txt; s=iport; t=1531836772; x=1533046372; h=subject:to:references:from:message-id:date:mime-version: in-reply-to:content-transfer-encoding; bh=Por5Wiub8th5fYh9CfA2QCaxHalBTAAa1sa2k0M2p1M=; b=H5Ilg+5kcpeEDcxPgbYTrea2zTKKSleJR31nRXRknSWETF9sDECVg6p2 ATnXKQwUwWuF7yjFpIJxgU7ZfkDaSOnlKIXzhvv9oLsl2D7siafCsbCEc 0przkBXUq93wR+UBXlB/9WAWmmOA01Mp4jHyfm6HT3b/ifdpbNRiTkuTf s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0B5AQDw901b/xbLJq1cGQEBAQEBAQEBAQEBAQcBAQEBAYUZEoQliGONPQgklzMLhGwCgxE3FQECAQECAQECbSiFNgEBAQMBIw8BBUYLCxgCAiYCAlcGAQwIAQEXgwWBeAiqaYEuhFuFaoELiU4/gTgMgjAuh3yCVQKZXAmPIQaBQ4QRgkglhSSMP4VVgVcigVIzGggbFYMlkG4jjXABAQ
X-IronPort-AV: E=Sophos;i="5.51,365,1526342400"; d="scan'208";a="5229599"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 17 Jul 2018 14:12:50 +0000
Received: from [10.61.227.226] ([10.61.227.226]) by aer-core-3.cisco.com (8.15.2/8.15.2) with ESMTP id w6HECmBm014705; Tue, 17 Jul 2018 14:12:49 GMT
To: Robert Wilton <rwilton=40cisco.com@dmarc.ietf.org>, Qin Wu <bill.wu@huawei.com>, "netconf@ietf.org" <netconf@ietf.org>
References: <B8F9A780D330094D99AF023C5877DABA9AEC24AC@nkgeml513-mbx.china.huawei.com> <b8fbfc3a-ff80-df51-60d4-c97458b3d1af@cisco.com> <20180717132528.xotht5ydvhjfwvdn@anna.jacobs.jacobs-university.de>
From: Robert Wilton <rwilton@cisco.com>
Message-ID: <eadb522e-f128-3117-0882-c2e7e01f212e@cisco.com>
Date: Tue, 17 Jul 2018 10:12:48 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <20180717132528.xotht5ydvhjfwvdn@anna.jacobs.jacobs-university.de>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/IVgp2zZ4PYv_hin4UsQ15UQPjQw>
Subject: Re: [Netconf] Solicit comments on inline action capability for NETCONF
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.27
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: Tue, 17 Jul 2018 14:12:55 -0000


On 17/07/2018 09:25, Juergen Schoenwaelder wrote:
> On Tue, Jul 17, 2018 at 08:08:47AM -0400, Robert Wilton wrote:
>> Hi Qin,
>>
>> Having read this draft, I can understand what the draft is proposing, but I
>> don't currently understand why this is useful. Specifically, I don't find
>> the example that is in the draft as compelling.  If the desire is to set the
>> MTU and enable the interface as one configuration operation, then wouldn't
>> the client just configure both mtu and enabled leaves at the same time.  Why
>> is a separate action required here to enable the interface?
>>
> I have asked myself the same question multiple times. ;-)
>
> If people want engineer transactions consisting of multiple
> operations, then they should do this for combinations of _arbitrary_
> operations. At the end, edit-config is just an operation like
> edit-data or any other operation.
I agree.

> Personally, I do not think heavy weight transactions is the way to go
> but if people want to engineer this, please make the solution at least
> generic and not bound to edit-config or something like that.
I also agree to both points.

Thanks,
Rob

>
> /js
>

v2.23.0 | Report a Bug | By Email