IETF Logo Mail Archive

Re: [rtcweb] Support for RFC7728 pause indication

Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com> Sat, 11 November 2017 09:29 UTC

Return-Path: <sergio.garcia.murillo@gmail.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 D2EA4129462 for <rtcweb@ietfa.amsl.com>; Sat, 11 Nov 2017 01:29:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 5DUt6benhemh for <rtcweb@ietfa.amsl.com>; Sat, 11 Nov 2017 01:29:34 -0800 (PST)
Received: from mail-wr0-x231.google.com (mail-wr0-x231.google.com [IPv6:2a00:1450:400c:c0c::231]) (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 6D431129449 for <rtcweb@ietf.org>; Sat, 11 Nov 2017 01:29:34 -0800 (PST)
Received: by mail-wr0-x231.google.com with SMTP id 15so10477547wrb.5 for <rtcweb@ietf.org>; Sat, 11 Nov 2017 01:29:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=l7uS4/5waPBg7FaYlxbYE32ad+qmjSLHfq3OCEao+bY=; b=MX0rx02f2TqxXtw8UJieBb7+PTlFoLANMWqmJCR+JbclV2rmANUJ9n+OaXxp6iktDT 28GdP5ngSPB/PaEp+kxOxuewnqC+dk892WsLjwZtDGXUuBr/hhE7XIo84JOKIdWpRQhT Hr1oijkrpKkWaw7VQxUHnyE4Eih2Tlcq1+vFldrmPiGIc6/1CXMV2oBGNfJlX4mMYrjk pbATJO50y1SSeg85elY7/NP3qea+0+3pS6Pa/UCWKAlRr1vz4SXHdZzMjDSrHeivqVGa YAMDL7WNJMzmAAXrtdHQWlxNmwzgiNm4sNY5ucE5QuzPk3/5Potvn4/5H5jAlXnTSK05 9Yiw==
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=l7uS4/5waPBg7FaYlxbYE32ad+qmjSLHfq3OCEao+bY=; b=aOppPwscPfhi8mGpJgHMzw6LdkgycIp9vmmRi6C+SY8QpUwKjziWa5T1u/C3mCGR73 y93PoM/4plmIqnq6ep5un/7dCboDvfJMoHkBBvIKIwvVQeWCJEKZmJLbigiLT8uTjjwk p5/mQVIoBk/E/4uQ/fvrMfqIlir073/WHrW30haZI3RNFCGs5w0Qk5W/UdHcKJ59XGRp QCOpXxwWzmuxesa5YyOBwWAkRB6VwVYOyAMsB7nCtYV/a/rcr68RVLUQzwsLEn77J7U8 QWgtsUrBaozUPXcx+UvOV3QkvN6pSn+vE0LDbhXFQ2Na7AzrX/w8CEG0+G64gHT2+TPN XOnA==
X-Gm-Message-State: AJaThX5xMcnkoW4qWxa+0SLNThfvYO2wlBU5wa0xk9AdQaVvrG4Yg9Vi GUlYn3HRcQ8Zrr0B6SuWoT8C7oXt3captrhG5mO7Kg==
X-Google-Smtp-Source: AGs4zMaDySQvh/ivUKnmCkXSpH3r4nQaOlv0NZ/6nZ+H+4lnHK5cyQevCGXD97xoMkn6IlrfuFg286j7T2+muyZEeUA=
X-Received: by 10.223.182.158 with SMTP id j30mr2323437wre.242.1510392572923; Sat, 11 Nov 2017 01:29:32 -0800 (PST)
MIME-Version: 1.0
Received: by 10.28.225.6 with HTTP; Sat, 11 Nov 2017 01:29:31 -0800 (PST)
Received: by 10.28.225.6 with HTTP; Sat, 11 Nov 2017 01:29:31 -0800 (PST)
In-Reply-To: <9b49201a-ac3c-0350-ff9d-abe29dee1bd5@alvestrand.no>
References: <91ddc524-6ef9-c3e1-7db5-eb4c4080bc91@gmail.com> <3BFD6388-4A07-4D9C-8F1A-CFBAF0EDB830@iii.ca> <CAOW+2du_sNhm4SKFAjpbOgi7HSsY-RgDK+rgCubLX_5u=N2ELA@mail.gmail.com> <266e6bdb-20b5-9d98-498e-7ddc2c2379a7@gmail.com> <CALiegfnFj5Jy1UGNvpXswfPiB6BEZqjmtTBGXL6PTw3pL86erQ@mail.gmail.com> <f3a0855b-7853-353d-a32a-ba5483cb293c@gmail.com> <CALiegfmrr0T9KtYq7QhOTdSNx0j1MzWoT=D5nqoE+B1GZZ5G2w@mail.gmail.com> <56b03aad-9d87-4465-0b96-1b9854d07c2a@gmail.com> <CALiegfnG-KTPxdSpFShskCgaamVaGBHMY4bpnCMYm7qg0=-GMw@mail.gmail.com> <CALiegfkFnpOQU+LizdCoDRJiZGtLTewEFeeYLWEvr4F0WctC0g@mail.gmail.com> <1f78b285-a9f3-6135-5e07-b9f72ac24546@gmail.com> <CALiegfm-HHWsUOeh7OPFNHq9=JFZjrOZ34__Sbu8sZ8+uvCxuw@mail.gmail.com> <f9d77638-24ad-930d-f446-f95700052c6d@gmail.com> <CALiegfkKQb92Hy+LoH7UyNePBqeX-edGWFmgL5eGcjvZbtH2bg@mail.gmail.com> <9b49201a-ac3c-0350-ff9d-abe29dee1bd5@alvestrand.no>
From: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
Date: Sat, 11 Nov 2017 10:29:31 +0100
Message-ID: <CA+ag07Y_vtVpLt+U=oKXZKcfioKUs_gy2hE0y5sohnN9ieWzDg@mail.gmail.com>
To: Harald Alvestrand <harald@alvestrand.no>
Cc: rtcweb@ietf.org
Content-Type: multipart/alternative; boundary="f40304388d74c7d317055db1ac93"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/r_pCGF4hoFEaOEcX5Rfa1BC4G9k>
Subject: Re: [rtcweb] Support for RFC7728 pause indication
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: Sat, 11 Nov 2017 09:29:37 -0000

Sure thing!

But would prefer it to be in the standard, even just as a SHOULD/COULD than
only libwebrtc implementation specific.

Best regards
Sergio

El 11/11/2017 10:00, "Harald Alvestrand" <harald@alvestrand.no> escribió:

> On 10/31/2017 12:27 PM, Iñaki Baz Castillo wrote:
> >> Nice. However, the last RTP packet sent before PAUSED may arrive after
> >> the PAUSED itself. Not sure how to handle that in the receiver side...
> >>
> >>    When entering the state, the RTP stream sender SHALL send a PAUSED
> >>    indication to all known RTP stream receivers, and SHALL also repeat
> >>    PAUSED in the next two regular RTCP reports, as long as it is then
> >>    still in paused state.
> > Should be enough to mitigate the issue.
> >
> >
> >> RFC 7728 allows partial implementation, with fine grained control about
> >> sending/receiving PAUSED indication:
> >>
> >>       "config" allows for partial implementation of this specification
> >>       according to the different roles in the use-cases section:
> >>
> >>       6  The implementation supports sent and received RTP streams being
> >>          paused due to local considerations and thus supports sending
> >>          and receiving PAUSED indications.
> >>
> >>       7  The implementation supports and desires to receive PAUSED
> >>          indications for received RTP streams but does not pause or send
> >>          PAUSED indications for sent RTP streams.  It does not support
> >>          any other messages defined in this specification.
> >>
> >>       8  The implementation supports pausing sent RTP streams and
> >>          sending PAUSED indications for them but does not support
> >>          receiving PAUSED indications for received RTP streams.  It does
> >>          not support any other messages defined in this specification.
> > Cool. Let's see how things go. BTW, TMMBR and TMMBN (2008 spec) also
> > seem easy to implement but, despite being mandatory, better don't send
> > a TMMBR to Chrome in 2017.
>
> Patches welcome.
>
> >
>
> --
> Surveillance is pervasive. Go Dark.
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>

v2.23.0 | Report a Bug | By Email