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

IETF · RFC · RFC7165

RFC7165 · Use Cases and Requirements for JSON Object Signing and Encryption (JOSE)

Use Cases and Requirements for JSON Object Signing and Encryption (JOSE)

Many Internet applications have a need for object-based security mechanisms in addition to security mechanisms at the network layer or transport layer. For many years, the Cryptographic Message Syntax (CMS) has provided a binary secure object format based on ASN.1. Over time, binary object encodings such as ASN.1 have become less common than text-based encodings, such as the JavaScript Object Notation (JSON). This document defines a set of use cases and requirements for a secure object format encoded using JSON, drawn from a variety of application security mechanisms currently in development.

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

Many Internet applications have a need for object-based security mechanisms in addition to security mechanisms at the network layer or transport layer. For many years, the Cryptographic Message Syntax (CMS) has provided a binary secure object format based on ASN.1. Over time, binary object encodings such as ASN.1 have become less common than text-based encodings, such as the JavaScript Object Notation (JSON). This document defines a set of use cases and requirements for a secure object format encoded using JSON, drawn from a variety of application security mechanisms currently in development.

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

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

Полные импортированные сведения карточки
{
  "id": "RFC7165",
  "number": 7165,
  "title_en": "Use Cases and Requirements for JSON Object Signing and Encryption (JOSE)",
  "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": "Many Internet applications have a need for object-based security mechanisms in addition to security mechanisms at the network layer or transport layer. For many years, the Cryptographic Message Syntax (CMS) has provided a binary secure object format based on ASN.1. Over time, binary object encodings such as ASN.1 have become less common than text-based encodings, such as the JavaScript Object Notation (JSON). This document defines a set of use cases and requirements for a secure object format encoded using JSON, drawn from a variety of application security mechanisms currently in development.",
  "authors": [
    "R. Barnes"
  ],
  "organizations": [],
  "publication_date": "2014-04-01",
  "current_status": "INFORMATIONAL",
  "current_status_ru": "Информационный",
  "publication_status": "INFORMATIONAL",
  "publication_status_ru": "Информационный",
  "lifecycle": "informational",
  "lifecycle_ru": "Справочный",
  "stream": "IETF",
  "stream_ru": "IETF",
  "area": "sec",
  "area_ru": "Безопасность",
  "working_group": "jose",
  "source_draft": "draft-ietf-jose-use-cases-06",
  "page_count": 25,
  "doi": "10.17487/RFC7165",
  "keywords": [
    "JWS",
    "JWE",
    "JWK",
    "JWA",
    "JWT",
    "CMS",
    "S/MIME",
    "JOSE",
    "XMPP",
    "ALTO",
    "OAuth"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc7165/",
    "html": "https://www.rfc-editor.org/rfc/rfc7165.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc7165.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc7165/"
  }
}