IETF Logo Mail Archive

Re: [Netconf] closure on dynamic model changes

Kent Watsen <kwatsen@juniper.net> Sat, 14 July 2018 20:27 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 AF7C0130E41 for <netconf@ietfa.amsl.com>; Sat, 14 Jul 2018 13:27:44 -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 AmfiJS02m6jv for <netconf@ietfa.amsl.com>; Sat, 14 Jul 2018 13:27:43 -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 013EA12F1A5 for <netconf@ietf.org>; Sat, 14 Jul 2018 13:27:42 -0700 (PDT)
Received: from pps.filterd (m0108160.ppops.net [127.0.0.1]) by mx0b-00273201.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w6EKRTM0028467; Sat, 14 Jul 2018 13:27:39 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-transfer-encoding : mime-version; s=PPS1017; bh=199fNxhtcEg2HuucmTLP8XcG7GVwEHf6ywYqUhO6R6o=; b=tG+F1LzRDHLyXt3cS4b5SSIj9swD0fF4YNse2WbfmasgMkWkl83DMNFBbndHbFYQk4LT bPQ5QYxOQLFCALXNIq68aLCb2+tIgZFNSqfT3eTARckL7xUoDrXGQJ3P9xJZ4SsMq4x4 ebMWijGsggDeMZFwkN0MxuTbfroGWCIhORWqxlFSlRnJRu7Y1KpV455DcvRenVryxNMO u5piPOUBZGnlj5d4vGC5iwAAVnIeVw87nKEgdruFkhS3rL+T3zeFsQat4qBBzK5/vpvB FZCRvU8M9MH6gmH2DhsCzLLnJOisf8ntLf2XzYVqFbv6nMsQbBkqOXIqk3AkXnONKDFh Bg==
Received: from nam01-sn1-obe.outbound.protection.outlook.com (mail-sn1nam01lp0112.outbound.protection.outlook.com [207.46.163.112]) by mx0b-00273201.pphosted.com with ESMTP id 2k7f3e8kvv-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Sat, 14 Jul 2018 13:27:39 -0700
Received: from BYAPR05MB4230.namprd05.prod.outlook.com (52.135.200.153) by BYAPR05MB4021.namprd05.prod.outlook.com (52.135.199.21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.952.14; Sat, 14 Jul 2018 20:27:36 +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.0952.017; Sat, 14 Jul 2018 20:27:36 +0000
From: Kent Watsen <kwatsen@juniper.net>
To: Ariel Otilibili Anieli <otilibil@eurecom.fr>
CC: "Jeffrey Ladouceur (jladouce)" <jladouce@cisco.com>, "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: [Netconf] closure on dynamic model changes
Thread-Index: AQHUGWDbLPbtZBdqVkidwW9feognvaSKkboA///JhQCAAV/DgIADdHA9
Date: Sat, 14 Jul 2018 20:27:36 +0000
Message-ID: <074B7635-6FB9-4D1F-9A1C-D2BE1390D872@juniper.net>
References: <17CA1DAB-73FF-498D-8EA6-5BD090B9F01E@juniper.net> <72E30569-5546-4165-B6EA-A424FB0B3C28@cisco.com> <9DA54FC9-E51F-4CF4-95CD-87BE581CA458@juniper.net>, <20180712174205.dzpjndq9gkwc8080@webmail.eurecom.fr>
In-Reply-To: <20180712174205.dzpjndq9gkwc8080@webmail.eurecom.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [2001:67c:1232:144:81fe:1441:42cd:5653]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BYAPR05MB4021; 7:dfC7P2z33HsB4f4qcQw+cHCMUU+TxhXy8+HdZ0dk+9fZeE36QL/lWwN00MrG0zPfQxTFS9SXJq8l0/A9WVGrWyUJGP0JycBrflMfKQ4vUXsu2NNma/9Fmdcv4wnMCPIiB/SLtQ0tpFjrmVN7IMzFhijVa4BdSpm2o8C825VU93YlUQiAnaQkrtYfDrTTZRo01uRvO3bhcfG7Wva4HxLGI5H4hOU4QBWTuJkX0mU4cytoPD2uUSGxhJoCt9hGy7Y0
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: e1464134-9e8f-42f1-603d-08d5e9c83cda
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989117)(5600053)(711020)(4534165)(4627221)(201703031133081)(201702281549075)(8990107)(48565401081)(2017052603328)(7153060)(7193020); SRVR:BYAPR05MB4021;
x-ms-traffictypediagnostic: BYAPR05MB4021:
x-microsoft-antispam-prvs: <BYAPR05MB402116F240804DD4439762A9A55F0@BYAPR05MB4021.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(3231311)(944501410)(52105095)(10201501046)(3002001)(93006095)(93001095)(6055026)(149027)(150027)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123562045)(20161123558120)(20161123564045)(6072148)(201708071742011)(7699016); SRVR:BYAPR05MB4021; BCL:0; PCL:0; RULEID:; SRVR:BYAPR05MB4021;
x-forefront-prvs: 07334CBCCD
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(136003)(39860400002)(396003)(346002)(376002)(366004)(199004)(189003)(93886005)(6116002)(6506007)(83716003)(2900100001)(106356001)(105586002)(14454004)(446003)(99286004)(102836004)(81156014)(81166006)(8936002)(86362001)(11346002)(305945005)(8676002)(46003)(6916009)(476003)(2616005)(14444005)(256004)(186003)(7736002)(76176011)(486006)(5660300001)(33656002)(53936002)(6246003)(54906003)(316002)(68736007)(5250100002)(229853002)(6436002)(6486002)(6512007)(25786009)(478600001)(36756003)(2906002)(97736004)(4326008)(82746002); DIR:OUT; SFP:1102; SCL:1; SRVR:BYAPR05MB4021; H:BYAPR05MB4230.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-microsoft-antispam-message-info: GHYii22GzrJKzvqx8Ieo89sHNBZpH0LogyRjkJFXfcif5rCtNmgPkevt4vfVBt+k5jc4u//OOwKexBR6ckXURgSRtPmKN4P4cE6Q4SdcXLcOeVfC04+nRBldEdVtF9xEDdVBLKb/wPRKLcZGpu7apr5FmgMURF4/0GUQmVn8Beu18pGV58x9c9NSXe1tszwZbTo+Mvh+XpUrgsfPfBW6jrqC1ENQWt+cyktCxvGJhElqHq7LUH/+zYWiSmXgCN0JgGCoXAlFzNgmpUJ95ecH1qJ0Ubc5GKAQEq610gcCj+AF8bLtGUhLFK2A5DiX4pdtU9WHSJnFE+i+X0zzWlg0xAZLEPgOVWskUtAS1HF3q6M=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: e1464134-9e8f-42f1-603d-08d5e9c83cda
X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Jul 2018 20:27:36.4527 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR05MB4021
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-07-14_05:, , 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=655 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1806210000 definitions=main-1807140247
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/ATKIc-RHK9vbjH7a_qsB0GQjAf8>
Subject: Re: [Netconf] closure on dynamic model changes
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: Sat, 14 Jul 2018 20:27:45 -0000

> If errors occur in the case you described, Kent, I would expect the base NETCONF protocol to raise them.

I don’t believe capabilities changing is an error.  The NC/RC protocols do “raise” the event, in the form of a notification.  This seems better than waiting for the client to send an RPC. Agreed?

Kent

v2.23.0 | Report a Bug | By Email