README
1 $OpenBSD: README,v 1.6 2022/12/26 19:16:03 jmc Exp $
2
3
4The following TELNET options are supported:
5
6 LINEMODE:
7 The LINEMODE option is supported as per RFC1116. The
8 FORWARDMASK option is not currently supported.
9
10 BINARY: The client has the ability to turn on/off the BINARY
11 option in each direction. Turning on BINARY from
12 server to client causes the LITOUT bit to get set in
13 the terminal driver on both ends, turning on BINARY
14 from the client to the server causes the PASS8 bit
15 to get set in the terminal driver on both ends.
16
17 TERMINAL-TYPE:
18 This is supported as per RFC1091. On the server side,
19 when a terminal type is received, termcap/terminfo
20 is consulted to determine if it is a known terminal
21 type. It keeps requesting terminal types until it
22 gets one that it recognizes, or hits the end of the
23 list. The server side looks up the entry in the
24 termcap/terminfo data base, and generates a list of
25 names which it then passes one at a time to each
26 request for a terminal type, duplicating the last
27 entry in the list before cycling back to the beginning.
28
29 NAWS: The Negotiate about Window Size, as per RFC 1073.
30
31 TERMINAL-SPEED:
32 Implemented as per RFC 1079
33
34 TOGGLE-FLOW-CONTROL:
35 Implemented as per RFC 1080
36
37 TIMING-MARK:
38 As per RFC 860
39
40 SGA: As per RFC 858
41
42 ECHO: As per RFC 857
43
44 LOGOUT: As per RFC 727
45
46 STATUS:
47 The server will send its current status upon
48 request. It does not ask for the clients status.
49 The client will request the servers current status
50 from the "send getstatus" command.
51
52 ENVIRON:
53 This option is currently being defined by the IETF
54 Telnet Working Group, and an RFC has not yet been
55 issued, but should be in the near future...
56
57 X-DISPLAY-LOCATION:
58 This functionality can be done through the ENVIRON
59 option, it is added here for completeness.
60