Response to RFC 597: Host status
Analyze & explore related research in Conceptio
Connect this record directly into your research workflow or AI agent. Explore citations across open repositories, query full text, and export structured proof bundles.
Network Working Group J.D. Burchfiel RFC # 603 BBN-TENEX NIC # 21022 31 December, 1973
Response to RFC # 597: Host Status
I have several questions about the November 1973 ARPANET topographical map:
1. AMES is 4-connected, i.e. four network connections will go down if the IMP fails. Is there some aspiration that IMPs should be no more than three connected?
2. The seven IMPS in the Washington area are arranged into a loop. This guarantees that local communication can take place even if one connection fails, and is probably a worthwhile preparation for area routing. On the other hand, for example, a break between MIT-IPC and MIT-MAC will require them to communicate through a 12-hop path through Washington. This can be remedied by a short (inexpensive) connection between Harvard and Lincoln Labs. Is there a plan to pull the Boston area, the San Francisco area, and the Los Angeles area into loops like the Washington area?
[ This RFC was put into machine readable form for entry ] [ into the online RFC archives by Alex McKenzie with ] [ support from GTE, formerly BBN Corp. 10/99 ]
Related documents
- Perspective on the Host Requirements RFCs#131712
- Response to RFC 467#500895
- Response to NWG/RFC 110#136694
- Response to NWG/RFC 346#212029
- Response to NWG/RFC 346#193173
Retrieved via Conceptio: every document is proof-bundled with source, license, and retrieval metadata.
Read the Docs → · View CLI source on GitHub · Conceptio Open Knowledge Archive