Browse Prior Art Database

Requirements for Open Pluggable Edge Services (OPES) Callout Protocols (RFC3836)

IP.com Disclosure Number: IPCOM000030869D
Original Publication Date: 2004-Aug-01
Included in the Prior Art Database: 2004-Aug-31
Document File: 14 page(s) / 28K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

A. Beck: AUTHOR [+5]

Abstract

This document specifies the requirements that the OPES (Open Pluggable Edge Services) callout protocol must satisfy in order to support the remote execution of OPES services. The requirements are intended to help evaluate possible protocol candidates, as well as to guide the development of such protocols.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 10% of the total text.

Network Working Group                                            A. Beck

Request for Comments: 3836                                    M. Hofmann

Category: Informational                              Lucent Technologies

                                                                H. Orman

                                               Purple Streak Development

                                                                R. Penno

                                                         Nortel Networks

                                                               A. Terzis

                                                Johns Hopkins University

                                                             August 2004

          Requirements for Open Pluggable Edge Services (OPES)

                           Callout Protocols

Status of this Memo

   This memo provides information for the Internet community.  It does

   not specify an Internet standard of any kind.  Distribution of this

   memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2004).

Abstract

   This document specifies the requirements that the OPES (Open

   Pluggable Edge Services) callout protocol must satisfy in order to

   support the remote execution of OPES services.  The requirements are

   intended to help evaluate possible protocol candidates, as well as to

   guide the development of such protocols.

Beck, et al.                 Informational                      [Page 1]

RFC 3836        Requirements for OPES Callout Protocols      August 2004

Table of Contents

   1.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2

   2.  Introduction. . . . . . . . . . . . . . . . . . . . . . . . .   2

   3.  Functional Requirements . . . . . . . . . . . . . . . . . . .   3

       3.1.  Reliability . . . . . . . . . . . . . . . . . . . . . .   3

       3.2.  Congestion Avoidance  . . . . . . . . . . . . . . . . .   3

       3.3.  Callout Transactions  . . . . . . . . . . . . . . . . .   3

       3.4.  Callout Connections . . . . . . . . . . . . . . . . . .   4

       3.5.  Asynchronous Message Exchange . . . . . . . . . . . . .   5

       3.6.  Message Segmentation  . . . . . . . . . . . . . . . . .   5

       3.7.  Support for Keep-Alive Mechanism  . . . . . . . . . . . ...