Re: A matter of principle Re: TAP is not proprietary
Eric Thomas <ERIC@searn.sunet.se> Wed, 09 September 1992 11:58 UTC
Received: from NRI.NRI.Reston.Va.US by IETF.NRI.Reston.VA.US id aa01747; 9 Sep 92 7:58 EDT
Received: from ietf.NRI.Reston.Va.US by NRI.Reston.VA.US id aa05640; 9 Sep 92 8:00 EDT
Received: from ietf.nri.reston.va.us by IETF.NRI.Reston.VA.US id aa01734; 9 Sep 92 7:58 EDT
Received: from NRI.NRI.Reston.Va.US by IETF.NRI.Reston.VA.US id aa01662; 9 Sep 92 7:54 EDT
Received: from venera.isi.edu by NRI.Reston.VA.US id aa05499; 9 Sep 92 7:57 EDT
Received: from searn.sunet.se by venera.isi.edu (5.65c/5.65+local-6) id <AA11552>; Wed, 9 Sep 1992 04:57:04 -0700
Message-Id: <199209091157.AA11552@venera.isi.edu>
Received: from SEARN.SUNET.SE by SEARN.SUNET.SE (IBM VM SMTP V2R2) with BSMTP id 9742; Wed, 09 Sep 92 13:56:51 +0200
Received: by SEARN (Mailer R2.08 R208004) id 2546; Wed, 09 Sep 92 13:56:50 +0200
Date: Wed, 09 Sep 1992 13:46:10 +0200
From: Eric Thomas <ERIC@searn.sunet.se>
Subject: Re: A matter of principle Re: TAP is not proprietary
To: ietf@isi.edu
In-Reply-To: Message of Tue, 8 Sep 92 22:15:58 PDT from Eliot Lear <lear@yeager.corp.sgi.com>
On Tue, 8 Sep 92 22:15:58 PDT Eliot Lear <lear@yeager.corp.sgi.com> said: >> I just don't understand the point of such an attitude. One can give >> IDENT the old TAP port and continue these silly discussions forever > >You completely misunderstand. It is TAP that is not a standard, and it >has been using (perhaps inappropriately) the port assigned for RFC-931. Hi Eliot, long time no fence. I am not that stupid Eliot, and you know it. I understand that TAP is not a rubber stamped standard, and you will recall that my note said that, if TAP were to prosper in spite of the new standard, it would be an indication to the IETF that TAP, too, should become a standard. But unless I am mistaken, RFC931 was not a workable protocol and that is how TAP came to be: people spontaneously fixed the holes in RFC931 in a certain way, a way that worked but wasn't the way IDENT chose. Again unless I am mistaken, TAP is what is being run on port 113 today - there is no "pure RFC931" client, or maybe there is one but it is on ice. >The *real* question is whether we should lend credence to a defacto >standard that is not ours? ^^^^ You have just hit the root of the problem. You guys are busy discussing whether or not to do something that might be construed as being nice to a non-standard protocol which is not *yours*. But as a user, I really don't give a damn whose standard it is. Users want their mac to purr when they click on the icon, if it shows them a bomb instead they are going to be pissed. Are you working for the users of for some sort of cultural/bureaucratic elite? Eric
- Re: A matter of principle Re: TAP is not propriet… Eliot Lear
- Re: A matter of principle Re: TAP is not propriet… Eric Thomas
- Re: A matter of principle Re: TAP is not propriet… Noel Chiappa
- Re: A matter of principle Re: TAP is not propriet… David Bridgham
- Re: A matter of principle Re: TAP is not propriet… Einar Stefferud
- Re: A matter of principle Re: TAP is not propriet… Eric Thomas