RFC 4236: HTTP Adaptation with Open Pluggable Edge Services (OPES)
In plain English — editorial summary, not part of the RFC
Open Pluggable Edge Services (OPES) framework documents several application-agnostic mechanisms such as OPES tracing, OPES bypass, and OPES callout protocol. This document extends those generic mechanisms for Hypertext Transfer Protocol (HTTP) adaptation. Together, application-agnostic OPES documents and this HTTP profile constitute a complete specification for HTTP adaptation with OPES. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4236
- Published
- November 2005
- Authors
- A. Rousskov; M. Stecher
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 27
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3836Requirements for Open Pluggable Edge Services (OPES) Callout ProtocolsCurrent
August 2004
- RFC 4237Voice Messaging Directory ServiceCurrent
October 2005
- RFC 4238Voice Message Routing ServiceUpdated
October 2005
- RFC 4239Internet Voice Messaging (IVM)Current
November 2005
- RFC 4259A Framework for Transmission of IP Datagrams over MPEG-2 NetworksCurrent
December 2005
- RFC 4287The Atom Syndication FormatUpdated
December 2005
- RFC 4161Guidelines for Optional Services for Internet Fax GatewaysCurrent
September 2005
- RFC 4160Internet Fax Gateway RequirementsCurrent
September 2005
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?