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

IETF · RFC · RFC8945

RFC8945 · Secret Key Transaction Authentication for DNS (TSIG)

Secret Key Transaction Authentication for DNS (TSIG)

This document describes a protocol for transaction-level authentication using shared secrets and one-way hashing. It can be used to authenticate dynamic updates to a DNS zone as coming from an approved client or to authenticate responses as coming from an approved name server. No recommendation is made here for distributing the shared secrets; it is expected that a network administrator will statically configure name servers and clients using some out-of-band mechanism. This document obsoletes RFCs 2845 and 4635.

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

This document describes a protocol for transaction-level authentication using shared secrets and one-way hashing. It can be used to authenticate dynamic updates to a DNS zone as coming from an approved client or to authenticate responses as coming from an approved name server. No recommendation is made here for distributing the shared secrets; it is expected that a network administrator will statically configure name servers and clients using some out-of-band mechanism. This document obsoletes RFCs 2845 and 4635.

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

obsoletes: RFC2845, RFC4635

is_also: STD93

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

Полные импортированные сведения карточки
{
  "id": "RFC8945",
  "number": 8945,
  "title_en": "Secret Key Transaction Authentication for DNS (TSIG)",
  "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 describes a protocol for transaction-level authentication using shared secrets and one-way hashing. It can be used to authenticate dynamic updates to a DNS zone as coming from an approved client or to authenticate responses as coming from an approved name server. No recommendation is made here for distributing the shared secrets; it is expected that a network administrator will statically configure name servers and clients using some out-of-band mechanism. This document obsoletes RFCs 2845 and 4635.",
  "authors": [
    "F. Dupont",
    "S. Morris",
    "P. Vixie",
    "D. Eastlake 3rd",
    "O. Gudmundsson",
    "B. Wellington"
  ],
  "organizations": [],
  "publication_date": "2020-11-01",
  "current_status": "INTERNET STANDARD",
  "current_status_ru": "Стандарт Интернета",
  "publication_status": "INTERNET 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-rfc2845bis-09",
  "page_count": 22,
  "doi": "10.17487/RFC8945",
  "keywords": [],
  "formats": [
    "HTML",
    "TXT",
    "PDF",
    "XML"
  ],
  "relations": {
    "obsoletes": [
      "RFC2845",
      "RFC4635"
    ],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [
      "STD93"
    ],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc8945/",
    "html": "https://www.rfc-editor.org/rfc/rfc8945.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc8945.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc8945/"
  }
}