Re: Telnet and FTP to Historic

Christian de Larrinaga <cdel@firsthand.net> Thu, 03 December 2020 12:27 UTC

Return-Path: <cdel@firsthand.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD2E03A08AA for <ietf@ietfa.amsl.com>; Thu, 3 Dec 2020 04:27:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.319
X-Spam-Level:
X-Spam-Status: No, score=-1.319 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=firsthand.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6cykjeDuAXkC for <ietf@ietfa.amsl.com>; Thu, 3 Dec 2020 04:27:22 -0800 (PST)
Received: from tranquility.default.cdelarrinaga.uk0.bigv.io (tranquility.default.cdelarrinaga.uk0.bigv.io [IPv6:2001:41c8:51:8b8::184]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 787B33A00C9 for <ietf@ietf.org>; Thu, 3 Dec 2020 04:27:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=firsthand.net; s=tranquility; h=Content-Type:MIME-Version:Message-ID:Date:In-reply-to:Reply-To:Subject:Cc:To:From:References; bh=s2BdiztFjt6WBVD1if9e+kcia9wNeHmYRRJUXlmMMl8=; b=eUrJwWNw66P2KJRFwtJNnpIyV9/NljcHR7zMvgne6GQ9FV/itSG4Pq0eMGDuKw1P+WIuptiLz89Ttx4LZacAKwKNVSnhlbh3vQs7GPSF+9QJPkqdVLm2DMBvnqOAKTlYlKMQWGDtdqLodZhBbvFS9Egx7DgStbFdLfnsfqV6uiQ=;
Received: from 60.88.155.90.in-addr.arpa ([90.155.88.60] helo=christian-yoga) by tranquility.default.cdelarrinaga.uk0.bigv.io with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from <cdel@firsthand.net>) id 1kknhd-00049G-DW; Thu, 03 Dec 2020 12:27:17 +0000
References: <AA1E0A8464BC45FB4FA44684@PSB> <2D63A357-E253-462C-864D-2BF96D3E2E18@tzi.org> <F4CD3381C5D0E24C91FC4A91@PSB> <20201201030759.GJ5364@mit.edu> <5720F933910C959C9278EBCF@PSB> <CAMm+LwgpcLxSdzgfJy2441hjNWP=Fui-f8Oq1bZB=2QdZeOUNQ@mail.gmail.com> <0c5a4935-f0b6-4b86-dc0e-3b4466bc09a4@nostrum.com> <F1FF9720-AA72-4B92-ABE7-6E0E875059BA@tzi.org> <16446.1606931808@localhost> <CAMm+Lwj51YLpwZLCxsVeg=6tBwaG845Kg4WN4hbA8Bv=pjjKrQ@mail.gmail.com> <C9D1281FC33DACED4FB385A3@PSB> <6B1BC8E3-913D-4683-A463-AD6099103749@sobco.com> <08035677-a35e-45ed-39e9-b01df6d01010@cs.tcd.ie> <87a6uvrvkz.fsf@firsthand.net> <cd04eebf-aece-c2a5-928d-9a7e954bd787@foobar.org>
User-agent: mu4e 1.5.5; emacs 28.0.50
From: Christian de Larrinaga <cdel@firsthand.net>
To: Nick Hilliard <nick@foobar.org>
Cc: ietf@ietf.org
Subject: Re: Telnet and FTP to Historic
Reply-To: cdel@firsthand.net
In-reply-to: <cd04eebf-aece-c2a5-928d-9a7e954bd787@foobar.org>
Date: Thu, 03 Dec 2020 12:27:16 +0000
Message-ID: <877dpzrs63.fsf@firsthand.net>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/6sU8r0xigy1e7vnrVAsEUk_bcvA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Dec 2020 12:27:24 -0000

Nick Hilliard writes:

> Christian de Larrinaga wrote on 03/12/2020 11:13
>> there are times when having telnet to test a mail server / email address is helpful?
>> 
>> Happy to have a better sweetie if you can suggest one
>
> netcat is probably better for this because it opens up a raw socket and 
> doesn't attempt to cook the transport layer, like telnet.

Yes John Levine mentioned nc earlier. I do use it for some usecases but I find
muscle memory takes over and telnet has a loooong history.  

I have been slowly reviewing and installing newer tools on my linux
laptops over the year. But gaining a 10,000 metre view of the current options takes
time.

>
> In any event, reclassifying a protocol as historic doesn't mean that the 
> tools will disappear.  It just means that as a protocol is at an 
> evolutionary dead end.

When one stops eating one's own dog food ....

>
> It's ok to admit this sort of thing and not see it as a bad thing. The 
> world moves on.
>
> The same applies to finger except more so.  And identd (rfc1413), 
> chargen (rfc864), echo/udp (rfc862) and, honestly, cartloads of the 
> earlier rfcs.  If there were a gigantic bonfire of a bunch of these, I 
> would be happy to supply the marshmallows.
>
> Nick

sounds like a job to build the wiki for this. 

C
-- 
Christian de Larrinaga