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

Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com> Mon, 03 December 2018 13:32 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 14B7F130E44 for <rtcweb@ietfa.amsl.com>; Mon, 3 Dec 2018 05:32:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, 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 02A9T2OgpcYo for <rtcweb@ietfa.amsl.com>; Mon, 3 Dec 2018 05:32:53 -0800 (PST)
Received: from mail-wm1-x32e.google.com (mail-wm1-x32e.google.com [IPv6:2a00:1450:4864:20::32e]) (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 7F98312D4E8 for <rtcweb@ietf.org>; Mon, 3 Dec 2018 05:32:53 -0800 (PST)
Received: by mail-wm1-x32e.google.com with SMTP id a18so5711753wmj.1 for <rtcweb@ietf.org>; Mon, 03 Dec 2018 05:32:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=nRbUFylODDcpHxOIqemXhjasCB1TeGgGK/a+YkW4gbc=; b=iBQY0dZFh7+N1ev+GTzxWkLF6Xfq9LyzqfS49Wl5pMVs8Zs7GGuUbCAjjrLwNne7Vz 7KNol60BPlykjj4YgqRBHLGZj38YE3VEDl/rK6042kSOuIPYqc7VRPhbJpdKK12m+AD5 EJhLDDKyxOACTg1gmc9/09TCvYwoTOi2QAkBrZ4seXaZcwXQV+MDyaE5V0QjeHQXJNwo 9DQsjA98dJCZ7xVI+9dcIDPzkbhqgMxwM1x0eElMKvzWqjrucvTqg0OOtIbCCFI54jIq VwvffWLNuvbraoXDcSlLQgNr7fBsy7/zG7tV+cA0GefAwy5RNPtrNbs2+p3c1jVl29vb qCcQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=nRbUFylODDcpHxOIqemXhjasCB1TeGgGK/a+YkW4gbc=; b=E1Ie6kxWxUOEU6A21ZWp37Tx60V5UtzDcvEmfRY6JABPhXwyO9Y+qYcuu7JY4YwmBX +sg6ukHMcfTVfHknbLP+YZ336yhTXtso22RfJOELnVIVzrtkfmv1gHSEg2Xx9NjoabbP C8GPd1lv6JCKzpaM7dZSKCllEWdAzggC5NqQgKVCveyMospgGe/UyuuwYP0zYW7Vz7K8 iDQg+UlGfoB2zjtvnQsIE4oJhh+bZH6v5UfpGjN3NgWUdQf5I2mgg8t796tdcDMGI51c dxCEunf7u87/CCo5KUT12GtvlesNR5/hGjGvl/jTAL9ah2KIe5F351HAgiXo/htUrFxG Md7w==
X-Gm-Message-State: AA+aEWaP0MAEhYyQ4hLdqjuTbPbTlupOJyzOQ/ne1QMLAL5etnHC8pqS sDbqpgk7KaQ9IRLSXyPA7gjI0v3A
X-Google-Smtp-Source: AFSGD/XpMbMha5p/vaQnZnksik14gg40QCBpxt0SaSptwOWVRLL12JiWJ5rNU7wpJFhkJbG7JFYvhw==
X-Received: by 2002:a1c:27c6:: with SMTP id n189mr8197044wmn.108.1543843971708; Mon, 03 Dec 2018 05:32:51 -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 o15sm15393540wrp.12.2018.12.03.05.32.50 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 03 Dec 2018 05:32:50 -0800 (PST)
To: Magnus Westerlund <magnus.westerlund@ericsson.com>, "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>
From: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
Message-ID: <13ff90af-d62e-2f47-3ccc-16ca4e9e3cac@gmail.com>
Date: Mon, 3 Dec 2018 14:36:32 +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: <AM0PR07MB4979571D1B2933258A18544A95AE0@AM0PR07MB4979.eurprd07.prod.outlook.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/nmG5tSNVZNTX5XVDG8yelUO9z-8>
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: Mon, 03 Dec 2018 13:32:55 -0000

On 03/12/2018 13:44, Magnus Westerlund wrote:
>>
>> How would that work, if we are not using simulcast, no rid will 
>> negotiated in the SDP (AFAIK) so we can't use RepairedStreamId and we 
>> will have to rely on mid header extension and pt multiplexing, right?
>
>
> That is my point, that we should define that when using RFC 4588 RTX 
> one should include RID and use the RepairedStreamID for dynamic 
> bindings of the SSRCs even if one doesn't use Simulcast. That would be 
> a stable and commonly operational solution.
>
>
Given than rid is not globally unique but unique per mid, the rtx packet 
would need to include the mid anyway, wouldn't rid be redundant for 
non-simulcast use case?

Best regards

Sergio