RFC 3835 on An Architecture for Open Pluggable Edge Services (OPES)
rfc-editor@rfc-editor.org Tue, 31 August 2004 23:56 UTC
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13956; Tue, 31 Aug 2004 19:56:44 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C2IWc-0002xc-TM; Tue, 31 Aug 2004 19:58:56 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C2IMt-0007nh-Li; Tue, 31 Aug 2004 19:48:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C2IKM-0006vD-1B for ietf-announce@megatron.ietf.org; Tue, 31 Aug 2004 19:46:14 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13363 for <ietf-announce@ietf.org>; Tue, 31 Aug 2004 19:46:11 -0400 (EDT)
Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C2IMO-0002mh-JK for ietf-announce@ietf.org; Tue, 31 Aug 2004 19:48:23 -0400
Received: from ISI.EDU (adma.isi.edu [128.9.160.239]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i7VNihJ01894; Tue, 31 Aug 2004 16:44:43 -0700 (PDT)
Message-Id: <200408312344.i7VNihJ01894@boreas.isi.edu>
To: ietf-announce@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Tue, 31 Aug 2004 16:44:43 -0700
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2
Cc: ietf-openproxy@imc.org, rfc-editor@rfc-editor.org
Subject: RFC 3835 on An Architecture for Open Pluggable Edge Services (OPES)
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f
A new Request for Comments is now available in online RFC libraries.
RFC 3835
Title: An Architecture for Open Pluggable Edge Services
(OPES)
Author(s): A. Barbir, R. Penno, R. Chen, M. Hofmann, H. Orman
Status: Informational
Date: August 2004
Mailbox: abbieb@nortelnetworks.com, chen@research.att.com,
hofmann@bell-labs.com, ho@alum.mit.edu,
rpenno@nortelnetworks.com
Pages: 17
Characters: 36113
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-opes-architecture-04.txt
URL: ftp://ftp.rfc-editor.org/in-notes/rfc3835.txt
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 document is a product of the Open Pluggable Edge Services Working
Group of the IETF.
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. 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@IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info@RFC-EDITOR.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@RFC-EDITOR.ORG. 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@RFC-EDITOR.ORG. 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.
_______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce