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

IETF · RFC · RFC5452

RFC5452 · Measures for Making DNS More Resilient against Forged Answers

Measures for Making DNS More Resilient against Forged Answers

The current Internet climate poses serious threats to the Domain Name System. In the interim period before the DNS protocol can be secured more fully, measures can already be taken to harden the DNS to make 'spoofing' a recursing nameserver many orders of magnitude harder. Even a cryptographically secured DNS benefits from having the ability to discard bogus responses quickly, as this potentially saves large amounts of computation. By describing certain behavior that has previously not been standardized, this document sets out how to make the DNS more resilient against accepting incorrect responses. This document updates RFC 2181. [STANDARDS-TRACK]

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

The current Internet climate poses serious threats to the Domain Name System. In the interim period before the DNS protocol can be secured more fully, measures can already be taken to harden the DNS to make 'spoofing' a recursing nameserver many orders of magnitude harder. Even a cryptographically secured DNS benefits from having the ability to discard bogus responses quickly, as this potentially saves large amounts of computation. By describing certain behavior that has previously not been standardized, this document sets out how to make the DNS more resilient against accepting incorrect responses. This document updates RFC 2181. [STANDARDS-TRACK]

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

updates: RFC2181

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

Полные импортированные сведения карточки
{
  "id": "RFC5452",
  "number": 5452,
  "title_en": "Measures for Making DNS More Resilient against Forged Answers",
  "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 current Internet climate poses serious threats to the Domain Name System. In the interim period before the DNS protocol can be secured more fully, measures can already be taken to harden the DNS to make 'spoofing' a recursing nameserver many orders of magnitude harder. Even a cryptographically secured DNS benefits from having the ability to discard bogus responses quickly, as this potentially saves large amounts of computation. By describing certain behavior that has previously not been standardized, this document sets out how to make the DNS more resilient against accepting incorrect responses. This document updates RFC 2181. [STANDARDS-TRACK]",
  "authors": [
    "A. Hubert",
    "R. van Mook"
  ],
  "organizations": [],
  "publication_date": "2009-01-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": "int",
  "area_ru": "Интернет",
  "working_group": "dnsext",
  "source_draft": "draft-ietf-dnsext-forgery-resilience-10",
  "page_count": 18,
  "doi": "10.17487/RFC5452",
  "keywords": [
    "spoofing",
    "source port",
    "hardening"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [
      "RFC2181"
    ],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc5452/",
    "html": "https://www.rfc-editor.org/rfc/rfc5452.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc5452.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc5452/"
  }
}