Re: [Uri-review] Is TCP a URI scheme?

Martin J. Dürst <duerst@it.aoyama.ac.jp> Fri, 22 February 2019 04:54 UTC

Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: uri-review@ietfa.amsl.com
Delivered-To: uri-review@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA4BD130EF2 for <uri-review@ietfa.amsl.com>; Thu, 21 Feb 2019 20:54:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.923
X-Spam-Level:
X-Spam-Status: No, score=-0.923 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FROM_EXCESS_BASE64=0.979, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=itaoyama.onmicrosoft.com
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 o8a6_vU-D9KF for <uri-review@ietfa.amsl.com>; Thu, 21 Feb 2019 20:54:16 -0800 (PST)
Received: from JPN01-OS2-obe.outbound.protection.outlook.com (mail-eopbgr1410129.outbound.protection.outlook.com [40.107.141.129]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 79F7D130EBB for <uri-review@ietf.org>; Thu, 21 Feb 2019 20:54:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=itaoyama.onmicrosoft.com; s=selector1-it-aoyama-ac-jp; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=2dwjYT8KEJUmohjZE9aBWFD3cSuj6lWhTUhL97ZqLdg=; b=FcvAVGnjxBv3yPrmhQDw9m3ZdtMzgDGYwNIG2LGTaiPu8o1HsbO6DZbhQvqLB14jwursAqLi5Y+cYQ9gyq3Xg2V//b/rtDg+GHbFVFIBS37h23pyCSPmFnBKugPcXN5FARdmWsqNqDgqNpZU0jOViHtX8PF6/Zj8hlvV46rFLuU=
Received: from TYAPR01MB5149.jpnprd01.prod.outlook.com (20.179.187.18) by TYAPR01MB3152.jpnprd01.prod.outlook.com (20.177.104.139) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1643.15; Fri, 22 Feb 2019 04:54:13 +0000
Received: from TYAPR01MB5149.jpnprd01.prod.outlook.com ([fe80::6d0f:10e4:f18d:70e7]) by TYAPR01MB5149.jpnprd01.prod.outlook.com ([fe80::6d0f:10e4:f18d:70e7%3]) with mapi id 15.20.1643.014; Fri, 22 Feb 2019 04:54:13 +0000
From: "Martin J. Dürst" <duerst@it.aoyama.ac.jp>
To: Eric Johnson <eric=40tibco.com@dmarc.ietf.org>
CC: "uri-review@ietf.org" <uri-review@ietf.org>
Thread-Topic: [Uri-review] Is TCP a URI scheme?
Thread-Index: AQHUykiPYtSVFWhFqU2G/Hb/tqU6laXrQL6A
Date: Fri, 22 Feb 2019 04:54:13 +0000
Message-ID: <38b9b695-9ac6-444c-5977-33fcb54aad6a@it.aoyama.ac.jp>
References: <CAKaEYh+X_uj39OQNLy9O+aq1pbwYftbvyjx8TG0Y84wsw_ymoA@mail.gmail.com> <CA+9kkMDYrgL17X_rFtTrA10A-UrpRLYb4iPJM2RmJ2=b12Lx2Q@mail.gmail.com> <CANu9=NcSP+rhsCR58i1RzAnA8EoaOvTWW_Tpg5eT+_xkZ7+3mg@mail.gmail.com>
In-Reply-To: <CANu9=NcSP+rhsCR58i1RzAnA8EoaOvTWW_Tpg5eT+_xkZ7+3mg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-clientproxiedby: TYAPR01CA0016.jpnprd01.prod.outlook.com (2603:1096:404::28) To TYAPR01MB5149.jpnprd01.prod.outlook.com (2603:1096:404:12e::18)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=duerst@it.aoyama.ac.jp;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [133.2.210.64]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 00e6e48e-29b8-4a34-ad85-08d69881ca95
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(7021145)(8989299)(4534185)(7022145)(4603075)(4627221)(201702281549075)(8990200)(7048125)(7024125)(7025125)(7027125)(7023125)(5600110)(711020)(4605104)(2017052603328)(7153060)(7193020); SRVR:TYAPR01MB3152;
x-ms-traffictypediagnostic: TYAPR01MB3152:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <TYAPR01MB3152E30A1ECF8D44EC9D4783CA7F0@TYAPR01MB3152.jpnprd01.prod.outlook.com>
x-forefront-prvs: 09565527D6
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(376002)(136003)(396003)(346002)(39840400004)(199004)(189003)(386003)(6436002)(6486002)(25786009)(97736004)(2616005)(476003)(26005)(6306002)(106356001)(11346002)(102836004)(74482002)(53546011)(6116002)(446003)(3846002)(85202003)(5660300002)(71190400001)(105586002)(508600001)(31686004)(229853002)(31696002)(85182001)(6506007)(86362001)(53936002)(6246003)(4326008)(6512007)(186003)(71200400001)(486006)(76176011)(305945005)(14454004)(786003)(81166006)(81156014)(8676002)(316002)(66066001)(68736007)(2906002)(52116002)(8936002)(256004)(7736002)(99286004)(966005); DIR:OUT; SFP:1102; SCL:1; SRVR:TYAPR01MB3152; H:TYAPR01MB5149.jpnprd01.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:0; MX:1;
received-spf: None (protection.outlook.com: it.aoyama.ac.jp does not designate permitted sender hosts)
x-microsoft-exchange-diagnostics: 1;TYAPR01MB3152;23:Q1yuAYWtdO5CCY0TmNtVKjV2/KDvhPI7jCwFydU67GEfI9DeSWb3qjp/IncnDaG4m8DzrNI3jh6GBuoZwNBk4Mo5Vee+k8yb2l45Vuk8oujdcd+3LTREl5PQ0t7OgnamoIvJ7BjgYCtgY9fMdXKipBDm9mDJualpWhrBel8+9qZyIB6vhgrGeKnJ34NPZh4XK6rZue0YFGJlNPrqS8BiMVAp35axd/b8PvxiB8WGg/nJOFoSD3I9MxuPZyyr23p0tBR9wplzM8G9+Cma+vQ4OwKvVMjYGBDQoeScg1jian+PDFHY02rYZbU5EvU9lfCv0DXhBxmMjJkicuQUD2yEYV3Wqzr4vdPMNjObNLAizE3L20B8bC/3lf5LmKXCySqaoNY7dye6JbPTtoqNJ6m38t4Gqh5jvLaNYNi3VhZ+hAEFnPj4vtCRbUx6q+VGU4Fowq0QD+gNaWda0Q3yDVbtoaHltrQeI/px9mQHZ+VWiJAVyKy0YTDaUFo05Do8GzVD2AFujW1VIt9agyywpHXJ2LIEfr/ApPAAOGvxCnj2RzrW4WIZSZRc/x6sAy9KI+QN7Vg07253cRvOejvQ/MGCwy2qsyn05zxb0QMsggNRlWNwlh6u1Yc9WbZChaHrMwxnc/GHNVImK4HV5sQlnEUJgngLfu9S8DdqPsle/4ZyL9vKiZFsDcZGh9L1a/PHT9PWFLXfB84xE7W0PQBB0AWqsnEP9deW12VLuoMEaIh4U4i/Hin/21CQLPO3gS9HaRZAUa5KNbLQM+c42lQlqr8reVyG2nGUH0ZkAWQFuMLPcab19o/jCzYSdOoGYsuk9IVB1LZFImPkDDKfEDqfzyweEPWqdpXcwSGuUJNSELa/DksPk9VQgdHSyuY8N2KSaKHN4qAnPBd3aTqBVtFjw/4a6jNa+/Al/gw6p6NweLr3usXkjPFcE81cmUSw+tax0fitecjKjH5kQouBnUiPs+B+7hAk4hvJtbhfNbvRWzlGSWKCQSd4w73tqPQY0ybQf23ldTNvPYhicoEkBKZTGorNG2NSypMpZu1v2ZaqHzGKWAgopCBzVZi9hEOc8JkdZS1kJtKUWYSvjuq5a/R+vp8EZtWAx8euuTFmuzQH1MCB0C3CODwYle/ViAMTzIYeq/BhP2WuCc2d6CeOuIA/5yl6PNpcOq9yuDD6ErUu6R6Dfbrn25NecXma8eV4bXwovhlk0sqDi2sCSEfvlB/C2ng7ehI9nmryF9VWUvy8cccd6AmGlNmSLgJNyudqDv4f4mkEF/dWBoXcVKHTLjfImEsNIl6saaYAdX2WmpBLy4qcjWo=
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: x5Tl+dd0hPIzT2+MAxtBHT2etfgPXvwVXreC4/zN1epuzqNVZ6unAriJxidJCnar15TUBuYJXl4wJM7mm9aTd8PorZdLhPzMIiS9NbNj5bg36UN9hV6e+iaKxhGGovM88yIg3e9lby8RWMGn40IH1fbJes3OJv/YHBLE+b7+fAVb5aRDAL4i+bKhHVPM1AAtIh0Ck/Jlmq47Q10Z83jbICA7pmMtAbUK4il6DEbDOStUDFfrdBIcdAVDfnutxD0614Tgih5BndBukbCp/PXtAcpb2poiVJoedBk9wHvf9QfMt3zZ85qCqP4xsK3u3lv+GUtCe3HvehPD/AdDvp8ndJ5G4iTtPwrHNnuAEs1/swAg//YOFQ4WvDixjcFj8rLeFN76MYVFVYm9yORSgDIs++Eqqc5wM5Qgc9KlTda0djc=
Content-Type: text/plain; charset="utf-8"
Content-ID: <AB71D52228156B43B899DECA65CD4606@jpnprd01.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: it.aoyama.ac.jp
X-MS-Exchange-CrossTenant-Network-Message-Id: 00e6e48e-29b8-4a34-ad85-08d69881ca95
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Feb 2019 04:54:13.6023 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-id: e02030e7-4d45-463e-a968-0290e738c18e
X-MS-Exchange-Transport-CrossTenantHeadersStamped: TYAPR01MB3152
Archived-At: <https://mailarchive.ietf.org/arch/msg/uri-review/Ho5t2mykOKLL-gXH-X82Fv-_aI8>
Subject: Re: [Uri-review] Is TCP a URI scheme?
X-BeenThere: uri-review@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Proposed URI Schemes <uri-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/uri-review>, <mailto:uri-review-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/uri-review/>
List-Post: <mailto:uri-review@ietf.org>
List-Help: <mailto:uri-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/uri-review>, <mailto:uri-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Feb 2019 04:54:24 -0000

Hello Eric, others,

On 2019/02/22 09:49, Eric Johnson wrote:

> Speaking somewhat on behalf of TIBCO, I'm not sure that the use of a string
> that begins "tcp:" means that what is contained is necessarily a URL. I did
> a small amount of very informal questioning of some of my fellow employees,
> and didn't get the impression that the use of "tcp:" was anything other
> than a signal for the type of thing that followed the prefix, and not
> strictly speaking a "resource" locator.

This overlaps quite a bit with what I'd have written as an answer to the 
original question if I had had some spare time when that comes up.

One of the core points of URIs is that they unify syntax at a very high 
level (the level of foo:). That makes them very useful for pointing at 
various things, from various places. The original place was the href 
attribute of the <a> element in HTML. There, the main schemes were 
http:, https:, ftp:, mailto:, and so on.

Other places where there was a need to point to something reused URIs, 
but once in a while, there was a need to point to something that didn't 
yet have an URI scheme. With the use of URIs expanding, such things got 
more and more diverse. That somebody somewhere wanted to point to a 
(potential) tcp connection, and would used tcp: for that, was just a 
matter of time.

For quite a while, registration of URI schemes was handled rather 
strictly. It's supposed to be easier today, but it's still some work, 
some discussion, and some wait. Also, the documents describing URIs are 
not necessarily an easy read for everyone, because they use general 
terms that can easily be misunderstood.

Also, please note that we are talking about URIs here, not URLs, so it's 
resource Resource Identifier, not Locator. And "resource" is really 
extremely general, even if for some schemes (e.g. mailto:), some care is 
needed when describing what exactly it stands for.

 > On Fri, Feb 1, 2019 at 9:18 AM Ted Hardie <ted.ietf@gmail.com> wrote:
 >
 >> I don't believe it has ever been registered, even provisionally, but you
 >> can find example syntax in both IBM and TIBCO documentation of their
 >> usage.  See, for example:
 >>
 >>
 >> 
https://docs.tibco.com/pub/activespaces/2.1.6/doc/html/GUID-CAE482DF-C20D-46C4-AD2D-337535551423.html

Looking at that page, it says "TCP Discovery URL Format". I'm not 
familiar with this "discovery" part, but it may have been better to use 
something like "tcp-disc:" or so as a prefix.

Regards,   Martin.