RFC 240
Site Status
RFC 240: SITE STATUS 🎀
okay bestie, here's the title block 💖
- Networking Group, Request for Comments: 240 (NIC #7665) ✨
- Title: SITE STATUS 🦋
- Author: A. McKenzie, BBN 👑
- Date: 30 September 1971 📅
- Categories: F, G.3 🌈
- Updates: none
- Obsoletes: RFC 235 💀 (this one is the reissue, iykyk)
- Also in the header: Rand 50ctu
Why this RFC exists 🙈
so RFC 235 had SO many typos 😭 like, extensive typographic errors, not cute. Alex decided to reissue the very first of the experimental site status reports, which is honestly iconic of him 🫶
Alex explains that for RFC 235 he went with timeliness over extremely careful editing, which he felt matched the original RFC philosophy. he says sorry to anyone who got embarrassed by it, and he takes full responsibility for what was in RFC 235 💅 he promises to do better next time, and we love a humble glow-up 🌸
Alex McKenzie 💜
SITE STATUS ✨
The plan 🧚
starting with this RFC, BBN is going to report on the status of most Network Hosts about once every two weeks 📆 the info comes from two places: chatting with people at each site, and from "data" 📊 the data is the result of daily login attempts to every Host that a Network user might be able to reach. the attempts are made from the BBN prototype Terminal IMP at a random time each weekday 🎲 the randomness is giving unbiased energy honestly
The hosts that are NOT in the daily testing 🙅♀️
okay so a few Hosts are currently left out of the daily testing, and they fall into two buckets:
- Hosts that aren't expected to work as servers (aka available for other sites to use) for at least a month 😴 the ones in this bucket are:
Network Site Computer
Address
71 Rand PDP-10
74 Lincoln TX2
11 Stanford PDP-10
13 Case PDP-10
14 Carnegie PDP-10
15 Paoli B6500- Hosts that are meant to be users only 🧑💻 this bucket has the Terminal IMPs currently on the Network (AMES, MITRE, and BBN[1]). it also includes the Network Control Center computer (Network Address 5), which is used solely for gathering statistics from the Network 📈 and finally, these Hosts are in here too:
Network Site Computer
Address
7 Rand IBM-360/65
73 Harvard PDP-1
12 Illinois PDP-11Predictions and the big status table 🔮
the tables on the next two pages condense the Host status info for September 13 through September 24 🗓️ here's the predictions table, with where each prediction came from:
PREDICTIONS
NETWORK SITE COMPUTER STATUS or PREDICTION OBTAINED
ADDRESS FROM
1 UCLA SIGMA - 7 Server Jon Postel
65 UCLA IBM-360/91 Remote Job Service now,
Time-sharing in January Steve Wolf
2 SRI(NIC) PDP-10 October 11 John Melvin
66 SRI(AI) PDP-10 November Len Chaiten
3 UCSB IBM-360-75 Server Jim White
4 UTAH PDP-10 "Soon" Barry Wessler
5 BBN DDP-516 NCC Alex McKenzie
69 BBN PDP-10 Server Dan Murphy
6 MIT(Multics) H-645 "Soon" Mike Padlipsky
70 MIT(DM) PDP-10 Server Bob Bressler
7 RAND IBM 360/65 User only Eric Harslem
71 RAND PDP-10 January Eric Harslem
8 SDC IBM-360/67 October 11 Bob Long
9 HARVARD PDP-10 "Soon" Bob Sundberg
73 HARVARD PDP-1 User only Bob Sundberg
10 LINCOLN IBM-360/67 "Soon" Joel Winnet
74 LINCOLN TX2 Uncertain Tom Barkalow
11 STANFORD PDP-10 November Andy Moorer
12 ILLINOIS PDP-11 User only John Cravits
13 CASE PDP-10 December 15 Charles Rose
14 CARNEGIE PDP-10 January Hal VanZoeren
15 PAOLI B6500 Uncertain John Cravits
16 AMES TIP Installed
17 MITRE TIP Installed
30 BBN TIP PrototypeThe status grids 🌈
first grid, September 13 through 20:
NETWORK SITE COMPUTER DATE AND TIME (P.M.)
ADDRESS 9/13 9/14 9/15 9/16 9/17 9/20
4:30 3:30 6:00 10:30 1:30 12:30
1 UCLA SIGMA-7 O O O D D D
65[2] UCLA IBM 360/91 O O O O O D
2 SRI(NIC) PDP-10 D D D D D D
66 SRI(AI) PDP-10 D D D D D D
3 UCSB IBM-360/75 O O O O O O
4 UTAH PDP-10 D D D D D D
69 BBN PDP-10 O 1/2 0 O T 1/2 O O
6 MIT(Multics) H-645 R R R D 1/2 O D
70 MIT(DM) PDP-10 T T T O O T
8 SDC IBM-360/67 D D D D T D
9 HARVARD PDP-10 T D T T T T
10 LINCOLN IBM-360/67 D 1/2 0 1/2 0 D T Dsecond grid, September 21 through 24:
NETWORK SITE COMPUTER DATE AND TIME (P.M.)
ADDRESS 9/21 9/22 9/23 9/24
4:30 3:30 2:00 5:00
1 UCLA SIGMA-7 O D T O
65[2] UCLA IBM 360/91 O O O O
2 SRI(NIC) PDP-10 D O D D
66 SRI(AI) PDP-10 D D D D
3 UCSB IBM-360/75 O O O O
4 UTAH PDP-10 D D D D
69 BBN PDP-10 O 1/2 O O O
6 MIT(Multics) H-645 1/2 O T T R
70 MIT(DM) PDP-10 1/2 O O D D
8 SDC IBM-360/67 D D D D
9 HARVARD PDP-10 D T D D
10 LINCOLN IBM-360/67 D D 1/2 0 DWhat the letters mean 🔤
where
D = Dead. (Destination Host either dead orinaccessible (due to
network partitioning or local IMP failure) from the BBN
Terminal IMP).
R = Refused. (Destination Host returned a CLS to the initial RFC.) T
= Timed Out. (Destination Host did not respond in any way to the
initial RFC, although not dead.)
1/2 0 = 1/2 Open. (Destination Host opened a connection but then
either immediately close it, or did not respond any
further.)
O = Open. (Destination Host opened a connection and was
accessible to users.)Endnotes 📝
[1] the BBN Terminal IMP (Network Address 158) is a prototype 🧪 so it's often not connected to the Network, because it's being used to refine and debug the Terminal IMP programs 🛠️
[2] the UCLA IBM-360 can currently only handle Remote Job Service ✨ BBN can't test that properly, but they're assuming that getting their canned message back means RJS is working too 🤞
[ This RFC was put into machine readable form for entry ] [ into the online RFC archives by Roy Zimmer 9/97 ]
📦 where this page comes from
- ietf: rfc240 1971-09
- 💖 girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms