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

IETF · RFC · RFC2632

RFC2632 · S/MIME Version 3 Certificate Handling

S/MIME Version 3 Certificate Handling

S/MIME (Secure/Multipurpose Internet Mail Extensions), provides a method to send and receive secure MIME messages. Before using a public key to provide security services, the S/MIME agent MUST certify that the public key is valid. S/MIME agents MUST use PKIX certificates to validate public keys as described in the Internet X.509 Public Key Infrastructure (PKIX) Certificate and CRL Profile. [STANDARDS-TRACK]

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

S/MIME (Secure/Multipurpose Internet Mail Extensions), provides a method to send and receive secure MIME messages. Before using a public key to provide security services, the S/MIME agent MUST certify that the public key is valid. S/MIME agents MUST use PKIX certificates to validate public keys as described in the Internet X.509 Public Key Infrastructure (PKIX) Certificate and CRL Profile. [STANDARDS-TRACK]

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

obsoleted_by: RFC3850

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

Полные импортированные сведения карточки
{
  "id": "RFC2632",
  "number": 2632,
  "title_en": "S/MIME Version 3 Certificate Handling",
  "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": "S/MIME (Secure/Multipurpose Internet Mail Extensions), provides a method to send and receive secure MIME messages. Before using a public key to provide security services, the S/MIME agent MUST certify that the public key is valid. S/MIME agents MUST use PKIX certificates to validate public keys as described in the Internet X.509 Public Key Infrastructure (PKIX) Certificate and CRL Profile. [STANDARDS-TRACK]",
  "authors": [
    "B. Ramsdell"
  ],
  "organizations": [],
  "publication_date": "1999-06-01",
  "current_status": "PROPOSED STANDARD",
  "current_status_ru": "Предлагаемый стандарт",
  "publication_status": "PROPOSED STANDARD",
  "publication_status_ru": "Предлагаемый стандарт",
  "lifecycle": "superseded",
  "lifecycle_ru": "Заменён",
  "stream": "IETF",
  "stream_ru": "IETF",
  "area": "sec",
  "area_ru": "Безопасность",
  "working_group": "smime",
  "source_draft": "draft-ietf-smime-cert-08",
  "page_count": 13,
  "doi": "10.17487/RFC2632",
  "keywords": [
    "encryption",
    "certificate",
    "multipurpose",
    "internet",
    "mail",
    "extensions",
    "secure"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [
      "RFC3850"
    ],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc2632/",
    "html": "https://www.rfc-editor.org/rfc/rfc2632.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc2632.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc2632/"
  }
}