Open Pluggable Edge Services (opes) 61st IETF Meeting Washington, D.C., USA.

8
Open Pluggable Edge Services (opes) 61st IETF Meeting Washington, D.C., USA

Transcript of Open Pluggable Edge Services (opes) 61st IETF Meeting Washington, D.C., USA.

Page 1: Open Pluggable Edge Services (opes) 61st IETF Meeting Washington, D.C., USA.

Open Pluggable Edge Services(opes)

61st IETF MeetingWashington, D.C., USA

Page 2: Open Pluggable Edge Services (opes) 61st IETF Meeting Washington, D.C., USA.

2M. Hofmann, T. Hansen 61st IETF Meeting, Open Pluggable Edge Services (opes)

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.

Page 3: Open Pluggable Edge Services (opes) 61st IETF Meeting Washington, D.C., USA.

3M. Hofmann, T. Hansen 61st IETF Meeting, Open Pluggable Edge Services (opes)

CalloutServer

Client

OPESProcessor

OriginServer

OPES Callout Protocol (OCP)

OPES Rules Language

OPES Framework

Page 4: Open Pluggable Edge Services (opes) 61st IETF Meeting Washington, D.C., USA.

4M. Hofmann, T. Hansen 61st IETF Meeting, Open Pluggable Edge Services (opes)

Callout Server e.g. AntiVirusScanner

WebBrowser

OPES Processor HTTP application(e.g. Web Cache)

WebServer

OPES Callout Protocol (OCP)

OPES Rules Language

Initial focus was on HTTP-based applications, but the design aims to support other application protocols as well.

Page 5: Open Pluggable Edge Services (opes) 61st IETF Meeting Washington, D.C., USA.

5M. Hofmann, T. Hansen 61st IETF Meeting, Open Pluggable Edge Services (opes)

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.

Page 6: Open Pluggable Edge Services (opes) 61st IETF Meeting Washington, D.C., USA.

6M. Hofmann, T. Hansen 61st IETF Meeting, Open Pluggable Edge Services (opes)

Structure of OPES Callout Protocol

OCP CoreOCP Core

HTTPprofileHTTPprofile

RTPProfile?

RTPProfile?

FTPProfile?

FTPProfile?

SMTPProfile?SMTP

Profile?MIME

Profile?MIME

Profile?...

TCP/IPTCP/IP OtherTransports

OtherTransports

Applicationprotocolagnostic

ApplicationProtocolProfiles

TCP mostcommon transport

Page 7: Open Pluggable Edge Services (opes) 61st IETF Meeting Washington, D.C., USA.

7M. Hofmann, T. Hansen 61st IETF Meeting, Open Pluggable Edge Services (opes)

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”.

Page 8: Open Pluggable Edge Services (opes) 61st IETF Meeting Washington, D.C., USA.

8M. Hofmann, T. Hansen 61st IETF Meeting, Open Pluggable Edge Services (opes)

Callout Server(e.g. w/Virus Scanner)

WebBrowser

Web Cache

WebServer

OPES Callout Protocol (OCP)

OPES Rules Language

Example Use Cases

HTTP

HTTP

SMTP

SMTP

EmailClient

SMTPMTA