Although our goals has not changed the languange
is changed to make clear that OPES is about devices that
will be IP endpoints.
Open Pluggable Endpoint Services (opes)
Co-chairs:
Michael Condry <condry(_at_)intel(_dot_)com>
Markus Hofmann <hofmann(_at_)lucent(_dot_)com>
Technical Team Lead:
Hilarie Orman <horman(_at_)volera(_dot_)com>
Mailing Lists:
General Discussion: ietf-openproxy(_at_)imc(_dot_)org
To Subscribe: ietf-openproxy-request(_at_)imc(_dot_)org
Web: http://www.ietf-opes.org
Archive: ftp://ftp.ietf.org/ietf-mail-archive/opes
Description of Working Group:
The Internet is facilitating multiple forms of distributed applications,
some of which employ application-level activities within Web-based service
engines. The Open Pluggable Endpoint Services (OPES) working group?s
primary task is to define application-level protocols enabling such
Web-based service environments to incorporate services that operate on
messages transported by HTTP and RTP/RTSP.
Web-based service engines are sometimes identified as "edge" servers, which
form an application-level overlay network on top of an IP network. They are
explicitly addressed at IP level and terminate a transport connection in a
normal way. Thus, they do not interfere with the end-to-end principle in
RFC 1958.
The protocols to be defined provide a framework for integrating a wide
range of services into application-level web service engines. The advantage
of standardizing such protocols is that services can be re-used across vendor
products without modifying the web service engines or services.
Web services are not transparent: They must be authorized by the
application endpoint (either the content requestor or the content
provider), corresponding to who requested the service. A key task for the
working group is to specify an appropriate authorization mechanism.
Authorized web services can be provided either on the content path between
origin server and client, or on remote callout servers off the content
path. One task for this working group is the development of callout
protocols that enable remote callout servers to receive the HTTP or
RTP/RTSP messages necessary for service provisioning.
The iCAP protocol provides similar function for services operating on iCAP
encapsulated HTTP messages. The working group will evaluate the iCAP
protocol as one candidate for passing HTTP messages for remote services. It
may decide to extend or even not use the iCAP protocol without being
obliged to retain any level of compatibility with the current iCAP proposal.
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.
Internet-Drafts in Working Group Plans
Taxonomy and Models Document
draft-tomlinson-opes-model-00.txt
Deployment Scenarios Document
draft-mchenry-opes-deployment-scenarios-00.txt
Policy Requirements for Edge Services
draft-rafalow-opes-policy-requirements-00.txt
Updated iCAP Callout Protocol:
draft-elson-opes-icap-03.txt
Related Internet-Drafts
Prior related requirements document (expired but available on the web site):
draft-tomlinson-epsfw-00.txt
A Rule Specification Language for Proxy Services:
draft-beck-opes-irml-01.txt
OPES Network Taxonomy:
draft-erikson-opes-net-taxonomy-00.txt
OPES Architecture for Rule Processing and Service Execution:
draft-yang-opes-rule-processing-service-execution-00.txt
OMML: OPES Meta-data Markup Language:
draft-maciocco-opes-omml-00.txt
Quality of Service Extension to IRML
draft-ng?opes-irmlqos-00.txt
Sub-System Extension to IRML
draft-ng?opes-irmlsubsys-00.txt
Goals and Milestones:
Dec 01: Working Group last call of OPES Models draft.
Dec 01: Working Group last call of OPES Deployment Scenarios draft.
Mar 02: Working Group last call of Callout Protocol Requirements draft.
Jul 02: Working Group last call of Callout Protocols.
Jul 02: Working group last call of OPES Policy Requirements draft.
Michael W. Condry
Director, Network Edge Technology