Re: Update of RFC 2838, tv: URI

Julian Reschke <julian.reschke@gmx.de> Sun, 20 August 2006 09:40 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GEjnV-0003ci-Ak; Sun, 20 Aug 2006 05:40:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GEjnT-0003cd-TE for discuss@apps.ietf.org; Sun, 20 Aug 2006 05:40:47 -0400
Received: from mail.gmx.net ([213.165.64.20]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GEjnS-0002if-Gg for discuss@apps.ietf.org; Sun, 20 Aug 2006 05:40:47 -0400
Received: (qmail invoked by alias); 20 Aug 2006 09:40:45 -0000
Received: from p508FA4F7.dip0.t-ipconnect.de (EHLO [192.168.178.22]) [80.143.164.247] by mail.gmx.net (mp026) with SMTP; 20 Aug 2006 11:40:45 +0200
X-Authenticated: #1915285
Message-ID: <44E82E18.6030605@gmx.de>
Date: Sun, 20 Aug 2006 11:40:40 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.0.4) Gecko/20060516 Thunderbird/1.5.0.4 Mnenhy/0.7.4.666
MIME-Version: 1.0
To: "Deventer, M.O. (Oskar) van" <oskar.vandeventer@tno.nl>
Subject: Re: Update of RFC 2838, tv: URI
References: <42F3BE57026C6E49B09E267EEF639D56C2A729@ms-dt01thalia.tsn.tno.nl>
In-Reply-To: <42F3BE57026C6E49B09E267EEF639D56C2A729@ms-dt01thalia.tsn.tno.nl>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: discuss@apps.ietf.org, "Keesmaat, N.W. (Iko)" <iko.keesmaat@tno.nl>, "Zigmond, Dan" <djz@google.com>
X-BeenThere: discuss@apps.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: general discussion of application-layer protocols <discuss.apps.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=unsubscribe>
List-Post: <mailto:discuss@apps.ietf.org>
List-Help: <mailto:discuss-request@apps.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=subscribe>
Errors-To: discuss-bounces@apps.ietf.org

Hi,

first of all, I was surprised to hear that there a "tv" URI scheme. 
Turns out, it hasn't been published through the IESG, and the URI scheme 
hasn't been registered through IANA.

I do agree with your analysis that the URI scheme in itself is 
insufficient. Maybe this would have been discovered if it would have 
been published through the IESG.

Now, as an informational spec what it says may be OK - it just documents 
what some vendors (probably mainly in the US) have been using.

Now if what you're looking for is a URI to be used on the Internet, 
requirements are higher. In particular, you should demonstrate that you 
actually need a URI scheme, which is not completely obvious to me.

Best regards, Julian