IETF Logo Mail Archive

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

Roman Shpount <roman@telurix.com> Wed, 03 July 2019 23:25 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 20334120173 for <rtcweb@ietfa.amsl.com>; Wed, 3 Jul 2019 16:25:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.888
X-Spam-Level:
X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01] autolearn=ham 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 u-iSl15wHfHv for <rtcweb@ietfa.amsl.com>; Wed, 3 Jul 2019 16:25:56 -0700 (PDT)
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 2F2F91200EC for <rtcweb@ietf.org>; Wed, 3 Jul 2019 16:25:56 -0700 (PDT)
Received: by mail-pf1-x42f.google.com with SMTP id j2so1996556pfe.6 for <rtcweb@ietf.org>; Wed, 03 Jul 2019 16:25:56 -0700 (PDT)
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; bh=3xrTJgqHjZzft0J8pKgKqJKM62wP9UObC7rcPWQ50K4=; b=kMmGtl4X+sqoU1cSYQKCrw3wtR7QQucdcE4ukia37K6xAs8v6XbWo0VRWp934RmRFb Ucak049Vf5Wz8lebT5YoCE4XAC7Nn4HM0q7AA+lUTMzDYWW/v0xcT2CPtSYZFq+8HImZ 4bMt19aFXxIYmqQRQygDKONSc0NUqVT90jvOob86VX2xwgbz5DR1ZaSLNkrC0B1QjS0G qgivpNJfmC72rbY9mCxWGK0nCkac+qf1Nwr5obip1Ibmw1NQBu5Qjsc33Mnub1VQD7nG 99ajSOnaidJeAx6s3Ee+d3RB7Ze0XRC3/DLdRoCSdQqJnlZmOwQsyjUbuR5q3WWIaYkm CfBg==
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; bh=3xrTJgqHjZzft0J8pKgKqJKM62wP9UObC7rcPWQ50K4=; b=NQOmHTFeOdC3jw+YhqxLxdporZzxzUTD28ph3PUZvvQtTa+Fa03fkGanI16+5tl33p +PH+NwuwolXxLTJvNGF/0tq8BS0QY/xj9UVdh5gAfh/ncJX47EuGmqhbbVVuEUVbSp0C SNZ5IsemggwLsBTkidi8ypxrET7qoV2vBKvEUFrtkZ0DD2T3ANQqqBJwmib43bSze9cC hVx783JjzEVBq2asTkxwdVc3tNOU4yEAqfc28JTdeEpns7mAmTcJg9qMuHSOM+UU4p0E waQNra1wb4+MuNl7OlTyT3ZGGbLh7Daqf3bCLK0EUinkNuY8XKcKhWIMZdP451PMMVSw 62Qw==
X-Gm-Message-State: APjAAAX3WeYN0Ym8UOE3wBTC4ZYZxgR9/K1pNYuKMBgv9Yg5XLbQg9XQ F5XaaiHfGx0qkmOlmwEqE1HuBgZF
X-Google-Smtp-Source: APXvYqyY44KvGBLP+X3vQK8T7udUWLSw2uOfJ4qnv7PDh52QTE1dOJMXvNm93bSSD2/SJnPRO429oA==
X-Received: by 2002:a17:90a:9905:: with SMTP id b5mr16042630pjp.70.1562196355249; Wed, 03 Jul 2019 16:25:55 -0700 (PDT)
Received: from mail-pl1-f181.google.com (mail-pl1-f181.google.com. [209.85.214.181]) by smtp.gmail.com with ESMTPSA id b3sm5738994pfp.65.2019.07.03.16.25.54 for <rtcweb@ietf.org> (version=TLS1_3 cipher=AEAD-AES128-GCM-SHA256 bits=128/128); Wed, 03 Jul 2019 16:25:54 -0700 (PDT)
Received: by mail-pl1-f181.google.com with SMTP id w24so2036498plp.2 for <rtcweb@ietf.org>; Wed, 03 Jul 2019 16:25:54 -0700 (PDT)
X-Received: by 2002:a17:902:bd0a:: with SMTP id p10mr45646008pls.134.1562196353859; Wed, 03 Jul 2019 16:25:53 -0700 (PDT)
MIME-Version: 1.0
References: <b03853a4-1006-4da0-d52f-9e7462a2cd0c@alvestrand.no> <D80CECAF-B520-40A2-BFBB-E39B73BA943D@sn3rd.com>
In-Reply-To: <D80CECAF-B520-40A2-BFBB-E39B73BA943D@sn3rd.com>
From: Roman Shpount <roman@telurix.com>
Date: Wed, 03 Jul 2019 19:25:44 -0400
X-Gmail-Original-Message-ID: <CAD5OKxsd-SE8VpwFgto3DLbabs+9O+cHMucy1+Cep7tCJQR6+w@mail.gmail.com>
Message-ID: <CAD5OKxsd-SE8VpwFgto3DLbabs+9O+cHMucy1+Cep7tCJQR6+w@mail.gmail.com>
To: "rtcweb@ietf.org" <rtcweb@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000bdc7a4058ccf2e15"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/UL1nmIEJNlT3M-B4tfw4Ssi8tPQ>
Subject: [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: Wed, 03 Jul 2019 23:25:58 -0000

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

v2.23.0 | Report a Bug | By Email