IETF Logo Mail Archive

Re: Reigistry for tv:URI's

Lisa Dusseault <lisa@osafoundation.org> Tue, 03 October 2006 16:13 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GUmu1-0007Mj-HP; Tue, 03 Oct 2006 12:13:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GUmu0-0007MI-KA for discuss@apps.ietf.org; Tue, 03 Oct 2006 12:13:52 -0400
Received: from laweleka.osafoundation.org ([204.152.186.98]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GUmtz-0007dd-6J for discuss@apps.ietf.org; Tue, 03 Oct 2006 12:13:52 -0400
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 5F555142284; Tue, 3 Oct 2006 09:13:42 -0700 (PDT)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 18743-09; Tue, 3 Oct 2006 09:13:41 -0700 (PDT)
Received: from [192.168.1.101] (c-69-181-78-47.hsd1.ca.comcast.net [69.181.78.47]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id CA61114226E; Tue, 3 Oct 2006 09:13:40 -0700 (PDT)
In-Reply-To: <42F3BE57026C6E49B09E267EEF639D56D38E10@ms-dt01thalia.tsn.tno.nl>
References: <42F3BE57026C6E49B09E267EEF639D56D38E10@ms-dt01thalia.tsn.tno.nl>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: multipart/alternative; boundary="Apple-Mail-30--951292511"
Message-Id: <881C4925-8842-4F6E-9D6A-3D6C65343F38@osafoundation.org>
From: Lisa Dusseault <lisa@osafoundation.org>
Subject: Re: Reigistry for tv:URI's
Date: Tue, 03 Oct 2006 09:13:37 -0700
To: "Keesmaat, N.W. (Iko)" <iko.keesmaat@tno.nl>
X-Mailer: Apple Mail (2.752.2)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
Cc: Mark Baker <distobj@acm.org>, "Zigmond, Dan" <djz@google.com>, discuss@apps.ietf.org
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

Resolvability might be a local matter in the meantime.  A device  
could have a configuration list of available channels containing  
their tv:URIs and their frequencies or other information on how to  
access.   Then when that device receives a tv: URI it is perfectly  
capable of turning on the right channel.  To schedule recordings or  
publicize showings, this could all be quite useful.

Lisa

On Oct 3, 2006, at 4:06 AM, Keesmaat, N.W. (Iko) wrote:

> About the resolvability of tv:URIs we have a future hope that they  
> might
> become resolvable by automatic means. But in the mean time we are  
> quite
> happy at getting the list of available tv:URIs and some identifying
> information. At configuration of a TV application, the tv:URI can then
> be configured by human intervention after a lookup in the tv:URI
> registry. Note that a similar situation already exists in Europe in  
> case
> of the use of Showview (see http://www.showview.com): each buyer of a
> video/hard disk recorder with Showview needs to configure the  
> mapping of
> Showview channels onto actual TV channels.

v2.23.0 | Report a Bug | By Email