[AVTCORE] Fwd: I-D Action: draft-ietf-payload-rtp-ttml-06.txt
Martin J. Dürst <duerst@it.aoyama.ac.jp> Fri, 22 November 2019 07:02 UTC
Return-Path: <duerst@it.aoyama.ac.jp>
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 CBAFF12009C for <avt@ietfa.amsl.com>; Thu, 21 Nov 2019 23:02:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 4bn1P4VrN33m for <avt@ietfa.amsl.com>; Thu, 21 Nov 2019 23:02:20 -0800 (PST)
Received: from JPN01-OS2-obe.outbound.protection.outlook.com (mail-eopbgr1410120.outbound.protection.outlook.com [40.107.141.120]) (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 DF95D12006F for <avtcore@ietf.org>; Thu, 21 Nov 2019 23:02:19 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=gss6ki4s6AAtT2ZIzvZoULDtg15IbrtSlwDabAMC0343V0B2qqevz2czrGpNskcc/OwYmrEWUPwEFNC2sjxccH6lf/gnP1eS6ZsYyc4hha3AgoGYrNEQ0qZE4PYvVjK1ol0GFZSL5uOzu9DPFwPdjE8GubE6VYZHOa4MBAzToq34nd8hltCCqr+QINQy+kqUGFntr+kUsGTr++Lm9huW6/8693+BRuT0CMuNMpsuxSyTNls2iomCoWZ0DsGC5l95tiUN9R5Rx/A60iwpOnVC/aLISp3H8EbyN610lqxikhRM6X9II0Bs9SJWTuEbMrkiTc4kiAIVu9GmV1Mtdql6Sw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=wLOI8MBazhJLjC8MHV6B9bbj2llL8cVFAZ3IOOr4XDk=; b=liV7acR6FRC1y8KsuWWtbk2SkxFnmVaEOjORdOEAFRrLx8sIYulSpO35QFq4O81PlzsaHFCZTHZUs7ozRy3Ob7eCBkdFgejNps9GNOR6zxz4p/qkFMuDwGivDr/YwH5E3JRkEAqbqD8cyLUqSdSKxtcpgFQDSbiS1B2Hf8bNm0vYs6xwGdHIdTKmm8nRWnsITv+IljST8zagPz4ILd9NYQr1G/W68L8v320NJoSYfcpBmFtGPQjWFG0B468XAkNNrMaOgKotln0BozoUoAHJdAbxEMu+VT6TEqDMucaSPoPzHMD+NVE+X8jH8Mjoo7U0Us7/fs1HIZA+x1ZB23RUbw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=it.aoyama.ac.jp; dmarc=pass action=none header.from=it.aoyama.ac.jp; dkim=pass header.d=it.aoyama.ac.jp; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=itaoyama.onmicrosoft.com; s=selector2-itaoyama-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=wLOI8MBazhJLjC8MHV6B9bbj2llL8cVFAZ3IOOr4XDk=; b=t+DdsHduv5US72TCERNoEP3cbYU3nBTVxJQce7wScizmWg8lX7XlcMWvIa+oKfcBoqDYEmCzHC3H+SrdS+w7wI7lvrexcSEbhk0g7JMZ14qEz7qNPndRRq0zlIPQPc6sv/h/LMIhDgiwi325VFA5Vy3B3k44v3X4M71pa3XSRXQ=
Received: from OSAPR01MB4450.jpnprd01.prod.outlook.com (20.179.176.211) by OSAPR01MB2418.jpnprd01.prod.outlook.com (52.134.247.149) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2474.17; Fri, 22 Nov 2019 07:02:17 +0000
Received: from OSAPR01MB4450.jpnprd01.prod.outlook.com ([fe80::5cee:56cf:c45e:11a]) by OSAPR01MB4450.jpnprd01.prod.outlook.com ([fe80::5cee:56cf:c45e:11a%7]) with mapi id 15.20.2474.019; Fri, 22 Nov 2019 07:02:17 +0000
From: "Martin J. Dürst" <duerst@it.aoyama.ac.jp>
To: Barry Leiba <barryleiba@computer.org>, Roni Even <Even.roni@huawei.com>, "james.sandford@bbc.co.uk" <james.sandford@bbc.co.uk>
CC: "avtcore@ietf.org" <avtcore@ietf.org>
Thread-Topic: I-D Action: draft-ietf-payload-rtp-ttml-06.txt
Thread-Index: AQHVoQLGw4W+D+qSjUS2dZ3BrVb+Yw==
Date: Fri, 22 Nov 2019 07:02:17 +0000
Message-ID: <df2cae07-8d15-d164-5ced-cd57bc3e58ae@it.aoyama.ac.jp>
References: <157418109116.21482.14671758061196232707@ietfa.amsl.com>
In-Reply-To: <157418109116.21482.14671758061196232707@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-clientproxiedby: TY1PR01CA0168.jpnprd01.prod.outlook.com (2603:1096:402::20) To OSAPR01MB4450.jpnprd01.prod.outlook.com (2603:1096:604:63::19)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=duerst@it.aoyama.ac.jp;
x-ms-exchange-messagesentrepresentingtype: 1
x-forwarded-message-id: <157418109116.21482.14671758061196232707@ietfa.amsl.com>
x-originating-ip: [133.2.210.64]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: ece34c32-a82c-473a-da18-08d76f19e904
x-ms-traffictypediagnostic: OSAPR01MB2418:
x-ms-exchange-purlcount: 7
x-microsoft-antispam-prvs: <OSAPR01MB2418A850B6B2FF62F5F42502CA490@OSAPR01MB2418.jpnprd01.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 02296943FF
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(136003)(396003)(39840400004)(376002)(346002)(366004)(189003)(199004)(5660300002)(25786009)(66574012)(305945005)(316002)(7736002)(110136005)(102836004)(86362001)(85182001)(966005)(52116002)(26005)(2501003)(786003)(508600001)(85202003)(6506007)(2616005)(76176011)(386003)(446003)(11346002)(4001150100001)(31696002)(66066001)(186003)(71200400001)(71190400001)(81156014)(8676002)(81166006)(6486002)(64756008)(31686004)(256004)(14444005)(14454004)(4326008)(229853002)(6306002)(8936002)(66446008)(2473003)(99286004)(6436002)(6512007)(2906002)(3846002)(6116002)(66946007)(66556008)(66476007); DIR:OUT; SFP:1102; SCL:1; SRVR:OSAPR01MB2418; H:OSAPR01MB4450.jpnprd01.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:0;
received-spf: None (protection.outlook.com: it.aoyama.ac.jp does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: Y6AAoueTvZlh5A0wV/2A+iwEz7lq/tFdMQh4tVYW71PyVhCCBq91gmK3QKd19a4etaV2KRYgQnY8xwMI6XQT34oAT5FyAo10EWQZzeP1tugvz+MNUnEKBxgcaqE6tYbZR2vOnw6wbTB5pwzftZJFRUzEXVvJCDeW6HsVfgUD0URsNc+65ajEvdLra7TCEtLmpg5WXkg8gx8nz5mtuul/Jh+m+kQVSs+q5eiIMztsqskzBaajpqrH3r+POsSVYYnigbMwqmRRAmkthHsw79d2UiB1nDkxVUao0eT0ls+c/ITGNM5xRkOnh2yZneyLTTvmYsOvtMhzAXwkNruVB5Tbm4j+umly6JM6xuYF9QrbaUJQ1h40KxBICue1129GJlAzP5JJgcjY3FpfktNxupxQZf5SAj8cd//RTs59ZesRwE+ot7e+FghrbSul+v+/+2cl8vzzg9kj9F/ir2JSfPzXSjwMNrqrPXYo+5KYnmhu+p8=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <082DCB770C7E4C4E93BA39D65C96DEFA@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: ece34c32-a82c-473a-da18-08d76f19e904
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Nov 2019 07:02:17.2638 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: e02030e7-4d45-463e-a968-0290e738c18e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: QVPYlZsgkAmsJz3BWYgGGrb4y5w6gxR0PpvNSOnQJPATZu/Qb9K1PGIdooDK1CR45qWvAoONWVGNBXe6OXryNA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: OSAPR01MB2418
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/i8D1XII6mqlXB9tKrW5CBzcLgPo>
Subject: [AVTCORE] Fwd: 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:02:23 -0000
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 .
- [AVTCORE] I-D Action: draft-ietf-payload-rtp-ttml… internet-drafts
- [AVTCORE] Fwd: I-D Action: draft-ietf-payload-rtp… Martin J. Dürst
- Re: [AVTCORE] I-D Action: draft-ietf-payload-rtp-… James Sandford
- Re: [AVTCORE] I-D Action: draft-ietf-payload-rtp-… Barry Leiba
- Re: [AVTCORE] I-D Action: draft-ietf-payload-rtp-… Martin J. Dürst
- Re: [AVTCORE] I-D Action: draft-ietf-payload-rtp-… James Sandford
- Re: [AVTCORE] I-D Action: draft-ietf-payload-rtp-… Martin J. Dürst
- Re: [AVTCORE] I-D Action: draft-ietf-payload-rtp-… James Sandford
- Re: [AVTCORE] I-D Action: draft-ietf-payload-rtp-… Martin J. Dürst
- Re: [AVTCORE] I-D Action: draft-ietf-payload-rtp-… Barry Leiba
- Re: [AVTCORE] I-D Action: draft-ietf-payload-rtp-… James Sandford