RFC 3897 on Open Pluggable Edge Services (OPES) Entities and End Points Communication

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.