IETF Logo Mail Archive

Re: [rtcweb] Rules for RTCMediaDiscardedEvent

Bernard Aboba <bernard.aboba@gmail.com> Wed, 28 January 2015 23:30 UTC

Return-Path: <bernard.aboba@gmail.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25D011A7005 for <rtcweb@ietfa.amsl.com>; Wed, 28 Jan 2015 15:30:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, SPF_PASS=-0.001] autolearn=ham
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 DcycI90j3P4T for <rtcweb@ietfa.amsl.com>; Wed, 28 Jan 2015 15:30:19 -0800 (PST)
Received: from mail-wi0-x236.google.com (mail-wi0-x236.google.com [IPv6:2a00:1450:400c:c05::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9DBF71A6FE7 for <rtcweb@ietf.org>; Wed, 28 Jan 2015 15:30:09 -0800 (PST)
Received: by mail-wi0-f182.google.com with SMTP id n3so16996142wiv.3 for <rtcweb@ietf.org>; Wed, 28 Jan 2015 15:30:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=CYbn63MbdFmUxJ5OHfWYqmnRyF9YOCcONZ89Exnfxtw=; b=NXVXgRNt1RiCetHSy2CZqfPSbOp2F7PYMsXCsX9zqwVSyAQIcdmUo4R5RloqU1sQDY 7+qYBQwqmUV6zNhn/WQomZsjTxsZjt20xNqMNu5F+vWi/NP9qRQhI/11FwLZHv5nSHPz bSSMUSrIT/KWIkCWKMCgOOCIryWaKYzOSSAU1SEi55NjKoW2L7ru40yp5ACOHmsV2N/2 GFy3Ym6jNn7IsRE3JXjhDDuaUOceKm9Jt0wh8jd3AmDeNGHicOmpxGOf5mZPRMl2Yfkp 803s7bhzKtvu6wkz/x2L+GSnut7nOSW6mlgofk7lh3dfwslel65r42qykcXZJS8v1DD/ CZtQ==
X-Received: by 10.180.74.229 with SMTP id x5mr11974383wiv.1.1422487808314; Wed, 28 Jan 2015 15:30:08 -0800 (PST)
MIME-Version: 1.0
Received: by 10.27.91.8 with HTTP; Wed, 28 Jan 2015 15:29:48 -0800 (PST)
In-Reply-To: <CA+9kkMC9uNocE_RKOK9sz3P+MBpu_43Qj2irJj8Yb_85Zjb4jA@mail.gmail.com>
References: <CAOW+2dtJbLvpShJq3dtpbMUYucHg2ZG8mdYRPQBXFodnCdcWbw@mail.gmail.com> <CA+9kkMC9uNocE_RKOK9sz3P+MBpu_43Qj2irJj8Yb_85Zjb4jA@mail.gmail.com>
From: Bernard Aboba <bernard.aboba@gmail.com>
Date: Wed, 28 Jan 2015 15:29:48 -0800
Message-ID: <CAOW+2duoGWBaMNBES4s5_OS8Uok4CLN8RTegJu5k+4q9r8hZgg@mail.gmail.com>
To: Ted Hardie <ted.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="f46d04389591831240050dbec09f"
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/xL97kJqrGdNkLVxI9O2GgwL4ijE>
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Rules for RTCMediaDiscardedEvent
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 28 Jan 2015 23:30:21 -0000

There is some text in draft-ietf-mmusic-bundle-negotiation Sections 9 and
10 that provides general guidelines. However, the most specific guidance is
found in draft-roach-mmusic-unified-plan Section 3.2, but does not appear
to be duplicated in any WG work item. So I'm wondering if that (now
expired) draft is what implementers should use or whether there is
something more current/authoritative out there.

On Wed, Jan 28, 2015 at 9:10 AM, Ted Hardie <ted.ietf@gmail.com> wrote:

> On Wed, Jan 28, 2015 at 5:32 PM, Bernard Aboba <bernard.aboba@gmail.com>
> wrote:
>
>> Martin submitted a pull request for RTCMediaDiscardedEvent (see
>> https://github.com/w3c/webrtc-pc/pull/29),  which is to be fired to
>> indicate reception of  “packets having an unknown SSRC, payload type, or
>> any other error that makes it impossible to attribute an RTP packet to a
>> specific MediaStreamTrack."
>>
>> I remember us discussing the rules for when such an error would occur,
>> but can't seem to find the text in any of the RTCWEB WG documents.
>>
>>
> ​Is the formulation "any error that makes it impossible to attribute an
> RTP packet to a MediaStream track" a problem? (That is, if the rules are to
> always fire an error when that would result, is that a problem?)  Or are
> you asking for a full enumeration?
>
> Ted​
>
>
>
>> _______________________________________________
>> rtcweb mailing list
>> rtcweb@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtcweb
>>
>>
>

v2.23.0 | Report a Bug | By Email