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

IETF · RFC · RFC7767

RFC7767 · Application-Initiated Check-Pointing via the Port Control Protocol (PCP)

Application-Initiated Check-Pointing via the Port Control Protocol (PCP)

This document specifies a mechanism for a host to indicate via the Port Control Protocol (PCP) which connections should be protected against network failures. These connections will then be subject to high-availability mechanisms enabled on the network side. This approach assumes that applications and/or users have more visibility about sensitive connections than any heuristic that can be enabled on the network side to guess which connections should be check-pointed.

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

This document specifies a mechanism for a host to indicate via the Port Control Protocol (PCP) which connections should be protected against network failures. These connections will then be subject to high-availability mechanisms enabled on the network side. This approach assumes that applications and/or users have more visibility about sensitive connections than any heuristic that can be enabled on the network side to guess which connections should be check-pointed.

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

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

Полные импортированные сведения карточки
{
  "id": "RFC7767",
  "number": 7767,
  "title_en": "Application-Initiated Check-Pointing via the Port Control Protocol (PCP)",
  "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 specifies a mechanism for a host to indicate via the Port Control Protocol (PCP) which connections should be protected against network failures. These connections will then be subject to high-availability mechanisms enabled on the network side. This approach assumes that applications and/or users have more visibility about sensitive connections than any heuristic that can be enabled on the network side to guess which connections should be check-pointed.",
  "authors": [
    "S. Vinapamula",
    "S. Sivakumar",
    "M. Boucadair",
    "T. Reddy"
  ],
  "organizations": [],
  "publication_date": "2016-02-01",
  "current_status": "INFORMATIONAL",
  "current_status_ru": "Информационный",
  "publication_status": "INFORMATIONAL",
  "publication_status_ru": "Информационный",
  "lifecycle": "informational",
  "lifecycle_ru": "Справочный",
  "stream": "INDEPENDENT",
  "stream_ru": "Независимый поток",
  "area": "",
  "area_ru": "",
  "working_group": "",
  "source_draft": "draft-vinapamula-flow-ha-14",
  "page_count": 12,
  "doi": "10.17487/RFC7767",
  "keywords": [
    "serviceability",
    "SDN",
    "resilience",
    "robustness",
    "network programmability",
    "network API",
    "application control",
    "service-aware networking",
    "automation"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc7767/",
    "html": "https://www.rfc-editor.org/rfc/rfc7767.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc7767.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc7767/"
  }
}