RFC 4037: Open Pluggable Edge Services (OPES) Callout Protocol (OCP) Core
In plain English — editorial summary, not part of the RFC
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. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4037
- Published
- March 2005
- Authors
- A. Rousskov
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 56
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3998Internet Printing Protocol (IPP): Job and Printer Administrative OperationsCurrent
March 2005
- RFC 3997Internet Printing Protocol (IPP): Requirements for IPP NotificationsCurrent
March 2005
- RFC 3996Internet Printing Protocol (IPP): The 'ippget' Delivery Method for Event NotificationsCurrent
March 2005
- RFC 3995Internet Printing Protocol (IPP): Event Notifications and SubscriptionsCurrent
March 2005
- RFC 3983Using the Internet Registry Information Service (IRIS) over the Blocks Extensible Exchange Protocol (BEEP)Updated
January 2005
- RFC 3982IRIS: A Domain Registry (dreg) Type for the Internet Registry Information Service (IRIS)Current
January 2005
- RFC 3981IRIS: The Internet Registry Information Service (IRIS) Core ProtocolUpdated
January 2005
- RFC 3977Network News Transfer Protocol (NNTP)Updated
October 2006
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?