Re: [rtcweb] JSEP-19: Impact of BYE on ssrc table (Appendix B)

Magnus Westerlund <magnus.westerlund@ericsson.com> Tue, 21 March 2017 14:16 UTC

Return-Path: <magnus.westerlund@ericsson.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 9DD5F12996E for <rtcweb@ietfa.amsl.com>; Tue, 21 Mar 2017 07:16:17 -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, 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
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 jWTGdozo6v6Z for <rtcweb@ietfa.amsl.com>; Tue, 21 Mar 2017 07:16:15 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (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 4654D12426E for <rtcweb@ietf.org>; Tue, 21 Mar 2017 07:16:15 -0700 (PDT)
X-AuditID: c1b4fb2d-64c6598000005be8-33-58d135ae8249
Received: from ESESSHC014.ericsson.se (Unknown_Domain [153.88.183.60]) by (Symantec Mail Security) with SMTP id BB.9E.23528.EA531D85; Tue, 21 Mar 2017 15:16:15 +0100 (CET)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.62) with Microsoft SMTP Server id 14.3.319.2; Tue, 21 Mar 2017 15:16:34 +0100
To: Cullen Jennings <fluffy@iii.ca>, Bernard Aboba <bernard.aboba@gmail.com>
References: <CAOW+2dvyV=mpY1Qh9ZQVirgAC3YUHT6dLxs+RPicKPGg9fKenw@mail.gmail.com> <30B46FE1-4E99-4622-8E2C-F4AA455D08D8@iii.ca>
CC: RTCWeb IETF <rtcweb@ietf.org>
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
Message-ID: <a46cbd91-006a-2fdd-ab51-8edeb28839d0@ericsson.com>
Date: Tue, 21 Mar 2017 15:16:12 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <30B46FE1-4E99-4622-8E2C-F4AA455D08D8@iii.ca>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrNLMWRmVeSWpSXmKPExsUyM2K7je5604sRBoenMVps2Pef2eLD+h+M Fmv/tbM7MHvsnHWX3WPJkp9MHpfPf2QMYI7isklJzcksSy3St0vgytjxs5+l4L9kxcvrF5ka GJeIdDFyckgImEjc3/uHuYuRi0NIYB2jxKy3fUwQznJGif7Li9m7GDk4hAXcJTb1K4A0iAj4 SNzdvIcRxBYSaGCU2DVHGcRmFlCU+LJ8PhuIzSZgIXHzRyMbSCuvgL1E27oYkDCLgKrEwh1b 2EFsUYEYiZYlH8DG8AoISpyc+YQFxOYUsJJYsvM/M0grM1Drg61lENPlJZq3zmaG2Kot0dDU wTqBUWAWku5ZCB2zkHQsYGRexShanFpcnJtuZKyXWpSZXFycn6eXl1qyiREYpAe3/Nbdwbj6 teMhRgEORiUe3oJ35yOEWBPLiitzDzFKcDArifC69l2IEOJNSaysSi3Kjy8qzUktPsQozcGi JM7rsA8oJZCeWJKanZpakFoEk2Xi4JRqYKyIl2VY2RnvmuE2mf1wQ/adzDnXfaumRn1Z/PVT RazJ+56raVfdXxtUv7fda99XeCvky65ztz0WZ9i3lT77OZG3RrqPJdzO6tK+qDldmXe+rV9q vu910gezExvjphSKunHNjLrx990SB9WWqyqXVx2q3cjhm33jznv2n39NGcySbvZdeHHM+5gS S3FGoqEWc1FxIgDsNKSETgIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/GWA3cQKCdw1XFYNkvVQFT2zHcb0>
Subject: Re: [rtcweb] JSEP-19: Impact of BYE on ssrc table (Appendix B)
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 21 Mar 2017 14:16:18 -0000

Hi,

I have to agree with Cullen here. If one sends a RTCP BYE on an SSRC 
that is signalled, then one better do an signalling update with a new 
signalled SSRC before starting the RTP stream if one changes ones mind 
about it being ended.

Cheers

Magnus

Den 2017-03-17 kl. 03:30, skrev Cullen Jennings:
>
> Looking at the RTP specs ... it seems like it would not matter if an
> endpoint initially learned about a SSRC via RTP or SDP, either way it
> seems like the state for the SSRC should be mostly removed at the BYE.
> Thoughts on why we would handle them differently ?
>
> (If we do need to handle them differently, this looks like an OK approach )
>
>
>> On Mar 10, 2017, at 3:31 PM, Bernard Aboba <bernard.aboba@gmail.com
>> <mailto:bernard.aboba@gmail.com>> wrote:
>>
>> In the algorithm described in Appendix B, SSRCs that are entered into
>> the SSRC table due to signalling are not distinguished from those that
>> are "latched" into the table dynamically.
>>
>> The distinction is important because only "latched" SSRCs should be
>> removed due to receipt of a BYE (or a timeout).
>>
>> My suggestion of how to address this is to add a "D" flag to an SSRC
>> table entry, indicating that the entry was added dynamically.
>>
>> For example:
>>
>>       If the packet has a MID, and the packet's extended sequence number
>>       is greater than that of the last MID update, as discussed in
>>       [RFC7941], Section 4.2.6
>> <https://tools.ietf.org/html/rfc7941#section-4.2.6>, update the incoming SSRC mapping table
>>       to include an entry [with the "D" flag set] that maps the packet's
>>       SSRC to the "m=" line for that MID.
>>
>> Also:
>>
>>       If the packet's payload type is in the payload type table, update
>>       the the incoming SSRC mapping table to include an entry
>>       [with the "D" flag set] that maps the packet's SSRC to the "m="
>>       line for that payload type.  In addition, route the packet to the
>>       associated "m=" line and stop.
>>
>> Then when a BYE is received, check the "D" flag:
>>
>>       If the packet is of type BYE, it indicates that the RTP streams
>>       referenced in the packet are ending.  Therefore, for each SSRC
>>       indicated in the packet that is found in the incoming SSRC table,
>>       first deliver a copy of the packet to the "m=" line associated
>>       with that SSRC, but then [if the "D" flag is set] remove the
>>       entry for that SSRC from the incoming SSRC table.
>>
>> _______________________________________________
>> rtcweb mailing list
>> rtcweb@ietf.org <mailto:rtcweb@ietf.org>
>> https://www.ietf.org/mailman/listinfo/rtcweb
>
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>


-- 

Magnus Westerlund

----------------------------------------------------------------------
Media Technologies, Ericsson Research
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Färögatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------