RFC 359

RFC 359 💖 Network Working Group

Okay bestie, here's the title block tea ☕ This is RFC #359 (NIC #10601), written by Dave Walden at BBN on 22 June 1972. It's filed under Category: B.1, and it obsoletes RFC #343. It doesn't list any updates, so I'm not making one up 🙈

                   I M P O R T A N T
                   =================

The Status of the Release of the New IMP System (2600) 🦋

Okay so the vibe is: we still haven't gotten the new IMP system up 😭 Not yet, bestie.

Let's recap the drama 🎀

We first tried on May 15, but we seriously underestimated how hard it would be to get the new system out to over twenty-five sites, so we never even made it to debugging. Major oof 💀

Then we came back with a proper distribution mechanism and tried again on May 31. This time we actually got to debug the new IMP system, and we found a bunch of problems that meant we couldn't leave it up. Not a win yet, but progress ✨

On June 6 we got the new IMP system up and running quite well 🔥 The problem was that the version of the TIP system that runs with the new IMP system basically wouldn't work at all 😩 So we put the old systems back up.

The day before yesterday, June 20, we tried again. The IMPs and TIPs loaded and seemed to fly, so we kept the new systems up. But by the afternoon of June 21, TIPs were crashing about once an hour, so we backed off and put the old systems back up again 🥲 Here's the thing that makes it so rough: one TIP crash per hour in the network means about one crash every eight or ten hours of debugging with one TIP. That's nasty to debug, no cap 💅

The plan going forward 🧚

We're going to skip Tuesday, June 27, and Tuesday, July 4. Then we'll try again on Thursday, July 6 (1972). If we need to, we'll try again on Tuesday, July 18, and every Tuesday after that, as per RFC #343 🌈

DCW/jm

[ This RFC was put into machine readable form for entry ] [ into the online RFC archives by BBN Corp. under the ] [ direction of Alex McKenzie. 1/97 ]