Re: Reducing normative dependencies

Hi Cullen,

When we wrote up the pc-stats, I noted that there was a desire to add items to the RTCStatsType, the current PC spec defines two:

enum RTCStatsType {
    "inbound-rtp",
    "outbound-rtp"
};

while the pc-stats adds a few more. 

enum RTCStatsType {
    "inboundrtp",
    "outboundrtp",
    "session",
    "track",
    "transport",
    "candidatepair",
    "localcandidate",
    "remotecandidate"
};

At the face-to-face, the question was: how to extend the enum? or should we update the PC spec with the additional items? Since getStats() is a partial interface, it was decided to move everything including IDL to the pc-stats spec. Now, if we want to keep the documents as they were before the PR, the above question needs to be resolved. I don’t have a strong feeling about where this should reside.

Cheers,
Varun

> On 04 Dec 2014, at 18:25, Cullen Jennings (fluffy) <fluffy@cisco.com> wrote:
> 
> 
> I don't want to be adding new normative dependencies to the PC spec at this point if we can avoid that. Previously we had agreed to keep the structure for the stats in PC spec so that other specs could define new stats but not have PC spec normatively depend on the all the specs that defined stats. I think this is the right decision and we should stick with it. Let me know if there is a good reason not to.
> 
> Thanks, Cullen
> 
> 
> 

—
http://www.netlab.tkk.fi/~varun

Received on Friday, 5 December 2014 08:16:00 UTC