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

IETF · RFC · RFC3552

RFC3552 · Guidelines for Writing RFC Text on Security Considerations

Guidelines for Writing RFC Text on Security Considerations

All RFCs are required to have a Security Considerations section. Historically, such sections have been relatively weak. This document provides guidelines to RFC authors on how to write a good Security Considerations section. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.

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

All RFCs are required to have a Security Considerations section. Historically, such sections have been relatively weak. This document provides guidelines to RFC authors on how to write a good Security Considerations section. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.

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

updated_by: RFC8996, RFC9416

is_also: BCP72

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

Полные импортированные сведения карточки
{
  "id": "RFC3552",
  "number": 3552,
  "title_en": "Guidelines for Writing RFC Text on Security Considerations",
  "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": "All RFCs are required to have a Security Considerations section. Historically, such sections have been relatively weak. This document provides guidelines to RFC authors on how to write a good Security Considerations section. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.",
  "authors": [
    "E. Rescorla",
    "B. Korver"
  ],
  "organizations": [],
  "publication_date": "2003-07-01",
  "current_status": "BEST CURRENT PRACTICE",
  "current_status_ru": "Лучшая современная практика",
  "publication_status": "BEST CURRENT PRACTICE",
  "publication_status_ru": "Лучшая современная практика",
  "lifecycle": "active",
  "lifecycle_ru": "Действующий",
  "stream": "IAB",
  "stream_ru": "Совет по архитектуре Интернета (IAB)",
  "area": "",
  "area_ru": "",
  "working_group": "",
  "source_draft": "draft-iab-sec-cons-03",
  "page_count": 44,
  "doi": "10.17487/RFC3552",
  "keywords": [
    "RFC",
    "Request for Comment",
    "Security Considerations"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [
      "RFC8996",
      "RFC9416"
    ],
    "is_also": [
      "BCP72"
    ],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc3552/",
    "html": "https://www.rfc-editor.org/rfc/rfc3552.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc3552.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc3552/"
  }
}