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

Roman Shpount <roman@telurix.com> Thu, 07 February 2019 16:01 UTC

Return-Path: <roman@telurix.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BD4A130EA3 for <rtcweb@ietfa.amsl.com>; Thu, 7 Feb 2019 08:01:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.01
X-Spam-Level:
X-Spam-Status: No, score=0.01 tagged_above=-999 required=5 tests=[DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_SPF_PERMERROR=0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.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 fF35KdDjNoZS for <rtcweb@ietfa.amsl.com>; Thu, 7 Feb 2019 08:01:27 -0800 (PST)
Received: from mail-pf1-x42f.google.com (mail-pf1-x42f.google.com [IPv6:2607:f8b0:4864:20::42f]) (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 E6846129C6A for <rtcweb@ietf.org>; Thu, 7 Feb 2019 08:01:26 -0800 (PST)
Received: by mail-pf1-x42f.google.com with SMTP id z9so129497pfi.2 for <rtcweb@ietf.org>; Thu, 07 Feb 2019 08:01:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=o1g5rkWcKWGEx7n0CudN65EaAdkhaD37UcLCl4jPQ0g=; b=oXsceddh5IRL3aEQRNjvO0NuJTsJzpCpmVHyUupnbgDgYAT6/y1a2fvdMOjb4sQMeD HRNxub2+DVcsVNWfmLEwt2kzxR7tFHNSVcNH7gJCjvn/SVDdolVBj+Wp7LdPuuTlcheI AZqJR+BT9hi/ey3hgTWp3kh0oDhAQ+Kom1v0Elx7O7Lvz4TyHtnkcadOXDir8u1ECt2Z Fxf17cb5mweNo4isJAsWBY70fPYM+lGqiPf6UjOoJ0U0Q6exvhBOP1PI8uMrqttQ0E9A BvnGGDX/g5atp3hQFPOgvZ2ZmWkn4cQxZQpYqQv0sJx6k0t/kmCZNdKywSz9esVN4B26 8Wsw==
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=o1g5rkWcKWGEx7n0CudN65EaAdkhaD37UcLCl4jPQ0g=; b=H2YfJBwVvXb+aw8IqgbUi5FZPc+JZQMuWD8wPnXBl+JvAtz/lr0xf87XnwG39B3b+2 kyJzKSRbFR8GKIXheiu3snq2wAdHH2GX6KX4rNaWhfyBHNF46JrrkLpJNuDq64ZyWVAo 7/KAuwP3EY4fpgDZWd8LLlOpXMYo0L8jhG/w8llYlCnx3bgr8qEE8dKpopdbQOJIkSt8 GLMwTM7RMn86TnRsALdMVuC44SE3Anf5jKm6YtM7Szd1oQgM6da7HHeQGqB5RwZEWNfZ 08Zb6ntnfMFvS62psiwWaAZ0rNhePuXWIoOJa1GlMZfG98hH06KnxKX3+MOtMQc1XFP1 aAAg==
X-Gm-Message-State: AHQUAubcnHWJSIY5TEoawrYJTexxs+QghZXf/RhuU+wO+RGlVYi1BeJz xPPmfkntQwlHC+5O9YPSEmXs6Q4xIHI=
X-Google-Smtp-Source: AHgI3IZsgyonxKiPefey69xfKWvVsQoDJPP25RuR+KSI6Sre+YF+hxltWAXJ7iJGQitGuOHCPOikPA==
X-Received: by 2002:a63:2a89:: with SMTP id q131mr11895077pgq.216.1549555286260; Thu, 07 Feb 2019 08:01:26 -0800 (PST)
Received: from mail-pg1-f172.google.com (mail-pg1-f172.google.com. [209.85.215.172]) by smtp.gmail.com with ESMTPSA id v15sm11710316pfn.94.2019.02.07.08.01.25 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 07 Feb 2019 08:01:25 -0800 (PST)
Received: by mail-pg1-f172.google.com with SMTP id d72so107137pga.9; Thu, 07 Feb 2019 08:01:25 -0800 (PST)
X-Received: by 2002:a63:db04:: with SMTP id e4mr907773pgg.40.1549555284882; Thu, 07 Feb 2019 08:01:24 -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> <CAOJ7v-1z4P-=RQfUb1o2JGduuVNs3G-HmXNXxuvrM-4XhRH_9w@mail.gmail.com> <CAD5OKxv72sfohGx1pYwsfb8hki8NPRvJ=2bbv+MrX88gk7xg1g@mail.gmail.com>
In-Reply-To: <CAD5OKxv72sfohGx1pYwsfb8hki8NPRvJ=2bbv+MrX88gk7xg1g@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
Date: Thu, 7 Feb 2019 11:01:11 -0500
X-Gmail-Original-Message-ID: <CAD5OKxui3MtNmjG+S1jNdo-D6QiLg_Y2=fSXV+XO6U8HXT5fEA@mail.gmail.com>
Message-ID: <CAD5OKxui3MtNmjG+S1jNdo-D6QiLg_Y2=fSXV+XO6U8HXT5fEA@mail.gmail.com>
To: Justin Uberti <juberti@google.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="00000000000050c2ff05814ff431"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/W65gSdJrOGQGVuAQmE0i0FhOqOg>
Subject: Re: [rtcweb] [MMUSIC] What goes into c= line address when FQDN is used for the default candidate?
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Feb 2019 16:01:34 -0000

Hi All,

>From what I can see there is a new problem identified during mDNS
discussion with using FQDN: If all the candidates are FQDN and these names
do not resolve or resolve to more then one address, so all the candidates
will end up being ignored. ICE agent might end up with no remote candidates
and no candidate pairs to form. I think  RFC 8445 does not handle this
situation, but I might be missing something.

P.S. I am not arguing against FQDN, I am just trying to figure out what
needs to be done to get this documented and operational.
_____________
Roman Shpount