[rfc-dist] RFC 3837 on Security Threats and Risks for Open Pluggable Edge Services (OPES)

rfc-editor at rfc-editor.org rfc-editor at rfc-editor.org
Tue Aug 31 16:47:39 PDT 2004

A new Request for Comments is now available in online RFC libraries.

        RFC 3837

        Title:      Security Threats and Risks for Open Pluggable Edge
                    Services (OPES)
        Author(s):  A. Barbir, O. Batuner, B. Srinivas, M. Hofmann,
                    H. Orman
        Status:     Informational
        Date:       August 2004
        Mailbox:    abbieb at nortelnetworks.com, batuner at attbi.com,
                    bindignavile.srinivas at nokia.com,
                    hofmann at bell-labs.com, ho at alum.mit.edu
        Pages:      14
        Characters: 31883
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-opes-threats-03.txt

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

The document investigates the security threats associated with
the Open Pluggable Edge Services (OPES) and discusses the
effects of security threats on the underlying architecture.  The main
goal of this document is threat discovery and analysis.  The document
does not specify or recommend any solutions.

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 at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info at 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 at 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 at 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.
-------------- next part --------------
Skipped content of type multipart/alternative

More information about the rfc-dist mailing list