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

Justin Uberti <juberti@google.com> Thu, 04 July 2019 15:12 UTC

Return-Path: <juberti@google.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 252D312013C for <rtcweb@ietfa.amsl.com>; Thu, 4 Jul 2019 08:12:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.499
X-Spam-Level:
X-Spam-Status: No, score=-17.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, 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_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham 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 vZzth8riQ_fn for <rtcweb@ietfa.amsl.com>; Thu, 4 Jul 2019 08:12:39 -0700 (PDT)
Received: from mail-ua1-x92e.google.com (mail-ua1-x92e.google.com [IPv6:2607:f8b0:4864:20::92e]) (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 5CC3612011A for <rtcweb@ietf.org>; Thu, 4 Jul 2019 08:12:38 -0700 (PDT)
Received: by mail-ua1-x92e.google.com with SMTP id c4so1237358uad.1 for <rtcweb@ietf.org>; Thu, 04 Jul 2019 08:12:38 -0700 (PDT)
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=iv1GLuA0y4HBHw0g1dT8D2ofnsJQ2wBdYd1z2pQ8Kfo=; b=Oolp7ZPdNVyF87CrdJ5MD3vMFiIo/n1djMAL6sZVgndt+br9KynqASs7U+yj0W9RtB TlVqNw3Toz48/j917oGhNsTfIyKmtRbvoR+GlZeVOHOipT9fVbKepHOOuKWy4nVw8t/B N+RAu2v999kVNeokbPIo1APEEd257z9VQ4QLiHmi0N1WHc0knfBVJFCpPb8O8xXRWdgH voY2r1sDhH6KQVJBc0bq2+v9jL/Pp67oTYngqD12R5JkSlW8HS0BoVO7mbYaGaQ+HFaK LjyXVFmz677G1GVBDGnQNDAmQlP9lNxU5cpkjZTWCCPbQ+1VsynrXijKTnQ0TCZxDzMs EP/g==
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=iv1GLuA0y4HBHw0g1dT8D2ofnsJQ2wBdYd1z2pQ8Kfo=; b=mqi8ahjriubcbGvdZPGbEX+On7M3SGTxV4ocBdNWKWjB7tpXE3kfxf6VrDwBGKDnAv 63v5FRWtUegaSYOrUZLXmvcPoicPLfPOBy3VxASjRQpf6O2rNV27xSz5WCuWlj+PqzrN qD7lUOY/J4vKCAqKERudgnqdtX1uJCckqH/A/wajbiZaJC5C6QK/OapKyNIhkszSxog9 ZtFv+a6s9hhuE3oUsvXRR88D98B2aWj6fTU/B54P1XX+s9fyYSlvSR99VVSLJtTOymmo FWUz4S/nmU9BG1hh43k5/WuTCwlk0qI5/iCbsiFlhk/mO0Y+JCa7Do/V8pQ1WiD7sX3o VVdg==
X-Gm-Message-State: APjAAAXb7ew+X2TLZopJFaKh8UiCKlUf+niJvHAP71Evy9EIDr0AzVce a7zGKKKFj5NpdcmJ34BszRe9881hrw8dSggePozWww==
X-Google-Smtp-Source: APXvYqwB6Np5eJQED1urtFmlPAZ9aiwgv1ViA8dNEGKGoW1muA36IjIRsjKsKnCKW+ORq1YCXyoQECoNNVr2aMBZPyU=
X-Received: by 2002:ab0:6198:: with SMTP id h24mr16187094uan.41.1562253157231; Thu, 04 Jul 2019 08:12:37 -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> <CAOW+2dvvXD9BTsu_rF2FFg+drhS36z6SXzYYp3Z2HMV6QzUVpw@mail.gmail.com>
In-Reply-To: <CAOW+2dvvXD9BTsu_rF2FFg+drhS36z6SXzYYp3Z2HMV6QzUVpw@mail.gmail.com>
From: Justin Uberti <juberti@google.com>
Date: Thu, 4 Jul 2019 08:12:25 -0700
Message-ID: <CAOJ7v-16Vp9mfC3ZPBKGEnRSk0YQC0xHQxm8E_2_Ey2Gdzrhyw@mail.gmail.com>
To: Bernard Aboba <bernard.aboba@gmail.com>
Cc: Nils Ohlmeier <nohlmeier@mozilla.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007cd40c058cdc6851"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/ZLHYcTllqlQrc4GCcQPHge0UNaE>
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 15:12:43 -0000

https://tools.ietf.org/html/rfc4566#section-9

; sub-rules of 'c='

connection-address =  multicast-address / unicast-address

...

unicast-address =     IP4-address / IP6-address / FQDN / extn-addr


On Wed, Jul 3, 2019 at 11:08 PM Bernard Aboba <bernard.aboba@gmail.com>
wrote:

> 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
>>
>