RFC 3752 on Open Pluggable Edge Services (OPES) Use Cases and Deployment Scenarios

[email protected]
Newsgroups gmane.ietf.opes
Message-ID <[email protected]>
A new Request for Comments is now available in online RFC libraries.


        RFC 3752

        Title:      Open Pluggable Edge Services (OPES)
                    Use Cases and Deployment Scenarios
        Author(s):  A. Barbir, E. Burger, R. Chen, S. McHenry,
                    H. Orman, R. Penno
        Status:     Informational
        Date:       April 2004
        Mailbox:    [email protected], [email protected],
                    [email protected], [email protected],
                    [email protected], [email protected]
        Pages:      14
        Characters: 29481
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-opes-scenarios-01.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3752.txt


This memo provides a discussion of use cases and deployment scenarios
for Open Pluggable Edge Services (OPES).  The work examines services
that could be performed to requests and/or responses.

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 [email protected].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [email protected].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [email protected] with the message body 
help: ways_to_get_rfcs.  For example:

        To: [email protected]
        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 [email protected].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
[email protected].  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.
(unnamed) (message/external-body, 102 B) - not displayed
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.