commit 417eebe5dd5b7ee9e9e8da11a48fc8a19df4eca3
author Taylor Brandstetter <deadbeef@webrtc.org> Mon May 23 23:02:19 2016
committer Taylor Brandstetter <deadbeef@webrtc.org> Mon May 23 23:02:29 2016
tree 86371255933b47c616af6e36cf85dbd829f392b6
parent 5b53b0eeb4068bd446c2f41939ea51113b73fc26

Fixing the behavior of the candidate filter with pooled candidates.

According to JSEP, the candidate filter does not affect pooled
candidates because they can be filtered once they're ready to be
surfaced to the application.

So, pooled port allocator sessions will use a filter of CF_ALL, with a
new filter applied when the session is taken by a P2PTransportChannel.

When the filter is applied:
* Some candidates may no longer be returned by ReadyCandidates()
* Some candidates may no longer have a "related address" (for privacy)
* Some ports may no longer be returned by ReadyPorts()

To simplify this, the candidate filtering logic is now moved up from
the Ports to the BasicPortAllocator, with some helper methods to perform
the filtering and stripping out of data.

R=honghaiz@webrtc.org, pthatcher@webrtc.org

Review URL: https://codereview.webrtc.org/1998813002 .

Cr-Commit-Position: refs/heads/master@{#12856}