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

IETF · RFC · RFC8198

RFC8198 · Aggressive Use of DNSSEC-Validated Cache

Aggressive Use of DNSSEC-Validated Cache

The DNS relies upon caching to scale; however, the cache lookup generally requires an exact match. This document specifies the use of NSEC/NSEC3 resource records to allow DNSSEC-validating resolvers to generate negative answers within a range and positive answers from wildcards. This increases performance, decreases latency, decreases resource utilization on both authoritative and recursive servers, and increases privacy. Also, it may help increase resilience to certain DoS attacks in some circumstances. This document updates RFC 4035 by allowing validating resolvers to generate negative answers based upon NSEC/NSEC3 records and positive answers in the presence of wildcards.

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

The DNS relies upon caching to scale; however, the cache lookup generally requires an exact match. This document specifies the use of NSEC/NSEC3 resource records to allow DNSSEC-validating resolvers to generate negative answers within a range and positive answers from wildcards. This increases performance, decreases latency, decreases resource utilization on both authoritative and recursive servers, and increases privacy. Also, it may help increase resilience to certain DoS attacks in some circumstances. This document updates RFC 4035 by allowing validating resolvers to generate negative answers based upon NSEC/NSEC3 records and positive answers in the presence of wildcards.

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

updates: RFC4035

updated_by: RFC9077

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

Полные импортированные сведения карточки
{
  "id": "RFC8198",
  "number": 8198,
  "title_en": "Aggressive Use of DNSSEC-Validated Cache",
  "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 DNS relies upon caching to scale; however, the cache lookup generally requires an exact match. This document specifies the use of NSEC/NSEC3 resource records to allow DNSSEC-validating resolvers to generate negative answers within a range and positive answers from wildcards. This increases performance, decreases latency, decreases resource utilization on both authoritative and recursive servers, and increases privacy. Also, it may help increase resilience to certain DoS attacks in some circumstances. This document updates RFC 4035 by allowing validating resolvers to generate negative answers based upon NSEC/NSEC3 records and positive answers in the presence of wildcards.",
  "authors": [
    "K. Fujiwara",
    "A. Kato",
    "W. Kumari"
  ],
  "organizations": [],
  "publication_date": "2017-07-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": "ops",
  "area_ru": "Эксплуатация и управление",
  "working_group": "dnsop",
  "source_draft": "draft-ietf-dnsop-nsec-aggressiveuse-10",
  "page_count": 13,
  "doi": "10.17487/RFC8198",
  "keywords": [
    "Negative cache",
    "NCACHE",
    "NSEC",
    "NSEC3"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [
      "RFC4035"
    ],
    "updated_by": [
      "RFC9077"
    ],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc8198/",
    "html": "https://www.rfc-editor.org/rfc/rfc8198.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc8198.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc8198/"
  }
}