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

IETF · RFC · RFC3226

RFC3226 · DNSSEC and IPv6 A6 aware server/resolver message size requirements

DNSSEC and IPv6 A6 aware server/resolver message size requirements

This document mandates support for EDNS0 (Extension Mechanisms for DNS) in DNS entities claiming to support either DNS Security Extensions or A6 records. This requirement is necessary because these new features increase the size of DNS messages. If EDNS0 is not supported fall back to TCP will happen, having a detrimental impact on query latency and DNS server load. This document updates RFC 2535 and RFC 2874, by adding new requirements. [STANDARDS-TRACK]

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

This document mandates support for EDNS0 (Extension Mechanisms for DNS) in DNS entities claiming to support either DNS Security Extensions or A6 records. This requirement is necessary because these new features increase the size of DNS messages. If EDNS0 is not supported fall back to TCP will happen, having a detrimental impact on query latency and DNS server load. This document updates RFC 2535 and RFC 2874, by adding new requirements. [STANDARDS-TRACK]

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

updates: RFC2535, RFC2874

updated_by: RFC4033, RFC4034, RFC4035

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

Полные импортированные сведения карточки
{
  "id": "RFC3226",
  "number": 3226,
  "title_en": "DNSSEC and IPv6 A6 aware server/resolver message size requirements",
  "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": "This document mandates support for EDNS0 (Extension Mechanisms for DNS) in DNS entities claiming to support either DNS Security Extensions or A6 records. This requirement is necessary because these new features increase the size of DNS messages. If EDNS0 is not supported fall back to TCP will happen, having a detrimental impact on query latency and DNS server load. This document updates RFC 2535 and RFC 2874, by adding new requirements. [STANDARDS-TRACK]",
  "authors": [
    "O. Gudmundsson"
  ],
  "organizations": [],
  "publication_date": "2001-12-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-message-size-04",
  "page_count": 6,
  "doi": "10.17487/RFC3226",
  "keywords": [
    "DNSSEC",
    "domain name system security extensions",
    "space",
    "security",
    "extensions",
    "EDNS0",
    "Extension Mechanisms for DNSEx"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [
      "RFC2535",
      "RFC2874"
    ],
    "updated_by": [
      "RFC4033",
      "RFC4034",
      "RFC4035"
    ],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc3226/",
    "html": "https://www.rfc-editor.org/rfc/rfc3226.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc3226.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc3226/"
  }
}