[Top] [All Lists]

Charter, last call

2001-03-20 09:52:54

Open Pluggable Edge Services(opes)

   Michael Condry <condry(_at_)intel(_dot_)com>
   Hilarie Orman <HORMAN(_at_)novell(_dot_)com>

Mailing Lists:
   General Discussion: ietf-openproxy(_at_)imc(_dot_)org
   To Subscribe: ietf-openproxy-request(_at_)imc(_dot_)org

Description of Working Group:

The Open Pluggable Edge Service (OPES) working group primary task is to define a protocol to be used to extend participating transit intermediaries to incorporate services executed on application data transported by HTTP and possibly RTP, RTSP. The protocol provides a framework for integrating a wide range of services into arbitrary intermediaries. Intermediaries may employ either local or remote ("callout") servers to perform a service, and as a result, the data may be diverted temporarily over a closed loop pathway different from the transit pathway.

Intermediary services provided in this way are not transparent: Either the content requestor or provider will be aware that a transformation has been performed.

As part of the development of this protocol the working group will produce an analysis of the security implications of this architecture.

A secondary task for this working group is to enumerate the requirements for management policies and associated administrative protocols that allow these services to be specified and deployed. This includes requirements on the rule systems used the define these policies and protocols.

The advantage of standardizing a protocol for this is that services can be re-used across vendor products without modifying the transit intermediaries or services.

The iCAP protocol already provides similar functionality and this working group may elect to use iCAP as a starting point for its work. However, the working group is not obliged to retain any level of compatibility with iCAP.

Existing Internet-Drafts
Early Requirements document (expired but available on the web site):
Updated iCAP Callout Server:
A Rule Specification Language for Proxy Services:
OPES Network Taxonomy:
OPES Architecture for Rule Processing and Service Execution:
OMML: OPES Meta-data Markup Language:
General Use Cases:

Goals and Milestones:

Apr 01: Consensus on the charter.
Jul 01: Protocol document last call.
Aug 01: Working group review of policy requirements document(s).
Dec 01: Policy requirements document last call.

Michael W. Condry
Director, Network Edge Technology

<Prev in Thread] Current Thread [Next in Thread>
  • Charter, last call, Michael W. Condry <=