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

Adam Roach <adam@nostrum.com> Wed, 19 July 2017 10:53 UTC

Return-Path: <adam@nostrum.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 0FEEA131C99; Wed, 19 Jul 2017 03:53:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.88
X-Spam-Level:
X-Spam-Status: No, score=-1.88 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 wu56na-7JY65; Wed, 19 Jul 2017 03:53:40 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 5110412714F; Wed, 19 Jul 2017 03:53:40 -0700 (PDT)
Received: from dhcp-8909.meeting.ietf.org (dhcp-8909.meeting.ietf.org [31.133.137.9]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v6JArTk5033324 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 19 Jul 2017 05:53:31 -0500 (CDT) (envelope-from adam@nostrum.com)
To: Bo Burman <bo.burman@ericsson.com>, =?UTF-8?Q?I=c3=b1aki_Baz_Castillo?= <ibc@aliax.net>
Cc: "mmusic (mmusic@ietf.org)" <mmusic@ietf.org>, "Taylor Brandstetter (deadbeef@google.com)" <deadbeef@google.com>, "draft-ietf-mmusic-rid@ietf.org" <draft-ietf-mmusic-rid@ietf.org>, "draft-ietf-mmusic-sdp-simulcast@ietf.org" <draft-ietf-mmusic-sdp-simulcast@ietf.org>
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> <AM5PR0701MB2577F4261814169B0AF408488D250@AM5PR0701MB2577.eurprd07.prod.outlook.com> <CALiegfmREKCotLeNkp9mj=zB8V-fir-Z=QQBUvVUUK9jsjELRQ@mail.gmail.com> <AM5PR0701MB257767A071B4BAE79A9DFE878D250@AM5PR0701MB2577.eurprd07.prod.outlook.com> <CALiegfm6rgrtpN55N3LYbt1ZMvKuxNSahEs4JikNc_eSHPfR0Q@mail.gmail.com> <AM5PR0701MB2577ACCA590E0F4FC4561F6C8DD50@AM5PR0701MB2577.eurprd07.prod.outlook.com>
From: Adam Roach <adam@nostrum.com>
Message-ID: <c8d8ca32-4f53-c6ee-c0b5-4c7c24c45112@nostrum.com>
Date: Wed, 19 Jul 2017 12:53:28 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <AM5PR0701MB2577ACCA590E0F4FC4561F6C8DD50@AM5PR0701MB2577.eurprd07.prod.outlook.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/zuX3vZj5b116o8FickxL7ohyPBI>
Subject: Re: [MMUSIC] FW: [rtcweb] How to signal RTX SSRCs with simulcast
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 19 Jul 2017 10:53:42 -0000

Thanks! These changes look good to me, and I've added them to a -11 
version of the document, and uploaded it to the i-d repository:

https://www.ietf.org/id/draft-ietf-mmusic-rid-11.txt

/a

On 7/6/17 13:49, Bo Burman wrote:
> To follow up on this, I suggest making the following addition to draft-ietf-mmusic-rid:
>
> ---- AFTER this text in section 4 ----
>
>     An "a=rid" SDP media attribute specifies restrictions defining a
>     unique RTP payload configuration identified via the "rid-id" field.
>     This value binds the restriction to the RTP Stream identified by its
>     RTP Stream Identifier SDES item [I-D.ietf-avtext-rid].  To be clear,
>     implementations that use the "a=rid" parameter in SDP MUST support
>     the RtpStreamId SDES item described in [I-D.ietf-avtext-rid].  Such
>     implementations MUST send it for all streams in an SDP media
>     description ("m=") that have "a=rid" lines remaining after applying
>     the rules in Section 6 and its subsections.
>
> ---- ... add this proposed, new text ----
>
>     Implementations that use the "a=rid" parameter in SDP and that
>     make use of redundancy RTP streams [RFC7656], e.g. RTP RTX
>     [RFC4588] or FEC [RFC5109][I-D.ietf-payload-flexible-fec-scheme],
>     for any of the source RTP streams that have "a=rid" lines remaining
>     after applying the rules in Section 6 and its subsections, MUST
>     support and use RepairedRtpStreamId SDES item described in
>     [I-D.ietf-avtext-rid] for those redundancy RTP streams. This provides
>     the binding between the source RTP stream and the corresponding
>     redundancy RTP stream, by setting RepairedRtpStreamId value for
>     the redundancy RTP stream to the RtpStreamId value of the source
>     RTP stream. The redundancy RTP stream MAY (but need not) have an
>     "a=rid" line of its own, in which case the RtpStreamId SDES item value
>     will be different from the corresponding source RTP stream.
>
> ---- End changes ----
>
> The -simulcast draft would be entirely agnostic to this clarification of "a=rid" and RepairedRtpStreamId usage and thereby transparently allow using redundancy RTP streams with simulcast.
>
> /Bo
> (as individual)
>
>> -----Original Message-----
>> From: Iñaki Baz Castillo [mailto:ibc@aliax.net]
>> Sent: den 13 mars 2017 14:43
>> 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 14:41 GMT+01:00 Bo Burman <bo.burman@ericsson.com>om>:
>>> [BoB] Usage of RepairedRtpStreamId and RtpStreamId are already defined on RTP level by -avtext-rid. If we have
>> preferences on how to best use them with redundancy RTP streams in general, I suggest we add text to -mmusic-rid
>> about it. This would be regardless if we go for option A or B, but decided once and for all, thus applicable to RFC 4588 rtx
>> and FLEX-FEC alike.
>>
>> Agreed.
>>
>>
>> --
>> Iñaki Baz Castillo
>> <ibc@aliax.net>