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

IETF · RFC · RFC3755

RFC3755 · Legacy Resolver Compatibility for Delegation Signer (DS)

Legacy Resolver Compatibility for Delegation Signer (DS)

As the DNS Security (DNSSEC) specifications have evolved, the syntax and semantics of the DNSSEC resource records (RRs) have changed. Many deployed nameservers understand variants of these semantics. Dangerous interactions can occur when a resolver that understands an earlier version of these semantics queries an authoritative server that understands the new delegation signer semantics, including at least one failure scenario that will cause an unsecured zone to be unresolvable. This document changes the type codes and mnemonics of the DNSSEC RRs (SIG, KEY, and NXT) to avoid those interactions. [STANDARDS-TRACK]

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

As the DNS Security (DNSSEC) specifications have evolved, the syntax and semantics of the DNSSEC resource records (RRs) have changed. Many deployed nameservers understand variants of these semantics. Dangerous interactions can occur when a resolver that understands an earlier version of these semantics queries an authoritative server that understands the new delegation signer semantics, including at least one failure scenario that will cause an unsecured zone to be unresolvable. This document changes the type codes and mnemonics of the DNSSEC RRs (SIG, KEY, and NXT) to avoid those interactions. [STANDARDS-TRACK]

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

obsoleted_by: RFC4033, RFC4034, RFC4035

updates: RFC2535, RFC3658

updated_by: RFC3757, RFC3845

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

Полные импортированные сведения карточки
{
  "id": "RFC3755",
  "number": 3755,
  "title_en": "Legacy Resolver Compatibility for Delegation Signer (DS)",
  "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": "As the DNS Security (DNSSEC) specifications have evolved, the syntax and semantics of the DNSSEC resource records (RRs) have changed. Many deployed nameservers understand variants of these semantics. Dangerous interactions can occur when a resolver that understands an earlier version of these semantics queries an authoritative server that understands the new delegation signer semantics, including at least one failure scenario that will cause an unsecured zone to be unresolvable. This document changes the type codes and mnemonics of the DNSSEC RRs (SIG, KEY, and NXT) to avoid those interactions. [STANDARDS-TRACK]",
  "authors": [
    "S. Weiler"
  ],
  "organizations": [],
  "publication_date": "2004-05-01",
  "current_status": "PROPOSED STANDARD",
  "current_status_ru": "Предлагаемый стандарт",
  "publication_status": "PROPOSED STANDARD",
  "publication_status_ru": "Предлагаемый стандарт",
  "lifecycle": "superseded",
  "lifecycle_ru": "Заменён",
  "stream": "IETF",
  "stream_ru": "IETF",
  "area": "int",
  "area_ru": "Интернет",
  "working_group": "dnsext",
  "source_draft": "draft-ietf-dnsext-dnssec-2535typecode-change-06",
  "page_count": 9,
  "doi": "10.17487/RFC3755",
  "keywords": [
    "dnssec",
    "DNS Security",
    "rr",
    "resource record",
    "DNS-SECEXT",
    "dns",
    "authentication",
    "nsec",
    "nextsecure"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [
      "RFC4033",
      "RFC4034",
      "RFC4035"
    ],
    "updates": [
      "RFC2535",
      "RFC3658"
    ],
    "updated_by": [
      "RFC3757",
      "RFC3845"
    ],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc3755/",
    "html": "https://www.rfc-editor.org/rfc/rfc3755.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc3755.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc3755/"
  }
}