Re: [rtcweb] Is rtcweb the right place for draft-ietf-rtcweb-mdns-ice-candidates?

Bernard Aboba <bernard.aboba@gmail.com> Thu, 04 July 2019 06:08 UTC

Return-Path: <bernard.aboba@gmail.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 EF1AC120128 for <rtcweb@ietfa.amsl.com>; Wed, 3 Jul 2019 23:08:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 dmLgjesbI7nS for <rtcweb@ietfa.amsl.com>; Wed, 3 Jul 2019 23:08:35 -0700 (PDT)
Received: from mail-lj1-x22d.google.com (mail-lj1-x22d.google.com [IPv6:2a00:1450:4864:20::22d]) (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 B3A79120111 for <rtcweb@ietf.org>; Wed, 3 Jul 2019 23:08:34 -0700 (PDT)
Received: by mail-lj1-x22d.google.com with SMTP id v24so4881966ljg.13 for <rtcweb@ietf.org>; Wed, 03 Jul 2019 23:08:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=bkVGGmJ0XaXsPy5xTHud+Jf4tqP0tcFdk41etIPmv2U=; b=UmvvyTQRI7lBuoQTYWiPIFMtEOrjoOfkwGBdoDGU6DOVxys3Ikr8IpVBqzLLBFle2U lipRqq4J5vK17LJuB4Hvehk6PlRKZ8DDmLA50UDF3CKyIaxdr8dm0Z5NlNHhBMMbOfOQ uqIko9XzIsbhuDC6Am/F1Sbq4dGp8LaYDYEQwOHYAbQYzRjx3m89n3Vbz7n+8NU2wSHR hazKCpvCZ7/ZuY52KkVYNzKp3HoUEMv1Gl+kp8wlEe2F4b/J4YOD7DOOymNRdV+X6yMP vai7LfSTuBe3xpWA0Fh+caxCQiwQvpXMPFbfm/yZ2jY9wsejrmWOGPUTSDUGqZxBmW3D 6vNQ==
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=bkVGGmJ0XaXsPy5xTHud+Jf4tqP0tcFdk41etIPmv2U=; b=fwka1gHPMd0NW5jkpvvhZ7QfLfh/1nok80M/ZcKM/M7+FKxxkTmLotQ0/Zh/g8PEBQ L1xJp+/RNN+PNIb6+HPHR6W4xomDCi1EC1EiHuFwOXKH9zGC6R19h+liW6a8DYyp7R3O +bvyKJHubvnrx/qjN7LjBSBba5zh2rykvRkBW8UGEGxIlrdEwu9oRASI90/rC+C7Ktr6 8Z9T62FQgrk7ypDEJe+wYrGnbX3WRAg4xWjBx+OXnfX84sbBUueqNsVP868c1yxz33wZ cg+D0KiKZ7lcn3GEdnQYDQ7VpO3sq/RJ0rRtQe/Ey7MGNpBuSDUN3bkUIk/T3kUDMY3+ iZmA==
X-Gm-Message-State: APjAAAWk0c8pByQ+hYFCF/zL0xG2zL58KUMxSB7bML2mWknhoXB80zwT bFK0QBG9M2wnHapfiZGT2pwK16YGWU+kGS5HT4M=
X-Google-Smtp-Source: APXvYqwKb+tKnkHyAsNAplwezvHXOke8aqs8kKmw4k9ghDrNVo3xsvsSP35IqvWBC9MY/9qutpCqDhWAabpTP/wh/LI=
X-Received: by 2002:a2e:124c:: with SMTP id t73mr23184837lje.190.1562220512391; Wed, 03 Jul 2019 23:08:32 -0700 (PDT)
MIME-Version: 1.0
References: <b03853a4-1006-4da0-d52f-9e7462a2cd0c@alvestrand.no> <D80CECAF-B520-40A2-BFBB-E39B73BA943D@sn3rd.com> <CAD5OKxsd-SE8VpwFgto3DLbabs+9O+cHMucy1+Cep7tCJQR6+w@mail.gmail.com> <CAOJ7v-2XrND6YWqo2tEiDbs7TZpEoiP+MGBAk2aF7hfoMiGk0Q@mail.gmail.com> <CAD5OKxtSzOfnN8WrV-duwwfmwa+VJX_3HACiXU43Xeym25GQaQ@mail.gmail.com> <CAOJ7v-1pKuvNfuPVqJQKj1d0U8Z7JH9aqNU0DkNDMYvec7jyUQ@mail.gmail.com> <40E6F158-7AA1-42AD-9D18-1B4C335ECD64@mozilla.com>
In-Reply-To: <40E6F158-7AA1-42AD-9D18-1B4C335ECD64@mozilla.com>
From: Bernard Aboba <bernard.aboba@gmail.com>
Date: Wed, 3 Jul 2019 23:08:38 -0700
Message-ID: <CAOW+2dvvXD9BTsu_rF2FFg+drhS36z6SXzYYp3Z2HMV6QzUVpw@mail.gmail.com>
To: Nils Ohlmeier <nohlmeier@mozilla.com>
Cc: Justin Uberti <juberti=40google.com@dmarc.ietf.org>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b3b9f0058cd4cefc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/B4nSFC_M4kK-VviLSItgmHSopBg>
Subject: Re: [rtcweb] Is rtcweb the right place for draft-ietf-rtcweb-mdns-ice-candidates?
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, 04 Jul 2019 06:08:38 -0000

Nils said:

"assuming it includes using mDNS in the connection line, will break interop"

[BA]  Can someone provide a legacy citation relating to FQDNs in the
connection line?  I am struggling to find one.

draft-ietf-mmusic-rfc4566bis
<https://tools.ietf.org/html/draft-ietf-mmusic-rfc4566bis>  Section 5.7
only talks about IPv4 and IPv6 addresses.  I do not see mention of FQDNs.

draft-ietf-mmusic-ice-sip-sdp does not mention FQDNs in the "c=" line and
all examples show IPv4 or IPv6 addresses.

RFC 3264 does not mention FQDNs in c= lines in the text, although it uses
FQDNs within examples (such as Sections 10.1 and 10.2).

JSEP does not mention FQDNs in "c=" lines as far as I can tell.

Also in these documents, I do not see instructions on how a legacy
implementation should gracefully react to FQDNs in the connection line
(e.g. ignoring it).

On Wed, Jul 3, 2019 at 9:50 PM Nils Ohlmeier <nohlmeier@mozilla.com> wrote:

> Probably not the ideal forum to point this out, but I hope the Chrome team
> is aware that rolling out this feature, assuming it includes using mDNS in
> the connection line, will break interop with Firefox.
> So I have to concur that rolling this out appears to be premature to me.
>
> Best
>   Nils Ohlmeier
>
> On 3Jul, 2019, at 17:58, Justin Uberti <
> juberti=40google.com@dmarc.ietf.org> wrote:
>
> Hmm, that's unfortunate. I think this is a mistake, given that we are
> about to throw the switch to enable mDNS for 100% of Chrome endpoints;
> Chrome (and soon all browsers) will have to ignore ice-sip-sdp until this
> extension spec is written.
>
> ice-sip-sdp isn't published yet, so it seems an update to that document
> could still be a possibility. If that's not an option, putting forth #1 as
> a specific extension that allows FQDN candidates to be generated in certain
> situations seems like the right path.
>
>
>
> On Wed, Jul 3, 2019 at 5:40 PM Roman Shpount <roman@telurix.com> wrote:
>
>> Part of the problem is that mmusic have decided to punt on the FQDN
>> support. In the current mmusic-ice-sip-sdp the final language that was
>> included:
>>
>> <connection-address>:  is taken from RFC 4566 [RFC4566].  It is the IP
>> address of the candidate, allowing for IPv4 addresses, IPv6 addresses, and
>> fully qualified domain names (FQDNs).  When parsing this field, an agent
>> can differentiate an IPv4 address and an IPv6 address by presence of a
>> colon in its value - the presence of a colon indicates IPv6.  *An agent
>> generating local candidates MUST NOT use FQDN addresses.  An agent
>> processing remote candidates MUST ignore candidate lines that include
>> candidates with FQDN *or IP address versions that are not supported or
>> recognized.  *The procedures for generation and handling of FQDN
>> candidates, as well as, how agents indicate support for such procedures,
>> need to be specified in an extension specification.*
>>
>> So, at this point we have two options:
>> 1. draft-ietf-rtcweb-mdns-ice-candidates can update ice-sip-sdp and
>> define how FQDN candidates generated by mdns are handled
>> 2. write a new draft in mmusic which defines FQDN handling
>>
>> In any case some sort of mmusic discussion is needed to reconcile this.
>>
>> Best Regards,
>> _____________
>> Roman Shpount
>>
>>
>> On Wed, Jul 3, 2019 at 8:28 PM Justin Uberti <juberti@google.com> wrote:
>>
>>> The problem this draft is trying to solve is fairly RTCWEB-specific. If
>>> there are individual issues to resolve, we can send them out to mmusic for
>>> discussion, but AFAIK no changes to existing ICE specs are needed.
>>>
>>> On Wed, Jul 3, 2019 at 4:26 PM Roman Shpount <roman@telurix.com> wrote:
>>>
>>>> Hi All,
>>>>
>>>> Is rtcweb the right place for draft-ietf-rtcweb-mdns-ice-candidates?
>>>> This entire draft seems to be ICE/SDP specific and not limited to rtcweb.
>>>> Also, there are significant interop implications for this draft
>>>> between browser and non-browser end points which probably warrant larger
>>>> discussion outside of rtcweb group. I would think mmusic would be a much
>>>> better place for this draft. I know there is an incentive to complete this
>>>> draft quickly but this has a potential to break a lot of things (it already
>>>> did break interop with almost every existing ICE implementation).
>>>>
>>>> Regards,
>>>> _____________
>>>> Roman Shpount
>>>> _______________________________________________
>>>> rtcweb mailing list
>>>> rtcweb@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/rtcweb
>>>>
>>> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>