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

IETF · RFC · RFC7696

RFC7696 · Guidelines for Cryptographic Algorithm Agility and Selecting Mandatory-to-Implement Algorithms

Guidelines for Cryptographic Algorithm Agility and Selecting Mandatory-to-Implement Algorithms

Many IETF protocols use cryptographic algorithms to provide confidentiality, integrity, authentication, or digital signature. Communicating peers must support a common set of cryptographic algorithms for these mechanisms to work properly. This memo provides guidelines to ensure that protocols have the ability to migrate from one mandatory-to-implement algorithm suite to another over time.

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

Many IETF protocols use cryptographic algorithms to provide confidentiality, integrity, authentication, or digital signature. Communicating peers must support a common set of cryptographic algorithms for these mechanisms to work properly. This memo provides guidelines to ensure that protocols have the ability to migrate from one mandatory-to-implement algorithm suite to another over time.

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

is_also: BCP201

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

Полные импортированные сведения карточки
{
  "id": "RFC7696",
  "number": 7696,
  "title_en": "Guidelines for Cryptographic Algorithm Agility and Selecting Mandatory-to-Implement Algorithms",
  "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": "Many IETF protocols use cryptographic algorithms to provide confidentiality, integrity, authentication, or digital signature. Communicating peers must support a common set of cryptographic algorithms for these mechanisms to work properly. This memo provides guidelines to ensure that protocols have the ability to migrate from one mandatory-to-implement algorithm suite to another over time.",
  "authors": [
    "R. Housley"
  ],
  "organizations": [],
  "publication_date": "2015-11-01",
  "current_status": "BEST CURRENT PRACTICE",
  "current_status_ru": "Лучшая современная практика",
  "publication_status": "BEST CURRENT PRACTICE",
  "publication_status_ru": "Лучшая современная практика",
  "lifecycle": "active",
  "lifecycle_ru": "Действующий",
  "stream": "IETF",
  "stream_ru": "IETF",
  "area": "",
  "area_ru": "",
  "working_group": "NON WORKING GROUP",
  "source_draft": "draft-iab-crypto-alg-agility-08",
  "page_count": 19,
  "doi": "10.17487/RFC7696",
  "keywords": [],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [
      "BCP201"
    ],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc7696/",
    "html": "https://www.rfc-editor.org/rfc/rfc7696.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc7696.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc7696/"
  }
}