1 / 8

Open Pluggable Edge Services (opes)

The OPES Working Group provides an update on their progress in designing a framework for authorization and invocation of networked services at the application level. The focus is on HTTP-based applications, but other protocols are also supported. The group discusses the proposed re-charter and new work items, including OCP profiles for SMTP and OPES rules language.

britanney-hall
Télécharger la présentation

Open Pluggable Edge Services (opes)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  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. Origin Server OPES Callout Protocol (OCP) Client OPES Framework OPESProcessor CalloutServer OPES Rules Language

  4. Web Server OPES Callout Protocol (OCP) Web Browser 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. Application Protocol Profiles HTTP profile RTP Profile? FTP Profile? SMTP Profile? MIME Profile? ... OCP Core Application protocolagnostic TCP mostcommon transport TCP/IP Other Transports 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

More Related