OPES Architecture for Rule Processing and Service Execution
draft-yang-opes-rule-processing-service-execution-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Lily Yang , Markus Hofmann | ||
| Last updated | 2001-02-27 | ||
| 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 specific architectural components of the Open Pluggable Edge Service (OPES) framework [1]. It defines the functionality of the OPES Administration Server and the OPES Service Engine and discusses the interaction with other OPES components. In particular, the document defines the operational flow for downloading rules and proxylets and the content flow for handling web requests and responses. A list of protocols and interfaces to be specified within the OPES framework is derived from the discussion.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)