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

IETF · RFC · RFC802

RFC802 · ARPANET 1822L Host Access Protocol

ARPANET 1822L Host Access Protocol

This document proposed two major changes to the current ARPANET host access protocol. The first change will allow hosts to use logical addressing (i.e., host addresses that are independent of their physical location on the ARPANET) to communicate with each other, and the second will allow a host to shorten the amount of time that it may be blocked by its IMP after it presents a message to the network (currently, the IMP can block further input from a host for up to 15 seconds). See RFCs 852 and 851.

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

This document proposed two major changes to the current ARPANET host access protocol. The first change will allow hosts to use logical addressing (i.e., host addresses that are independent of their physical location on the ARPANET) to communicate with each other, and the second will allow a host to shorten the amount of time that it may be blocked by its IMP after it presents a message to the network (currently, the IMP can block further input from a host for up to 15 seconds). See RFCs 852 and 851.

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

obsoleted_by: RFC851

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

Полные импортированные сведения карточки
{
  "id": "RFC802",
  "number": 802,
  "title_en": "ARPANET 1822L Host Access Protocol",
  "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": "This document proposed two major changes to the current ARPANET host access protocol. The first change will allow hosts to use logical addressing (i.e., host addresses that are independent of their physical location on the ARPANET) to communicate with each other, and the second will allow a host to shorten the amount of time that it may be blocked by its IMP after it presents a message to the network (currently, the IMP can block further input from a host for up to 15 seconds). See RFCs 852 and 851.",
  "authors": [
    "A.G. Malis"
  ],
  "organizations": [],
  "publication_date": "1981-11-01",
  "current_status": "UNKNOWN",
  "current_status_ru": "Статус не назначен",
  "publication_status": "UNKNOWN",
  "publication_status_ru": "Статус не назначен",
  "lifecycle": "superseded",
  "lifecycle_ru": "Заменён",
  "stream": "Legacy",
  "stream_ru": "Исторический поток",
  "area": "",
  "area_ru": "",
  "working_group": "",
  "source_draft": "",
  "page_count": 45,
  "doi": "10.17487/RFC802",
  "keywords": [],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [
      "RFC851"
    ],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc802/",
    "html": "https://www.rfc-editor.org/rfc/rfc802.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc802.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc802/"
  }
}