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

IETF · RFC · RFC5016

RFC5016 · Requirements for a DomainKeys Identified Mail (DKIM) Signing Practices Protocol

Requirements for a DomainKeys Identified Mail (DKIM) Signing Practices Protocol

DomainKeys Identified Mail (DKIM) provides a cryptographic mechanism for domains to assert responsibility for the messages they handle. A related mechanism will allow an administrator to publish various statements about their DKIM signing practices. This document defines requirements for this mechanism, distinguishing between those that must be satisfied (MUST), and those that are highly desirable (SHOULD). This memo provides information for the Internet community.

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

DomainKeys Identified Mail (DKIM) provides a cryptographic mechanism for domains to assert responsibility for the messages they handle. A related mechanism will allow an administrator to publish various statements about their DKIM signing practices. This document defines requirements for this mechanism, distinguishing between those that must be satisfied (MUST), and those that are highly desirable (SHOULD). This memo provides information for the Internet community.

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

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

Полные импортированные сведения карточки
{
  "id": "RFC5016",
  "number": 5016,
  "title_en": "Requirements for a DomainKeys Identified Mail (DKIM) Signing Practices Protocol",
  "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": "DomainKeys Identified Mail (DKIM) provides a cryptographic mechanism for domains to assert responsibility for the messages they handle. A related mechanism will allow an administrator to publish various statements about their DKIM signing practices. This document defines requirements for this mechanism, distinguishing between those that must be satisfied (MUST), and those that are highly desirable (SHOULD). This memo provides information for the Internet community.",
  "authors": [
    "M. Thomas"
  ],
  "organizations": [],
  "publication_date": "2007-10-01",
  "current_status": "INFORMATIONAL",
  "current_status_ru": "Информационный",
  "publication_status": "INFORMATIONAL",
  "publication_status_ru": "Информационный",
  "lifecycle": "informational",
  "lifecycle_ru": "Справочный",
  "stream": "IETF",
  "stream_ru": "IETF",
  "area": "art",
  "area_ru": "Приложения и взаимодействие в реальном времени",
  "working_group": "dkim",
  "source_draft": "draft-ietf-dkim-ssp-requirements-05",
  "page_count": 15,
  "doi": "10.17487/RFC5016",
  "keywords": [
    "cryptographic"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc5016/",
    "html": "https://www.rfc-editor.org/rfc/rfc5016.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc5016.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc5016/"
  }
}