RFC 747
Recent extensions to the SUPDUP Protocol
RFC 747: Recent Extensions to the SUPDUP Protocol π
okay so the title block is giving πβ¨ Author: Mark Crispin (SU-AI). Date: 21 March 1978. Updates: RFC 734. See also: RFC 746. the doc doesn't list a category or say what it obsoletes, so there's nothing to add there π€·ββοΈ here's the original header, verbatim:
NWG/RFC# 747 MRC 21-MAR-78 44015
NIC number is 44015, network working group, all the official stuff π
The Tea β
okay bestie, so some extensions have been made to SUPDUP π¦ RFC 746 by Richard Stallman documented the SUPDUP graphics extension π¨. on top of that, a TTYOPT bit got added and two more variables got added to the initial negotiation πΈ this RFC covers what changed from RFC 734, but skips the detailed stuff in RFC 746 (that's its own whole thing π).
these extensions are upward and downward compatible and totally optional β¨ for most SUPDUP user and server programs, RFC 734 is still an adequate description of the protocol π BUT, if the console's line speed is known, the user SUPDUP should be modified to send the new ISPEED and OSPEED variables (sending 0 for SMARTS if the graphics extension is not to be used) so the server can handle buffering for the terminal better π«Ά this is lowkey the main thing you want to do!!
Why There's No New 734 Yet π€
since the changes are compatible and optional, and since SUPDUP is still actively being worked on, the author chose to issue this update RFC instead of an updated version of RFC 734 π a new 734 will come out once the protocol stabilizes again π
The New Variables π
three new variables have been added to the initial negotiation π§ in order they are SMARTS, ISPEED, and OSPEED. because of that, the count should now be -10,,0, or in octal, 777770000000 π
the math is giving β¨
SMARTS π§
SMARTS says what "smarts" the terminal has, which is basically its graphics capabilities π¨ same as the TTYOPT variable, a bit being true means the terminal has that option π¦ RFC 746 explains this variable and the SUPDUP graphics option in full detail π if the graphics extension isn't being used, SMARTS should be set to 0 π
ISPEED and OSPEED β‘
these two are the input and output baud rates of the terminal, if they're known π example: a 150./1200. baud terminal would have an ISPEED of 150. and an OSPEED of 1200. πΈ a speed of zero means the line speed is indeterminate π
The %TPPRN TTYOPT Bit π
the %TPPRN TTYOPT bit (value 0,,200) has been added β¨ this bit tells the system to swap parentheses with square brackets on input π₯ this is super useful for LISP users on a terminal where parentheses are a shift character but square brackets aren't ππ the bit is normally off, and servers are not required to implement it π«Ά
aside: "not required" means servers can skip it. no pressure, no drama π
-1-
and that's the tea π΅π periodt.
π¦ where this page comes from
- ietf: rfc747 1978-03
- π girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms