ETSI TISPAN interest in tv:URI

"Deventer, M.O. (Oskar) van" <oskar.vandeventer@tno.nl> Wed, 04 July 2007 09:35 UTC

Return-path: <discuss-bounces@apps.ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I61Gl-0006Sw-Qv; Wed, 04 Jul 2007 05:35:31 -0400
Received: from discuss by megatron.ietf.org with local (Exim 4.43) id 1I61Gl-0006Sr-H6 for discuss-confirm+ok@megatron.ietf.org; Wed, 04 Jul 2007 05:35:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I61Gl-0006Si-7H for discuss@apps.ietf.org; Wed, 04 Jul 2007 05:35:31 -0400
Received: from mail93.messagelabs.com ([194.106.220.67]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1I61Gh-0006cC-NU for discuss@apps.ietf.org; Wed, 04 Jul 2007 05:35:31 -0400
X-VirusChecked: Checked
X-Env-Sender: oskar.vandeventer@tno.nl
X-Msg-Ref: server-8.tower-93.messagelabs.com!1183541724!9104402!1
X-StarScan-Version: 5.5.12.11; banners=tno.nl,-,-
X-Originating-IP: [134.221.2.2]
Received: (qmail 28411 invoked from network); 4 Jul 2007 09:35:24 -0000
Received: from zeus.tno.nl (HELO zeus.tno.nl) (134.221.2.2) by server-8.tower-93.messagelabs.com with SMTP; 4 Jul 2007 09:35:24 -0000
Received: from ms-dt01thalia.tsn.tno.nl (ms-dt01thalia.tno.nl [134.221.225.157]) by zeus.tno.nl (8.11.7p1+Sun/8.11.7) with ESMTP id l649ZNx06055 for <discuss@apps.ietf.org>; Wed, 4 Jul 2007 11:35:24 +0200 (MEST)
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
Subject: ETSI TISPAN interest in tv:URI
Date: Wed, 04 Jul 2007 11:35:22 +0200
Message-ID: <42F3BE57026C6E49B09E267EEF639D56019F7C94@ms-dt01thalia.tsn.tno.nl>
In-Reply-To: <42F3BE57026C6E49B09E267EEF639D56D38E21@ms-dt01thalia.tsn.tno.nl>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: ETSI TISPAN interest in tv:URI
Thread-Index: AcboWEdyz2u14ulLQmOOXlEqwqG1OQDJhFfwNKOJfCA=
From: "Deventer, M.O. (Oskar) van" <oskar.vandeventer@tno.nl>
To: discuss@apps.ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f
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

All,

The issue of identification of television channels has been discussed in
the ETSI TISPAN 14bis meeting of last week. The application of this
identification is IPTV Presence: a presentity can publish which TV
channel he is watching. The fact that ETSI TISPAN has requirements
related to the identification of TV channels (e.g. tv:URI) is reflected
in the recent update of our internet draft
http://www.ietf.org/internet-drafts/draft-keesmaat-tvreg-01.txt.

TISPAN WG1 (services) and WG2 (architecture) have defined the following
requirements, relevant to our IETF APPS mailing list discussions on the
tv:URI last October.

========== Start of TISPAN requirements ==========

WI01044 (Draft TS 181 016):
"Users' presence information may be related to, e.g., their connection
status, location information, channel currently accessed or acceptable
communication means. Presence information on channel currently accessed
may be used by another user to instruct his set-top box with a single
click to switch to the identified channel, or to instruct his set-top
box to keep following identified channel changes. There may be
significant delays in this following, depending on the update speed of
the presence service.
Any published presence information should only be disseminated other
users that are authorised to receiving this presence information
according to the presentity policies
Users can also define a set of access rules to control access to their
presence information.
6.2.1.1		It must be possible to define presence information
related to the IPTV experience, e.g. channel currently accessed. The
identification of the channel currently accessed shall be
machine-readable. Language dependent information may also be made
available to watchers."

WI02048 (Draft TS 182 027):
"The following specific IPTV attributes may also be supported:
channel currently accessed,
program currently watched, when available.
content currently accessed.
If the IPTV presence attribute "channel currently accessed" is
supported, then the machine-readable part of the identification of the
channel shall be globally unique. The term globally unique here means
that there is no ambiguity in the identification of the channel if
presentity and watcher (for terminology, see in ETSI 182 008) are with
different network operators and/or in different countries."

========== End of TISPAN requirements ==========

TISPAN WG4 (identifiers) has allocated a session in next TISPAN meeting
dedicated to "Tv URI identifier and resolution". The meeting details for
this session are as follows.
Meeting: ETSI TISPAN 14ter
Location: ETSI Headquarters, Sophia Antipolis
Dates: 3-7 September 2007
WG4 session on tv:URI: Wednesday 5 September, 11:15-13:00

With this email, I would like to invite interested parties to
participate and/or contribute to this WG4 session.

Best regards,

Oskar 

-----Original Message-----
From: Keesmaat, N.W. (Iko) 
Sent: maandag 9 oktober 2006 13:25
To: discuss@apps.ietf.org
Cc: Clive D.W. Feather; Zigmond, Dan
Subject: RE: Reigistry for tv:URI's

[... previous mail thread ...]

This e-mail and its contents are subject to the DISCLAIMER at http://www.tno.nl/disclaimer/email.html