Framework for Use of ECA (Event Condition Action) in Network Self Management
draft-bwd-netmod-eca-framework-00
|
Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2019-11-03
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
pdf
htmlized
bibtex
|
Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
NETMOD Working Group M. Boucadair
Internet-Draft Orange
Intended status: Standards Track Q. Wu
Expires: May 6, 2020 Z. Wang
Huawei
D. King
Lancaster University
C. Xie
China Telecom
November 3, 2019
Framework for Use of ECA (Event Condition Action) in Network Self
Management
draft-bwd-netmod-eca-framework-00
Abstract
Event-driven management is meant to provide a useful method to
monitor state change of managed objects and resources, and facilitate
automatic triggering of a response to events, based on an established
set of rules. This would provide rapid autonomic responses to
specific conditions, enabling self-management behaviors, including:
self-configuration, self-healing, self-optimization, and self-
protection.
This document provides a framework that describes the architecture
for supporting event-driven management of managed object state across
devices. It does not describe specific protocols or protocol
extensions needed to realize the objectives and capabilities
discussed in the document.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 6, 2020.
Boucadair, et al. Expires May 6, 2020 [Page 1]
Internet-Draft ECA Framework November 2019
Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4
2. Problem Statement . . . . . . . . . . . . . . . . . . . . . . 4
2.1. Defining Network Event and Network Control Logic . . . . 4
2.2. Delegating Network Control Logic to Network Device . . . 4
2.3. Executing ECA Script in the Network Device . . . . . . . 5
2.4. Event-Driven Notification Handling . . . . . . . . . . . 6
2.5. Requisite State Information . . . . . . . . . . . . . . . 6
3. Architectural Concepts . . . . . . . . . . . . . . . . . . . 7
3.1. What is Defined in ECA Policy? . . . . . . . . . . . . . 7
3.2. Where is ECA Script and State Held? . . . . . . . . . . . 8
3.3. What State is Held? . . . . . . . . . . . . . . . . . . . 9
4. Architecture Overview . . . . . . . . . . . . . . . . . . . . 9
4.1. Telemetry Automation in the Network Device . . . . . . . 10
4.2. Detecting and Resolving Policy Conflict . . . . . . . . . 12
4.3. Chain Reaction of Coordinated Events . . . . . . . . . . 12
5. Security Considerations . . . . . . . . . . . . . . . . . . . 12
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 13
7.1. Normative References . . . . . . . . . . . . . . . . . . 13
7.2. Informative References . . . . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15
1. Introduction
Network management data objects can often take two different values:
the value configured by the administrator or an application
(configuration) and the value that the device is actually using
Show full document text