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

IETF · RFC · RFC9416

RFC9416 · Security Considerations for Transient Numeric Identifiers Employed in Network Protocols

Security Considerations for Transient Numeric Identifiers Employed in Network Protocols

Poor selection of transient numerical identifiers in protocols such as the TCP/IP suite has historically led to a number of attacks on implementations, ranging from Denial of Service (DoS) or data injection to information leakages that can be exploited by pervasive monitoring. Due diligence in the specification of transient numeric identifiers is required even when cryptographic techniques are employed, since these techniques might not mitigate all the associated issues. This document formally updates RFC 3552, incorporating requirements for transient numeric identifiers, to prevent flaws in future protocols and implementations.

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

Poor selection of transient numerical identifiers in protocols such as the TCP/IP suite has historically led to a number of attacks on implementations, ranging from Denial of Service (DoS) or data injection to information leakages that can be exploited by pervasive monitoring. Due diligence in the specification of transient numeric identifiers is required even when cryptographic techniques are employed, since these techniques might not mitigate all the associated issues. This document formally updates RFC 3552, incorporating requirements for transient numeric identifiers, to prevent flaws in future protocols and implementations.

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

updates: RFC3552

is_also: BCP72

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

Полные импортированные сведения карточки
{
  "id": "RFC9416",
  "number": 9416,
  "title_en": "Security Considerations for Transient Numeric Identifiers Employed in Network Protocols",
  "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": "Poor selection of transient numerical identifiers in protocols such as the TCP/IP suite has historically led to a number of attacks on implementations, ranging from Denial of Service (DoS) or data injection to information leakages that can be exploited by pervasive monitoring. Due diligence in the specification of transient numeric identifiers is required even when cryptographic techniques are employed, since these techniques might not mitigate all the associated issues. This document formally updates RFC 3552, incorporating requirements for transient numeric identifiers, to prevent flaws in future protocols and implementations.",
  "authors": [
    "F. Gont",
    "I. Arce"
  ],
  "organizations": [],
  "publication_date": "2023-07-01",
  "current_status": "BEST CURRENT PRACTICE",
  "current_status_ru": "Лучшая современная практика",
  "publication_status": "BEST CURRENT PRACTICE",
  "publication_status_ru": "Лучшая современная практика",
  "lifecycle": "active",
  "lifecycle_ru": "Действующий",
  "stream": "IETF",
  "stream_ru": "IETF",
  "area": "",
  "area_ru": "",
  "working_group": "NON WORKING GROUP",
  "source_draft": "draft-gont-numeric-ids-sec-considerations-11",
  "page_count": 10,
  "doi": "10.17487/RFC9416",
  "keywords": [
    "security",
    "vulnerability",
    "algorithm",
    "attack",
    "fingerprinting"
  ],
  "formats": [
    "HTML",
    "TXT",
    "PDF",
    "XML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [
      "RFC3552"
    ],
    "updated_by": [],
    "is_also": [
      "BCP72"
    ],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc9416/",
    "html": "https://www.rfc-editor.org/rfc/rfc9416.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc9416.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc9416/"
  }
}