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

IETF · RFC · RFC7912

RFC7912 · Message Authorizing Email Header Field and Its Use for the Draft and Release Procedure

Message Authorizing Email Header Field and Its Use for the Draft and Release Procedure

This document describes a procedure for when a Military Message Handling System (MMHS) message is composed by one user and is only released to the mail transfer system when one or more Authorizing Users authorize release of the message by adding the MMHS-Authorizing-Users header field. The resulting message can be optionally signed by the sender and/or reviewer, allowing recipients to verify both the original signature (if any) and the review signatures.

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

This document describes a procedure for when a Military Message Handling System (MMHS) message is composed by one user and is only released to the mail transfer system when one or more Authorizing Users authorize release of the message by adding the MMHS-Authorizing-Users header field. The resulting message can be optionally signed by the sender and/or reviewer, allowing recipients to verify both the original signature (if any) and the review signatures.

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

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

Полные импортированные сведения карточки
{
  "id": "RFC7912",
  "number": 7912,
  "title_en": "Message Authorizing Email Header Field and Its Use for the Draft and Release Procedure",
  "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 procedure for when a Military Message Handling System (MMHS) message is composed by one user and is only released to the mail transfer system when one or more Authorizing Users authorize release of the message by adding the MMHS-Authorizing-Users header field. The resulting message can be optionally signed by the sender and/or reviewer, allowing recipients to verify both the original signature (if any) and the review signatures.",
  "authors": [
    "A. Melnikov"
  ],
  "organizations": [],
  "publication_date": "2016-06-01",
  "current_status": "INFORMATIONAL",
  "current_status_ru": "Информационный",
  "publication_status": "INFORMATIONAL",
  "publication_status_ru": "Информационный",
  "lifecycle": "informational",
  "lifecycle_ru": "Справочный",
  "stream": "INDEPENDENT",
  "stream_ru": "Независимый поток",
  "area": "",
  "area_ru": "",
  "working_group": "",
  "source_draft": "draft-melnikov-mmhs-authorizing-users-14",
  "page_count": 11,
  "doi": "10.17487/RFC7912",
  "keywords": [
    "MMHS",
    "S/MIME",
    "MIXER",
    "email"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc7912/",
    "html": "https://www.rfc-editor.org/rfc/rfc7912.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc7912.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc7912/"
  }
}