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

Roman Shpount <roman@telurix.com> Fri, 01 February 2019 04:43 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 0AFDD130DF1 for <rtcweb@ietfa.amsl.com>; Thu, 31 Jan 2019 20:43:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.03
X-Spam-Level:
X-Spam-Status: No, score=-2.03 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.142, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] 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 cyQmaEWFyjGD for <rtcweb@ietfa.amsl.com>; Thu, 31 Jan 2019 20:43:26 -0800 (PST)
Received: from mail-pg1-x535.google.com (mail-pg1-x535.google.com [IPv6:2607:f8b0:4864:20::535]) (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 4D5EF131203 for <rtcweb@ietf.org>; Thu, 31 Jan 2019 20:43:26 -0800 (PST)
Received: by mail-pg1-x535.google.com with SMTP id z11so2369476pgu.0 for <rtcweb@ietf.org>; Thu, 31 Jan 2019 20:43: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=KU533c4k4G9BA5pVpb10aItcLkL4Zip6Pk/bXC77de8=; b=2TuPimj4C6YvywfK9QIyzctmdG9u2sUmmaKyOE1f4aNf7k/TvlkP9przhwaJyGZU/5 EWdJrCgy5M/7zv0jOvrA9kQ6+UW9DqDtbo90cSJI4v0i5OucS6OykJ7yPysoB+o3mhxI sKWQnbw1u3yIdgdI9DqGDlbE4eANPd4SJ/GEuZSSeouWsh2asSEyP6mOCSkuI4y15yNH WUAoUs19O5NpmBrCQ51Pp1xsJKCB4KcCEptvQ8+nZlXRKa7c5HV7rfn1g8sp+rpCT8o4 eYDVP/yetwJ7O6oWo5lXMzXWgViemPhuJtX2sTLvHGsKiQJ53QGWBuKfZ5gCh5kgUwDv Bz5A==
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=KU533c4k4G9BA5pVpb10aItcLkL4Zip6Pk/bXC77de8=; b=sxVRo9xV6z3yuHGYloh4TtSpMalYWJhvhPkl6YFDJx61vsw9hRNL1ppO4hR5jKEpy3 4QoYAEWsLPvAo5cwzJq5HoYVZ0T6iWqQ1c8eSlh8x1ZBskO8Lgauc/M8oCbYQjjGPUGe MgmYMVkHuPQ9Rg36Tsjc5f3cOPYlmQ0ACTc2RSkgWC7Go8zaovMRxFm/vOq3MPo0hUAg FBbWLBwtiqKzvZfIgwGpreNTSl4O8xqVXp4GVtDrrxtLDTkZu3Ms6+OdK94nBp+k8x35 no8GJsPP4qEqPLXOWSQG+/DsQbweYv+8+J9ob6TublPre8mLkR9XM8GP1tXBNu3Q4jeZ ILuQ==
X-Gm-Message-State: AHQUAuafolDSmZRsJwgi+gDEu1z80kRtPffrG+85tYmErZQuc2jHc3Jj eRaLkAMoxH6V2SPHVIFjWiGLCRDXASk=
X-Google-Smtp-Source: AHgI3IYA2067a5vmWKfSqg0mWr85xamkKY6EjSowk5GZqRFGyNEPjne1IpsOiquXPYUl5GI/3D3y7Q==
X-Received: by 2002:a63:981:: with SMTP id 123mr768302pgj.444.1548996205720; Thu, 31 Jan 2019 20:43:25 -0800 (PST)
Received: from mail-pl1-f178.google.com (mail-pl1-f178.google.com. [209.85.214.178]) by smtp.gmail.com with ESMTPSA id m198sm7289520pga.10.2019.01.31.20.43.24 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 31 Jan 2019 20:43:24 -0800 (PST)
Received: by mail-pl1-f178.google.com with SMTP id gn14so2544939plb.10; Thu, 31 Jan 2019 20:43:24 -0800 (PST)
X-Received: by 2002:a17:902:8b88:: with SMTP id ay8mr38466463plb.55.1548996203897; Thu, 31 Jan 2019 20:43:23 -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>
In-Reply-To: <CAOJ7v-2ZWxDFAtfoXTB4OsfJBAaFFqZ1jt0SSCCm4Qi3Qqfj6g@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
Date: Thu, 31 Jan 2019 23:43:13 -0500
X-Gmail-Original-Message-ID: <CAD5OKxuAUaCcO8X+ESoekHMq2Ba5-hviZ08G1Vyg_qSh4mR73Q@mail.gmail.com>
Message-ID: <CAD5OKxuAUaCcO8X+ESoekHMq2Ba5-hviZ08G1Vyg_qSh4mR73Q@mail.gmail.com>
To: Justin Uberti <juberti@google.com>
Cc: "Dale R. Worley" <worley@ariadne.com>, RTCWeb IETF <rtcweb@ietf.org>, mmusic WG <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007debae0580cdc8dd"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/_r0lgxwOSZ3YYNuNgSjWoG83t4w>
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: Fri, 01 Feb 2019 04:43:29 -0000

On Thu, Jan 31, 2019 at 10:58 PM Justin Uberti <juberti@google.com> wrote:

> We can however all agree that "c=IN IP6" is busted:
> https://bugs.chromium.org/p/chromium/issues/detail?id=927309
>
>>
>>>
I guess one way to interpret this that each address should have a MDNS
alias. So, if you are dealing with dual stack host, it should provide two
MDNS candidates, one of which is IPv4 and another IPv6. The c= line should
specify FQDN for one of those candidates and specify the type (IP4 or IP6).

There are two problems:

1. There is no way to know which address type is in the candidate-address
when FQDN is used there. Guidance in ice-sip-sdp is talking about the
presence of column in IP6 address, but this definitely does not apply to
FQDN. It would've been better to specify something like local4 and local6
as FQDN suffix in MDNS alias to specify the candidate-address type so that
correct DNS request can be issued.

2. A lot (if not most) SDP/ICE implementations do no support parsing FQDN
in candidate-address or c= line. This might create interop problems since
RFC 5245 specified that candidate-address is an IP Address.

Regards,
_____________
Roman Shpount