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

IETF · RFC · RFC8007

RFC8007 · Content Delivery Network Interconnection (CDNI) Control Interface / Triggers

Content Delivery Network Interconnection (CDNI) Control Interface / Triggers

This document describes the part of the Content Delivery Network Interconnection (CDNI) Control interface that allows a CDN to trigger activity in an interconnected CDN that is configured to deliver content on its behalf. The upstream CDN can use this mechanism to request that the downstream CDN pre-position metadata or content or to request that it invalidate or purge metadata or content. The upstream CDN can monitor the status of activity that it has triggered in the downstream CDN.

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

This document describes the part of the Content Delivery Network Interconnection (CDNI) Control interface that allows a CDN to trigger activity in an interconnected CDN that is configured to deliver content on its behalf. The upstream CDN can use this mechanism to request that the downstream CDN pre-position metadata or content or to request that it invalidate or purge metadata or content. The upstream CDN can monitor the status of activity that it has triggered in the downstream CDN.

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

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

Полные импортированные сведения карточки
{
  "id": "RFC8007",
  "number": 8007,
  "title_en": "Content Delivery Network Interconnection (CDNI) Control Interface / Triggers",
  "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": "This document describes the part of the Content Delivery Network Interconnection (CDNI) Control interface that allows a CDN to trigger activity in an interconnected CDN that is configured to deliver content on its behalf. The upstream CDN can use this mechanism to request that the downstream CDN pre-position metadata or content or to request that it invalidate or purge metadata or content. The upstream CDN can monitor the status of activity that it has triggered in the downstream CDN.",
  "authors": [
    "R. Murray",
    "B. Niven-Jenkins"
  ],
  "organizations": [],
  "publication_date": "2016-12-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": "wit",
  "area_ru": "Веб и транспорт Интернета",
  "working_group": "cdni",
  "source_draft": "draft-ietf-cdni-control-triggers-15",
  "page_count": 49,
  "doi": "10.17487/RFC8007",
  "keywords": [
    "CDN",
    "pre-position",
    "invalidate",
    "purge"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc8007/",
    "html": "https://www.rfc-editor.org/rfc/rfc8007.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc8007.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc8007/"
  }
}