home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.protocols.tcp-ip
- Path: sparky!uunet!ferkel.ucsb.edu!taco!rock!stanford.edu!ames!sun-barr!cs.utexas.edu!torn!utzoo!henry
- From: henry@zoo.toronto.edu (Henry Spencer)
- Subject: Re: Is telnet protocol documented?
- Message-ID: <Bxo93A.2AJ@zoo.toronto.edu>
- Date: Fri, 13 Nov 1992 20:33:09 GMT
- References: <1391@minya.UUCP>
- Organization: U of Toronto Zoology
- Lines: 20
-
- In article <1391@minya.UUCP> jc@minya.UUCP (John Chambers) writes:
- >...except that when the connect() returned success and the program
- >wrote something down the line, instead of a "login:" that I get when I
- >type "telnet %s", it gets utter garbage. The garbage is quite
- >consistent: It consists of the 3 bytes FF FD 18...
-
- Uh, telnet is a *protocol*; it is not an uninterpreted data path. You're
- looking at a telnet option-negotiation sequence.
-
- >Any idea how I might get documentation of telnetd's protocol? Is there
- >an RFC on it that someone can email me? ...
-
- You get documentation on telnet the same way you get documentation on
- any of the Internet protocols: read the relevant RFCs. For telnet, it
- starts with RFC 854. Actually, you probably want to look at the telnet
- section of RFC 1123 first, as there are a whole bunch of telnet-related
- RFCs and you need to know which ones matter.
- --
- MS-DOS is the OS/360 of the 1980s. | Henry Spencer @ U of Toronto Zoology
- -Hal W. Hardenbergh (1985)| henry@zoo.toronto.edu utzoo!henry
-