⌕ Поиск по атласу

IETF · RFC · RFC4236

RFC4236 · HTTP Adaptation with Open Pluggable Edge Services (OPES)

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 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]

Официальная английская аннотация

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]

Связи документа

Официальный источник · 2005-11-01

Полные импортированные сведения карточки
{
  "id": "RFC4236",
  "number": 4236,
  "title_en": "HTTP Adaptation with Open Pluggable Edge Services (OPES)",
  "title_ru": "",
  "summary_ru": "",
  "purpose_ru": "",
  "use_ru": "",
  "full_translation_path": "",
  "full_translation_checked_at": "",
  "full_translation_source_sha256": "",
  "architect_note_ru": "",
  "topics_ru": [],
  "translation_state": "not_prepared",
  "verification_level": "not_prepared",
  "verification_level_ru": "Русская выжимка не подготовлена",
  "verification_note_ru": "",
  "abstract_en": "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]",
  "authors": [
    "A. Rousskov",
    "M. Stecher"
  ],
  "organizations": [],
  "publication_date": "2005-11-01",
  "current_status": "PROPOSED STANDARD",
  "current_status_ru": "Предлагаемый стандарт",
  "publication_status": "PROPOSED STANDARD",
  "publication_status_ru": "Предлагаемый стандарт",
  "lifecycle": "active",
  "lifecycle_ru": "Действующий",
  "stream": "IETF",
  "stream_ru": "IETF",
  "area": "app",
  "area_ru": "app",
  "working_group": "opes",
  "source_draft": "draft-ietf-opes-http-03",
  "page_count": 27,
  "doi": "10.17487/RFC4236",
  "keywords": [
    "callout protocol",
    "ocp",
    "opes tracing",
    "opes bypass"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc4236/",
    "html": "https://www.rfc-editor.org/rfc/rfc4236.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc4236.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc4236/"
  }
}