Re: [AVTCORE] draft-ietf-avtcore-multi-party-rtt-mix-08.txt - please review

Paul Kyzivat <pkyzivat@alum.mit.edu> Mon, 12 October 2020 15:04 UTC

Return-Path: <pkyzivat@alum.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 26EE13A1559 for <avt@ietfa.amsl.com>; Mon, 12 Oct 2020 08:04:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.915
X-Spam-Level:
X-Spam-Status: No, score=-1.915 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, NICE_REPLY_A=-0.213, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (body has been altered)" 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 e3hdLVSTGPqL for <avt@ietfa.amsl.com>; Mon, 12 Oct 2020 08:04:52 -0700 (PDT)
Received: from NAM11-DM6-obe.outbound.protection.outlook.com (mail-dm6nam11on2072.outbound.protection.outlook.com [40.107.223.72]) (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 6963E3A1558 for <avt@ietf.org>; Mon, 12 Oct 2020 08:04:52 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=kPKcNUJUbR4bvzEReafgRP7OIuDamXAaYKRac8sef2IuJUWffu/CsJUQGDyfwPhdcnwsec/opHwV+Rk7mqeXO3024oelCbr65sc3oCV0vullcogJKRjcd6eqlQLWv0VuorK+CQHke2v8bllhv8ZLTdZpFZbsxjf3HBAW2HoRgE0N5oc2qg5kR/8OOMfkC5z0x7Ql3cCWHptybxMF4qx0LUmoqSWxgZOgNFRLxx0jWPvQTFNSfx4YszqIoLT38iYuOankc+RyBd0289O/Bt8gF2SopS+Go/TOC8eT9/3NS4YUrSPP9KjXVsOI/OORXnGAv9RRIEcaRLMNszFUdaDiFA==
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=oPRmJt4p2pXCwpkpOF4Vu4yugco7zoXR3k8VatzlovA=; b=SrRN7bbBOfFGx2UwluJYZHaV+BhrpnxIHeDsk1dFiUkrIO64UAXMltbuz358qhQ1df0rxwKf7o9VQ5OjnYCBQBDYpm0Hem4Z3E0wU1McXBYXo2z+ycCwAPuGhoN4uGnsA7OJW0+OELiPL8D2AfV9n7ZobLUfmUwmnlSey+hnrhUTCCr1FQTXlN2hG5GrrcWjpxFfLViYeP+QrcQIHHtzMTL6ewskbJkZhV+50V7XI/cxmV7tvnlrDTdHWQ5nEeJZDha1Ror1DfC2JnaTedi5Ny/r170nTJDZhLxp25tJJzpjFszkpDV3G5FH7wL3b8JJLuNEvJiFXdBXKwCkP+gstw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass (sender ip is 18.7.68.33) smtp.rcpttodomain=ghaccess.se 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=oPRmJt4p2pXCwpkpOF4Vu4yugco7zoXR3k8VatzlovA=; b=U88BLTDhhn0zb1km9Ht0SlET7iTpr7DP6CHK2+ViFENkPQsBYmgnNpKBm0p0bb2tVHVbAn+yKG8YMCHVYfWPClxOfErBaHYHEpu7IX7G0wqSsHR3+8wxuAPauG/3vCEn3bgHlnD9SkI+as/9HOgxqLthsZXn++2fdk38TSbM7S4=
Received: from SA9PR11CA0002.namprd11.prod.outlook.com (2603:10b6:806:6e::7) by BYAPR12MB3368.namprd12.prod.outlook.com (2603:10b6:a03:dc::20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3455.25; Mon, 12 Oct 2020 15:04:49 +0000
Received: from SN1NAM02FT051.eop-nam02.prod.protection.outlook.com (2603:10b6:806:6e:cafe::ff) by SA9PR11CA0002.outlook.office365.com (2603:10b6:806:6e::7) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3455.26 via Frontend Transport; Mon, 12 Oct 2020 15:04:49 +0000
X-MS-Exchange-Authentication-Results: spf=pass (sender IP is 18.7.68.33) smtp.mailfrom=alum.mit.edu; ghaccess.se; dkim=none (message not signed) header.d=none;ghaccess.se; 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 SN1NAM02FT051.mail.protection.outlook.com (10.152.73.103) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3455.25 via Frontend Transport; Mon, 12 Oct 2020 15:04:48 +0000
Received: from Kokiri.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 09CF4jkQ017175 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT); Mon, 12 Oct 2020 11:04:46 -0400
To: =?UTF-8?Q?Gunnar_Hellstr=c3=b6m?= <gunnar.hellstrom@ghaccess.se>, avt@ietf.org
References: <159725784100.26501.7801603611291404620@ietfa.amsl.com> <cea92434-e74b-2fba-dc29-f1b29f5e22d9@ghaccess.se> <7c6ab084-95b6-1c07-fa78-c280a7a0ca6b@ghaccess.se> <7f90dd6d-8a66-bc7c-0865-d1ce566c2306@alum.mit.edu> <62ab2139-6a5b-7116-a54a-abbb6ea95b69@ghaccess.se>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <9ea0fc69-8443-2714-b390-19ddf563cf18@alum.mit.edu>
Date: Mon, 12 Oct 2020 11:04:45 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:78.0) Gecko/20100101 Thunderbird/78.3.2
MIME-Version: 1.0
In-Reply-To: <62ab2139-6a5b-7116-a54a-abbb6ea95b69@ghaccess.se>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-EOPAttributedMessage: 0
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 2b3a28b3-17a4-42a2-7149-08d86ec0298f
X-MS-TrafficTypeDiagnostic: BYAPR12MB3368:
X-Microsoft-Antispam-PRVS: <BYAPR12MB33682AB64CE116AF32F29799F9070@BYAPR12MB3368.namprd12.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:10000;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: iPBXLwx8IcbJm6Pl6Mg1zfVIIykozu5IYcfQvR5HjUzTbYIENSoJ2K3QxjXnrmGh58vmqAucOKJQLBpS848NY8G1Cps5OTkHaiFarizFQVuZOcexEWgCV9Fb5t6zcsBaNb4pK8ZGyPCkGob9mVqC2jfFpM52TdxIusohsyl31vbOo7rAUy8ROQ8M+aWIt8ISf1XnLuv2uqhdOK0MSdsw+ZhwnrwMicvIdEZ3meO553pl7g2bgBIG7GLDSmMQfU2MDgzGUjVuxgnKhJZNkrVO7yeV/U/gZCFoZCZrNwM1mDa50jYYW/JG9vqhLPVDu7k60eLKJkG4qDmJxqtxBghxCpsSaP6ZsvMEjNCnCKlxsxn2AaZAk7DGmLnrXHM7mWEm6O8vlRBgFv8eFrFmfWWkjhg67N7unPvA+uQ0YOnSo6m9Xpb4cLGLOfeeQs9230lr
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)(376002)(346002)(396003)(39860400002)(46966005)(336012)(2616005)(83380400001)(956004)(8676002)(70586007)(31696002)(53546011)(70206006)(86362001)(82310400003)(356005)(31686004)(66574015)(8936002)(786003)(2906002)(5660300002)(186003)(47076004)(4001150100001)(316002)(82740400003)(36906005)(26005)(478600001)(75432002)(7596003)(43740500002); DIR:OUT; SFP:1101;
X-OriginatorOrg: alum.mit.edu
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 12 Oct 2020 15:04:48.0309 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 2b3a28b3-17a4-42a2-7149-08d86ec0298f
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: SN1NAM02FT051.eop-nam02.prod.protection.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Anonymous
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR12MB3368
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/r0LEgiA_OHfBuqj2-tZjniaNNaY>
Subject: Re: [AVTCORE] draft-ietf-avtcore-multi-party-rtt-mix-08.txt - please review
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: Mon, 12 Oct 2020 15:04:54 -0000

