RFC 3836: Requirements for Open Pluggable Edge Services (OPES) Callout Protocols
In plain English — editorial summary, not part of the RFC
This document specifies the requirements that the OPES (Open Pluggable Edge Services) callout protocol must satisfy in order to support the remote execution of OPES services. The requirements are intended to help evaluate possible protocol candidates, as well as to guide the development of such protocols. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3836
- Published
- August 2004
- Authors
- A. Beck; M. Hofmann; H. Orman; R. Penno; A. Terzis
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- app
- Pages
- 13
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4236HTTP Adaptation with Open Pluggable Edge Services (OPES)Current
November 2005
- RFC 4254The Secure Shell (SSH) Connection ProtocolUpdated
January 2006
- RFC 3835An Architecture for Open Pluggable Edge Services (OPES)Current
August 2004
- RFC 3837Security Threats and Risks for Open Pluggable Edge Services (OPES)Current
August 2004
- RFC 3838Policy, Authorization, and Enforcement Requirements of the 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
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?