Re: [AVTCORE] Benjamin Kaduk's No Objection on draft-ietf-payload-rtp-ttml-03: (with COMMENT)

Benjamin Kaduk <kaduk@mit.edu> Fri, 18 October 2019 19:38 UTC

Return-Path: <kaduk@mit.edu>
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 02640120817; Fri, 18 Oct 2019 12:38:12 -0700 (PDT)
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_HELO_NONE=0.001, SPF_PASS=-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 iurY2552-udD; Fri, 18 Oct 2019 12:38:10 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (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 11A461208DE; Fri, 18 Oct 2019 12:38:09 -0700 (PDT)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id x9IJbskP001689 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 18 Oct 2019 15:37:56 -0400
Date: Fri, 18 Oct 2019 12:37:53 -0700
From: Benjamin Kaduk <kaduk@mit.edu>
To: James Sandford <james.sandford@bbc.co.uk>
Cc: The IESG <iesg@ietf.org>, "draft-ietf-payload-rtp-ttml@ietf.org" <draft-ietf-payload-rtp-ttml@ietf.org>, Roni Even <roni.even@huawei.com>, "avtcore-chairs@ietf.org" <avtcore-chairs@ietf.org>, "avt@ietf.org" <avt@ietf.org>
Message-ID: <20191018193753.GJ43312@kduck.mit.edu>
References: <157127900013.9968.12681926421251344475.idtracker@ietfa.amsl.com> <734752AF0E88364D983373FE5CEFED5770DE4C0A@bgb01xud1001>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <734752AF0E88364D983373FE5CEFED5770DE4C0A@bgb01xud1001>
User-Agent: Mutt/1.12.1 (2019-06-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/nYUW_l7LqZYxGxkeDXM6gvVzW7A>
Subject: Re: [AVTCORE] Benjamin Kaduk's No Objection on draft-ietf-payload-rtp-ttml-03: (with COMMENT)
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, 18 Oct 2019 19:38:12 -0000

On Fri, Oct 18, 2019 at 03:01:58PM +0000, James Sandford wrote:
> Hello,
> I'm updating the I-D to address these (and other) comments. I'm unsure what isn't meant by the last item, though. "I might include a short note that the text contents are meant to be interpreted by a human, and content from untrusted sources should be viewed with appropriate levels of skepticism". Surely this applies to any media carried over RTP? Or at least any which may be rendered for a human audience.

Basically so, yes.  So not adding such a note is perfectly fine.  As a
little more background, I had started off by thinking about the possible
consequences of modifying the timeslot for which a piece of text would be
active (whether in the XML or by way of the RTP-timestamp epoch, and
whether by direct modification of the contents or by cutting/pasting
contents/headers).  When the text is subtitles on audio/video content, such
rearrangement could cause misattribution or similar.  But, as you note, the
general case is nothing new.

-Ben