RFC1621 · Pip Near-term Architecture

{
  "id": "RFC1621",
  "number": 1621,
  "title_en": "Pip Near-term Architecture",
  "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": "The purpose of this RFC and the companion RFC \"Pip Header Processing\" are to record the ideas (good and bad) of Pip. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.",
  "authors": [
    "P. Francis"
  ],
  "organizations": [],
  "publication_date": "1994-05-01",
  "current_status": "HISTORIC",
  "current_status_ru": "Исторический",
  "publication_status": "INFORMATIONAL",
  "publication_status_ru": "Информационный",
  "lifecycle": "historic",
  "lifecycle_ru": "Исторический",
  "stream": "IETF",
  "stream_ru": "IETF",
  "area": "int",
  "area_ru": "Интернет",
  "working_group": "pip",
  "source_draft": "draft-ietf-pip-architecture-01",
  "page_count": 51,
  "doi": "10.17487/RFC1621",
  "keywords": [
    "Internet Protocol",
    "IPng"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc1621/",
    "html": "https://www.rfc-editor.org/rfc/rfc1621.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc1621.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc1621/"
  }
}