WG Review: Open Pluggable Edge Services (opes)
The IESG <iesg-secretary@ietf.org> Fri, 15 June 2001 13:35 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07730; Fri, 15 Jun 2001 09:35:43 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id JAA18286 for ietf-123-outbound.10@ietf.org; Fri, 15 Jun 2001 09:25:01 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id JAA18253 for <all-ietf@loki.ietf.org>; Fri, 15 Jun 2001 09:18:58 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06795; Fri, 15 Jun 2001 09:18:33 -0400 (EDT)
Message-Id: <200106151318.JAA06795@ietf.org>
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce:;
cc: new-work@ietf.org
Subject: WG Review: Open Pluggable Edge Services (opes)
Date: Fri, 15 Jun 2001 09:18:33 -0400
Sender: scoya@cnri.reston.va.us
A new IETF working group has been proposed in the Applications Area. The IESG has not made any determination as yet. The following Description was submitted, and is provided for informational purposes only: Open Pluggable Edge Services (opes) ----------------------------------- Current Status: Proposed Working Group Description of Working Group: The Open Plugable Edge Service (OPES) WG 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. The protocol provides a framework for integrating arbitrary 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 tranformation has been performed. As part of the development of this protocol the WG will produce an analysis of the security impliciations of this architecture. A secondary task for this WG is to enumerate the requirements for management policies and associated administrative protocols that allow these services to be specified and deployed. 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 WG 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. A number of existing Internet-Drafts will become WG documents: Early Requirements document (expired but available on the web site): draft-tomlinson-epsfw-00.txt Updated iCAP Callout Server: draft-elson-opes-icap-01.txt A Rule Specification Language for Proxy Services: draft-beck-opes-imrl-00.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 General Use Cases: draft-beck-opes-esfnep-01.txt