IETF Logo Mail Archive

Re: [Netconf] Does NMDA support synchronous configuration operation?

Kent Watsen <kwatsen@juniper.net> Mon, 25 June 2018 14:47 UTC

Return-Path: <kwatsen@juniper.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 0000B130DF9 for <netconf@ietfa.amsl.com>; Mon, 25 Jun 2018 07:47:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 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_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.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 LkiupmnugqDy for <netconf@ietfa.amsl.com>; Mon, 25 Jun 2018 07:46:58 -0700 (PDT)
Received: from mx0b-00273201.pphosted.com (mx0b-00273201.pphosted.com [67.231.152.164]) (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 40EE4130DEE for <netconf@ietf.org>; Mon, 25 Jun 2018 07:46:58 -0700 (PDT)
Received: from pps.filterd (m0108161.ppops.net [127.0.0.1]) by mx0b-00273201.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w5PEidv1023860; Mon, 25 Jun 2018 07:46:56 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=PPS1017; bh=mHwfAwf039jIp62w0h7HsIZr0wq+rrYzemnzEQrW4ag=; b=vclyG8VsbZbZrpP5lxSJZrjWRbNCk/Fp0m+yxOby5HE3EYfeyYiwvIECqSv/k30egYEC U01VYm1M6GdB19FjoCr2pk7A9+KUfycZbDJPBtk+4yxtBZ7krmHHjWW5NNEcmMXCQcz1 Tz2c5BMm3gBO0UbQM1i2rHMFue+W7lsV46Wc1i3E3ZlPd59RANUP3sVimA9dL7o57cjw aXQweHoCGdATcAOsH/Ti1ohFqrtWdv41IoFBWrGptv8924MA+KiLZyUNAhKNMxYkF0Vm Vc1z1QFxmB1AFUlRZq0fdoNgM783A0tXapgIbzgBoCUZpgfZ3KUi+YUSDF1bEu82QQEs tg==
Received: from nam05-dm3-obe.outbound.protection.outlook.com (mail-dm3nam05lp0116.outbound.protection.outlook.com [216.32.181.116]) by mx0b-00273201.pphosted.com with ESMTP id 2jtq8k0y02-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Mon, 25 Jun 2018 07:46:55 -0700
Received: from BYAPR05MB4230.namprd05.prod.outlook.com (52.135.200.153) by BYAPR05MB4085.namprd05.prod.outlook.com (52.135.199.142) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.884.16; Mon, 25 Jun 2018 14:46:54 +0000
Received: from BYAPR05MB4230.namprd05.prod.outlook.com ([fe80::959d:9fbe:90e4:3cc]) by BYAPR05MB4230.namprd05.prod.outlook.com ([fe80::959d:9fbe:90e4:3cc%4]) with mapi id 15.20.0906.018; Mon, 25 Jun 2018 14:46:54 +0000
From: Kent Watsen <kwatsen@juniper.net>
To: Henry Yu <hyu2010b@gmail.com>, "j.schoenwaelder@jacobs-university.de" <j.schoenwaelder@jacobs-university.de>, "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: [Netconf] Does NMDA support synchronous configuration operation?
Thread-Index: AQHUCmhGfb4kM6A7NUyZddtAHgM4baRs4TCAgAGO1ACAAKY5AIABLC2AgACMbAA=
Date: Mon, 25 Jun 2018 14:46:54 +0000
Message-ID: <A2A3EF88-AA18-4E9B-857A-A0EEA83A163B@juniper.net>
References: <CAFsbzLmF+=x7Uiru8mT_17gGxmPwaLn_k735JMDVyo3OTumZRQ@mail.gmail.com> <20180622224731.dvjo3vzcxkc46ggl@anna.jacobs.jacobs-university.de> <CAFsbzL==MsLiQznaLgjEsPV5D5tBPgpgcdG76riD4Yy_DODHOA@mail.gmail.com> <20180624082954.jboxxqxpuj732vat@anna.jacobs.jacobs-university.de> <CAFsbzLmWQ4me9=bsnJSNM6cKdHdGoh4EWNCxwobwtxbAVhqHRg@mail.gmail.com>
In-Reply-To: <CAFsbzLmWQ4me9=bsnJSNM6cKdHdGoh4EWNCxwobwtxbAVhqHRg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.20.0.170309
x-originating-ip: [66.129.241.10]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BYAPR05MB4085; 7:JHLRXBmNujYUPwIn/n2etVynLs2ZqxnBxAaGwiv8IRmBRRP08Mf4p9optVr5LtjIKHzHEgZhJ3TDecfYgtKrlftnTBi+zKVbNQGhS2Q8/BUhSJwocNz4gP+JXWuhUife4CQ/datZHhUr4KUP4gB2hub4YBvIimkbntSlbm03882J2pKg8kH6yzFIGQt0GkOUjhF80wN9APN3bv9BKfZdli54eF4U8plwRajIiqNFm1SysInweEtm70EfMQ0QjiyE
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 020eb990-4129-4452-e42b-08d5daaa7e70
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(8989117)(4534165)(4627221)(201703031133081)(201702281549075)(8990107)(5600026)(711020)(48565401081)(2017052603328)(7153060)(7193020); SRVR:BYAPR05MB4085;
x-ms-traffictypediagnostic: BYAPR05MB4085:
x-microsoft-antispam-prvs: <BYAPR05MB4085987D35C39D156CD62FD8A54A0@BYAPR05MB4085.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(158342451672863);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(93006095)(93001095)(3231254)(944501410)(52105095)(10201501046)(3002001)(6055026)(149027)(150027)(6041310)(20161123558120)(20161123560045)(20161123562045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123564045)(6072148)(201708071742011)(7699016); SRVR:BYAPR05MB4085; BCL:0; PCL:0; RULEID:; SRVR:BYAPR05MB4085;
x-forefront-prvs: 0714841678
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(346002)(39860400002)(39380400002)(366004)(376002)(189003)(199004)(3280700002)(6436002)(2201001)(36756003)(26005)(2900100001)(2501003)(53936002)(6512007)(82746002)(66066001)(39060400002)(97736004)(86362001)(5250100002)(11346002)(478600001)(68736007)(6246003)(229853002)(14454004)(105586002)(6486002)(106356001)(446003)(81166006)(102836004)(83716003)(3660700001)(2906002)(186003)(6346003)(6506007)(316002)(476003)(486006)(99286004)(25786009)(305945005)(58126008)(5660300001)(110136005)(93886005)(59450400001)(3846002)(7736002)(8936002)(81156014)(2616005)(6116002)(8676002)(33656002)(76176011); DIR:OUT; SFP:1102; SCL:1; SRVR:BYAPR05MB4085; H:BYAPR05MB4230.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-microsoft-antispam-message-info: n+iJPGM4oH7Cwuh913bsvQncCbolnSKgvDDjkOH7ZqE7Wh+HUlPNeBrv1XTPGR1hOmuTpcFEBTk5ekS5+Q6urAWvs8toN1cQEuxPO59H8nLq4sQloEf8vGI667pGbQdU96qTuZVPeqFYwKNfwCzIWcyphvOH9GVCVXFEwRCZHt2kBXzzQ8bgMKWLRkiWNfHB4P3Np7vrUJSLsXqdqdn2bTr0q6NXWPOctoPK4QFfEUKWS/ea8JXZS9Emoh5Ufv6lqhH+yaPQIN8EQhQif09MPgxHYmPjHLyakbc/zWAco/JkDwxgoxPoOPlEPIygoAdQO/+2gmYsroLMeFCy1yU6kA==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <140BD171A921E94A9333A9C6BFAB4EBD@namprd05.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: 020eb990-4129-4452-e42b-08d5daaa7e70
X-MS-Exchange-CrossTenant-originalarrivaltime: 25 Jun 2018 14:46:54.2895 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR05MB4085
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-06-25_07:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1806210000 definitions=main-1806250172
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/dcO5KSetu-p9pwFxXgYkwHR1ONA>
Subject: Re: [Netconf] Does NMDA support synchronous configuration operation?
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, 25 Jun 2018 14:47:02 -0000

Hi Henry,

> In contrast, the definition of Synchronous Configuration Operation in
> [draft-ietf-netmod-opstate-reqs-04] states that "the server MUST fully
> attempt to apply the configuration change to all impacted components
> in the server, updating both the server's intended and applied
> configuration, before replying to the client. The reply to the client
> indicates whether there are any errors in the request or errors from
> applying the configuration change."

It is accurate that both nmda-netconf and nmda-restconf drafts do not
yet implement this "requirement" (in quotes since the opstate-reqs
draft was never published as an RFC).

Kent

v2.34.0 | Report a Bug | By Email | System Status