Re: New functionality in PR - priority

I'm having a little trouble squaring this with my understanding of the
proposed decision policy. Isn't this a situation where "editors bring
technical solutions in the specifications that have not been reviewed by
the group"?

With this as an example, can someone explain to me what they believe the
procedure for integrating a PR like this into the spec is supposed to be?

-Ekr

On Fri, May 22, 2015 at 5:52 AM, Harald Alvestrand <harald@alvestrand.no>
wrote:

> Hi,
>
> just a heads-up (or something like that):
>
> There's a pull request in the queue for adding a "priority" field to
> RTPSender and to DataChannels:
>
> https://github.com/w3c/webrtc-pc/pull/228
>
> This is to support the priority mechanism specified here:
>
> draft-ietf-rtcweb-transport section 4
> draft-ietf-rtcweb-rtp-usage section 12.1.3
> draft-ietf-tsvwg-rtcweb-qos
>
> I don't think there's anything controversial in it, but it's nice that
> the WG is aware of what's happening when we add new functionality into
> the spec (even when it's been talked about for a long time).
>
> Harald
>
>