RFC 162

NETBUGGER3 ✨

Okay bestie, so this is RFC 162 🦋, written by M. Kampe of UCLA-NMC (NIC #6774) and dated 22 May 1971. It's filed under categories C.2, C.3, D.1, D.2, and D.3. It doesn't update anything and doesn't obsolete anything, so it's a totally standalone vibe 💅.

NETBUGGER3 is a third level program for the debugging of second and third level programs, experimentation with and simulation of third level protocols. 🧚

Okay, the origin story is so relatable 😭 The writer was building an RJE FILENET to interact with UCLA-CCN, but surprise, UCLA-CCN wasn't going to be up for a few months 💀. So they needed a program that would simulate CCN, so they could actually talk to it and debug their FILENET. It hit them that all over the network, people had the same problem. Programs couldn't be debugged because the intended server wasn't up yet. So they started writing a third level debugger-simulater 🎀.

Here's what NETBUGGER3 can actually do 🔥

With NETBUGGER3 the user can easily issue RTSs, STRs, and LISTENs, interrogate the status of connections, receive and display NCP-USER events, and transmit and receive data over as many as twelve connections (per copy of program running). Received data can be displayed in ASCII, EBCDIC on HEX. The user can, of course, originate data for transmission in the same forms. NETBUGGER3 can be initiator, receiver and/or intermediate in connections 👑.

An example of how NETBUGGER3 could be of use to other hosts on the Net follows 🌸.

Host X has a special third level Filenet to debug. The host they plan to interact with won't be up for several months. Host X can arrange with us to interact with NETBUGGER3, which will simulate the proposed third level protocol and transactions 🫶.

An alternate possibility is for Host X to use his Telnet to enter our system and start NETBUGGER3 himself. He can then be running NETBUGGER3 on one console and his filenet on another.

An alternate possibility is for Host X to use his Telnet to enter our system and start NETBUGGER3 himself. He can then be running NETBUGGER3 on one console and his filenet on another.

Then, later on when the other server Host is up, NETBUGGER3 can be used an intermediate between Host X and his serving host. Every message from Host X to server and vice versa can be displayed, examined and, if necessary, edited as it passes through the NETBUGGER3 console, thus making possible the debugging and measurements. Main character energy, no notes 🌈✨

This is only one example. If you're interested in using, receiving, documentation, making suggestions, or anything else regarding NETBUGGER3, please contact the Network liaison at UCLA - NMC 🍓💜.

[ This RFC was put into machine readable form for entry ] [ into the online RFC archives by Alison De La Cruz 12/00 ]