[apps-discuss] tn3270

"Lyndon Nerenberg (VE6BBM/VE7TFX)" <lyndon@orthanc.ca> Fri, 19 November 2010 05:57 UTC

Return-Path: <lyndon@gandalf.orthanc.ca>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 980163A67AD; Thu, 18 Nov 2010 21:57:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B2hzc34WEk1P; Thu, 18 Nov 2010 21:57:03 -0800 (PST)
Received: from orthanc.ca (ve6bbm-1-pt.tunnel.tserv13.ash1.ipv6.he.net [IPv6:2001:470:7:139::2]) by core3.amsl.com (Postfix) with ESMTP id 9DA7F3A67B0; Thu, 18 Nov 2010 21:57:03 -0800 (PST)
Received: from orthanc.ca (localhost [127.0.0.1]) by orthanc.ca (8.14.4/8.14.4) with ESMTP id oAJ5vp79008558 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 18 Nov 2010 21:57:51 -0800 (PST) (envelope-from lyndon@gandalf.orthanc.ca)
Received: (from uucp@localhost) by orthanc.ca (8.14.4/8.14.4/Submit) with UUCP id oAJ5vp3G008557; Thu, 18 Nov 2010 21:57:51 -0800 (PST) (envelope-from lyndon@gandalf.orthanc.ca)
Received: from gandalf.orthanc.ca (frodo.orthanc.ca [172.16.0.3]) by legolas.orthanc.ca (8.14.4/8.14.4) with ESMTP id oAJ5vn5U042218; Thu, 18 Nov 2010 21:57:49 -0800 (PST) (envelope-from lyndon@gandalf.orthanc.ca)
Message-ID: <55895239d7e7df2d41b9da075c4f149c@gandalf.orthanc.ca>
To: uri-review@ietf.org, apps-discuss@ietf.org
From: "Lyndon Nerenberg (VE6BBM/VE7TFX)" <lyndon@orthanc.ca>
Date: Thu, 18 Nov 2010 21:57:49 -0800
In-Reply-To: <201011181753.SAA16070@TR-Sys.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: [apps-discuss] tn3270
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Nov 2010 05:58:29 -0000

> Well, AFAIK, 3270 emulation is still in some limited use in commercial
> legacy mixed-platform environments, but I've never heard of practical
> usage of the 'tn3270' URI scheme in that context -- all such business
> applications are likely to operate based on tightly controlled local
> configuration of the access points and not driven by some kind of
> browser software operating on 'tn3270' URIs.

That's an awfully presumptive generalization to make about how other
people's businesses operate.  That aside, "must be accessible to the
global Internet" isn't a criteria for (or against) standardization (or
registration).  Standards can also apply inside walled gardens.

> There's a single RFC (RFC 3049) that contains a few embedded examples
> of 'tn3270' URIs, but it remains rather vague and does not give a
> reference for the definition of such scheme either.

I strongly suspect that's because the community of users for this scheme
are painfully aware of what the service represents, and therefore didn't
see a need to write it up.  It wouldn't take much effort to document it
in an RFC.

> So I'm also in support of declaring that provisional URI scheme
> Historic.

What is gained by doing this?  tn3270 is a very distinct service from
the NVT-ASCII terminal presumed by telnet:, even though both are
served over the TELNET protocol.  And the TN3270 service is far from
dead (e.g.  there are more than a few AS/400 systems connected to the
Internet).

Someone mentioned the tn3270 scheme made no sense being typed into a
browser.  URIs are used in *many* places other than browsers.  (On the
terminal I'm typing this on, right-clicking on any string prefixed
with 'tn3270://' will launch a tn3270 terminal emulator connection to
the specified host.)  While there's no formal specification for the
tn3270 scheme, it's pretty obvious what to do with the URI if you're
handed one in a context where you can establish the connection.

So let me turn this around and ask: what harm is actively being caused
by the tn3270 scheme that requires us to kick it to the curb?

--lyndon