IETF Logo Mail Archive

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

Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com> Mon, 03 December 2018 10:08 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 DE722130E4A for <rtcweb@ietfa.amsl.com>; Mon, 3 Dec 2018 02:08:17 -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 fRZEp7585Ttm for <rtcweb@ietfa.amsl.com>; Mon, 3 Dec 2018 02:08:16 -0800 (PST)
Received: from mail-wr1-x433.google.com (mail-wr1-x433.google.com [IPv6:2a00:1450:4864:20::433]) (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 14C48130E19 for <rtcweb@ietf.org>; Mon, 3 Dec 2018 02:08:16 -0800 (PST)
Received: by mail-wr1-x433.google.com with SMTP id j10so11449065wru.4 for <rtcweb@ietf.org>; Mon, 03 Dec 2018 02:08:15 -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=K62Zi1U00ldTiwupK2jliwt1cbCzAJJlxwrw3u4Rxuw=; b=QcOK/HqUUSeafpVzKi2/Iyg2qvBuY8JqFHlgTfl77OtUqQTfC/K3VwJH8GowiPcpc5 FWWntZM3bhr22jyarIutIjda0EcUbhIhtzwhPGjeyYz39haXCUQONZO9csub+P4428EA VAbinUUVU7bzMq0Emrx7xTfGIH5mYNK01s0AJ5SdODx1dKqAI4c5+lWdUpaI2v4TNVyJ vqO0PERGAIfgmsjL8cqtYgkfs709iDapP0dlKyHsA+U2fHxVJjo4apEXO0wJxE44Y4Rb +8j1LExjggWS6TC7Cz/U+eippECuxOQNtSspbDoSi+NO3dCfDVtHri885HRgvf3OKJYW ilWQ==
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=K62Zi1U00ldTiwupK2jliwt1cbCzAJJlxwrw3u4Rxuw=; b=DFQsvumXO00qsoWLXahcUSbbXRXP+HQx+wE4toTBOiP7wqUCrLKK+pbpwkJbKYGYA7 y/3SfyJXJwW+T2HhyZ0hU7nEfq8GZUBf+BAk8nSTvt+9LqyfqSIoXRc97M8WqJ0hcW+a n2cmycOHNIwH34Cu2thRg5kmvPrjxfxq4Swydkg9A5bH+4gF6ud15GGTlJgjI4u92IdP M0YdWRVr7FIVO+MvIQJSXO9PHQU5CpYp22ihodlW4ItRxtGH9FK5rDGbmdljZp4/HiL7 EZoeL+7AbsxdmR9DHWidqtvl5/5OEPSgetyH+ZoZYzkF6abVAKCiBfqeQEWSqAqATEoM vuJw==
X-Gm-Message-State: AA+aEWZ1I+W1faGorCFHC32/nmGrCNaXLreQ1gX+xS9v9qfjXjAl0AV+ oK3aLAjyUjlS9I5wyhXNqknF+tcX
X-Google-Smtp-Source: AFSGD/WIHAWoBAb4pXJW4bCCHgboqGjQDBbjMahizwWE/GiOcpGjXljApk3SsyXr4oXExR2JHfVqgg==
X-Received: by 2002:adf:9246:: with SMTP id 64mr14277288wrj.130.1543831694148; Mon, 03 Dec 2018 02:08:14 -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 v1sm14725320wrw.90.2018.12.03.02.08.13 for <rtcweb@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 03 Dec 2018 02:08:13 -0800 (PST)
To: rtcweb@ietf.org
References: <CALiegfm=++8o=Ou1Tgu6bxyiVdw2ysgM5HnjRqi2hJBoy476yg@mail.gmail.com> <AM0PR07MB4979C0EC8765FA2DF70E613395AE0@AM0PR07MB4979.eurprd07.prod.outlook.com>
From: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
Message-ID: <45beb8d6-6578-dc98-4ff7-1be7a55c0687@gmail.com>
Date: Mon, 03 Dec 2018 11:11:55 +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: <AM0PR07MB4979C0EC8765FA2DF70E613395AE0@AM0PR07MB4979.eurprd07.prod.outlook.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/N30Y-C8OW_QUBepNsH_N1tWQR80>
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 10:08:18 -0000

On 03/12/2018 11:02, Magnus Westerlund wrote:
> To attempt to restate your question. For RTP sessions, where there are a
> single source media stream per Media Description in SDP (m= block) and
> where there is explicit MID signalling and SSRC signalling, then one
> will not need RepairedStreamId and can instead rely on explicit MID
> signalling for the RTX stream?
>
> I think no. I think using RepairedStreamId independent if there is
> multiple source RTP streams or not per media description provides a more
> consistent experience

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?

Best regards

Sergio

v2.23.0 | Report a Bug | By Email