IRML: A Rule Specification Language for Intermediary Services
draft-beck-opes-irml-03
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Andre Beck , Markus Hofmann | ||
| Last updated | 2003-06-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
The Intermediary Rule Markup Language (IRML) is an XML-based language that can be used to specify rules for the execution of Web services in general and OPES content services in particular. OPES services are a new class of applications running on network intermediaries, such as caches, proxies, gateways, etc. or dedicated (callout) servers. They are invoked through intermediaries acting on behalf of application endpoints. IRML is designed to serve as a simple and efficient, but yet powerful language to express the service execution policies of application endpoints. IRML rules are typically processed by intermediaries that trigger the execution of OPES services according to these rules and policies.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)