RFC3514 · The Security Flag in the IPv4 Header

{
  "id": "RFC3514",
  "number": 3514,
  "title_en": "The Security Flag in the IPv4 Header",
  "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": "Firewalls, packet filters, intrusion detection systems, and the like often have difficulty distinguishing between packets that have malicious intent and those that are merely unusual. We define a security flag in the IPv4 header as a means of distinguishing the two cases. This memo provides information for the Internet community.",
  "authors": [
    "S. Bellovin"
  ],
  "organizations": [],
  "publication_date": "2003-04-01",
  "current_status": "INFORMATIONAL",
  "current_status_ru": "Информационный",
  "publication_status": "INFORMATIONAL",
  "publication_status_ru": "Информационный",
  "lifecycle": "informational",
  "lifecycle_ru": "Справочный",
  "stream": "INDEPENDENT",
  "stream_ru": "Независимый поток",
  "area": "",
  "area_ru": "",
  "working_group": "",
  "source_draft": "",
  "page_count": 6,
  "doi": "10.17487/RFC3514",
  "keywords": [
    "evil",
    "evil bit"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc3514/",
    "html": "https://www.rfc-editor.org/rfc/rfc3514.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc3514.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc3514/"
  }
}