Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watmath!clyde!rutgers!gatech!bloom-beacon!mit-eddie!ll-xn!ames!sdcsvax!ucbvax!QUABBIN.SCRC.SYMBOLICS.COM!DCP From: DCP@QUABBIN.SCRC.SYMBOLICS.COM.UUCP Newsgroups: comp.protocols.tcp-ip Subject: RCTE Message-ID: <870928095131.6.DCP@KOYAANISQATSI.S4CC.Symbolics.COM> Date: Mon, 28-Sep-87 09:51:00 EDT Article-I.D.: KOYAANIS.870928095131.6.DCP Posted: Mon Sep 28 09:51:00 1987 Date-Received: Tue, 29-Sep-87 04:43:09 EDT References: <8709261909.AA10409@topaz.rutgers.edu> Sender: daemon@ucbvax.BERKELEY.EDU Distribution: world Organization: The ARPA Internet Lines: 13 RCTE sounds a lot like the echo-negotiation protocol that the Multics Emacs people developed circa 1980. I'm sorry I can't give you a reference; they may not have published anything. There is and has been a display oriented terminal protocol for a long, long time. The only reason it needs "dusting off" is because only now are commonplace terminals and computer systems really able to take advantage of it. Most operating systems were (originally) written with printing terminals in mind, which is why it has been hard to graft this into existing systems, such as TOPS20. I'm refering, of course, to the SUPDUP protocol, RFC 734 of 1978. If you want graphics, you can do that too: the SUPDUP Graphics extension, RFC 746 March 1978. I suggest you look at these before doing too much wheel reinvention.