Folks,
based on comments and discussions from the London meeting, please find
below a re-worded charter for review. And, yes, we're back to "Edge"
again :)
Thanks,
Markus
======================================================
Open Pluggable Edge 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 facilitates distributed applications, particularly
Web-based applications and services. The Open Pluggable Edge Services
(OPES) working group's task is to define application-level protocols
that facilitate Web programming in a distributed style. The working
group will focus on applications that use HTTP or RTP/RTSP transport.
The nodes supplying the distributed application environment are called
"Web-based service engines" or "edge" Web servers. They form an
application overlay network on top of an IP network.
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.
A key task for the working group is to specify an appropriate
authorization mechanism for these services. The primary subjects for
authorization are the content requestor and/or the content provider. A
security model supporting identification, authorization, and possibly,
validation, is a required product of the working group. The model will
specify the entities, privileges, notifications, and authorization
actions affecting protocol payloads. In addition, the model will show
how end-to-end services and data integrity concepts are mapped onto
the OPES architecture.
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 and
reply to the HTTP or RTP/RTSP messages vectored off the content path.
The iCAP protocol provides such a vectoring 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 the iCAP protocol without
being obliged to retain any level of compatibility with the current
iCAP proposal, or it might define an alternative protocol altogether.
Another working group task is to enumerate the requirements for
management policies and associated administrative protocols that allow
these services to be specified and deployed. This includes
requirements for the rule systems used to specify conditions defining
the conditions under which a service is executed.
All the protocols involved in Web-based processing are end-to-end
protocols, and all protocols to be defined by this group will be
end-to-end protocols.
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
Related Internet-Drafts
Prior related requirements document (expired but
available on the web site):
draft-tomlinson-epsfw-00.txt
Updated iCAP Callout Protocol:
draft-elson-opes-icap-01.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.