[netmod] ECA model draft: Exception handling

Qin Wu <bill.wu@huawei.com> Tue, 03 November 2020 15:38 UTC

Return-Path: <bill.wu@huawei.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CEDF3A0C9D for <netmod@ietfa.amsl.com>; Tue, 3 Nov 2020 07:38:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 hgiLix3DRsL0 for <netmod@ietfa.amsl.com>; Tue, 3 Nov 2020 07:38:20 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 D3E323A0AA6 for <netmod@ietf.org>; Tue, 3 Nov 2020 07:38:19 -0800 (PST)
Received: from lhreml743-chm.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 9A783F7C39C5E9638F2D for <netmod@ietf.org>; Tue, 3 Nov 2020 15:38:15 +0000 (GMT)
Received: from lhreml743-chm.china.huawei.com (10.201.108.193) by lhreml743-chm.china.huawei.com (10.201.108.193) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Tue, 3 Nov 2020 15:38:15 +0000
Received: from DGGEML402-HUB.china.huawei.com (10.3.17.38) by lhreml743-chm.china.huawei.com (10.201.108.193) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.1913.5 via Frontend Transport; Tue, 3 Nov 2020 15:38:15 +0000
Received: from DGGEML511-MBS.china.huawei.com ([169.254.4.33]) by DGGEML402-HUB.china.huawei.com ([fe80::fca6:7568:4ee3:c776%31]) with mapi id 14.03.0487.000; Tue, 3 Nov 2020 23:38:10 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: ECA model draft: Exception handling
Thread-Index: Adax9wpw3XwU2/BtQLCw1a9Br5Bhsg==
Date: Tue, 3 Nov 2020 15:38:09 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABAADB1FC13@dggeml511-mbs.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.48.26.199]
Content-Type: multipart/alternative; boundary="_000_B8F9A780D330094D99AF023C5877DABAADB1FC13dggeml511mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/jGazTmEODjcdRiH9kWGeFr0OUWo>
Subject: [netmod] ECA model draft: Exception handling
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Nov 2020 15:38:21 -0000

*        Not all errors can be detected at configuration time. Error that occur while ECA logic is being evaluated will cause the server to generate an eca-exception notification.
-      Q1:Does an exception cause the ECA entry to be disabled automatically?
-      Q2: What else exceptions and details parameters need to be defined?
*        Proposal to Q1:
-      In case of one time ECA, it will generate exception notification, stop executing other actions associated with the same event, exit ECA execution process
-      In case of periodical ECA execution, it will generate exception notification, stop executing other action associated with the same event, exit ECA execution process in the current period, move to the next period, if the same exception is generated, the ECA entry will be disabled, send another exception notification;

*        Proposal to Q2:

-      The action can be executed in the form of RPC function or function call, therefore function invoke error, rpc invoke error should be defined, in addition, we may allow bind policy variable with xpath expression, variable binding unknown should be defined to cover exception case. When ECA entry can be disabled, the corresponding notification can be generated, we can call it eca entry disable exception.