Re: [MMUSIC] New Version Notification for draft-abhishek-mmusic-superimposition-grouping-00.txt(Internet mail)

Paul Kyzivat <pkyzivat@alum.mit.edu> Tue, 19 January 2021 17:17 UTC

Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23E353A09D7 for <mmusic@ietfa.amsl.com>; Tue, 19 Jan 2021 09:17:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.264
X-Spam-Level:
X-Spam-Status: No, score=-2.264 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, NICE_REPLY_A=-0.262, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=alum.mit.edu
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 M3LF0fSgHsIX for <mmusic@ietfa.amsl.com>; Tue, 19 Jan 2021 09:17:00 -0800 (PST)
Received: from NAM12-DM6-obe.outbound.protection.outlook.com (mail-dm6nam12on2082.outbound.protection.outlook.com [40.107.243.82]) (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 43A983A09C9 for <mmusic@ietf.org>; Tue, 19 Jan 2021 09:17:00 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=lhXL+huwb+yRYuiocR2YZxHOfzjCA/reWxl9bv4HU7nqfCmOxgjyTGIi/T3aBWuAUm8EV5jGAeRRFm1Ya8GjPOLCrjX9+1Dgjrw3A2ZApu8uOwSGAq/85Tni7wNxDZ2rP/lpRRcaA4ZQiEAyRHS+rZOltdlZhVlkvdcwu7dSAk1hQyHhAK6vJoidGQMUeYF+U6VSSL3KSHY352zfcg29yWWl8DPBtpqIWnA4dq0ae0XzdmezZApBeVVAEP4BfQgYUAOI7IMy/4cOCdWF94OAv12XevDgms14D2fLPIXmo8kTFmRVlfcktgozr43gE/+i53c3SGjnrJRPS2sUJ0TOxA==
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=QRGBL6qkZey+69rAq/bmbya9eXstRT66SXp9pe2JVTY=; b=MyGTh81APXT9/pcYC22+2MNl0UP3l3sDXTogpwSy6o0aTLDU8NBDmyyoSbkbVyZDLJs1P3FcP2MvYq89WWysq+QY3lqKu1g0d2cZ/R4O6vRCyjdc/QzRDxfjBexHRYAi53b3ybBBniDJumKbUAkhdJvPGUQ6qJU5Kx5NPd3J5dtyusKOh0DCQtkqX0vVqb301QwkKrQ8fEKUzzC0Baf6bBUsHKIGUCGTWaCEd8qNh2QCk9RaUwXtIe6kHiN+wxVfKH3XbFe7nJWWNaNgiUeUDbKMklTi3u9kNa5YdC5y/Ugq2W+tci8DK8w5hLFZx6neglKO1W9hGySIGQajfGP69g==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass (sender ip is 18.7.68.33) smtp.rcpttodomain=tencent.com smtp.mailfrom=alum.mit.edu; dmarc=bestguesspass action=none header.from=alum.mit.edu; dkim=none (message not signed); arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alum.mit.edu; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=QRGBL6qkZey+69rAq/bmbya9eXstRT66SXp9pe2JVTY=; b=CR6pb3mwkLNXEvcMlDIx1aV3BxIb86GpxXNyhPQDnlBkk/jepzMD2gqqJ48bHueKZP4vHUEtsxjcTwdl/APg9zvzq/X5g5q2qBSFoOObf1xBJ/nRN83MgxoyJG7U9ZCGyrVTcguhCrRm+V41aemaaPvLAfOF+C9DKOrsuK4Rc1o=
Received: from SN6PR01CA0022.prod.exchangelabs.com (2603:10b6:805:b6::35) by CY4PR12MB1816.namprd12.prod.outlook.com (2603:10b6:903:11c::18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3763.14; Tue, 19 Jan 2021 17:16:58 +0000
Received: from SN1NAM02FT064.eop-nam02.prod.protection.outlook.com (2603:10b6:805:b6:cafe::b5) by SN6PR01CA0022.outlook.office365.com (2603:10b6:805:b6::35) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3763.10 via Frontend Transport; Tue, 19 Jan 2021 17:16:57 +0000
X-MS-Exchange-Authentication-Results: spf=pass (sender IP is 18.7.68.33) smtp.mailfrom=alum.mit.edu; tencent.com; dkim=none (message not signed) header.d=none;tencent.com; dmarc=bestguesspass action=none header.from=alum.mit.edu;
Received-SPF: Pass (protection.outlook.com: domain of alum.mit.edu designates 18.7.68.33 as permitted sender) receiver=protection.outlook.com; client-ip=18.7.68.33; helo=outgoing-alum.mit.edu;
Received: from outgoing-alum.mit.edu (18.7.68.33) by SN1NAM02FT064.mail.protection.outlook.com (10.152.72.143) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3763.12 via Frontend Transport; Tue, 19 Jan 2021 17:16:56 +0000
Received: from MacBook-Air.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.14.7/8.12.4) with ESMTP id 10JHGrFr023794 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT); Tue, 19 Jan 2021 12:16:54 -0500
To: "rabhishek(RohitAbhishek)" <rabhishek@tencent.com>, "mmusic@ietf.org" <mmusic@ietf.org>
References: <160771931179.3111.1400354969020371031@ietfa.amsl.com> <BLAPR07MB75720867628E07B8C3D07F23F3CA0@BLAPR07MB7572.namprd07.prod.outlook.com> <AM0PR07MB3860502D06574BC64596665A93C90@AM0PR07MB3860.eurprd07.prod.outlook.com> <ac9b28ee-d9fe-93e2-2e14-6fe95df53ddf@alum.mit.edu> <28946d30-d203-9890-1048-5ceeaefc3c27@alum.mit.edu> <b463a0b1-aad8-8534-e33e-f2c415441b60@alum.mit.edu> <AM0PR07MB38605AA9594E6511CBD0BDCB93A80@AM0PR07MB3860.eurprd07.prod.outlook.com> <d0ccc4f1-46b8-0b0e-4981-856a1eadd5a6@alum.mit.edu> <9554D892-4C5F-4D8D-BD90-3784DB456752@tencent.com> <ccf67fd2-43fd-e531-388d-b898209cb1f6@alum.mit.edu> <A39C2CEE-6F55-49CF-9713-E66E25FD7E8C@tencent.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <cc3a4661-5d52-11b8-ce0a-3413db525b79@alum.mit.edu>
Date: Tue, 19 Jan 2021 12:16:53 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.16; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <A39C2CEE-6F55-49CF-9713-E66E25FD7E8C@tencent.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-EOPAttributedMessage: 0
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 0e88d5ee-931e-4dd4-ba5f-08d8bc9e05f6
X-MS-TrafficTypeDiagnostic: CY4PR12MB1816:
X-LD-Processed: 3326b102-c043-408b-a990-b89e477d582f,ExtAddr,ExtFwd
X-MS-Exchange-Transport-Forked: True
X-Microsoft-Antispam-PRVS: <CY4PR12MB1816A708E8A341B6A2CEE38AF9A30@CY4PR12MB1816.namprd12.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:9508;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: O0QzbX3qrqaFijt7M7a1qowsvFeHjmlltWOWBafLutNrC0TUIAfIe9sn1gjLfJJf/2afYp/1nUk3A5qsrvCWRVnMzM+ldM3H+4Abc2lCy5ABU1ARPxxfeqsCiUJByyysO1jDJRZhmcqFsQoyhRHW2Pghu36dx5PwV3SVkVO75YlugY1nu6ftWsqdafD89yZzmPEoYOUxqqaZAxRiRR1pW6s3U1eaMyx7Drkqhmlgq24V05O2l+SazFaEPtVgbvObh998I0TMehra1IE6CNMiXHseWLqpOehQGZv9qUbM0699nAjrjDgxN07TCCIoQ6u48BBCk0FlsxJ96MeAV1QH2rSYw5mVdCB/RCBZBiWJJ66nlcef+iNDNFmkTp8omHtFC3bYU1QSK7esK1WZ+AYst/7qObwtGtDG648f236vRvJSJhyDY7XXJY7qyrBlzK72k+PQuapKK7i7zZQT0a+U/vrN6QBzjSsFJIXk0AnqTGwjMpnGUIU5oEkpVTU5SDXY
X-Forefront-Antispam-Report: CIP:18.7.68.33; CTRY:US; LANG:en; SCL:1; SRV:; IPV:CAL; SFV:NSPM; H:outgoing-alum.mit.edu; PTR:outgoing-alum.mit.edu; CAT:NONE; SFS:(136003)(39860400002)(396003)(376002)(346002)(46966006)(31686004)(5660300002)(8676002)(47076005)(82310400003)(31696002)(956004)(2616005)(2906002)(8936002)(336012)(356005)(86362001)(7596003)(186003)(82740400003)(36906005)(316002)(83380400001)(786003)(26005)(70206006)(110136005)(53546011)(70586007)(478600001)(75432002)(15650500001)(43740500002); DIR:OUT; SFP:1101;
X-OriginatorOrg: alum.mit.edu
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 19 Jan 2021 17:16:56.1846 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 0e88d5ee-931e-4dd4-ba5f-08d8bc9e05f6
X-MS-Exchange-CrossTenant-Id: 3326b102-c043-408b-a990-b89e477d582f
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=3326b102-c043-408b-a990-b89e477d582f; Ip=[18.7.68.33]; Helo=[outgoing-alum.mit.edu]
X-MS-Exchange-CrossTenant-AuthSource: SN1NAM02FT064.eop-nam02.prod.protection.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Anonymous
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR12MB1816
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/lOwJeixq7eXidwacx8KQSYSBrcI>
Subject: Re: [MMUSIC] New Version Notification for draft-abhishek-mmusic-superimposition-grouping-00.txt(Internet mail)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jan 2021 17:17:02 -0000

