Re: [rtcweb] Clarification on simulcast and RID and RepairedRtpStreamId

Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com> Tue, 04 December 2018 11:22 UTC

Return-Path: <sergio.garcia.murillo@gmail.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F9FC130EC2 for <rtcweb@ietfa.amsl.com>; Tue, 4 Dec 2018 03:22:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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_NONE=-0.0001, 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 BtO2NKRee6Rv for <rtcweb@ietfa.amsl.com>; Tue, 4 Dec 2018 03:22:45 -0800 (PST)
Received: from mail-wm1-x334.google.com (mail-wm1-x334.google.com [IPv6:2a00:1450:4864:20::334]) (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 A70C3130EC1 for <rtcweb@ietf.org>; Tue, 4 Dec 2018 03:22:44 -0800 (PST)
Received: by mail-wm1-x334.google.com with SMTP id m22so8940084wml.3 for <rtcweb@ietf.org>; Tue, 04 Dec 2018 03:22:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=P5PxbEZMY2dAW6B73RsuStFgPD/Uruth81xCiyHsSsA=; b=iqMziFJHfGtcGDqL3P7Tjk7kq5PR4G/jnUx2/SiyoXLgX7cUFWSXGQe+nw1UaAo6+0 g2NT2O+8DF4wAJnyec/LFSwll1xIKJARCnmTTpXJM/0rZmY+Sn7H3gHdks0WYbCvZnb2 JojRykHxSCNfs1cO6HxYdflTgs1svckaUauKL6Bf6j6CG3D/ec81pr1QawcSPcVyo4MI OoBef4NjQL9fgrjtjr7W76Mg4wvz6zZHr8k+mRffTVdOtdmi19Jth9ZPmNL9q2MTqaa9 +GYdtMD4ybrn6rqX6F4Gmu6UAIzWc0dNEK88xDs4ZZAXsxxBMQFgDwJ1G1tHQF4fZs22 0zng==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=P5PxbEZMY2dAW6B73RsuStFgPD/Uruth81xCiyHsSsA=; b=T5kimxrJ5s9CRnBsJVjcT6R7iNGspeKF55/MTW4yJUsO/Sh2DFonr/8LaSFCn8J9dT 6YJlWxDh1RIlvLPGM0w8yQdMAr4w/IPG01n3vnZ2qVhf7HRMPTXgACPtv0/cAq6lVflc u8usOhLGrgOR/xJXd0rZJx3tDtJ+3QItpEC7DZNeCqk+WuBde6RA/liOjjmoLbaQB/IJ xBzp4ZCkOtvjuWlMRUaVNOtaqo3UeLT5xfjKUlZmHCYVFsNrFdE1Q4vxtLF7PljVpFfS jCnqNxGe3GDcS8nkmE9PajCs4bBQJgCf2xplRbi/Mu9zIa5eaobbkU5lllLKjKi6SOq8 29Hw==
X-Gm-Message-State: AA+aEWaf6PBlPij/Fp+GSavVWXB0gQ2AzPCSZEgrLu2pxJqU2Ew0Zt6S TJqb3UQ5u3xNeuBP5kr6J5X7+ACQ
X-Google-Smtp-Source: AFSGD/XYX271KNro1jFjtTM1SZE9tpv5r7PM3vrnAbS/fAsHFDNELMHNLNI2AwPdCfRQ5D6ftXTZyw==
X-Received: by 2002:a1c:44d6:: with SMTP id r205mr12346246wma.50.1543922562718; Tue, 04 Dec 2018 03:22:42 -0800 (PST)
Received: from [192.168.0.111] (37.red-80-28-109.staticip.rima-tde.net. [80.28.109.37]) by smtp.googlemail.com with ESMTPSA id v19sm23534970wrd.46.2018.12.04.03.22.40 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 04 Dec 2018 03:22:41 -0800 (PST)
To: Magnus Westerlund <magnus.westerlund@ericsson.com>, =?UTF-8?Q?I=c3=b1aki_Baz_Castillo?= <ibc@aliax.net>
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
References: <CALiegfm=++8o=Ou1Tgu6bxyiVdw2ysgM5HnjRqi2hJBoy476yg@mail.gmail.com> <AM0PR07MB4979C0EC8765FA2DF70E613395AE0@AM0PR07MB4979.eurprd07.prod.outlook.com> <45beb8d6-6578-dc98-4ff7-1be7a55c0687@gmail.com> <AM0PR07MB4979571D1B2933258A18544A95AE0@AM0PR07MB4979.eurprd07.prod.outlook.com> <13ff90af-d62e-2f47-3ccc-16ca4e9e3cac@gmail.com> <CALiegfnh-_mMXpmwWnjjX=iayN0WaveHZOHuMrXk9=Tfgx2Z+Q@mail.gmail.com> <2613a4ff-0855-4f78-d3f0-9f9aaaf9ecdb@gmail.com> <CALiegf=ROnLmc388vDO3BJZdzO8q=Sy9mP6F4xTY7rGVZ9CtyQ@mail.gmail.com> <1af3105f-5e66-548d-cb31-6aaf9f2cd0b4@gmail.com> <AM0PR07MB49796A63E10D9CC57E1DD20F95AF0@AM0PR07MB4979.eurprd07.prod.outlook.com> <2d9ca83e-4b81-23e2-ccbb-3c3e4423d291@gmail.com> <AM0PR07MB4979D844B0C0B6D81FB7D27595AF0@AM0PR07MB4979.eurprd07.prod.outlook.com>
From: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
Message-ID: <8571e2cb-85fb-9638-097a-831a5949a69a@gmail.com>
Date: Tue, 4 Dec 2018 12:26:23 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.3.2
MIME-Version: 1.0
In-Reply-To: <AM0PR07MB4979D844B0C0B6D81FB7D27595AF0@AM0PR07MB4979.eurprd07.prod.outlook.com>
Content-Type: multipart/alternative; boundary="------------D8735F7748E7564157EB0D58"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/UbeJMAPVjLQrNmiIWgpIULI2qfk>
Subject: Re: [rtcweb] Clarification on simulcast and RID and RepairedRtpStreamId
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Dec 2018 11:22:48 -0000

On 04/12/2018 11:51, Magnus Westerlund wrote:
> On 2018-12-04 11:01, Sergio Garcia Murillo wrote:
>>> However, an RTP middlebox has the freedom to introduce those header
>>> extensions when switching. They do not need to be sent end-to-end all
>>> the time. So after the initial establishment of them, I see it as the
>>> central middlebox responsibility to ensure that they are included in the
>>> down stream legs towards the conference participants. Also at least for
>>> video introducing them only on reception of a FIR also makes sense.
>> Same could be said about changing the ssrc to avoid collisions and we
>> would have avoided our selves to introduced all this new ids.
> I think you are significantly misrepresenting the reasons why RID's are
> needed. The fact that we have multiple models for how RTP middleboxes
> works is a significant contributing factor. The next is in RTP ancestry
> as a non-centralized multi-party protocol, i.e. intended to work over
> any source multicast. And as simulcast do implies a selection by the
> middlebox that aspect do needs to be handled. A clean-slate approach
> could possibly select another set of constraints and maybe be somewhat
> simpler but not a lot.
>
> I do note that also the MIDs and RIDs only have per signalling context
> and may require translation between the various legs of the conference
> in a multi-party one.


I disagree with several of those statements, but my intention was not to 
start a new discussion about the need of mids/rids, but the usage in RTX 
which I have not yet got a good answer.

Trying to get back to the discussion:

  * What headers should contain a RTX packet from a track added via
    addTrack or addTransceiver without encodings
  * What headers should contain an RTX packet from a track added via
    addTransceiver with several encoding+rids

Best regards

Sergio