W3C home > Mailing lists > Public > public-webrtc@w3.org > October 2014

[Bug 20819] no priority API

From: Cullen Jennings (fluffy) <fluffy@cisco.com>
Date: Fri, 31 Oct 2014 16:33:33 +0000
To: public-webrtc <public-webrtc@w3.org>
Message-ID: <60981B4C-456B-45E1-9894-0CC45846CE5E@cisco.com>

So first of all replying to bugs does not seem to work and people should be aware it is failing.

2nd I am not OK with this resolution. I think several people feel we need the API in 1.0

Begin forwarded message:

From: Mail Delivery System <MAILER-DAEMON@alln-iport-6.cisco.com<mailto:MAILER-DAEMON@alln-iport-6.cisco.com>>
Subject: Delivery Status Notification (Failure)
Date: October 31, 2014 at 9:24:44 AM PDT
To: <fluffy@cisco.com<mailto:fluffy@cisco.com>>

The following message to <bugzilla@jessica.w3.org<mailto:bugzilla@jessica.w3.org>> was undeliverable.
The reason for the problem:
5.1.0 - Unknown address error 550-'relay not permitted'
Reporting-MTA: dns; alln-iport-6.cisco.com<http://alln-iport-6.cisco.com>

Final-Recipient: rfc822;bugzilla@jessica.w3.org<mailto:bugzilla@jessica.w3.org>
Action: failed
Status: 5.0.0 (permanent failure)
Remote-MTA: dns; []
Diagnostic-Code: smtp; 5.1.0 - Unknown address error 550-'relay not permitted' (delivery attempts: 0)

From: "Cullen Jennings (fluffy)" <fluffy@cisco.com<mailto:fluffy@cisco.com>>
Subject: Re: [Bug 20819] no priority API
Date: October 31, 2014 at 9:23:17 AM PDT
To: "bugzilla@jessica.w3.org<mailto:bugzilla@jessica.w3.org>" <bugzilla@jessica.w3.org<mailto:bugzilla@jessica.w3.org>>

On Oct 31, 2014, at 9:10 AM, bugzilla@jessica.w3.org<mailto:bugzilla@jessica.w3.org> wrote:


Harald Alvestrand <harald@alvestrand.no> changed:

         What    |Removed                     |Added
           Status|NEW                         |RESOLVED
               CC|                            |harald@alvestrand.no
       Resolution|---                         |LATER

--- Comment #6 from Harald Alvestrand <harald@alvestrand.no> ---
The WG consensus is that we can live without this for the 1.0 API version

The likely control surface is the RTPSender API.


Uh, I don't think that works for a bunch of us. As previously agreed we would like the high, med, low, of whatever the levels are. Not OK with this result.
Received on Friday, 31 October 2014 16:34:02 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:18:01 UTC