Re: TELNET question
Theodore Ts'o <tytso@mit.edu> Fri, 18 November 1994 20:31 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa08968; 18 Nov 94 15:31 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa08964; 18 Nov 94 15:31 EST
Received: from timbuk.cray.com by CNRI.Reston.VA.US id aa14912; 18 Nov 94 15:31 EST
Received: from sdiv.cray.com (daemon@ironwood.cray.com [128.162.21.36]) by timbuk.cray.com (8.6.9/8.6.9M) with SMTP id OAA00281; Fri, 18 Nov 1994 14:19:33 -0600
Received: by sdiv.cray.com (5.0/CRI-5.15.b.orgabbr Sdiv) id AA20630; Fri, 18 Nov 1994 14:19:28 -0600
Received: from timbuk.cray.com by sdiv.cray.com (5.0/CRI-5.15.b.orgabbr Sdiv) id AA20625; Fri, 18 Nov 1994 14:19:27 -0600
Received: from MIT.EDU (SOUTH-STATION-ANNEX.MIT.EDU [18.72.1.2]) by timbuk.cray.com (8.6.9/8.6.9M) with SMTP id OAA00272 for <telnet-ietf@cray.com>; Fri, 18 Nov 1994 14:19:26 -0600
Received: from DCL.MIT.EDU by MIT.EDU with SMTP id AA19254; Fri, 18 Nov 94 15:18:51 EST
Received: by dcl.MIT.EDU (5.0/4.7) id AA15037; Fri, 18 Nov 1994 15:18:50 +0500
Date: Fri, 18 Nov 1994 15:18:50 +0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Theodore Ts'o <tytso@mit.edu>
Message-Id: <9411182018.AA15037@dcl.MIT.EDU>
To: braden@isi.edu
Cc: lee@huachuca-jitcosi.army.mil, billw@cisco.com, iptp@huachuca-jitcosi.army.mil, telnet-ietf@cray.com
In-Reply-To: braden@ISI.EDU's message of Fri, 18 Nov 1994 12:12:43 -0800, <199411182012.AA21232@can.isi.edu>
Subject: Re: TELNET question
Address: 1 Amherst St., Cambridge, MA 02139
Phone: (617) 253-8091
Content-Length: 1114
Date: Fri, 18 Nov 1994 12:12:43 -0800 From: braden@ISI.EDU Both FTP and SMTP both use "telnet streams", with CRLF as end of line. I would expect that 1. was the right answer, as a question of philosophy. Of course, reality sometimes intervenes... True, although I don't think SMTP is obligated to handle telnet IAC options. FTP does, if I remember correctly. (Easy enough to look up). Actually, after doing a bit of looking at the BSD telnet implementation, I couldn't see anything that indicates that the BSD telnet implementation would do different things as far as CRLF interpretation if a non-standard port was given. The only that might happen with a nonstandard port is that unless the non-standard port was prefixed with a '-', the telnet client (sorry, telnet user implementation) wouldn't actually initiate any telnet options negotiation --- which is legal, as far as I can tell. Of course, it could very well be that I missed something obvious (this was a less than 3 minute investigation) or it was completely different implementation that was under going testing.... - Ted
- TELNET question Lee Chastain
- Re: TELNET question William Chops Westfield
- Re: TELNET question Theodore Ts'o
- Re: TELNET question Lee Chastain
- Re: TELNET question Philippe-Andre Prindeville
- Re: TELNET question William Chops Westfield
- Re: TELNET question Theodore Ts'o
- Re: TELNET question braden
- Re: TELNET question Theodore Ts'o