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

IETF · RFC · RFC6376

RFC6376 · DomainKeys Identified Mail (DKIM) Signatures

DomainKeys Identified Mail (DKIM) Signatures

DomainKeys Identified Mail (DKIM) permits a person, role, or organization that owns the signing domain to claim some responsibility for a message by associating the domain with the message. This can be an author's organization, an operational relay, or one of their agents. DKIM separates the question of the identity of the Signer of the message from the purported author of the message. Assertion of responsibility is validated through a cryptographic signature and by querying the Signer's domain directly to retrieve the appropriate public key. Message transit from author to recipient is through relays that typically make no substantive change to the message content and thus preserve the DKIM signature. This memo obsoletes RFC 4871 and RFC 5672. [STANDARDS-TRACK]

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

DomainKeys Identified Mail (DKIM) permits a person, role, or organization that owns the signing domain to claim some responsibility for a message by associating the domain with the message. This can be an author's organization, an operational relay, or one of their agents. DKIM separates the question of the identity of the Signer of the message from the purported author of the message. Assertion of responsibility is validated through a cryptographic signature and by querying the Signer's domain directly to retrieve the appropriate public key. Message transit from author to recipient is through relays that typically make no substantive change to the message content and thus preserve the DKIM signature. This memo obsoletes RFC 4871 and RFC 5672. [STANDARDS-TRACK]

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

obsoletes: RFC4871, RFC5672

updated_by: RFC8301, RFC8463, RFC8553, RFC8616

is_also: STD76

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

Полные импортированные сведения карточки
{
  "id": "RFC6376",
  "number": 6376,
  "title_en": "DomainKeys Identified Mail (DKIM) Signatures",
  "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) permits a person, role, or organization that owns the signing domain to claim some responsibility for a message by associating the domain with the message. This can be an author's organization, an operational relay, or one of their agents. DKIM separates the question of the identity of the Signer of the message from the purported author of the message. Assertion of responsibility is validated through a cryptographic signature and by querying the Signer's domain directly to retrieve the appropriate public key. Message transit from author to recipient is through relays that typically make no substantive change to the message content and thus preserve the DKIM signature. This memo obsoletes RFC 4871 and RFC 5672. [STANDARDS-TRACK]",
  "authors": [
    "D. Crocker",
    "T. Hansen",
    "M. Kucherawy"
  ],
  "organizations": [],
  "publication_date": "2011-09-01",
  "current_status": "INTERNET STANDARD",
  "current_status_ru": "Стандарт Интернета",
  "publication_status": "DRAFT STANDARD",
  "publication_status_ru": "Проект стандарта (устаревшая стадия)",
  "lifecycle": "active",
  "lifecycle_ru": "Действующий",
  "stream": "IETF",
  "stream_ru": "IETF",
  "area": "art",
  "area_ru": "Приложения и взаимодействие в реальном времени",
  "working_group": "dkim",
  "source_draft": "draft-ietf-dkim-rfc4871bis-15",
  "page_count": 76,
  "doi": "10.17487/RFC6376",
  "keywords": [
    "email",
    "architecture",
    "abuse",
    "verification",
    "anti-abuse",
    "identity",
    "integrity",
    "responsible",
    "author",
    "sender",
    "originator",
    "email filtering",
    "anti-phishing",
    "mail signature"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [
      "RFC4871",
      "RFC5672"
    ],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [
      "RFC8301",
      "RFC8463",
      "RFC8553",
      "RFC8616"
    ],
    "is_also": [
      "STD76"
    ],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc6376/",
    "html": "https://www.rfc-editor.org/rfc/rfc6376.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc6376.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc6376/"
  }
}