Re: [AVTCORE] I-D Action: draft-ietf-payload-rtp-ttml-06.txt

James Sandford <james.sandford@bbc.co.uk> Fri, 22 November 2019 07:56 UTC

Return-Path: <james.sandford@bbc.co.uk>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D0C112011E for <avt@ietfa.amsl.com>; Thu, 21 Nov 2019 23:56:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 VnPFgfZphULH for <avt@ietfa.amsl.com>; Thu, 21 Nov 2019 23:56:43 -0800 (PST)
Received: from mailout0.telhc.bbc.co.uk (mailout0.telhc.bbc.co.uk [132.185.161.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A80EC1200B5 for <avtcore@ietf.org>; Thu, 21 Nov 2019 23:56:43 -0800 (PST)
Received: from BGB01XI1011.national.core.bbc.co.uk (bgb01xi1011.national.core.bbc.co.uk [10.161.14.15]) by mailout0.telhc.bbc.co.uk (8.15.2/8.15.2) with ESMTP id xAM7ucBg022558; Fri, 22 Nov 2019 07:56:38 GMT
Received: from BGB01XUD1001.national.core.bbc.co.uk ([10.184.52.80]) by BGB01XI1011.national.core.bbc.co.uk ([10.161.14.15]) with mapi id 14.03.0408.000; Fri, 22 Nov 2019 07:56:37 +0000
From: James Sandford <james.sandford@bbc.co.uk>
To: "Martin J. Dürst" <duerst@it.aoyama.ac.jp>, Barry Leiba <barryleiba@computer.org>, Roni Even <Even.roni@huawei.com>
CC: "avtcore@ietf.org" <avtcore@ietf.org>
Thread-Topic: I-D Action: draft-ietf-payload-rtp-ttml-06.txt
Thread-Index: AQHVoQLK8QBdHqzYmk6qquUDeBWEa6eW0Pdi
Date: Fri, 22 Nov 2019 07:56:36 +0000
Message-ID: <734752AF0E88364D983373FE5CEFED577E79914F@bgb01xud1001>
References: <157418109116.21482.14671758061196232707@ietfa.amsl.com>, <df2cae07-8d15-d164-5ced-cd57bc3e58ae@it.aoyama.ac.jp>
In-Reply-To: <df2cae07-8d15-d164-5ced-cd57bc3e58ae@it.aoyama.ac.jp>
Accept-Language: en-GB, en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [217.155.207.88]
x-exclaimer-md-config: c91d45b2-6e10-4209-9543-d9970fac71b7
x-tm-as-product-ver: SMEX-12.5.0.1300-8.2.1013-24054.007
x-tm-as-result: No-16.041300-8.000000-10
x-tmase-matchedrid: /77LoUQXvQ+7lpQUW6Uvz7iMC5wdwKqdwZLXS0hN8p2o+b+yOP0oGOEt b6e4qSOWCJYDy+Bt38vI/eRE19UjxGNwa9aM37neqa6SJk58+LanD+CrMu2JyQFHdaY+PNgrFWn lWpPcqhierMHa9k/L4xYO6DMwMrycFp2/4Xy5xIjCtSG/SQAC8XLhUU/qa4OG64D1DRNlnW215M 3sftCcB9OBE41facYbRoBFWJaq5ctHOh+HtZFlz0hEDfw/93BuQR8ML/5xWaYifM7JMNHW6+Hwo KIjQi1ujq/V/8vFgOXdEXfBhcHtg4+eiI05y0fplUgQqGVMqmwfN1sSaNSB9VXzges/EJ9shILj 1WsdJh2qzOnd87YWPXo8EHaw/bpny5j7H7ClYgfLtNJZxvPj1uPmXK6rwg5B+Cckfm+bb6AUAYC BFYQn1IQW51ucJ5ntPjm43gvFDc/sQvNjLUt1edxajlW+zwxCIfyQNHR2naYFt5BIjeJMnzolD4 pSQo0FI38a8gQHPxGZWAQnOZTR+rcH4/RZ7lQnCLNfGU4dffgZKp0SZ4P+dal3hIudi9H4AHvW0 Kjb/UH9sTyFzgtJ5tpmIkCPyKwkVjB2sAdY1mUc8J6ZrWP/q1Fa7g7C8t2EmyiLZetSf8my5/tF Zu9S3LqN6SfkrETcC24oEZ6SpSkgbhiVsIMQKxZ5+8y352uC
x-tm-as-user-approved-sender: Yes
x-tm-as-user-blocked-sender: No
x-tmase-result: 10--16.041300-8.000000
x-tmase-version: SMEX-12.5.0.1300-8.2.1013-24054.007
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/NWG0glQCeDtYexAA04vgfL0O00M>
Subject: Re: [AVTCORE] I-D Action: draft-ietf-payload-rtp-ttml-06.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Nov 2019 07:56:50 -0000

Hello,
Thanks for your comments. I don't believe "workflow" is broadcast specific. I've seen it used in the context of many processes where multiple actors handle something in sequence. This includes manufacturing workflows, software development workflows, and even RFC creation. From the tools.ietf.org page:

    The New Internet Draft Submission Tool replaces the older Draft Submission Tool and the even older email submission workflow

Are you unfamiliar with the term "workflow" or suggesting its inappropriate in this context?

Regards,
James

==========
James Sandford
R&D Project Engineer

BBC Research and Development
5th Floor
Dock House
MediaCityUK
Salford
M50 2LH

Tel: 030304 (09549)
Web: http://www.bbc.co.uk/rd

________________________________________
From: Martin J. Dürst [duerst@it.aoyama.ac.jp]
Sent: 22 November 2019 07:02
To: Barry Leiba; Roni Even; James Sandford
Cc: avtcore@ietf.org
Subject: Fwd: I-D Action: draft-ietf-payload-rtp-ttml-06.txt

Sorry that this only just now cought my eye, but the document is in the
RFC Editor's queue for only 1 day yet, and I think there are serious
editorial changes that would improve the document quite a bit.

The document mentions the word "workflow" to describe TTML several
times, in particular two times in the abstract. This was surprising to
me because while I have been involved in W3C for a long time, I have
never heard the word "workflow" in connection with TTTML.

I just checked, and indeed Timed Text Markup Language 2 (TTML2)
(W3C Recommendation 08 November 2018, https://www.w3.org/TR/ttml2/)
doesn't mention the word "workflow" a single time. The way TTML
describes itself is:

    The Timed Text Markup Language is a content type that
    represents timed text media for the purpose of interchange
    among authoring systems. Timed text is textual information
    that is intrinsically or extrinsically associated with
    timing information.

The word "workflow" may have a very specific meaning in the television
industry, which lead the author of this document to choose this word,
but it is very confusing for readers not familiar with such terminology.
So in order to avoid such confusion, I strongly suggest to
remove/replace the word "workflow" from the document, and in particular
from the abstract. Given the nature of RTP, it seems to me that it's
pretty obvious that a payload format is needed for 'live' use cases, and
not for file transfer (which may be done with HTTP or FTP or whatever
else). So I don't think there is a need to bring in the specific
viewpoint of the TV industry and therewith confuse people from other
industries and describe TTML in a completely different way than people
in general are understanding it.

Sorry this got a bit long, but I hope I got my point across. If I should
send this somewhere else, please tell me.

Regards,   Martin.

-------- Forwarded Message --------
Subject: I-D Action: draft-ietf-payload-rtp-ttml-06.txt
Date: Tue, 19 Nov 2019 08:31:31 -0800
From: internet-drafts@ietf.org
Reply-To: internet-drafts@ietf.org, avt@ietf.org
To: i-d-announce@ietf.org
CC: avt@ietf.org


A New Internet-Draft is available from the on-line Internet-Drafts
directories.
This draft is a work item of the Audio/Video Transport Core Maintenance
WG of the IETF.

         Title           : RTP Payload for TTML Timed Text
         Author          : James Sandford
        Filename        : draft-ietf-payload-rtp-ttml-06.txt
        Pages           : 17
        Date            : 2019-11-19

Abstract:
    This memo describes a Real-time Transport Protocol (RTP) payload
    format for TTML, an XML based timed text format for live and file
    based workflows from W3C.  This payload format is specifically
    targeted at live workflows using TTML.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-payload-rtp-ttml/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-payload-rtp-ttml-06
https://datatracker.ietf.org/doc/html/draft-ietf-payload-rtp-ttml-06

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-payload-rtp-ttml-06


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
.