RFC1675 · Security Concerns for IPng

{
  "id": "RFC1675",
  "number": 1675,
  "title_en": "Security Concerns for IPng",
  "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": "A number of the candidates for IPng have some features that are somewhat worrisome from a security perspective. While it is not necessary that IPng be an improvement over IPv4, it is mandatory that it not make things worse. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.",
  "authors": [
    "S. Bellovin"
  ],
  "organizations": [],
  "publication_date": "1994-08-01",
  "current_status": "INFORMATIONAL",
  "current_status_ru": "Информационный",
  "publication_status": "INFORMATIONAL",
  "publication_status_ru": "Информационный",
  "lifecycle": "informational",
  "lifecycle_ru": "Справочный",
  "stream": "Legacy",
  "stream_ru": "Исторический поток",
  "area": "",
  "area_ru": "",
  "working_group": "",
  "source_draft": "draft-bellovin-ipng-sec-concerns-00",
  "page_count": 4,
  "doi": "10.17487/RFC1675",
  "keywords": [
    "White",
    "Paper"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc1675/",
    "html": "https://www.rfc-editor.org/rfc/rfc1675.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc1675.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc1675/"
  }
}