Open Pluggable Edge Services (opes)

1
Open Pluggable Edge Services(opes)

• 61st IETF Meeting
• Washington, D.C., USA

2
Working Group Status

• IETF Working Group chartered beginning of 2002.
• Initial Charter Design of a framework that
  enables authorization and invocation of networked
  services at the application level, including
• A protocol for invocation of remote call-out
  services,
• Standard formats for description of invocation
  rules (postponed),
• Trust and thread model for application services
  inside the network.

3
OPES Framework
OPESProcessor
CalloutServer
OPES Rules Language
4
Initial focus was on HTTP-based applications, but
the design aims to support other application
protocols as well.
OPES Processor HTTP application (e.g. Web Cache)
Callout Server e.g. AntiVirus Scanner
OPES Rules Language
5
Working Group Status (continued)

• Work addresses IAB considerations for OPES (RFC
  3238).
• Status
• 7 RFCs published, 1 RFC in RFC editor queue, 1 ID
  under IESG review,
• Initial charter finished,
• Proposed re-charter under IESG/IETF review.

6
Structure of OPES Callout Protocol
7
Summary Of Proposed Re-Charter

• Consensus on new charter has been established via
  mailing list discussions.
• New charter proposal is stable and has been
  submitted to IESG.
• Propose re-charter was sent out to IETF Announce
  list.
• Proposed work items are focused and narrow, and
  follow the established OPES framework.
• Continue to address IAB considerations for OPES
  (RFC 3238).
• Two new work items
• OCP profile(s) that will support OPES services
  operating on SMTP.
• Includes a document on scenarios and use cases.
• First profile will address the needs of at least
  the MTA.
• OPES rules language
• Includes discussion of relationship to sieve.
• Possibly based on previous work on P.

8
Example Use Cases
Web Server
OPES Callout Protocol (OCP)
HTTP
SMTP
Web Cache
SMTPMTA
Callout Server (e.g. w/Virus Scanner)
HTTP
SMTP
OPES Rules Language
EmailClient
WebBrowser