Re: [apps-discuss] [Uri-review] Provisional URI registrations

"Michael Wojcik" <Michael.Wojcik@microfocus.com> Wed, 24 November 2010 15:31 UTC

Return-Path: <Michael.Wojcik@microfocus.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 CA1083A6A62; Wed, 24 Nov 2010 07:31:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.746
X-Spam-Level:
X-Spam-Status: No, score=-2.746 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_LOW=-1]
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 Wb78znFUrNiU; Wed, 24 Nov 2010 07:31:47 -0800 (PST)
Received: from cluster-a.mailcontroller.altohiway.com (clustera.mailcontroller.co.uk [213.83.66.193]) by core3.amsl.com (Postfix) with ESMTP id 98C0A3A690E; Wed, 24 Nov 2010 07:31:44 -0800 (PST)
Received: from rlya7a.mailcontroller.altohiway.com (localhost.localdomain [127.0.0.1]) by rlya7a.mailcontroller.altohiway.com (MailController) with ESMTP id oAOFWWw4032681; Wed, 24 Nov 2010 15:32:37 GMT
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by rlya7a.mailcontroller.altohiway.com (MailControl) id oAOFVv2Y030795; Wed, 24 Nov 2010 15:31:57 GMT
Received: from MTV-EXCHANGE.microfocus.com ([216.52.8.28]) by rlya7a-eth0.mailcontroller.altohiway.com (envelope-sender <Michael.Wojcik@microfocus.com>) (MIMEDefang) with ESMTP id oAOFVtds030551; Wed, 24 Nov 2010 15:31:57 +0000 (GMT)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 24 Nov 2010 07:30:01 -0800
Message-ID: <81F42F63D5BB344ABF294F8E80990C7902782A73@MTV-EXCHANGE.microfocus.com>
In-Reply-To: <002f01cb8bb3$6bc87fe0$4001a8c0@gateway.2wire.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [apps-discuss] [Uri-review] Provisional URI registrations
Thread-Index: AcuLvB79CrlaVBclRDeylb3qsAAgDwALheSw
References: <201011222034.VAA22485@TR-Sys.de><81F42F63D5BB344ABF294F8E80990C7902782A63@MTV-EXCHANGE.microfocus.com> <4CEBE19C.6020408@ninebynine.org> <002f01cb8bb3$6bc87fe0$4001a8c0@gateway.2wire.net>
From: Michael Wojcik <Michael.Wojcik@microfocus.com>
To: uri-review@ietf.org, apps-discuss@ietf.org
X-Scanned-By: MailControl A-09-22-20 (www.mailcontrol.com) on 10.60.1.117
Subject: Re: [apps-discuss] [Uri-review] Provisional URI registrations
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: Wed, 24 Nov 2010 15:31:48 -0000

> From: t.petch [mailto:ietfc@btconnect.com]
> Sent: Wednesday, 24 November, 2010 03:40
> 
> Who needs a definition?  I did a quick 'literature search' and found
> plenty of references to tn3270 as a URI but no definition; the
examples
> were all of the form scheme :// host : port No parameters, queries,
> fragments or anything fancy.  On reflection, this seems right; tn3270
> is more sophisticated than many IETF protocols and if it wants
> something, it negotiates it, so no need for a complex URI to specify
> things in advance.

There are many things in TN3270 that can't simply be negotiated, and
that could usefully be represented in a URI. LU name, terminal type and
model, and printer association, for example; those are all things that
TN3270 clients typically let the user configure.

The tn3270 URI syntax might also conceivably let the user override the
default capability negotiation, for example to force Classic TN3270
rather than TN3270E, or request a non-default subset of TN3270E
functions. That would be useful for testing, among other things.

And while there's no obvious use for path, fragment, and query URI
components in the tn3270 scheme, I can easily imagine an implementor
using them for TN3270 extensions, such as using the path to select an
initial transaction.

> One could write a universal URI definition for such schemes scheme
host
> port means set up a connection of protocol 'scheme' to 'host', default
> port from IANA, but, arguably, we already have all we need in RFC3986.

I think we still need at least a basic tn3270 definition, if we're going
to consider the scheme well-defined. (Whether its status should be
changed from "provisional" to "historic" in the absence of such a
definition is another question; I have no strong feelings about that.)
There's a lot of variation among TN3270 implementations and the relevant
RFCs don't provide enough direction.

-- 
Michael Wojcik
Principal Software Systems Developer, Micro Focus



This message has been scanned for viruses by MailController - www.MailController.altohiway.com