ietf-openproxy
[Top] [All Lists]

RFC 4037 on Open Pluggable Edge Services (OPES) Callout Protocol (OCP) Core

2005-03-11 12:13:03

A new Request for Comments is now available in online RFC libraries.


        RFC 4037

        Title:      Open Pluggable Edge Services (OPES) Callout
                    Protocol (OCP) Core
        Author(s):  A. Rousskov
        Status:     Standards Track
        Date:       March 2005
        Mailbox:    rousskov(_at_)measurement-factory(_dot_)com
        Pages:      56
        Characters: 131487
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-opes-ocp-core-05.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc4037.txt


This document specifies the core of the Open Pluggable Edge Services
(OPES) Callout Protocol (OCP).  OCP marshals application messages from
other communication protocols: An OPES intermediary sends original
application messages to a callout server; the callout server sends
adapted application messages back to the processor.  OCP is designed
with typical adaptation tasks in mind (e.g., virus and spam
management, language and format translation, message anonymization, or
advertisement manipulation).  As defined in this document, the OCP
Core consists of application-agnostic mechanisms essential for
efficient support of typical adaptations.

This document is a product of the Open Pluggable Edge Services Working
Group of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST(_at_)IETF(_dot_)ORG(_dot_)  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST(_at_)RFC-EDITOR(_dot_)ORG(_dot_)

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info(_at_)RFC-EDITOR(_dot_)ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info(_at_)RFC-EDITOR(_dot_)ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to 
RFC-Manager(_at_)RFC-EDITOR(_dot_)ORG(_dot_)  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR(_at_)RFC-EDITOR(_dot_)ORG(_dot_)  Please consult RFC 2223, 
Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
<ftp://ftp.isi.edu/in-notes/rfc4037.txt>
<Prev in Thread] Current Thread [Next in Thread>
  • RFC 4037 on Open Pluggable Edge Services (OPES) Callout Protocol (OCP) Core, rfc-editor <=