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

Bo Burman <bo.burman@ericsson.com> Mon, 13 March 2017 11:41 UTC

Return-Path: <bo.burman@ericsson.com>
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 20E72129587; Mon, 13 Mar 2017 04:41:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level:
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.onmicrosoft.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 mq39X3ljuuww; Mon, 13 Mar 2017 04:41:14 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (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 C7214129586; Mon, 13 Mar 2017 04:41:13 -0700 (PDT)
X-AuditID: c1b4fb30-3623498000006a1c-27-58c68557ac46
Received: from ESESSHC009.ericsson.se (Unknown_Domain [153.88.183.45]) by (Symantec Mail Security) with SMTP id F2.CB.27164.75586C85; Mon, 13 Mar 2017 12:41:12 +0100 (CET)
Received: from EUR01-HE1-obe.outbound.protection.outlook.com (153.88.183.145) by oa.msg.ericsson.com (153.88.183.45) with Microsoft SMTP Server (TLS) id 14.3.319.2; Mon, 13 Mar 2017 12:41:11 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.onmicrosoft.com; s=selector1-ericsson-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=lA8FzDsJrYVMTZ3kqB3LbaAynp8gLnCHpmJ05GWUWEA=; b=hVzI5+iPMqOGEFAurNpC+mDer1ovuTd1hZFQAU5HgN8fySG9lxKtYQG2zwgUCePOKneEGn1kpdnQCOe3p4uFkB05QBV6WysqWYsdUGFMPFxMK1FJsZvppWxoqNHn7XvCsucWdlEEWMJt4IIrKXaoaN2QNGx3ID/OMha1q39FiPE=
Received: from AM5PR0701MB2577.eurprd07.prod.outlook.com (10.173.92.21) by AM5PR0701MB2578.eurprd07.prod.outlook.com (10.173.92.22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.961.8; Mon, 13 Mar 2017 11:41:10 +0000
Received: from AM5PR0701MB2577.eurprd07.prod.outlook.com ([10.173.92.21]) by AM5PR0701MB2577.eurprd07.prod.outlook.com ([10.173.92.21]) with mapi id 15.01.0961.021; Mon, 13 Mar 2017 11:41:10 +0000
From: Bo Burman <bo.burman@ericsson.com>
To: =?utf-8?B?ScOxYWtpIEJheiBDYXN0aWxsbw==?= <ibc@aliax.net>
Thread-Topic: [MMUSIC] FW: [rtcweb] How to signal RTX SSRCs with simulcast
Thread-Index: AQHSmSRXaXEak/rxUUuXLqrZPXzB4qGOeTSAgAADuwCAADM6gIAAAMcAgAAFxYCAA7fx4IAALRSAgAANzbA=
Date: Mon, 13 Mar 2017 11:41:10 +0000
Message-ID: <AM5PR0701MB2577F4261814169B0AF408488D250@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> <CALiegfnUqrd_5z2gsgjsOqHxUXyciDv1uN1z+EJw_A8rNXmFMQ@mail.gmail.com>
In-Reply-To: <CALiegfnUqrd_5z2gsgjsOqHxUXyciDv1uN1z+EJw_A8rNXmFMQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: aliax.net; dkim=none (message not signed) header.d=none;aliax.net; dmarc=none action=none header.from=ericsson.com;
x-originating-ip: [192.176.1.84]
x-microsoft-exchange-diagnostics: 1; AM5PR0701MB2578; 7:zGPMHEJu0UZj7gDiQW11ozWRNznjHWWKkvU/9P4TPyigQkBmGRDWKnEGGdFGBn97A+qHATW5pj5o7X1MbVP5FlUf1vCVWqVJsieJaVt1yZ/6PFJws2zydhiCGHxl80wcL2R5XLXirO+UNTi8uW28lpX9GAn3LAHkb4OSJ/m6rLz9SUjl0UI4x0d5jILbVMYgJmRHrgOB/zjdGmjUwMCmGj0IPYKNaNRsK9ieVLH5d7Aj4rR7c8h0gD311p2MOfjKEQRGtycew5t4gb2s2qgKAQSENl6yTh4onHpR39i3/6xYNnTUUOtc22IYiJ+7QE1p2xYD80/GwSyI+4QJuWR4GQ==
x-ms-office365-filtering-correlation-id: 8a25c60f-b94d-4a53-6fde-08d46a05d87b
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001); SRVR:AM5PR0701MB2578;
x-microsoft-antispam-prvs: <AM5PR0701MB25780963F9A0345356CF156A8D250@AM5PR0701MB2578.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(37575265505322)(211936372134217);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046)(6041248)(20161123558025)(20161123555025)(20161123564025)(20161123562025)(20161123560025)(6072148); SRVR:AM5PR0701MB2578; BCL:0; PCL:0; RULEID:; SRVR:AM5PR0701MB2578;
x-forefront-prvs: 0245702D7B
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(39450400003)(377424004)(13464003)(93886004)(2906002)(110136004)(38730400002)(6246003)(3280700002)(2950100002)(6916009)(74316002)(53936002)(86362001)(7696004)(3660700001)(189998001)(6116002)(53546006)(305945005)(7736002)(3846002)(102836003)(77096006)(54906002)(6506006)(55016002)(106116001)(81166006)(6436002)(25786008)(229853002)(66066001)(6306002)(9686003)(122556002)(4326008)(2900100001)(50986999)(8936002)(76176999)(54356999)(5660300001)(8676002)(33656002); DIR:OUT; SFP:1101; SCL:1; SRVR:AM5PR0701MB2578; H:AM5PR0701MB2577.eurprd07.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Mar 2017 11:41:10.3239 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM5PR0701MB2578
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprGKsWRmVeSWpSXmKPExsUyM2K7rm5E67EIg4df+Cwur3jIajFx/Tom i+ezXrBYTN9nYzF1+WMWB1aPcw3v2T0WbCr1WLLkJ1MAcxSXTUpqTmZZapG+XQJXxoOV89kK tkhWrD40naWB8YFEFyMnh4SAicTtFVNZQWwhgXWMEi2/vLsYuYDsE4wS29/+ZwVxWAR6mSU2 rD/NBJGZziSxeM8Fdriyi7dPsYH0swloSMzfcZcRxBYRsJH4dwGkiJODWWAqk8T3Fj8QW1jA U2LCp8tsEDVeEh/af0LZSRJPrk4C62URUJWY8G8xmM0rkCDx+fM2qGWLWSTO337JApLgFAiU WPjvK1gzo4CYxPdTa5gglolL3HoynwniOQGJJXvOM0PYohIvH/8D+4dRoJdRovn7FxaIhILE q+4GNpCEhEAfs0TfvK1ADgeQ4yvxsjUMwvSXWPQtFqI8X6Lrehc7RNhbovOpMkTnPCaJJ22f 2CBqZCQW7WiFGtnAKvG26xU7xPdSEnevdDJC2DISL+7sZZ3AqDkLyd2zgOYyC2hKrN+lDxFW lJjS/ZB9FjgsBCVOznzCsoCRZRWjaHFqcVJuupGRXmpRZnJxcX6eXl5qySZGYGo5uOW3wQ7G l88dDzEKcDAq8fBumHU0Qog1say4MvcQowQHs5II76yWYxFCvCmJlVWpRfnxRaU5qcWHGKU5 WJTEec1W3g8XEkhPLEnNTk0tSC2CyTJxcEo1MG4xOtM3m/vHl6McBeVO+za5V9jfe8N3JFBF 0u7qd426z4lzLDLf8gh9MGJbtuJKUIuWk7BYeKPqJrk34Qfk2j+G3T/PYKJlHNf9RG++i26y vfCZszOcnPZPurTO9MwP/w+b9mXHL+2zueivE7uHbWfwiS92AuzW0XJlvS9aX53Yf2PT72N8 3kosxRmJhlrMRcWJAK6rA9ApAwAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/9s7mpPkR4IHzBfyOuk9k32rEbUY>
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 11:41:16 -0000

