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

Justin Uberti <juberti@google.com> Sat, 11 March 2017 00:12 UTC

Return-Path: <juberti@google.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 1E4CF1294CC for <rtcweb@ietfa.amsl.com>; Fri, 10 Mar 2017 16:12:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 OKboe9rmX-zO for <rtcweb@ietfa.amsl.com>; Fri, 10 Mar 2017 16:12:00 -0800 (PST)
Received: from mail-it0-x236.google.com (mail-it0-x236.google.com [IPv6:2607:f8b0:4001:c0b::236]) (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 37D3C1289C4 for <rtcweb@ietf.org>; Fri, 10 Mar 2017 16:12:00 -0800 (PST)
Received: by mail-it0-x236.google.com with SMTP id g138so5879206itb.0 for <rtcweb@ietf.org>; Fri, 10 Mar 2017 16:12:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=tSAcT4SfCvqkhAkXAz/F3IRMzMSaF2cVFOu2jcazNlU=; b=dBm+waIsC2398FPzvboF4DHVg+TqPbuDZdXPtiy6Atsl4DTuiAAbuEVTebvbJfDSNR +4KsdvUnaL1TgR23E4romLkbnWGkxR9ggmYcZenyUthBYkC1VGVaqbU1DeQn2b31G+Fl xMTfdRdTgzaArlQi2QURkWM7jjzYBApMxMSW7/Gu5Ld4w9IDC3t6Et+w8ASs7EnpCb+h 0ID2EOaFDmwhtjfNS+6/yrIrBLd8OlTmlBBOUTrt290vFTBXmRkAmQQSO5E6ftaugnW6 uKhZS1e/hPkHM73IrQuiTcauur9qhRrFjPSvRdH2d/BFZRw+ZNZOeWW88CsnwLEAVeik itVg==
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; bh=tSAcT4SfCvqkhAkXAz/F3IRMzMSaF2cVFOu2jcazNlU=; b=N4dpVCxl9i+37jgal7AayPTNb03fgegFmFgxhvC8Fst9+4nMBgrgM1jLiuubE5bF/B bptdSrPj0/H/mBb1By4db8Tp1pW1zWP9tAPgu19mcpAO0XBCr+BAUAEK4CqTohlra7kU JJsjAi8gF8126n4NgF1Fd4rsbDUpEAt0Q15gREeAeGa97dqBcbOGswE6qmGOxgO9H/n8 K9rBAuY6KgDdrzhOKVYskVewzohHc0YgibYOUJpXLIGqYb3pHpBPngsZKDPiwga09hlp sSI0m9Y1ikIUo/IliaMX7BPQNnD8m6SpwGeLzZSSvZgN8w17w7PN9jm+cs15o1l/Rzb3 J5Ng==
X-Gm-Message-State: AFeK/H06H7adcW/rTbaPB8DsWtvmICkF2BgI7q/r7TbD8WexBuLwo2gWpOZ3DUQbCj5GkEGG5bPNA/FtKgD/UY7J
X-Received: by 10.36.9.202 with SMTP id 193mr1626574itm.98.1489191119362; Fri, 10 Mar 2017 16:11:59 -0800 (PST)
MIME-Version: 1.0
Received: by 10.107.48.195 with HTTP; Fri, 10 Mar 2017 16:11:38 -0800 (PST)
In-Reply-To: <CAOW+2dvyV=mpY1Qh9ZQVirgAC3YUHT6dLxs+RPicKPGg9fKenw@mail.gmail.com>
References: <CAOW+2dvyV=mpY1Qh9ZQVirgAC3YUHT6dLxs+RPicKPGg9fKenw@mail.gmail.com>
From: Justin Uberti <juberti@google.com>
Date: Fri, 10 Mar 2017 16:11:38 -0800
Message-ID: <CAOJ7v-075LxWbWUazDmaF1+DWz=5ZOk5evrwYnuB6frDvYa2yQ@mail.gmail.com>
To: Bernard Aboba <bernard.aboba@gmail.com>
Content-Type: multipart/alternative; boundary="001a11375fbeac9766054a6953fb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/Fd04L-bBbUU9kfhx4iQEaI3hsko>
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] JSEP-19: Impact of BYE on ssrc table (Appendix B)
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.17
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: Sat, 11 Mar 2017 00:12:02 -0000

This makes sense to me. Alternatively, we could leave the flag as an
implementation detail, and simply say to cull dynamically created entries
upon receiving a BYE:

      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, *and, if it was created dynamically via receipt*

*      of a RTP or RTCP packet*, remove the entry for that SSRC from the

      incoming SSRC table.


On Fri, Mar 10, 2017 at 2:31 PM, Bernard Aboba <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
> https://www.ietf.org/mailman/listinfo/rtcweb
>
>