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

IETF · RFC · RFC3560

RFC3560 · Use of the RSAES-OAEP Key Transport Algorithm in Cryptographic Message Syntax (CMS)

Use of the RSAES-OAEP Key Transport Algorithm in Cryptographic Message Syntax (CMS)

This document describes the conventions for using the RSAES-OAEP key transport algorithm with the Cryptographic Message Syntax (CMS). The CMS specifies the enveloped-data content type, which consists of an encrypted content and encrypted content-encryption keys for one or more recipients. The RSAES-OAEP key transport algorithm can be used to encrypt content-encryption keys for intended recipients. [STANDARDS-TRACK]

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

This document describes the conventions for using the RSAES-OAEP key transport algorithm with the Cryptographic Message Syntax (CMS). The CMS specifies the enveloped-data content type, which consists of an encrypted content and encrypted content-encryption keys for one or more recipients. The RSAES-OAEP key transport algorithm can be used to encrypt content-encryption keys for intended recipients. [STANDARDS-TRACK]

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

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

Полные импортированные сведения карточки
{
  "id": "RFC3560",
  "number": 3560,
  "title_en": "Use of the RSAES-OAEP Key Transport Algorithm in Cryptographic Message Syntax (CMS)",
  "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 the conventions for using the RSAES-OAEP key transport algorithm with the Cryptographic Message Syntax (CMS). The CMS specifies the enveloped-data content type, which consists of an encrypted content and encrypted content-encryption keys for one or more recipients. The RSAES-OAEP key transport algorithm can be used to encrypt content-encryption keys for intended recipients. [STANDARDS-TRACK]",
  "authors": [
    "R. Housley"
  ],
  "organizations": [],
  "publication_date": "2003-07-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": "sec",
  "area_ru": "Безопасность",
  "working_group": "smime",
  "source_draft": "draft-ietf-smime-cms-rsaes-oaep-07",
  "page_count": 18,
  "doi": "10.17487/RFC3560",
  "keywords": [
    "CMS",
    "Cryptographic Message Syntax",
    "security encryption"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc3560/",
    "html": "https://www.rfc-editor.org/rfc/rfc3560.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc3560.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc3560/"
  }
}