Relation between a track's constraints/settings and how it is transmitted

Hi,

reading the webrtc-pc spec, I can't find any text on the relation 
between a MediaStreamTrack's applied constraints/settings and how that 
track would be transmitted if added to a PeerConnection.

Is this an oversight or intentional?

It seems to me that it would be logical for a web author to expect, if a 
video track is constrained to e.g. a certain width, height and 
framerate, the UA to try (of course there are situations when it is not 
possible to fulfill the constraints - there may be network congestion or 
CPU limitations for example) to honor this if the track is transmitted 
to a peer using PeerConnection. But as I read the spec the UA is free to 
completely disregard the constraints that have been applied.

Stefan