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

IETF · RFC · RFC6411

RFC6411 · Applicability of Keying Methods for RSVP Security

Applicability of Keying Methods for RSVP Security

The Resource reSerVation Protocol (RSVP) allows hop-by-hop integrity protection of RSVP neighbors. This requires messages to be cryptographically protected using a shared secret between participating nodes. This document compares group keying for RSVP with per-neighbor or per-interface keying, and discusses the associated key provisioning methods as well as applicability and limitations of these approaches. This document also discusses applicability of encrypting RSVP messages. This document is not an Internet Standards Track specification; it is published for informational purposes.

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

The Resource reSerVation Protocol (RSVP) allows hop-by-hop integrity protection of RSVP neighbors. This requires messages to be cryptographically protected using a shared secret between participating nodes. This document compares group keying for RSVP with per-neighbor or per-interface keying, and discusses the associated key provisioning methods as well as applicability and limitations of these approaches. This document also discusses applicability of encrypting RSVP messages. This document is not an Internet Standards Track specification; it is published for informational purposes.

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

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

Полные импортированные сведения карточки
{
  "id": "RFC6411",
  "number": 6411,
  "title_en": "Applicability of Keying Methods for RSVP Security",
  "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": "The Resource reSerVation Protocol (RSVP) allows hop-by-hop integrity protection of RSVP neighbors. This requires messages to be cryptographically protected using a shared secret between participating nodes. This document compares group keying for RSVP with per-neighbor or per-interface keying, and discusses the associated key provisioning methods as well as applicability and limitations of these approaches. This document also discusses applicability of encrypting RSVP messages. This document is not an Internet Standards Track specification; it is published for informational purposes.",
  "authors": [
    "M. Behringer",
    "F. Le Faucheur",
    "B. Weis"
  ],
  "organizations": [],
  "publication_date": "2011-10-01",
  "current_status": "INFORMATIONAL",
  "current_status_ru": "Информационный",
  "publication_status": "INFORMATIONAL",
  "publication_status_ru": "Информационный",
  "lifecycle": "informational",
  "lifecycle_ru": "Справочный",
  "stream": "IETF",
  "stream_ru": "IETF",
  "area": "wit",
  "area_ru": "Веб и транспорт Интернета",
  "working_group": "tsvwg",
  "source_draft": "draft-ietf-tsvwg-rsvp-security-groupkeying-11",
  "page_count": 19,
  "doi": "10.17487/RFC6411",
  "keywords": [
    "RSVP authentication",
    "RSVP integrity",
    "Resource reservation protocol",
    "GDOI",
    "Group domain of interpretation"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc6411/",
    "html": "https://www.rfc-editor.org/rfc/rfc6411.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc6411.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc6411/"
  }
}