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

IETF · RFC · RFC9276

RFC9276 · Guidance for NSEC3 Parameter Settings

Guidance for NSEC3 Parameter Settings

NSEC3 is a DNSSEC mechanism providing proof of nonexistence by asserting that there are no names that exist between two domain names within a zone. Unlike its counterpart NSEC, NSEC3 avoids directly disclosing the bounding domain name pairs. This document provides guidance on setting NSEC3 parameters based on recent operational deployment experience. This document updates RFC 5155 with guidance about selecting NSEC3 iteration and salt parameters.

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

NSEC3 is a DNSSEC mechanism providing proof of nonexistence by asserting that there are no names that exist between two domain names within a zone. Unlike its counterpart NSEC, NSEC3 avoids directly disclosing the bounding domain name pairs. This document provides guidance on setting NSEC3 parameters based on recent operational deployment experience. This document updates RFC 5155 with guidance about selecting NSEC3 iteration and salt parameters.

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

updates: RFC5155

is_also: BCP236

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

Полные импортированные сведения карточки
{
  "id": "RFC9276",
  "number": 9276,
  "title_en": "Guidance for NSEC3 Parameter Settings",
  "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": "NSEC3 is a DNSSEC mechanism providing proof of nonexistence by asserting that there are no names that exist between two domain names within a zone. Unlike its counterpart NSEC, NSEC3 avoids directly disclosing the bounding domain name pairs. This document provides guidance on setting NSEC3 parameters based on recent operational deployment experience. This document updates RFC 5155 with guidance about selecting NSEC3 iteration and salt parameters.",
  "authors": [
    "W. Hardaker",
    "V. Dukhovni"
  ],
  "organizations": [],
  "publication_date": "2022-08-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-nsec3-guidance-10",
  "page_count": 10,
  "doi": "10.17487/RFC9276",
  "keywords": [
    "DNSSEC",
    "DNS",
    "NSEC3",
    "NSEC",
    "Denial of Existence"
  ],
  "formats": [
    "HTML",
    "TXT",
    "PDF",
    "XML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [
      "RFC5155"
    ],
    "updated_by": [],
    "is_also": [
      "BCP236"
    ],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc9276/",
    "html": "https://www.rfc-editor.org/rfc/rfc9276.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc9276.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc9276/"
  }
}