IETF Logo Mail Archive

Re: [MMUSIC] FW: [rtcweb] How to signal RTX SSRCs with simulcast

Iñaki Baz Castillo <ibc@aliax.net> Mon, 13 March 2017 10:46 UTC

Return-Path: <ibc@aliax.net>
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 1309B12954B for <mmusic@ietfa.amsl.com>; Mon, 13 Mar 2017 03:46:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=aliax-net.20150623.gappssmtp.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 GlKAFfJxPSEN for <mmusic@ietfa.amsl.com>; Mon, 13 Mar 2017 03:46:24 -0700 (PDT)
Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (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 A6E3512945D for <mmusic@ietf.org>; Mon, 13 Mar 2017 03:46:23 -0700 (PDT)
Received: by mail-wm0-x22c.google.com with SMTP id n11so36529005wma.0 for <mmusic@ietf.org>; Mon, 13 Mar 2017 03:46:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aliax-net.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=EMUKBSE1cbUHhyjbH1zwvKJt854GTwTAz0Rhm+usAT4=; b=X/DA8QBEKLTw5PNnwqlgT1lainf/d8jXHyZL8g/DsqgeAAMAD3qv/p+qazX3FQEgi1 sUAgbMgueL9XIjjW9cMbnhDUq5a5pNWjWzR0ZXO7waF7JZ/1nuWFHYC1YDYETBMpJf2R GuyI0/ZlhGN3gLI3BhofINZmAINBMAMMiLfDk+XjdisUXTfov0CE9Of5o/oLqXVcG4fU 8aTI4fXZrIhqPdHcjLrUvfS9lqgVBIqS0B+RkBWMNVOPUUmad6z9VKs7JuDV2DE+iw69 Jcb+OsZx6xzeKVw445OQrOHD+ujs5XfLF7T88Y+KW/SFaGBTkr323du0UW1PevUAb+GS vU7Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=EMUKBSE1cbUHhyjbH1zwvKJt854GTwTAz0Rhm+usAT4=; b=Zxipb0E8zYpUc5onIwDo1+VRykqaQc/FOqkfO1SA9A540kNSg7UosAVimCobaELXuT T9qBcpNxjaVD8i3t/0bOiokVU5IqcOLiPZTw85lq6Yj6qTfMS5aeutkE7XuWhXq4C5g+ ffxoO985jq6YLI7T05samiOnc3/Hk+VL7jSW1i2WFV2qpV5+xuQf33ZqiSOQwxOkI6hp PPDlMFdH/STwpYWaBfhIJpgNO5EH0IUexjDFN6ZcSb5/0JPkM9PtcpbI32N8RTGQINC6 BzIaMGUVPEjQV2luXNZyXT43u0vSCta55N7tKZKDmQSlL0GWv0CGyICTIbxw2fmhY+Qj QqBA==
X-Gm-Message-State: AFeK/H3VcAhf1WmsVIx7htPuKvaeFlQvJSmqn7OcTlzsqwzPRGt5A95vE+TTyKaJ2tPbUQ55IYyPY/Gae44j4A==
X-Received: by 10.28.182.7 with SMTP id g7mr9912186wmf.108.1489401982136; Mon, 13 Mar 2017 03:46:22 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.80.138.222 with HTTP; Mon, 13 Mar 2017 03:46:01 -0700 (PDT)
In-Reply-To: <AM5PR0701MB2577FD1D3E43697C4672F80C8D250@AM5PR0701MB2577.eurprd07.prod.outlook.com>
References: <CALiegfkM+Gh5tnu_LU+Lo4FM_OVy+TixyBt2zBtoREucHHAsCg@mail.gmail.com> <3A98F0E8-772E-40E3-A872-5414AC8FDF35@iii.ca> <CALiegfm0+GkfTvUk0Kfj2SLf+zcw-k6b-xnqXd4omnVy7mPTEg@mail.gmail.com> <12EA18B8-39F0-491F-92B6-D41F3D640209@iii.ca> <CALiegfndNRoBH-1TYvLhC2TZsWApaLLZ0WBjh3HzL4pYJtCmGQ@mail.gmail.com> <CAK35n0ZuGu+FxYsdDGkX4aomeTC68XvBd0MniKS7NzdAeuEACQ@mail.gmail.com> <AM5PR0701MB2577FD1D3E43697C4672F80C8D250@AM5PR0701MB2577.eurprd07.prod.outlook.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Mon, 13 Mar 2017 11:46:01 +0100
Message-ID: <CALiegfnUqrd_5z2gsgjsOqHxUXyciDv1uN1z+EJw_A8rNXmFMQ@mail.gmail.com>
To: Bo Burman <bo.burman@ericsson.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/MQP81p9ezYE8kXjRZJ6McIEeUbI>
Cc: "draft-ietf-mmusic-rid@ietf.org" <draft-ietf-mmusic-rid@ietf.org>, "mmusic (mmusic@ietf.org)" <mmusic@ietf.org>, "draft-ietf-mmusic-sdp-simulcast@ietf.org" <draft-ietf-mmusic-sdp-simulcast@ietf.org>
Subject: Re: [MMUSIC] FW: [rtcweb] How to signal RTX SSRCs with simulcast
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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: Mon, 13 Mar 2017 10:46:26 -0000

2017-03-13 10:56 GMT+01:00 Bo Burman <bo.burman@ericsson.com>:
> I’m personally slightly inclined to suggest always using RepairedRtpStreamId
> in the rtx redundancy RTP stream to relate it to the original RTP stream
> (second “if” bullet above), mainly to avoid having to change interpretation
> of RtpStreamId based on the optional presence of RepairedRtpStreamId. I’m of
> course open to arguments.

Personally I prefer option A (use a shared RtpStreamId). My rationale:

If we go with option B (RepairedRtpStreamId) then we will need
something similar when it comes to FLEX-FEC [*]:

        v=0
        o=ali 1122334455 1122334466 IN IP4 fec.example.com
        s=2-D Parity FEC with no in band signalling Example
        t=0 0
        m=video 30000 RTP/AVP 100 110
        c=IN IP4 233.252.0.1/127
        a=rtpmap:100 MP2T/90000
        a=rtpmap:110 flexfec/90000
        a=fmtp:110 L:5; D:10; ToP:2; repair-window:200000
        a=ssrc:1234
        a=ssrc:2345
        a=ssrc-group:FEC-FR 1234 2345


For me it's to think in RtpStreamId as "the identificator of a media
stream and, optionally, also the identificator of the RTX stream and
FEC stream of such a media stream".



[*] https://tools.ietf.org/html/draft-ietf-payload-flexible-fec-scheme-03


-- 
Iñaki Baz Castillo
<ibc@aliax.net>

v2.23.0 | Report a Bug | By Email