Could you elaborate a bit to help me understand why that would be needed for FLEX-FEC when using RepairedRtpStreamId?

Is it that you get explicit indication in SDP, like "a=rid:<rid-id> send pt=<media-fmt>,<redundancy-fmt> ..." when using RtpStreamId for both original and redundancy RTP stream?

I guess that use of RtpStreamId or RepairedRtpStreamId on RTP level (in the RTP and RTCP packets) should not matter much, neither for FLEX-FEC nor RTX, as long as it is clearly defined what it means?

/Bo
(as individual)

> -----Original Message-----
> From: Iñaki Baz Castillo [mailto:ibc@aliax.net]
> Sent: den 13 mars 2017 11:46
> To: Bo Burman <bo.burman@ericsson.com>
> Cc: mmusic (mmusic@ietf.org) <mmusic@ietf.org>rg>; Taylor Brandstetter (deadbeef@google.com)
> <deadbeef@google.com>om>; draft-ietf-mmusic-rid@ietf.org; draft-ietf-mmusic-sdp-simulcast@ietf.org
> Subject: Re: [MMUSIC] FW: [rtcweb] How to signal RTX SSRCs with simulcast
> 
> 2017-03-13 10:56 GMT+01:00 Bo Burman <bo.burman@ericsson.com>om>:
> > 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>