Rohit,

On 1/19/21 2:57 AM, rabhishek(RohitAbhishek) wrote:
> Hi Paul,
> 
> Thanks again for your feedback.
> 
> My comments below
> 
> On 1/18/21, 7:32 AM, "Paul Kyzivat" <pkyzivat@alum.mit.edu> wrote:
> 
>      On 1/17/21 5:29 PM, rabhishek(RohitAbhishek) wrote:
> 
>      > Hi Paul, Christer,
> 
>      >
> 
>      > My understanding is the transparent attribute is same as alpha 
> compositing which would control the linear interpolation between the 
> foreground and the background pixels. Here’s an example wrt figure 1 in 
> the draft.
> 
>      First, I'm concerned with you starting your reply with "my 
> understanding
> 
>      is ...". This is your draft! The goal is to ensure that all readers 
> come
> 
>      to the same understanding. There should be no vagueness.
> 
> *Rohit: I will make sure to phrase it correctly moving forward **😃***
> 
>      Another thing: Section 5 says:
> 
>              transparency-attribute =
> 
>                           "a=transparency:" transparency-tag
> 
>              transparency-tag =tranparency-value *("," 
> tranparency-value) CRLF
> 
>              transparency-value= alpha
> 
>          Alpha describes the transparency for the foreground media 
> stream.  It
> 
>          is identified by its transparency-tag values in the transparency-
> 
>          attribute.  It could be an integer with values between 0 and 100.
> 
>          This is an informative value.  Details of interpretion to be left
> 
>          open to the renderer, expect that a value of 0 means foreground 
> media
> 
>          is opaque and value of 100 means that it is transparent.
> 
>       From an ABNF perspective "alpha" is undefined. The text says it 
> *could
> 
>      be" an integer between 0 and 100, but "details of interpretation are
> 
>      open to the renderer". That negates the value of creating a standard.
> 
>      The whole point of a standard is to ensure that interoperating parties
> 
>      handle things the same way.
> 
> *Rohit: The value can be between 0-1/0-10/0-100 with lowest value 
> indicating opaque and highest value indicates that it is transparent. 
>   Do you mean I should be specific with the values or will changing the 
> text to " expect that lowest value means foreground media is opaque and 
> highest value means that it is transparent" be acceptable?*

