RFC 3837: Security Threats and Risks for Open Pluggable Edge Services (OPES)
In plain English — editorial summary, not part of the RFC
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 memo provides information for the Internet community.
Document record
- Document ID
- RFC3837
- Published
- August 2004
- Authors
- A. Barbir; O. Batuner; B. Srinivas; M. Hofmann; H. Orman
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- app
- Pages
- 14
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7430Analysis of Residual Threats and Possible Fixes for Multipath TCP (MPTCP)Current
July 2015
- RFC 3838Policy, Authorization, and Enforcement Requirements of the Open Pluggable Edge Services (OPES)Current
August 2004
- RFC 3836Requirements for Open Pluggable Edge Services (OPES) Callout ProtocolsCurrent
August 2004
- RFC 3835An Architecture for Open Pluggable Edge Services (OPES)Current
August 2004
- RFC 3859Common Profile for Presence (CPP)Current
August 2004
- RFC 3860Common Profile for Instant Messaging (CPIM)Current
August 2004
- RFC 3861Address Resolution for Instant Messaging and PresenceCurrent
August 2004
- RFC 3862Common Presence and Instant Messaging (CPIM): Message FormatCurrent
August 2004
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?