Open Pluggable Edge Services (opes)
Michael Condry <condry(_at_)intel(_dot_)com>
Markus Hofmann <hofmann(_at_)lucent(_dot_)com>
Technical Team Lead:
Hilarie Orman <horman(_at_)volera(_dot_)com>
General Discussion: ietf-openproxy(_at_)imc(_dot_)org
To Subscribe: ietf-openproxy-request(_at_)imc(_dot_)org
Description of Working Group:
The Internet is facilitating multiple forms of distributed applications,
some of which employ application-level intermediaries. The Open Pluggable
Edge Services (OPES) working group's primary task is to define
application-level protocols enabling such intermediaries to incorporate
services that operate on messages transported by HTTP and RTP/RTSP. At the
IP level, the participating intermediaries are endpoints that are
The protocols to be defined provide a framework for integrating a wide
range of services into application-level intermediaries. The advantage of
standardizing such protocols is that services can be re-used across vendor
products without modifying the intermediaries or services.
Intermediary services provided in this way are not transparent: They must
be authorized by the application endpoint (either the content requestor or
the content provider) that requests the intermediary service.
A key task for
the working group is to specify an appropriate authorization mechanism.
Intermediaries may employ services executed either locally or on a remote
("callout") server. One task for this working group is the development of
callout protocols that enable the receiving callout service to either
receive encapsulated HTTP or RTP/RTSP messages or, through some other
mechanism, for the callout service to receive the application data
necessary to perform its services.
The iCAP protocol provides similar function for services operating on
iCAP-encapsulated HTTP application data. The working group will evaluate
the iCAP protocol as one candidate for passing HTTP application data for
remote services. It may decide to extend or even not usethe iCAP protocol
without being obliged to retain any level of compatibility with the current
Another 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 to specify conditions under which services are executed.
The working group will develop a security model for OPES services in which
authorization and enforcement will be defined. The model will specify the
entities, privileges, notifications, and authorization actions affecting
content. In addition, the model will show how end-to-end services and data
integrity concepts are mapped onto the OPES architecture.
Prior related requirements document (expired but available on the web site):
Updated iCAP Callout Protocol:
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:
Aug 01: Working Group review of OPES Deployment Scenarios document.
Sep 01: Working Group review of callout protocol requirements.
Nov 01: iCAP Protocol review.
Jan 02: Working group review of policy requirements document(s).
Feb 02: Working group last call for callout protocol.
Mar 02: Policy requirements document last call.
Michael W. Condry
Director, Network Edge Technology