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

IETF · RFC · RFC3225

RFC3225 · Indicating Resolver Support of DNSSEC

Indicating Resolver Support of DNSSEC

In order to deploy DNSSEC (Domain Name System Security Extensions) operationally, DNSSEC aware servers should only perform automatic inclusion of DNSSEC RRs when there is an explicit indication that the resolver can understand those RRs. This document proposes the use of a bit in the EDNS0 header to provide that explicit indication and describes the necessary protocol changes to implement that notification. [STANDARDS-TRACK]

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

In order to deploy DNSSEC (Domain Name System Security Extensions) operationally, DNSSEC aware servers should only perform automatic inclusion of DNSSEC RRs when there is an explicit indication that the resolver can understand those RRs. This document proposes the use of a bit in the EDNS0 header to provide that explicit indication and describes the necessary protocol changes to implement that notification. [STANDARDS-TRACK]

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

updated_by: RFC4033, RFC4034, RFC4035

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

Полные импортированные сведения карточки
{
  "id": "RFC3225",
  "number": 3225,
  "title_en": "Indicating Resolver Support of DNSSEC",
  "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": "In order to deploy DNSSEC (Domain Name System Security Extensions) operationally, DNSSEC aware servers should only perform automatic inclusion of DNSSEC RRs when there is an explicit indication that the resolver can understand those RRs. This document proposes the use of a bit in the EDNS0 header to provide that explicit indication and describes the necessary protocol changes to implement that notification. [STANDARDS-TRACK]",
  "authors": [
    "D. Conrad"
  ],
  "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-dnssec-okbit-03",
  "page_count": 6,
  "doi": "10.17487/RFC3225",
  "keywords": [
    "DNSSEC",
    "domain name system security extensions"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [
      "RFC4033",
      "RFC4034",
      "RFC4035"
    ],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc3225/",
    "html": "https://www.rfc-editor.org/rfc/rfc3225.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc3225.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc3225/"
  }
}