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

IETF · RFC · RFC6277

RFC6277 · Online Certificate Status Protocol Algorithm Agility

Online Certificate Status Protocol Algorithm Agility

The Online Certificate Status Protocol (OCSP) requires server responses to be signed but does not specify a mechanism for selecting the signature algorithm to be used. This may lead to avoidable interoperability failures in contexts where multiple signature algorithms are in use. This document specifies rules for server signature algorithm selection and an extension that allows a client to advise a server that specific signature algorithms are supported. [STANDARDS-TRACK]

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

The Online Certificate Status Protocol (OCSP) requires server responses to be signed but does not specify a mechanism for selecting the signature algorithm to be used. This may lead to avoidable interoperability failures in contexts where multiple signature algorithms are in use. This document specifies rules for server signature algorithm selection and an extension that allows a client to advise a server that specific signature algorithms are supported. [STANDARDS-TRACK]

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

obsoleted_by: RFC6960

updates: RFC2560

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

Полные импортированные сведения карточки
{
  "id": "RFC6277",
  "number": 6277,
  "title_en": "Online Certificate Status Protocol Algorithm Agility",
  "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 Online Certificate Status Protocol (OCSP) requires server responses to be signed but does not specify a mechanism for selecting the signature algorithm to be used. This may lead to avoidable interoperability failures in contexts where multiple signature algorithms are in use. This document specifies rules for server signature algorithm selection and an extension that allows a client to advise a server that specific signature algorithms are supported. [STANDARDS-TRACK]",
  "authors": [
    "S. Santesson",
    "P. Hallam-Baker"
  ],
  "organizations": [],
  "publication_date": "2011-06-01",
  "current_status": "PROPOSED STANDARD",
  "current_status_ru": "Предлагаемый стандарт",
  "publication_status": "PROPOSED STANDARD",
  "publication_status_ru": "Предлагаемый стандарт",
  "lifecycle": "superseded",
  "lifecycle_ru": "Заменён",
  "stream": "IETF",
  "stream_ru": "IETF",
  "area": "sec",
  "area_ru": "Безопасность",
  "working_group": "pkix",
  "source_draft": "draft-ietf-pkix-ocspagility-11",
  "page_count": 11,
  "doi": "10.17487/RFC6277",
  "keywords": [
    "ocsp"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [
      "RFC6960"
    ],
    "updates": [
      "RFC2560"
    ],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc6277/",
    "html": "https://www.rfc-editor.org/rfc/rfc6277.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc6277.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc6277/"
  }
}