RFC 356

ARPA Network Control Center ✨

okay bestie, this is RFC 356 🎀 It was written by R. Alter at Bolt Beranek and Newman Inc. and dated June 21, 1972, with NIC number 10598. It has no category, and it doesn't update or obsolete any other RFC, so those fields are blank. It's a short, practical memo about how to reach the ARPA Network Control Center (NCC) 📞

1. Schedule 🕐

The NCC ops staff just got a glow-up, so the NCC is now manned 24 hours a day, 7 days a week 💅 That means you should contact the NCC about any IMP/TIP or Network problems at any time, day or night. No more "it's 3am, I'll wait" 😭

2. NCC Phone Number 📱

We heard that people trying to reach the NCC were getting busy signals sometimes, which is so frustrating 🙈 So the team installed a new set of phone numbers. The new number for the Network Control Center is (617) 661-0100. Please post it prominently near the IMPs and tell everyone who needs it 🫶 The old number will keep working for a while too, so don't panic.

Now, if you get a busy signal, be sure to tell the NCC operator about it once you do get through. Just don't confuse it with the "fast busy signal," which means "busy circuits" and is a totally different vibe 💀 If you hit a regular busy signal, be persistent and keep calling. You've got this 💪

3. Mail to the NCC should be addressed to: 💌

Send your mail here:

               ARPA Network Control Center
               c/o Bolt Beranek and Newman Inc.
               50 Moulton Street
               Cambridge, Massachusetts 02138

And the cc list is giving main character energy 👑

cc:  Honeywell Field Service Managers
     R. Kerrian (Honeywell)
     K. Stanley (Long Lines)
     NCC contacts at sites not having Station Agents

This RFC was put into machine readable form for entry into the online RFC archives by BBN Corp. under the direction of Alex McKenzie, in 1/97. 🦋 Iconic archivists, honestly 🌈