Re: [webrtc-pc] rename RTCIceCandidate.ip to address?

Mapping an IP to a FQDN is impossible in principle.
We can make it a requirement to store the FQDN that the IP was learned from, and report that in "address", but that's the way we have to phrase it.
For remote peer-reflexive addresses (I think that was the name), we don't have the FQDN that it was learned from (we pick up the address from the from address an incoming STUN packet on one of our announced interfaces).

WRT the DNS processing returning multiple candidates, this is now covered by https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-16 section 5.1, with slightly more convoluted language:

"
                                                                               An IP
      address SHOULD be used, but an FQDN MAY be used in place of an IP
      address.  In that case, when receiving an offer or answer
      containing an FQDN in an a=candidate attribute, the FQDN is looked
      up in the DNS first using an AAAA record (assuming the agent
      supports IPv6), and if no result is found or the agent only
      supports IPv4, using an A record.  The rules from section 6 of
      [RFC6724] is followed by fixing the source address to be one from
      the candidate pair to be matched against destination addresses
      reported by FQDN, in cases where the DNS query returns more than
      one IP address."

I'm not completely sure what the last portion means.

-- 
GitHub Notification of comment by alvestrand
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1913#issuecomment-399761738 using your GitHub account

Received on Sunday, 24 June 2018 14:44:03 UTC