Not beyond what is already exposed in WebRTC 1.0.
No
3.3 Does this specification introduce new state for an origin that persists across browsing sessions?
No.
Not beyond what is already exposed by the WebRTC 1.0 specification itself
3.5 Does this specification expose any other data to an origin that it doesn’t currently have access to?
The properties exposed by RTCReceivedRTPStreamStats, RTCRemoteInboundRTPStreamStats, RTCSentRTPStreamStats, RTCOutboundRTPStreamStats, RTCRemoteOutboundRTPStreamStats, RTCIceCandidatePairStats, RTCTransportStats expose network-layer data not currently available to the JavaScript layer.
In addition, we expect that the behavior of WebRTC Stats (in particular RTCMediaStreamTrackStats) on isolated media streams (which aren't otherwise available to the JavaScript layer) will need further work (see w3c/webrtc-pc#1613).
No.
Beyond the risks associated with IP addresses as discussed in the WebRTC 1.0 specification, some combination of some of the network properties uniquely exposed by this specification can be correlated with location.
For instance, the round-trip time exposed in RTCRemoteInboundRTPStreamStats can give some coarse indication on how far aparts the peers are located, and thus, if one of the peer's location is known, this may reveal information about the other peer.
No
3.9 Does this specification allow an origin access to aspects of a user’s local computing environment?
Not beyond what is already achievable via getUserMedia and WebRTC 1.0.
No
No.
No.
No.
No specific behavior defined.
No.
Yes.
No.