On 10/12/20 10:35 AM, Gunnar Hellström wrote:
> Paul, thanks for the review,
> 
> I have accepted all your proposals and done the easy ones in my draft.
> 
> Will continue with the proposed restructuring of section 2.1.

Sounds good.

> See a few comments below.

I have one followup comment below.

> Den 2020-10-10 kl. 20:50, skrev Paul Kyzivat:

>> * Section 2.1:
>>
>> Why was "rtt-mix-rtp-mixer" chosen as the name of the attribute? It 
>> seems cumbersome and redundant. Wouldn't "rtt-mixer" be sufficient?
> Yes, a better name may be needed.
> draft-hellstrom-avtcore-multi-party-rtt-solutions has in sections 6.3 
> and 6.4 a discussion on the sdp attribute. I agree that the name is long 
> and maybe confusing. The thought is that the first part, "rtt-mix", 
> indicates the purpose: to indicate support for a type of mixer for 
> real-time text. The second part, "rtp-mixer", indicates what type of 
> mixer that is supported. It is the rtp-mixer style as described in RFC 
> 3550.
> 
> There is no plan right now, but it would be possible that later work 
> specifies another mixer type as an alternative. It could be a 
> multi-stream mixer using the rtp-translator style from RFC 3550. That 
> work could then register another attribute, e.g. called 
> "rtt-mix-rtp-translator". That is not sufficiently likely to motivate 
> the effort to now create an attribute with values, but the reasoning 
> motivated a name that indicates both the purpose and the solution.
> 
> That said, looking at your name proposal "rtt-mixer", I find that it can 
> meet the criteria. "rtt-" indicates that it is about real-time text, and 
> "mixer" can be taken to mean the "rtp-mixer" style. It was also used as 
> the name in early versions of this draft.
> 
> So, the simple conclusion is: Yes, accepted and done.

When I looked at "rtt-mix-rtp-mixer" my first thought was as you 
describe - that there would be several attributes pertaining to rtt 
mixers. But then I found no others in the draft, and none starting with 
"rtt-mix" already in the iana registry. So simplifying seemed in order.

But, if you foresee some possibility of others being defined in the 
future then it might indeed be worth planning for that now. As you see 
fit, or perhaps it should be further discussed.

	Thanks,
	Paul