Open Proxy Extended Services architecture (opes)
Co-chairs:
Michael Condry <condry(_at_)intel(_dot_)com>
Hilarie Orman <HORMAN(_at_)novell(_dot_)com>
Mailing Lists: [TENTATIVE]
General Discussion: ietf-openproxy(_at_)imc(_dot_)org
To Subscribe: ietf-openproxy-request(_at_)imc(_dot_)org
Web: http://www.extproxy.org
Archive: ftp://ftp.ietf.org/ietf-mail-archive/opes
Description of Working Group:
The Open Proxy Extensible Services architecture (OPES) enables
construction of services "inside the network"; these can be used by
content providers for efficient caching, content administration,
communication, and network control functions. Other users of the
services include third-party content-related services such as
transcoders, regional affiliates, etc.
The open proxy extensible services architecture focuses on situations
with intermediate network elements providing the locus of control and
execution of the service function. The proxy services are content
directed: thus, the proxy understands at least some of the content
semantics and provides a service platform that operates within the
content flow. For example, it provides an opportunity to instruct the
cache that certain types of data are cacheable. The OPES WG will
work with WEBI/WREC group to define or follow specifications for
communication between the web cache sub-system and proxies to take
advantage of this information in creating a strategy for caching
and proxying that is more efficient than being "content ignorant".
The OPES WG will develop protocols for the proxy server to provide
"callout" services (e.g. iCAP, the content adaptation protocol) and
provide a forum for iCAP to submit and discuss its specifications. The
callout server may create copies of web pages, possibly in a different
form, e.g. a different natural language. Open Proxy protocols will
have the ability to communicate cache and proxy specific information
with surrogates and/or origin servers, for example, in order to inform
the origin that it has two representations of the same content. There
are points of interoperation required with Content Distribution
Networks, for example, in exchanging accounting related
information. Content Distribution Networks are the primary subject of
the CDNP group.
After the initial protocols have been specified, the open proxy
extensible
services group also will develop protocols to facilitate routing traffic
within cache system (specified by WEBI/WREC) along alternate paths
to minimize time or cost.
Goals and Milestones:
Feb 01: Requirements and roadmap documents for WG
Feb 01: First draft callout protocol; first draft information model
Mar 01: Meet at Minneapolis IETF
Mar 01: Update of OPES architecture document,
draft-tomlinson-epsfw-00.txt.
Jun 01: Submission of security and authentication architecture
Aug 01: Meet at London IETF
Aug 01: Final submission of callout protocol; final submission
of information model
Oct 01: Submission of data model for service description, invocation,
results
Dec 01: Salt Lake City IETF, final submission of architecture document
Agenda for December, San Diego Meeting
Introduction: Hilarie Orman
Use Cases: Marcus Hofmann
Workshop Summary: Michael Condry
ICAP Progress: Mark Nottingham
Relationship to CDN Peering: Mark Day
Document Roadmap: Hilarie Orman
Charter Bashing: Michael Condry
Architecture Requirements Discussion: Hilarie Orman
Discussion of other documents
Assignments and Administrivia