title: TURN server XOR-RELAYED-ADDRESS IP different from its own public IP
body: <p>Suppose I am running a TURN server bound to a public IP (say 100.0.0.1). When the server creates a relay port for a create allocation request, is it ever the case that the server would send back an IP address that is different from whatever it is bound to (100.0.0.1 in this case) in the XOR-RELAYED-ADDRESS attribute? I'm not familiar enough with networking to know all possible scenarios, and the <a href="https://www.rfc-editor.org/rfc/rfc5766#section-6.2" rel="nofollow noreferrer">RFC 5766</a> doesn't really say anything specific (as far as I can tell).</p>
  <p>Phrased another way, is the IP address in the XOR-RELAYED-ADDRESS redundant? In all cases I have considered, the client only needs to know the port allocated, and could completely ignore the IP of XOR-RELAYED-ADDRESS. As long as the client knows the relay port, it can always send relay data to the TURN server public IP (it already knows the IP since it had to connect initially...) at the relay port.</p>
  <p>Any comments?</p>