RFC3114 · Implementing Company Classification Policy with the S/MIME Security Label

{
  "id": "RFC3114",
  "number": 3114,
  "title_en": "Implementing Company Classification Policy with the S/MIME Security Label",
  "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 discusses how company security policy for data classification can be mapped to the S/MIME security label. Actual policies from three companies provide worked examples. This memo provides information for the Internet community.",
  "authors": [
    "W. Nicolls"
  ],
  "organizations": [],
  "publication_date": "2002-05-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": "smime",
  "source_draft": "draft-ietf-smime-seclabel-04",
  "page_count": 14,
  "doi": "10.17487/RFC3114",
  "keywords": [
    "data",
    "multipurpose",
    "internet mail extensions",
    "access control",
    "information classification",
    "security category"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc3114/",
    "html": "https://www.rfc-editor.org/rfc/rfc3114.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc3114.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc3114/"
  }
}