Re: [Slim] Moving forward on draft-ietf-slim-negotiating-human-language

Bernard Aboba <bernard.aboba@gmail.com> Wed, 22 November 2017 00:20 UTC

Return-Path: <bernard.aboba@gmail.com>
X-Original-To: slim@ietfa.amsl.com
Delivered-To: slim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F10B129C00 for <slim@ietfa.amsl.com>; Tue, 21 Nov 2017 16:20:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 6yzmB9oLPfQb for <slim@ietfa.amsl.com>; Tue, 21 Nov 2017 16:20:15 -0800 (PST)
Received: from mail-vk0-x22f.google.com (mail-vk0-x22f.google.com [IPv6:2607:f8b0:400c:c05::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B72FF129493 for <slim@ietf.org>; Tue, 21 Nov 2017 16:20:15 -0800 (PST)
Received: by mail-vk0-x22f.google.com with SMTP id o145so8806866vkd.0 for <slim@ietf.org>; Tue, 21 Nov 2017 16:20:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=+DzuxBdLA3n9fJafjBDbSqTIDSB6Amp7hiFzUPC5PIQ=; b=Bz7lZzHvPRsC68wTTeRODibXPi1UZrg0lHW5Ny+TFG742K8gUpAbq5DdRfauLOaXhG hwkKUDG4DagTJVnII1wpk+HJ2z/DOSFyjC92lTfTbn6wzCs9x56CaNDamRjWgdgAqTkc BMs5SIQKemz3yd/4UvW3qX8ECblcPmJo9nlsMalJ2uRiA30y7qV/rvCyj81nbifI45ZR tmqcchzzqqfHUbJBHV1+NMlMqmyP5IdRapm73ykoNI7dRFHDihZDr7fjQja/uNcOptlv qBkoRgFVHssFbli6w2KW3rCNdJNukgNmTRC6VPpEGNa5JwYefqJEA5wothdXBLI/Bag6 skOg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=+DzuxBdLA3n9fJafjBDbSqTIDSB6Amp7hiFzUPC5PIQ=; b=tW6SQ8wzqAtUinsWfd4LH3IzWc9Rpf1RALOttMXhVd7DEt6WEsUvqWeOeaVIbzD3x3 IcWuGD0lDuF5ZHe/fRaUl5AjlcufEHJKgszFQlb5CjkOqujKwJ7k8SKPzRzWoRn/xhjM WTnv6giUfs2/zInvEz75f4n6PmB3oRmGvQLmg5HgASSb/X+tW8+hgXHq8ugs1l75Hi/z +vdflsec1/g1QEx4OPThSMyqYEy6qtuUMF6sYoXniAAIvGgxq8cm7XhteqhCWqt+c3B4 li9bapPOHoMo+wEwvMYIbbrIfKhjlBVoPDrAo7Maqbvf2l4cVnoGor0aTgb0nwUrSZuq cqEA==
X-Gm-Message-State: AJaThX6x8urhKdgfZJB9gMTxtlNKEgmnAjc8S2W19yl/azwa1BjPyGZX m6F90s06HpSXdoycS8GczJrEKcCs8izKGKHKtes=
X-Google-Smtp-Source: AGs4zMbHc8UQjYJ4Z02150pomckPGvmhaWgjMv7CoeLMpXJ+Q2TQ/qSZnG+eBIguKk1LlPne9FDgHHHGcP3ZEJILKv4=
X-Received: by 10.31.92.22 with SMTP id q22mr14431732vkb.10.1511310014546; Tue, 21 Nov 2017 16:20:14 -0800 (PST)
MIME-Version: 1.0
Received: by 10.159.54.230 with HTTP; Tue, 21 Nov 2017 16:19:53 -0800 (PST)
In-Reply-To: <p06240605d63a508522b9@99.111.97.136>
References: <CAOW+2dsZtuciPiKMfif=ZmUqBcUd9TyYtL5gPYDp7ZfLOHHDBA@mail.gmail.com> <p06240600d637c6f98ecc@99.111.97.136> <CAOW+2dv5NSiCbW=p1exvPV=PF8YCVdiz2gi-OCxmaUB-jGe22w@mail.gmail.com> <p06240600d6389cd2043f@99.111.97.136> <97d9a6b8-de3b-9f79-483b-18376fcf0ced@omnitor.se> <CAOW+2dtpRoeYkMJzX9vyNUojJDax4DQUU2F4PauBwt1sm-83Hg@mail.gmail.com> <55f2b336-3f14-f49a-ec78-f00b0373db00@omnitor.se> <bc5b7aa5-7c6a-5096-47d0-01e5ee079e93@omnitor.se> <CAOW+2duUPsTY=Ygzwfu0eOYbHaBAwMqm+oxA6AdMXinxTMNM1A@mail.gmail.com> <165d2c07-19ca-f2b1-2aac-3aac842b97e9@omnitor.se> <CAOW+2dsrRoCE4YQ1U+y448C4qmMY1Hb+8jM=aTyzvsPBYA0akg@mail.gmail.com> <14297efe-82c5-a6d9-94f7-fe82be6b423a@alum.mit.edu> <CAOW+2dtej1p3pD5-FbVjnkWbXH3O6TYO7zVBqy0PAfReA1Lh4A@mail.gmail.com> <e70a716e-0e43-c39e-9ac2-71b9d4afe20a@omnitor.se> <4efeeff4-bcd7-661e-93c9-23e6fec3704b@alum.mit.edu> <p06240605d63a508522b9@99.111.97.136>
From: Bernard Aboba <bernard.aboba@gmail.com>
Date: Tue, 21 Nov 2017 16:19:53 -0800
Message-ID: <CAOW+2due6Lc1sZAcEkRoc1vsjpA7CCo+DxAqbRkeUYCkLdYSQg@mail.gmail.com>
To: Randall Gellens <rg+ietf@randy.pensive.org>
Cc: Paul Kyzivat <pkyzivat@alum.mit.edu>, slim@ietf.org
Content-Type: multipart/alternative; boundary="001a114e61a2900b10055e8748d2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/slim/G9hF3yt38hkjLtHc7XKTqoQXCdg>
Subject: Re: [Slim] Moving forward on draft-ietf-slim-negotiating-human-language
X-BeenThere: slim@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Selection of Language for Internet Media <slim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/slim>, <mailto:slim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/slim/>
List-Post: <mailto:slim@ietf.org>
List-Help: <mailto:slim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/slim>, <mailto:slim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Nov 2017 00:20:19 -0000

Randall said:

"Since the context of the draft is interactive real-time media, and since
we want to keep the draft as simple as possible, we're probably better off
not getting into lip sync.  We can just avoid mention, and it can be added
in later work."

[BA] RFC 5888 already defines how to handle lip sync negotiation in SDP.  I
think Paul's point was that that document is sufficient so that referring
to a need for "later work" is misleading.

On Tue, Nov 21, 2017 at 1:54 PM, Randall Gellens <rg+ietf@randy.pensive.org>
wrote:

> At 3:53 PM -0500 11/21/17, Paul Kyzivat wrote:
>
>  I wonder if they do it even when it isn't true.
>>
>>  For instance, consider a movie that was created in English. So the
>> actors are speaking English, the audio is labeled as English, and there is
>> lip sync.
>>
>>  Now take the same movie and dub it in Spanish. Now the audio ought to be
>> labeled as Spanish. But lip sync should no longer be indicated. Is that
>> what happens in practice?
>>
>>  Of course, a totally deaf English speaking lip reader will understand
>> both equally well. But there may not be anything in the signaling to
>> indicate that he will have English lip motion.
>>
>>  The above isn't assuming that the content is being created explicitly to
>> accommodate deaf people. If the goal is specifically to focus on that then
>> some different policies might help.
>>
>
> Since the context of the draft is interactive real-time media, and since
> we want to keep the draft as simple as possible, we're probably better off
> not getting into lip sync.  We can just avoid mention, and it can be added
> in later work.
>
> --
> Randall Gellens
> Opinions are personal;    facts are suspect;    I speak for myself only
> -------------- Randomly selected tag: ---------------
> Hospitals are Sued by 7 Foot Doctors
> --Newspaper headline
>
>
> _______________________________________________
> SLIM mailing list
> SLIM@ietf.org
> https://www.ietf.org/mailman/listinfo/slim
>