Re: [MMUSIC] What goes into c= line address when FQDN is used for the default candidate?

[[e-mail] (Dale R. Worley)]

Roman Shpount <[e-mail]> writes:
> I wanted to see if it was ever decided if c= line should contain IN IP4 or
> IN IP6 when default ICE candidate address contains FQDN.
>
> For instance, in the following SDP:
>
> m=audio 59372 UDP/TLS/RTP/SAVPF 0
> *c=IN IP6 3557773f-5f01-46a4-aa14-54ab35b3d778.local *
> a=rtcp:9 IN IP4 0.0.0.0
> a=candidate:1962264367 1 udp 2122260223
> 3557773f-5f01-46a4-aa14-54ab35b3d778.local 59372 typ host
> a=ice-ufrag:3iia
> a=ice-pwd:HMo0mGLq8nYb9pfnG/nH3pNI
> a=rtcp-mux
>
> Is it correct to use "c=IN IP6 3557773f-5f01-46a4-aa14-54ab35b3d778.local "
> or should it be "c=IN IP4 3557773f-5f01-46a4-aa14-54ab35b3d778.local"?

In regard to ICE *candidates*, RFC 8445 makes it clear that a candidate
is an IP address, not an FQDN:

   2.1.  Gathering Candidates

   In order to execute ICE, an ICE agent identifies and gathers one or
   more address candidates.  A candidate has a transport address -- a
   combination of IP address and port for a particular transport
   protocol (with only UDP specified here).  There are different types
   of candidates; some are derived from physical or logical network
   interfaces, and others are discoverable via STUN and TURN.

The discussion of "default candidates" is a little vague due to the fact
that the ICE specification factors out ICE from any protocol that uses
it, but the default candidate is always a *candidate* and thus an
address, not an FQDN:

   5.2.  Lite Implementation Procedures

   Next, an agent chooses a default candidate for each component of each
   data stream.  If a host is IPv4 only, there would only be one
   candidate for each component of each data stream; therefore, that
   candidate is the default.  If a host is IPv6 only, the default
   candidate would typically be a globally scoped IPv6 address.  Dual-
   stack hosts SHOULD allow configuration whether IPv4 or IPv6 is used
   for the default candidate, and the configuration needs to be based on
   which one its administrator believes has a higher chance of success
   in the current network environment.


   5.3.  Exchanging Candidate Information

   The using protocol may (or may not) need to deal with backwards
   compatibility with older implementations that do not support ICE.  If
   a fallback mechanism to non-ICE is supported and is being used, then
   presumably the using protocol provides a way of conveying the default
   candidate (its IP address and port) in addition to the ICE
   parameters.

Dale