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

IETF · RFC · RFC10026

RFC10026 · Operational Recommendations for DNSSEC Delegation Signer (DS) Automation

Operational Recommendations for DNSSEC Delegation Signer (DS) Automation

Enabling support for automatic acceptance of DNSSEC Delegation Signer (DS) parameters from the Child DNS operator (via RFCs 7344, 8078, and 9615) requires the Parental Agent, often a registry or registrar, to make a number of technical decisions around acceptance checks, error and success reporting, and multi-party issues such as concurrent updates. This document describes recommendations about how these points are best addressed in practice.

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

Enabling support for automatic acceptance of DNSSEC Delegation Signer (DS) parameters from the Child DNS operator (via RFCs 7344, 8078, and 9615) requires the Parental Agent, often a registry or registrar, to make a number of technical decisions around acceptance checks, error and success reporting, and multi-party issues such as concurrent updates. This document describes recommendations about how these points are best addressed in practice.

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

is_also: BCP246

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

Полные импортированные сведения карточки
{
  "id": "RFC10026",
  "number": 10026,
  "title_en": "Operational Recommendations for DNSSEC Delegation Signer (DS) Automation",
  "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": "Enabling support for automatic acceptance of DNSSEC Delegation Signer (DS) parameters from the Child DNS operator (via RFCs 7344, 8078, and 9615) requires the Parental Agent, often a registry or registrar, to make a number of technical decisions around acceptance checks, error and success reporting, and multi-party issues such as concurrent updates. This document describes recommendations about how these points are best addressed in practice.",
  "authors": [
    "S. Sheng",
    "P. Thomassen"
  ],
  "organizations": [],
  "publication_date": "2026-07-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": "ops",
  "area_ru": "Эксплуатация и управление",
  "working_group": "dnsop",
  "source_draft": "draft-ietf-dnsop-ds-automation-09",
  "page_count": 21,
  "doi": "10.17487/RFC10026",
  "keywords": [
    "DNS",
    "DS"
  ],
  "formats": [
    "HTML",
    "TXT",
    "PDF",
    "XML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [
      "BCP246"
    ],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc10026/",
    "html": "https://www.rfc-editor.org/rfc/rfc10026.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc10026.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc10026/"
  }
}