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

IETF · RFC · RFC4986

RFC4986 · Requirements Related to DNS Security (DNSSEC) Trust Anchor Rollover

Requirements Related to DNS Security (DNSSEC) Trust Anchor Rollover

Every DNS security-aware resolver must have at least one Trust Anchor to use as the basis for validating responses from DNS signed zones. For various reasons, most DNS security-aware resolvers are expected to have several Trust Anchors. For some operations, manual monitoring and updating of Trust Anchors may be feasible, but many operations will require automated methods for updating Trust Anchors in their security-aware resolvers. This document identifies the requirements that must be met by an automated DNS Trust Anchor rollover solution for security-aware DNS resolvers. This memo provides information for the Internet community.

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

Every DNS security-aware resolver must have at least one Trust Anchor to use as the basis for validating responses from DNS signed zones. For various reasons, most DNS security-aware resolvers are expected to have several Trust Anchors. For some operations, manual monitoring and updating of Trust Anchors may be feasible, but many operations will require automated methods for updating Trust Anchors in their security-aware resolvers. This document identifies the requirements that must be met by an automated DNS Trust Anchor rollover solution for security-aware DNS resolvers. This memo provides information for the Internet community.

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

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

Полные импортированные сведения карточки
{
  "id": "RFC4986",
  "number": 4986,
  "title_en": "Requirements Related to DNS Security (DNSSEC) Trust Anchor Rollover",
  "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": "Every DNS security-aware resolver must have at least one Trust Anchor to use as the basis for validating responses from DNS signed zones. For various reasons, most DNS security-aware resolvers are expected to have several Trust Anchors. For some operations, manual monitoring and updating of Trust Anchors may be feasible, but many operations will require automated methods for updating Trust Anchors in their security-aware resolvers. This document identifies the requirements that must be met by an automated DNS Trust Anchor rollover solution for security-aware DNS resolvers. This memo provides information for the Internet community.",
  "authors": [
    "H. Eland",
    "R. Mundy",
    "S. Crocker",
    "S. Krishnaswamy"
  ],
  "organizations": [],
  "publication_date": "2007-08-01",
  "current_status": "INFORMATIONAL",
  "current_status_ru": "Информационный",
  "publication_status": "INFORMATIONAL",
  "publication_status_ru": "Информационный",
  "lifecycle": "informational",
  "lifecycle_ru": "Справочный",
  "stream": "IETF",
  "stream_ru": "IETF",
  "area": "int",
  "area_ru": "Интернет",
  "working_group": "dnsext",
  "source_draft": "draft-ietf-dnsext-rollover-requirements-04",
  "page_count": 11,
  "doi": "10.17487/RFC4986",
  "keywords": [
    "dns signed zone"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc4986/",
    "html": "https://www.rfc-editor.org/rfc/rfc4986.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc4986.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc4986/"
  }
}