Triggers and Handles Framework
draft-pham-triggers-and-handles-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Hien Pham , Dominique Chantrain , Claudune Batsleer | ||
| Last updated | 2001-11-26 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document describes a communication mechanism named 'triggers and handles' between service logic and network elements. The concept defines a trigger as a notification that a network element sends to the service logic. A handle is defined as a command that the service logic sends to a network element. Triggers are bound to network events and allow network elements to notify service logic of occurring events in the network whereas handles allow taking control of network elements.
Authors
Hien Pham
Dominique Chantrain
Claudune Batsleer
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)