You have to imagine that the offerer and the answerer know nothing about 
each other. So the offerer needs to understand: is the value to be from 
0-1, 0-10, or 0-100? And is it an integer or a real.

So you need to decide this and put it in the spec. And define the syntax 
and associated normative text to make this clear.

And yes, also the significance of lower and higher values.

>      > X= Background Image
> 
>      > A, B, C= foreground image (Media C partially over B)
> 
>      > Transparency(to be applied each pixel) =alpha(A), beta (B), gamma (C)
> 
>      > Background media which shows through A= (1-alpha)X
> 
>      > Background media which shows through B and C = (1-beta)( 1-gamma)X
> 
>      > Overall composed image= gamma.C+ (1-gamma)[beta.B+ (1- beta.B)X]
> 
>      I don't know much about this technology, so perhaps this would be well
> 
>      known to implementers. But it shouldn't just be assumed. If this is 
> then
> 
>      intended mechanism then it should be specified in the document, either
> 
>      directly or by reference to some public document.
> 
> **
> 
> *Rohit: Will include the reference in the update*

That will help.

>      Finally, ISTM that you don't need to treat the background document 
> as a
> 
>      special case. The grouping mechanism can be used to identify all the
> 
>      media streams participating in this superposition mechanism, including
> 
>      the one you are considering to be the background.
> 
>      IIUC the scheme you describe defines the result of superposition based
> 
>      on the transparency values of the individual streams, so that no other
> 
>      ordering mechanism is needed. (Do I have that right?) If so, isn't the
> 
>      background just the media stream with tranparency = 100?
> 
> *Rohit: The ordering mechanism will be needed. Suppose we have a 
> background X with transparency=100, and a superimposed media A with 
> transparency=50. A over X would mean that X would visible partially 
> through A, however X over A would mean that A wouldn't show through X.*

If the ordering is needed, then you need to specify how it is 
determined. IMO it is permissible to use the order of values in the 
a=group: line to specify this ordering. (RFC5888 doesn't ascribe any 
semantics to this ordering of values, but neither does it forbid 
assigning meaning for particular grouping semantics.) I am not certain 
if Christer agrees with me on this point. The alternative is to use a 
new attribute in the grouped media descriptions for this purpose.)

And then you really need to specify the algorithm by which the layering 
plus the transparency is applied to the media streams to yield the 
composed media stream.

	Thanks,
	Paul