Support port range for IPC P2P UDP sockets.

content/browser/renderer_host/p2p/socket_host_tcp_server.cc

Index: content/browser/renderer_host/p2p/socket_host_tcp_server.cc
diff --git a/content/browser/renderer_host/p2p/socket_host_tcp_server.cc b/content/browser/renderer_host/p2p/socket_host_tcp_server.cc
index a2c031e769830ac990c307744b3ca49d57c802d1..a4af785b3300a6d5a942ea4740125a375610a2d6 100644
--- a/content/browser/renderer_host/p2p/socket_host_tcp_server.cc
+++ b/content/browser/renderer_host/p2p/socket_host_tcp_server.cc
@@ -39,7 +39,10 @@ P2PSocketHostTcpServer::~P2PSocketHostTcpServer() {
   }
 }
 
+// TODO(guidou): Add support for port range.

[tommi (sloooow) - chröme, 2016/07/11 17:54:59]

I guess this means a separate policy then?

[Guido Urdaneta, 2016/07/12 10:15:00]

In the meantime the only call site is
https://cs.chromium.org/chromium/src/content/renderer/p2p/ipc_socket_factory....
which ignores the range.

In this PS we pass the range to the browser, but ignore it there.
What do you think we should do in this CL?

[tommi (sloooow) - chröme, 2016/07/12 10:21:46]

I think it's OK to not address it in this CL but a followup CL would be good.

 bool P2PSocketHostTcpServer::Init(const net::IPEndPoint& local_address,
+                                  uint16_t min_port,
+                                  uint16_t max_port,
                                   const P2PHostAndIPEndPoint& remote_address) {
   DCHECK_EQ(state_, STATE_UNINITIALIZED);