Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Open Pluggable Edge Services (OPES) Callout Protocol (OCP) Core (RFC4037)

IP.com Disclosure Number: IPCOM000090521D
Original Publication Date: 2005-Mar-01
Included in the Prior Art Database: 2005-Mar-05

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

A. Rousskov: AUTHOR

Abstract

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 text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 2% of the total text.

Network Working Group                                        A. Rousskov

Request for Comments: 4037                       The Measurement Factory

Category: Standards Track                                     March 2005

    Open Pluggable Edge Services (OPES) Callout Protocol (OCP) Core

Status of This Memo

   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.

Copyright Notice

   Copyright (C) The Internet Society (2005).

Abstract

   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.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3

       1.1.  Scope  . . . . . . . . . . . . . . . . . . . . . . . . .  4

       1.2.  OPES Document Map  . . . . . . . . . . . . . . . . . . .  5

       1.3.  Terminology  . . . . . . . . . . . . . . . . . . . . . .  6

   2.  Overall Operation  . . . . . . . . . . . . . . . . . . . . . .  7

       2.1.  Initialization . . . . . . . . . . . . . . . . . . . . .  7

       2.2.  Original Dataflow  . . . . . . . . . . . . . . . . . . .  8

       2.3.  Adapted Dataflow . . . . . . . . . . . . . . . . . . . .  8

       2.4.  Multiple Application Messages  . . . . . . . . . . . . .  9

       2.5.  Termination  . . . . . . . . . . . . . . . . . . . . . .  9

       2.6.  Message Exchange Patterns  . . . . . . . . . . . . . . .  9

       2.7.  Timeouts . . . . . . . . . . . . . . . . . . . . . . . . 10

       2.8.  Environment  . . . . . . . . . . . . . . . . . . . . . . 11

   3.  Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Rousskov                    Standards Track                     [Page 1]

RFC 4037               OPES Callout Protocol Core             March 2005

       3.1.  Message Format . . . . . . . . . . . . . . . . . . . . . 12

       3...