RFC 106
User/Server Site Protocol Network Host Questionnaire
RFC 106 β¨ USER/SERVER SITE PROTOCOL NETWORK HOST QUESTIONNAIRE
Okay bestie, the title block first π
- Number and title: RFC #106, USER/SERVER SITE PROTOCOL NETWORK HOST QUESTIONNAIRE
- Series: Network Working Group, NIC 5776
- Author: Thomas O'Sullivan, RDS
- Date: 3 March 1971
- Category or status: The document doesn't list one π€·ββοΈ
- Obsoletes or updates: It doesn't name any RFCs that it obsoletes or updates
What This Is All About π¦
The answers to a bunch of questions about how Network HOSTS behave and operate are going to be super useful for people building some early versions of TELNET, and/or for the USER/SERVER SITE PROTOCOL Committee as they figure out a full TELNET PROTOCOL specification π§
The Plan ποΈ
The questions everyone's curious about are on the attached questionnaire. The Technical Liaison contact at each HOST site is asked to look them over and fill in the answers as soon as convenient after getting them π
One of the committee members listed below will call each HOST site in the next few days to record the answers π
The Committee π
Bob Long SDC
John Melvin SRI/ARC
Ed Meyer MIT/MAC
Tom O'Sullivan RDS
Once everything's in, the results will be tabulated and distributed as an RFC πβ¨
Network Host Questionnaire π
For TELNET Consideration πΈ
Installation __________________________ Prepared By _______________
System** _____________________________ Date _____________________
1.) Okay, so does the system handle keyboard input one character at a time (like searching for a special character other than end of line)? Or does it collect a whole line and only operate on it once a special character shows up, like Carriage Return (CR)? Pick the one that fits π
[ ] Line at time
[ ] Character at time
[ ] Both (Explain) __________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
2.) What's the maximum buffer size your system gives for input of a physical line from a keyboard terminal, and for output to a terminal, printer, or screen? π
Input______Char
Output_____Char
Remarks: ____________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
=================
* If there is insufficient space on the questionnaire, continue
answers on back of page.
** Fill out separate questionnaire for each HOST to be directly
interfaced to an IMP.
3.) Describe the effect that these keying conventions have in your system. Say how each one is implemented. Is there a hardware interrupt? Does the terminal respond, and how? What gets sent into the system as data, what gets echoed, and so on? If a key isn't available, say so (like Newline on some systems, or line feed on 2741's). If it's available but has no meaning, say that too π
Key Strokes Implementation System Action
CR __________________________ __________________
LF __________________________ __________________
NL __________________________ __________________
CR,LF __________________________ __________________
Terminal Type = __________________________
If it's relevant, enter data for other terminal types on the back of this page π
4.) What special character or characters does your system use to wake up some process while data is being entered from a terminal? Examples are control C on some systems, or break on others π₯
Character(s) Operation
___________ ___________________________________________
___________ ___________________________________________
___________ ___________________________________________
___________ ___________________________________________
5.) List the types of keyboard terminals and codes your system supports β¨οΈ
__________________________________________________________
__________________________________________________________
__________________________________________________________
6.) What internal code or codes does your system use to represent character sets? If it's not ASCII or EBCDIC, attach a copy of the code π§ββοΈ
__________________________________________________________
__________________________________________________________
__________________________________________________________
7.) For each terminal type, do you support it in each of these modes? π¦
Half Duplex (Pure) _______________________________________
Half Duplex (with Break or Attention) ____________________
Half Duplex (Break & Reverse Break) ______________________
Full Duplex (without echo) _______________________________
Full Duplex (with echo) __________________________________
8.) For systems with optional echo, is the terminal assumed to need an echo when it first connects? π
[ ] Yes
[ ] No
9.) Does your system do error detection on terminal input (like a parity check)? If so, is that a hardware check or a software check? π
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
10.) Does your system support punched paper tape input? If it does, what sort of end of line sequence does it use? ποΈ
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
[ This RFC was put into machine readable form for entry ]
[ into the online RFC archives by S.M.H. 5/97 ]
And that's the whole questionnaire, bestie! ππ
π¦ where this page comes from
- ietf: rfc106 1971-03
- π girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms