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

Justin Uberti <juberti@google.com> Thu, 04 July 2019 00:58 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 0A11D1206A4 for <rtcweb@ietfa.amsl.com>; Wed, 3 Jul 2019 17:58:45 -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 kNuBC4Z6ygvh for <rtcweb@ietfa.amsl.com>; Wed, 3 Jul 2019 17:58:42 -0700 (PDT)
Received: from mail-vs1-xe34.google.com (mail-vs1-xe34.google.com [IPv6:2607:f8b0:4864:20::e34]) (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 35A4F120629 for <rtcweb@ietf.org>; Wed, 3 Jul 2019 17:58:42 -0700 (PDT)
Received: by mail-vs1-xe34.google.com with SMTP id m8so976141vsj.0 for <rtcweb@ietf.org>; Wed, 03 Jul 2019 17:58:42 -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=UWHSldNF4DF1VRBS0nHbTyG4adXpK7+4hxTK8RxN5Bc=; b=TQyp+VtKxyvIv911X7SJe0qyW7Xx7idtFV0DbwBSMLIJIq40RbMbFd3P72nLWwngFu nkvJ9jEp4HfcN8b4L0EyDyg5V26TcYQ/MgOi+J/0STDVXWcagUQOVo797omSvnqft4bv QkbTDSbNVTcuymo6FzqxwP4pKdd9ZEEcym/ib0/q1okDDAwfY/zLaoe3+ERh92Pxm3Kf GqahIcTGPOoYeFE7qpLfcOdAQF1xuKjkP3XlbtsBahEbtH3o47Z6f/Ro5/x7LRduwVFR oFbu7JgTinvFaP8sNBARzg5EKWlbbeYDxlO7AuZrrn4nl+BEymAuDtOl/K+bZrdc/3Pe DWBg==
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=UWHSldNF4DF1VRBS0nHbTyG4adXpK7+4hxTK8RxN5Bc=; b=G335omSYK1kZ82AavCHdU804O++ukWmtXs1qMuQbtYVAf3R4RjQ4m59HQbYjAbsNdz UWrjSipyEVTSuY49ZPurb0pdvBZvFlN99k+nFPVRItZVv5BfP8Khk7dbMV2Gk6S3hloG 0kzWyv4+0CuNStBN+o1iGHCCBgABjXwKymzUTLb6D3jTV82wRt/CBSDqkNyFgljx7x2Q +QrS97ZRNAXmg/lf357GHeyrF0gcwcpDsrXtzMv81yHnF/YYFjijT2WqCV0RHQgD5n3Z fJVLbR+K3YTCzinBX8fQRHdTUgxLWBJXbNVl/KGEDnhwhWH04O2cgvlUuYKbWyj2KZuT C4dQ==
X-Gm-Message-State: APjAAAXI8r88h4KG0yAra7RJ2SbP4qKRugO4snpK75LvQ+HOnkeBsYJA 0CyCSQ+zAewU3GbJLCMAUcnkmyYJfIsuW1kByBf9aA==
X-Google-Smtp-Source: APXvYqwi+E4c/x8vz63YbpcLA/l41tXxDaSaetiMMt0d4O8IAE0FDtisa+iOKicNRJkYdaBBG2Yi78YLb4/dqmMt36A=
X-Received: by 2002:a67:8d8a:: with SMTP id p132mr19465472vsd.103.1562201920450; Wed, 03 Jul 2019 17:58:40 -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>
In-Reply-To: <CAD5OKxtSzOfnN8WrV-duwwfmwa+VJX_3HACiXU43Xeym25GQaQ@mail.gmail.com>
From: Justin Uberti <juberti@google.com>
Date: Wed, 3 Jul 2019 17:58:28 -0700
Message-ID: <CAOJ7v-1pKuvNfuPVqJQKj1d0U8Z7JH9aqNU0DkNDMYvec7jyUQ@mail.gmail.com>
To: Roman Shpount <roman@telurix.com>
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000898db5058cd07ac6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/9QMG0U_Vy_luzsFjWedFfkV2IhE>
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 00:58:51 -0000

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