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

IETF · RFC · RFC9447

RFC9447 · Automated Certificate Management Environment (ACME) Challenges Using an Authority Token

Automated Certificate Management Environment (ACME) Challenges Using an Authority Token

Some proposed extensions to the Automated Certificate Management Environment (ACME) rely on proving eligibility for certificates through consulting an external authority that issues a token according to a particular policy. This document specifies a generic Authority Token Challenge for ACME that supports subtype claims for different identifiers or namespaces that can be defined separately for specific applications.

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

Some proposed extensions to the Automated Certificate Management Environment (ACME) rely on proving eligibility for certificates through consulting an external authority that issues a token according to a particular policy. This document specifies a generic Authority Token Challenge for ACME that supports subtype claims for different identifiers or namespaces that can be defined separately for specific applications.

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

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

Полные импортированные сведения карточки
{
  "id": "RFC9447",
  "number": 9447,
  "title_en": "Automated Certificate Management Environment (ACME) Challenges Using an Authority Token",
  "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": "Some proposed extensions to the Automated Certificate Management Environment (ACME) rely on proving eligibility for certificates through consulting an external authority that issues a token according to a particular policy. This document specifies a generic Authority Token Challenge for ACME that supports subtype claims for different identifiers or namespaces that can be defined separately for specific applications.",
  "authors": [
    "J. Peterson",
    "M. Barnes",
    "D. Hancock",
    "C. Wendt"
  ],
  "organizations": [],
  "publication_date": "2023-09-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": "sec",
  "area_ru": "Безопасность",
  "working_group": "acme",
  "source_draft": "draft-ietf-acme-authority-token-09",
  "page_count": 11,
  "doi": "10.17487/RFC9447",
  "keywords": [
    "ACME"
  ],
  "formats": [
    "HTML",
    "TXT",
    "PDF",
    "XML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc9447/",
    "html": "https://www.rfc-editor.org/rfc/rfc9447.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc9447.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc9447/"
  }
}