Re: [apps-discuss] tn3270

John C Klensin <john-ietf@jck.com> Fri, 19 November 2010 08:10 UTC

Return-Path: <john-ietf@jck.com>
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 0358228C113; Fri, 19 Nov 2010 00:10:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 M3tyNa4J3nQg; Fri, 19 Nov 2010 00:10:40 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id A878B28C0CF; Fri, 19 Nov 2010 00:10:39 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PJM46-000INd-St; Fri, 19 Nov 2010 03:11:27 -0500
Date: Fri, 19 Nov 2010 03:11:26 -0500
From: John C Klensin <john-ietf@jck.com>
To: "Lyndon Nerenberg (VE6BBM/VE7TFX)" <lyndon@orthanc.ca>, uri-review@ietf.org, apps-discuss@ietf.org
Message-ID: <175AC1CC70EF63F569DB1757@PST.JCK.COM>
In-Reply-To: <55895239d7e7df2d41b9da075c4f149c@gandalf.orthanc.ca>
References: <55895239d7e7df2d41b9da075c4f149c@gandalf.orthanc.ca>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Subject: Re: [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 08:10:44 -0000

While I'm no fan of the 3270 (and wasn't back when I was doing
programming that depended on them), I have to agree with Lyndon.
There is almost certainly no harm in keeping the URI definition
and probably some harm in getting rid of it.   One could argue
that the spec should be retired because it is inadequate and
obsolete, but inventing and applying that criterion is IMO
unreasonable unless we intend to start applying the "time out
and die" provisions of RFC 2026 for the first time in history.

    john


--On Thursday, November 18, 2010 21:57 -0800 "Lyndon Nerenberg
(VE6BBM/VE7TFX)" <lyndon@orthanc.ca> wrote:

>> 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.
>...