Hi,
time for a brief status update on our OPES activities and on immediate
next steps.
Document Status
===============
Three WG drafts have been submitted to the IESG for consideration as
informal RFC, namely
"An Architecture for Open Pluggable Edge Services (OPES)"
"Requirements for OPES Callout Protocols"
"OPES Use Cases and Deployment Scenarios"
The first version of our "document on endpoint authorization and
enforcement requirements", named
"Requirements for Policy, Authorization and Enforcement of OPES
Services"
has been published as Internet Draft. Please read it carefully and
provide comments and feedback via this mailing list ASAP. We'd like to
wrap up this draft very soon - please read and discuss it *now*!
A few folks are currently preparing a first version of our "document
on threat/risk model for OPES services". We expect to have it
pusblished as an Internet Draf in October, in time for the next IETF
meeting.
OPES Protocol Work
==================
Since we hope being able to close pretty soon on the five initial
documents that somehow lay the foundation for our more technical work,
it's time to start thinking on how to get started on the OPES protocol
work.
Looking at the charter, we see that "The working group will consider
the ICAP protocol drafts as an OPES precursor and will will support
development of an analysis that explains the limitations of ICAP, to
accompany informational publication of that protocol.".
As such, it's time for all of us to carefully read the ICAP Internet Draft
"ICAP - the Internet Content Adaptation Protocol"
draft-elson-icap-01.txt
and to provide comments on this protocol specification in the context
of OPES. Please be aware that the ICAP specification is *not* a
product of the OPES WE, but represents an individual submission,
documenting a "status quo". Nevertheless, it's of quite some relevance
for our WG, and we better have a careful look at and comment on it. In
particular, it might be interesting to discuss:
(a) How does ICAP fit into the OPES context and how does it stack
up to the OPES protocol requirements?
(b) If there are open issues, would it make sense for the WG trying
to recommend extensions toICAP so that it'll meet all
requirements?
(c) What are the strengths, the weaknesses, and the limitations of
the current ICAP specification? Are there lesson to be learned
from the spec and from the work on ICAP?
(d) Given that there are several (commercial) implementations
of ICAP out and in use - are there any lesses learned from these
implementations? Is the current specification stable and clear,
or are there any open issues or issues to clarify?
(e) Are there any findings/measurements with respect to ICAP
performance that would be interesting to be shared with the WG?
(f) More, more, more,... please add...
A good starting point might also be the individual Internet Draft on
"Evaluating the ICAP protocol regarding the OPES callout protocol
requirements"
draft-stecher-opes-icap-eval-00.txt
So, please check out both ICAP-related drafts and share your thoughts
on this mailing list. Should be enough material for some interessting
discussions.
Cheers,
Markus