IETF Logo Mail Archive

Re: [netconf] Clarification on NETCONF edit-config default-operation replace

"Sterne, Jason (Nokia - CA/Ottawa)" <jason.sterne@nokia.com> Mon, 09 March 2020 13:20 UTC

Return-Path: <jason.sterne@nokia.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 CED9B3A0FDC for <netconf@ietfa.amsl.com>; Mon, 9 Mar 2020 06:20:03 -0700 (PDT)
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, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nokia.onmicrosoft.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 3fKk_l3OxKTM for <netconf@ietfa.amsl.com>; Mon, 9 Mar 2020 06:20:02 -0700 (PDT)
Received: from NAM12-BN8-obe.outbound.protection.outlook.com (mail-bn8nam12on2122.outbound.protection.outlook.com [40.107.237.122]) (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 B50923A0FF4 for <netconf@ietf.org>; Mon, 9 Mar 2020 06:20:01 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=TfXUd7LMjoGx/zUP6iG919rbSko1k+mWE2KnOuW0uO3BK/a8W5fe+rxVgzctD+mQJbHjouTIZ58FzHq/CVvmPCDwGvc+zooyxbBATz7LiM0jOicYVEFnlSPcTiaFopUsy+UDi715nV/y5YOu/XYa+ELJZneX9vwdrcATWbTz+A/19NyvGYkcCEw6HEmiwWkg9PKb8DplzlPcxWIYJ77eWJI5T2t4MlxHKZ8+hiG/BJnbOMqczy4mGG9bqc+jE0mALse61avnuGnD6VqDnMzvpACaQh3Sls4OfBlkt2mbqTsUwALMmdGsqFKMpjgHQgHvdidCDLVAl8QmyEA9Q7L2oA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;bh=x3H5L0DzlnEW9RAVDyyR3VWi8bYQz+sSgscndp+v/n4=; b=RlJFb1G5/YzijeQc7uTLD3ti+8ZQ3fOMDtQemvIVgZH3vOuwBkmj00kcdQIO5Z88dH5daL8MwBwWOvzIIVOJyoDaFjWMI1tExTtK03NNPYGTAmte8dkKZ36DkiYgfs4dydj4GmrGg9yt5A97M3ZmFOiV0BbqakiKpFP2Utwj+h0VoehMQ2ckElB0OO8USyBLIlHCe9uelRt3928XH8CGcM2rj2Vgi/UFJ2YA5c8RZWDwMU5Ph6xNHBWd6QHGyASHHNcpcrYfMqxcQOV0B16NtTX1OoFnUht75pBtmvQcAeGB50/NjoUNRA8IX+SotFdLVfuA9noIc2vEfib/9Gmm8A==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=nokia.com; dmarc=pass action=none header.from=nokia.com; dkim=pass header.d=nokia.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nokia.onmicrosoft.com; s=selector1-nokia-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=x3H5L0DzlnEW9RAVDyyR3VWi8bYQz+sSgscndp+v/n4=; b=ATnGlEf2XXhU8S/jth8e/6flEUsg0E+MXAJ7TKtO5L9f7QmH35mIr9zkTofdgN73qxwHx4HK4UgPs0ygFpTfty82e7HXQ3ZHOGuBB4YQT6zzSMXA3pJWiO/n0/3q9rNKQ+uVRVGk93/wqJLSreK66UzgiQJgA9ZBxJPejKfqX8o=
Received: from DM5PR08MB2633.namprd08.prod.outlook.com (2603:10b6:3:ca::21) by DM5PR08MB2761.namprd08.prod.outlook.com (2603:10b6:3:14f::9) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2793.17; Mon, 9 Mar 2020 13:19:57 +0000
Received: from DM5PR08MB2633.namprd08.prod.outlook.com ([fe80::455:66cb:efa2:fabb]) by DM5PR08MB2633.namprd08.prod.outlook.com ([fe80::455:66cb:efa2:fabb%9]) with mapi id 15.20.2793.013; Mon, 9 Mar 2020 13:19:48 +0000
From: "Sterne, Jason (Nokia - CA/Ottawa)" <jason.sterne@nokia.com>
To: "Ivory, William" <william.ivory@intl.att.com>, "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: Clarification on NETCONF edit-config default-operation replace
Thread-Index: AQHV8up3fXrFXOpHlkeLycpqDm3qRahAQ71g
Date: Mon, 09 Mar 2020 13:19:48 +0000
Message-ID: <DM5PR08MB2633A0708C35C95BBB73B9029BFE0@DM5PR08MB2633.namprd08.prod.outlook.com>
References: <b586413eb1a939e144191c07ea8267843ac092bd.camel@intl.att.com>
In-Reply-To: <b586413eb1a939e144191c07ea8267843ac092bd.camel@intl.att.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=jason.sterne@nokia.com;
x-originating-ip: [65.110.215.75]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: a5660a75-717f-4291-5be8-08d7c42c8b36
x-ms-traffictypediagnostic: DM5PR08MB2761:
x-microsoft-antispam-prvs: <DM5PR08MB2761846CD2B0A3F90F19DF619BFE0@DM5PR08MB2761.namprd08.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0337AFFE9A
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(136003)(366004)(346002)(396003)(39850400004)(376002)(199004)(189003)(186003)(55016002)(9326002)(52536014)(110136005)(26005)(8936002)(81166006)(81156014)(5660300002)(316002)(33656002)(66946007)(2906002)(8676002)(66476007)(66556008)(64756008)(76116006)(66446008)(9686003)(478600001)(7696005)(71200400001)(6506007)(53546011)(86362001); DIR:OUT; SFP:1102; SCL:1; SRVR:DM5PR08MB2761; H:DM5PR08MB2633.namprd08.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: nokia.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: zCqBfvaCgfnO/80jcJRQ5/rQjY7gsDaTCu12ouoWrf1JL0h1XSomVnaXLoWrWvuaGyJEbPd+6QfeAoYcmL6IzXGdbdY3RQkuy2kPGvZsxlBQZ8SnvZWk1Ys5v4kt9G1rBrEpcf78j4HZ0cgzY4TZEcVY/Scr2nR/8x9+di9b669bNZc0i+5brDdZ10WD26Jd+yjUbhdu9JDe6ufTG9Ei3HqXv4Yh+QPOT6YAWiXwB/Iy8S9ZDh74awf0uEwLUsAllqijxZWzyCvxyOE2jzcajNnYWiZ1ZFyr0t32CgvxJUkrHxo/OjrFJrmlthAqQCH1BPpl3NNhLGrpltn+9pWamsTABD0w4AfCLNZSBBhm2tilcvFXsO2XwqCOmyLlY6ksj0nvIP2PBMxmDyCs0mXLEgPmxBFSTg7UfvvmqtILmZ1ZL5UkwulzW8iK+kObTdK9
x-ms-exchange-antispam-messagedata: GYkah5bcFT7ErLmyNXZiODkTvZfBvgT4OUdGOg9IUbg5lKnA2699PdxtNC3W17eLsj5r3/guy4qBBbn6PIihSSPjLvhatyJ/enb7U9VRMiqs5BExYVBQOf9zq9R3qHVq7WwoWTHNJ3NgLhpn8WqXGg==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_DM5PR08MB2633A0708C35C95BBB73B9029BFE0DM5PR08MB2633namp_"
MIME-Version: 1.0
X-OriginatorOrg: nokia.com
X-MS-Exchange-CrossTenant-Network-Message-Id: a5660a75-717f-4291-5be8-08d7c42c8b36
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Mar 2020 13:19:48.8695 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: jlrLcsA4vBeZpiLbFkOYv0tV4XztjPgoBIt1KPcLbNqoN1KFD8jfb5F5Ld/J3bucXckXSpvCq5JIlCoR+8WjfQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR08MB2761
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/UBzfnx11bJbF9p6ELE7a-a-4sqk>
Subject: Re: [netconf] Clarification on NETCONF edit-config default-operation replace
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, 09 Mar 2020 13:20:13 -0000

Hello William,

There was a discussion about this on the list a few years ago.  See the thread with subject:

Clarification request for NETCONF edit-config default-operation replace

An edit-config can't be used as a replacement for a full "replace at root" of the entire config like a copy-config.

Jason

From: netconf <netconf-bounces@ietf.org> On Behalf Of Ivory, William
Sent: Thursday, March 5, 2020 7:35 AM
To: netconf@ietf.org
Subject: [netconf] Clarification on NETCONF edit-config default-operation replace

Hi,

I'd appreciate clarification on the following NETCONF operations relating to copy-config and edit-config:

My understanding is as follows:

- <copy-config> completely replaces any existing configuration

- <edit-config> with operation:replace attribute will replace any existing configuration with new configuration for nodes specified inside the <config> operation. The attribute may be at any level in the request, and applies only to the node specified and nodes under that node.

Where I'm not clear is the <edit-config> operation with the default-operation parameter set to replace. RFC 6241 section 7.2 states:


         replace:  The configuration data in the <config> parameter

            completely replaces the configuration in the target

            datastore.  This is useful for loading previously saved

            configuration data.


Does this mean that this is the equivalent of the <copy-config> operation, ie ALL existing configuration should be removed, even if there is no explicit replacement in the new <config> section?

Thanks,

William

v2.23.0 | Report a Bug | By Email