RFC 3897 on Open Pluggable Edge Services (OPES) Entities and End Points Communication
rfc-editor@rfc-editor.org Fri, 24 September 2004 17:09 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 NAA26955; Fri, 24 Sep 2004 13:09:15 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CAtgN-0006Ll-UX; Fri, 24 Sep 2004 13:16:34 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CAtEI-00056G-6r; Fri, 24 Sep 2004 12:47:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CAsyB-0000f3-GX for ietf-announce@megatron.ietf.org; Fri, 24 Sep 2004 12:30:51 -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 MAA22685 for <ietf-announce@ietf.org>; Fri, 24 Sep 2004 12:30:49 -0400 (EDT)
Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CAt5D-000541-3u for ietf-announce@ietf.org; Fri, 24 Sep 2004 12:38:07 -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 i8OGSmJ19609; Fri, 24 Sep 2004 09:28:48 -0700 (PDT)
Message-Id: <200409241628.i8OGSmJ19609@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: Fri, 24 Sep 2004 09:28:48 -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: a2c12dacc0736f14d6b540e805505a86
Cc: ietf-openproxy@imc.org, rfc-editor@rfc-editor.org
Subject: RFC 3897 on Open Pluggable Edge Services (OPES) Entities and End Points Communication
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: a8a20a483a84f747e56475e290ee868e
A new Request for Comments is now available in online RFC libraries.
RFC 3897
Title: Open Pluggable Edge Services (OPES) Entities
and End Points Communication
Author(s): A. Barbir
Status: Informational
Date: September 2004
Mailbox: abbieb@nortelnetworks.com
Pages: 14
Characters: 33890
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-opes-end-comm-08.txt
URL: ftp://ftp.rfc-editor.org/in-notes/rfc3897.txt
This memo documents tracing and non-blocking (bypass) requirements
for Open Pluggable Edge Services (OPES).
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