UNLIMITED FREE
ACCESS TO THE WORLD'S BEST IDEAS

SUBMIT
Already a GlobalSpec user? Log in.

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.

Customize Your GlobalSpec Experience

Select Your Free Newsletters

Industry Newsletters

Select Your Free Product Alerts

Finish!
Privacy Policy

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.

IETF RFC 4236

HTTP Adaptation with Open Pluggable Edge Services (OPES)

active, Most Current
Buy Now
Organization: IETF
Publication Date: 1 November 2005
Status: active
Page Count: 27
scope:

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.

Document History

IETF RFC 4236
November 1, 2005
HTTP Adaptation with Open Pluggable Edge Services (OPES)
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...

References

This document references:
IETF RFC 2616 - Hypertext Transfer Protocol -- HTTP/1.1
Published by IETF on June 1, 1999
A description is not available for this item.
This document references:
IETF RFC 4037 - Open Pluggable Edge Services (OPES) Callout Protocol (OCP) Core
Published by IETF on March 1, 2005
This document specifies the core of the Open Pluggable Edge Services (OPES) Callout Protocol (OCP). OCP marshals application messages from other communication protocols: An OPES intermediary sends...
Advertisement