HTTP Adaptation with Open Pluggable Edge Services (OPES)
RFC 4236
Document | Type |
RFC - Proposed Standard
(November 2005; No errata)
Was draft-ietf-opes-http (opes WG)
|
|
---|---|---|---|
Authors | Alex Rousskov , Martin Stecher | ||
Last updated | 2013-03-02 | ||
Stream | Internent Engineering Task Force (IETF) | ||
Formats | plain text html pdf htmlized (tools) htmlized bibtex | ||
Stream | WG state | (None) | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 4236 (Proposed Standard) | |
Action Holders |
(None)
|
||
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Ted Hardie | ||
Send notices to | (None) |
Network Working Group A. Rousskov Request for Comments: 4236 The Measurement Factory Category: Standards Track M. Stecher CyberGuard Corporation November 2005 HTTP Adaptation with Open Pluggable Edge Services (OPES) Status of This Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (2005). Abstract 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. Rousskov & Stecher Standards Track [Page 1] RFC 4236 HTTP Adaptation with OPES November 2005 Table of Contents 1. Scope ...........................................................3 2. OPES Document Map ...............................................3 3. Callout Protocol ................................................4 3.1. Application Message Parts ..................................5 3.2. Application Profile Features ...............................6 3.2.1. Profile Parts .......................................6 3.2.2. Profile Structure ...................................8 3.2.3. Aux-Parts ...........................................8 3.2.4. Pause-At-Body .......................................9 3.2.5. Stop-Receiving-Body ................................10 3.2.6. Preservation-Interest-Body .........................10 3.2.7. Content-Encodings ..................................11 3.2.8. Profile Negotiation Example ........................12 3.3. Application Message Start Message .........................13 3.4. DUM Message ...............................................13 3.5. Selective Adaptation ......................................14 3.6. Hop-by-hop Headers ........................................15 3.7. Transfer Encodings ........................................15 3.8. HTTP Header Correctness ...................................16 3.8.1. Message Size Recalculation .........................16 3.8.2. Content-MD5 Header .................................17 3.9. Examples ..................................................18 4. Tracing ........................................................22 5. Bypass .........................................................24 6. IAB Considerations .............................................24 7. Security Considerations ........................................24 8. IANA Considerations ............................................24 9. Compliance .....................................................25 10. References ....................................................25 10.1. Normative References .....................................25 10.2. Informative References ...................................25 Rousskov & Stecher Standards Track [Page 2] RFC 4236 HTTP Adaptation with OPES November 2005 1. Scope The Open Pluggable Edge Services (OPES) framework documents several application-agnostic mechanisms such as OPES processor and endpoints communications [RFC3897] or OPES callout protocol [RFC4037]. This document extends those generic mechanisms for adaptation of a specific application protocol, HTTP [RFC2616]. Together, application-agnostic OPES documents and this HTTP profile constitute a complete specification for HTTP adaptation with OPES. The primary sections of this document specify HTTP-specific extensions for the corresponding application-agnostic mechanisms documented elsewhere. 2. OPES Document Map This document belongs to a large set of OPES specifications produced by the IETF OPES Working Group. Familiarity with the overall OPES approach and typical scenarios is often essential when trying to comprehend isolated OPES documents. This section provides an index of OPES documents to assist the reader with finding "missing" information. o The document on "OPES Use Cases and Deployment Scenarios"Show full document text