RFC949 · FTP unique-named store command

{
  "id": "RFC949",
  "number": 949,
  "title_en": "FTP unique-named store command",
  "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": "There are various contexts in which it would be desirable to have an FTP command that had the effect of the present STOR but rather than requiring the sender to specify a file name istead caused the resultant file to have a unique name relative to the current directory. This RFC proposes an extension to the File Transfer Protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. See RFC-959.",
  "authors": [
    "M.A. Padlipsky"
  ],
  "organizations": [],
  "publication_date": "1985-07-01",
  "current_status": "UNKNOWN",
  "current_status_ru": "Статус не назначен",
  "publication_status": "UNKNOWN",
  "publication_status_ru": "Статус не назначен",
  "lifecycle": "unknown",
  "lifecycle_ru": "Статус не определён",
  "stream": "Legacy",
  "stream_ru": "Исторический поток",
  "area": "",
  "area_ru": "",
  "working_group": "",
  "source_draft": "",
  "page_count": 2,
  "doi": "10.17487/RFC949",
  "keywords": [],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc949/",
    "html": "https://www.rfc-editor.org/rfc/rfc949.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc949.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc949/"
  }
}