home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.protocols.tcp-ip:5891 comp.protocols.tcp-ip.ibmpc:7313
- Newsgroups: comp.protocols.tcp-ip,comp.protocols.tcp-ip.ibmpc
- Path: sparky!uunet!think.com!linus!linus.mitre.org!jcmorris
- From: jcmorris@mwunix.mitre.org (Joe Morris)
- Subject: TELNET terminal types
- Message-ID: <jcmorris.726603002@mwunix>
- Keywords: telnet terminal option rfc1060
- Sender: news@linus.mitre.org (News Service)
- Nntp-Posting-Host: mwunix.mitre.org
- Organization: The MITRE Corporation
- Date: Sat, 9 Jan 1993 18:10:02 GMT
- Lines: 29
-
- [I haven't been monitoring this group before, so excuse me if this
- is an FAQ...]
-
- I'm looking for some help in resolving a problem of common usage versus
- RFC standards in the tcp/ip arena.
-
- Our corporate standard PC-based TCP/IP package (Wollongong's PathWay for DOS)
- gives us problems when it is used to attach via telnet to the various UNIX
- boxes around the campus. In particular, in the terminal-type options
- negotiation (per RFC 1091) the Wollongong product is delivering the text
- string:
-
- DEC-VT100
-
- (or "DEC-VT220" or whatever) to the host. Unless I've missed something
- this actually does conform to the requirements of RFC 1060 ("Assigned
- Numbers") dated 3/90.
-
- The trouble is that none of our UNIX boxes (typically running SUN-OS,
- IBM's AIX (RS-6000), or Silicon Graphics' IRIX) have the faintest
- idea what to do with this terminal type; their terminfo files expect
- something like "vt100". One problem is that RFC 1060 does not include
- any terminal types of the form "VTxxx".
-
- So...any comments? Is Wollongong alone in adhering to RFC 1060, or do
- the UNIX vendors say "RFC's aren't legal standards", or have I missed
- some obvious point here?
-
- Joe Morris / MITRE
-