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

Justin Uberti <juberti@google.com> Wed, 06 February 2019 00:57 UTC

Return-Path: <juberti@google.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D169128CE4 for <mmusic@ietfa.amsl.com>; Tue, 5 Feb 2019 16:57:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.642
X-Spam-Level:
X-Spam-Status: No, score=-17.642 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.142, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c_zle3vVdyso for <mmusic@ietfa.amsl.com>; Tue, 5 Feb 2019 16:57:34 -0800 (PST)
Received: from mail-it1-x136.google.com (mail-it1-x136.google.com [IPv6:2607:f8b0:4864:20::136]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 691F1128B01 for <mmusic@ietf.org>; Tue, 5 Feb 2019 16:57:34 -0800 (PST)
Received: by mail-it1-x136.google.com with SMTP id a6so2463560itl.4 for <mmusic@ietf.org>; Tue, 05 Feb 2019 16:57:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=lNMNPz7PRH05KqR1BtjFReUSJ13QsK6ioyH3/IOKo8I=; b=PD3odNS/vMaV7fw0lM1XAXLDXgDXcKJ9UKN9Nb27broQDfANTcBuJWgJC5vSsp9Qn5 IQCbmjs2Pt8tvQ5cK1pgIAYr+Y+nXdiI/3ejPMSf4EP8hduvbmEQFkCGNfpf1H+OLZOX /DT4wbPrbX43bE5dRNI6Q84JIm1H4UG1x9zNE4M28iy/FAjOKWfYWaB8mDaVRng6KWfl 0Fw89HN3LmUHEVHBDSxE2KP8BoWp6z2CA8kL//CfB062ZFTQYGzbAAsGZq1WazRccpZH Q4CCW+qwz4RnmCsMzIEX0IyEVmKV+rDZV0EBKthh4QTJnTJ6Sft0pnycEwEW58QQ+2W+ qkKw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=lNMNPz7PRH05KqR1BtjFReUSJ13QsK6ioyH3/IOKo8I=; b=kmESYiZQjojIE35kXDvhbRTDTLgA/Ew7sz41wHqy//Yt3pdV1f2XSxblObiT2dNAc3 z/0vYxLJMfdgUUq8+dFXaTL6FWA599yGbo6P8I9IUhcaHhTlSWpxhbk7jHuLqV6Q0cec DUuP+USRZos8Bo58lJB8NP1F688cHq6hfJt0E7koXsDIf3v0g1J1Gd5RHF3QBvtYb9zJ QkgZBGt3rgQDBJCc2eAYlsFubSh7zYiB9jRL3/ioUWI/xJoqi+1myMACBOXuZ99lavn0 DSr13p11IPizx1uEeWSGr03YIMqg5hBB777LDOeNHK+rlAOHmO0yJpuWXN0iUEzNpyRI KwIg==
X-Gm-Message-State: AHQUAuYsv0UJxrW/7iijallZicqOtGC/ZlNueBKD2RF6QKRn1xcSYIPQ ly3N34regg6hCJN+odgyWakahMk4COnjRqSSvjg6Xg==
X-Google-Smtp-Source: AHgI3IaWIHlB7CyCoa2uXbZJ7nldnvnd9Y/GvURh7kRmvfxzK/dS2JICWODU5lMpHrFBWQkfgIjFj1zdd1IUhZ+1nE8=
X-Received: by 2002:a24:738f:: with SMTP id y137mr897186itb.136.1549414653359; Tue, 05 Feb 2019 16:57:33 -0800 (PST)
MIME-Version: 1.0
References: <CAD5OKxuGEPccJUJ1E0bSmz9RW6CWhhSqW+Dke1Cywrjp-dvaoA@mail.gmail.com> <874l9ousuk.fsf@hobgoblin.ariadne.com> <CAD5OKxut+Y8NnL2FbFQkubU-8up4eu6F9hOxs-8oBOJoCnTQwg@mail.gmail.com> <CAOJ7v-2GC2UWBaqSccZh1MKg6E93NrNKQJagzMCOfuE6SxuptA@mail.gmail.com> <CAOJ7v-2ZWxDFAtfoXTB4OsfJBAaFFqZ1jt0SSCCm4Qi3Qqfj6g@mail.gmail.com> <CAD5OKxuAUaCcO8X+ESoekHMq2Ba5-hviZ08G1Vyg_qSh4mR73Q@mail.gmail.com> <CAOJ7v-0T8gbNtr22MiZzVSsAX8+4ZP-pVueKFVOuSSJLBmv8RA@mail.gmail.com> <CAD5OKxtqxcqrQGCWc_2L1np9ftk_Q=prU3MMXk7Y+wbLCq0rYA@mail.gmail.com> <CAOJ7v-1MXjLtBKJ8gN4nVm-Z9m0HB=ye9E6Wcm5zeOx5y2zkSw@mail.gmail.com> <CAD5OKxuZPX3DbDEEVXbVamHynazJkv5G6CDMqMPmdMwiW4SNdg@mail.gmail.com> <CAOJ7v-2c7baQ9UUzxxuA41jbNqeOD8SdqJgCTDAUPXwOZ7r_4Q@mail.gmail.com> <CAD5OKxsc4F4DOW6=u3XU5N3NJ4jPx35Q-8WNF_0MGZziy7=b=g@mail.gmail.com> <HE1PR07MB31617DB79BE41B64AECF082693920@HE1PR07MB3161.eurprd07.prod.outlook.com> <CAD5OKxu7Sjnp6zLo1jxnqS5_3URM6Fj9KrijSLKXERHBqr1Pkw@mail.gmail.com> <24551658-0943-431C-B319-D74B5DC169B9@gmail.com> <CAD5OKxtn4TCZCgV_4r17AqUgbFxgk1NjMBNCR0Gcn-67zRJCwQ@mail.gmail.com>
In-Reply-To: <CAD5OKxtn4TCZCgV_4r17AqUgbFxgk1NjMBNCR0Gcn-67zRJCwQ@mail.gmail.com>
From: Justin Uberti <juberti@google.com>
Date: Tue, 5 Feb 2019 16:57:21 -0800
Message-ID: <CAOJ7v-1z4P-=RQfUb1o2JGduuVNs3G-HmXNXxuvrM-4XhRH_9w@mail.gmail.com>
To: Roman Shpount <roman@telurix.com>
Cc: Alan Ford <alan.ford@gmail.com>, Simon Perreault <sperreault@jive.com>, RTCWeb IETF <rtcweb@ietf.org>, mmusic WG <mmusic@ietf.org>, Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary="0000000000000667ea05812f360e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/sS_wfsiIzWuy3i9qBSJvcSY9fKU>
Subject: Re: [MMUSIC] [rtcweb] What goes into c= line address when FQDN is used for the default candidate?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Feb 2019 00:57:38 -0000

On Tue, Feb 5, 2019 at 10:19 AM Roman Shpount <roman@telurix.com> wrote:

> On Tue, Feb 5, 2019 at 10:03 AM Alan Ford <alan.ford@gmail.com> wrote:
>
>> If that update was to be made, this goes against the text
>> in draft-ietf-rtcweb-mdns-ice-candidates-02 which says:
>>
>>    An ICE agent that supports mDNS candidates MUST support the situation
>>    where the hostname resolution results in more than one IP address.
>>    In this case, the ICE agent MUST take exactly one of the resolved IP
>>    addresses and ignore the others.  The ICE agent SHOULD, if available,
>>    use the first IPv6 address resolved, otherwise the first IPv4
>>    address.
>>
>
> This is obviously not going to work. At the very minimum ICE client should
> be listening for connectivity checks on all addresses to which FQDN
> candidate resolves, including IPv4 and IPv6. It also should do connectivity
> checks to all addresses. Otherwise, if you have two clients, one dual stack
> and another single stack, they are not going to see each other, since one
> will be listening and sending connectivity checks via IPv6 and another via
> IPv4. This is why language about FQDN was removed from mmusic-ice-sip-sdp
> -- it was broken.
>

> For ICE to work, you want to include all possible addresses for FQDN in
> the candidate list and then proceed with nomination as if they were
> independent candidates.
>

I don't think this is correct behavior, but it's really beside the point
since we can ignore it if we have the one-FQDN-per-address concept we
discussed.

>
> But there’s a bigger problem here, which is how to cope with an FQDN is
>> not resolvable.. So the intention, as I understand it, is that when these
>> host candidates leave the mDNS domain and are thus not resolvable, they
>> will be treated as peer reflexive candidates.
>>
>> But at that point there is no address family information available, so
>> how does an ICE agent know to do pairing with these candidates, which
>> requires the address family to be known?
>>
>
> I do not think this is a problem. For peer reflexive candidates, ICE agent
> knows address family/local address/port where connectivity check was
> received and the address family/remote address/port from which the
> connectivity check was received. Everything, including the address family
> is known in this case and agent can proceed with nomination as with any
> other peer reflexive candidate.
>

Right - this is implemented today in Chrome and appears to be working well
so far (with a few minor bugs discovered along the way).