Browse Prior Art Database

An Architecture for Open Pluggable Edge Services (OPES) (RFC3835)

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

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

A. Barbir: AUTHOR [+5]

Abstract

This memo defines an architecture that enables the creation of an application service in which a data provider, a data consumer, and zero or more application entities cooperatively implement a data stream service.

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

Network Working Group                                          A. Barbir

Request for Comments: 3835                                      R. Penno

Category: Informational                                  Nortel Networks

                                                                 R. Chen

                                                               AT&T Labs

                                                              M. Hofmann

                                           Bell Labs/Lucent Technologies

                                                                H. Orman

                                               Purple Streak Development

                                                             August 2004

        An Architecture for Open Pluggable Edge Services (OPES)

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 memo defines an architecture that enables the creation of an

   application service in which a data provider, a data consumer, and

   zero or more application entities cooperatively implement a data

   stream service.

Barbir, et al.               Informational                      [Page 1]

RFC 3835                An Architecture for OPES             August 2004

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  2

   2 . The Architecture . . . . . . . . . . . . . . . . . . . . . . .  3

       2.1.  OPES Entities. . . . . . . . . . . . . . . . . . . . . .  3

             2.1.1.  Data Dispatcher. . . . . . . . . . . . . . . . .  5

       2.2.  OPES Flows . . . . . . . . . . . . . . . . . . . . . . .  6

       2.3.  OPES Rules . . . . . . . . . . . . . . . . . . . . . . .  6

       2.4.  Callout Servers. . . . . . . . . . . . . . . . . . . . .  7

       2.5.  Tracing Facility . . . . . . . . . . . . . . . . . . . .  8

   3.  Security and Privacy Considerations  . . . . . . . . . . . . .  9

       3.1.  Trust Domains. . . . . . . . . . . . . . . . . . . . . .  9

       3.2.  Establishing Trust and Service Authorization . . . . . . 11

       3.3.  Callout Protocol . . . . . . . . . . . . . . . . . . . ....