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

Roman Shpount <roman@telurix.com> Wed, 14 August 2019 21:21 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 A5D63120D44 for <rtcweb@ietfa.amsl.com>; Wed, 14 Aug 2019 14:21:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.887
X-Spam-Level:
X-Spam-Status: No, score=-1.887 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, URIBL_BLOCKED=0.001] 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 hls7u2uT1liS for <rtcweb@ietfa.amsl.com>; Wed, 14 Aug 2019 14:21:30 -0700 (PDT)
Received: from mail-pl1-x629.google.com (mail-pl1-x629.google.com [IPv6:2607:f8b0:4864:20::629]) (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 D74601201B7 for <rtcweb@ietf.org>; Wed, 14 Aug 2019 14:21:30 -0700 (PDT)
Received: by mail-pl1-x629.google.com with SMTP id m12so172144plt.5 for <rtcweb@ietf.org>; Wed, 14 Aug 2019 14:21:30 -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=rVq+bQsOamnUtmYqPPQaWBnzi4527AoiHNtSgeNV1TI=; b=thTVUao8J9kpMcFbLNitb1YrGorExIIacZJ5KvA0QjTqQZLrtxQdeL8cX/QSyZxeU0 OThFO9cYNTVmWnztvNXyqYz+dlNAyZacxx70Bw1N2egxOQSaoRH4+M+f3PqMh2IzitA0 /ThNCNyK0hbkjsUvm9wppQ6dVWplvqjHcxeULBD0Cn0dL67erSzqk6PwJg/wWYvfFhKN k5wamHDNfdbli2ZdoMBF13cmengzPeUBule21Sx2rfREO0aS8Zalg0HnNwsX8P8YQmpx ievDTwRRhEZeVVZx3zeFEutQ+d9TrCs/TdP6iTt8cdAIV+inh9/pFqAQLpDwreM56QxM dhIA==
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=rVq+bQsOamnUtmYqPPQaWBnzi4527AoiHNtSgeNV1TI=; b=r1onTREyJjJ2NE0HHmY5GEAdIll6uYJ2Dp7qIoZlr7vBUZ/Vfw4JCL365lId2V5FUu fNWCJIH2ZGb3bt0MPHvxj7dpzPDwFphgy9OUgSBrBT8KtDLCUqowgBZJB5Sb6cnkKg+u 4n8tlTy5fYo9/CyDWwAiVs1GqbRIL/ehQdVnC81FkSIMZemoBPGGBo6KhPEcrDdJOMhn nAIHRPlieEIahgAS6UhY5nWVmfiamq8J2kV1PyEF+dPlJNmzFO5Gvivu/CXdJO0ZL9+O BHLwpH00Rs84X+zd1D5hGUKPn/aDUdBojqUHCJa9h9EaHsSCf34Xpid6axZld4tfFVwe EilA==
X-Gm-Message-State: APjAAAWBV/2O9L5ygBXtPnlwfutgSDzK2kOzFmHjL1/ibG+by9aDd0S8 e1BL8Pjx0uVPmCqx95DAca/JsScn0Wo=
X-Google-Smtp-Source: APXvYqxRlZao4ZA7pftv2Qv+jbPl/pbl+1vuycPZ4XPEL3bJlILSUG4vKTFZF6kzgRfq06fYzVMVqg==
X-Received: by 2002:a17:902:8492:: with SMTP id c18mr1284103plo.279.1565817689642; Wed, 14 Aug 2019 14:21:29 -0700 (PDT)
Received: from mail-pf1-f180.google.com (mail-pf1-f180.google.com. [209.85.210.180]) by smtp.gmail.com with ESMTPSA id x1sm640020pjo.4.2019.08.14.14.21.28 for <rtcweb@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 14 Aug 2019 14:21:28 -0700 (PDT)
Received: by mail-pf1-f180.google.com with SMTP id 196so104617pfz.8 for <rtcweb@ietf.org>; Wed, 14 Aug 2019 14:21:28 -0700 (PDT)
X-Received: by 2002:a63:7a06:: with SMTP id v6mr963595pgc.115.1565817688099; Wed, 14 Aug 2019 14:21:28 -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> <CAOJ7v-2CWAX0W02qdRes3G-_5hiWGhWEdLhregO-nb1m2EDZZQ@mail.gmail.com> <CAD5OKxu3sCBaN3MmWmeawuYB-sPqfZt6TqF=dSfs6Q0QdXNYKg@mail.gmail.com> <c6649705-465e-0d7e-1a8b-d93b3867cdb4@alvestrand.no> <CAD5OKxsZtgtWK19jJB4kRDDqZ1NzR9-78fRjgVwJALLFPLRASw@mail.gmail.com> <dee38d45-5561-7e9c-0f48-f0c69ec71403@alvestrand.no>
In-Reply-To: <dee38d45-5561-7e9c-0f48-f0c69ec71403@alvestrand.no>
From: Roman Shpount <roman@telurix.com>
Date: Wed, 14 Aug 2019 17:21:16 -0400
X-Gmail-Original-Message-ID: <CAD5OKxtfv5pu3TuE=B=Wq=eni1q_Ch2cwFfYW46nk4Na1MALtQ@mail.gmail.com>
Message-ID: <CAD5OKxtfv5pu3TuE=B=Wq=eni1q_Ch2cwFfYW46nk4Na1MALtQ@mail.gmail.com>
To: RTCWeb IETF <rtcweb@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000015199305901a57f4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/MtM-tht9Iu5HWavjcflEa5Bb_og>
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: Wed, 14 Aug 2019 21:21:33 -0000

Hi All,

Since RTCWEB is closed, I am going to ask once again: Should we
move draft-ietf-rtcweb-mdns-ice-candidates to mmusic?

I know people are unhappy with mmusic draft development speed, but if
enough people participate, we should be able to complete mdns draft quickly
and potentially develop an additional draft which will clarify generic FQDN
candidate processing procedures.

Thank You,
_____________
Roman Shpount


On Sun, Jul 7, 2019 at 3:47 AM Harald Alvestrand <harald@alvestrand.no>
wrote:

> On 7/6/19 10:15 PM, Roman Shpount wrote:
>
>
> Given mmusic's traditional processing speed, I am not sure there's any
>> point in formally moving the document at this point.
>>
>
> It is especially slow when none of the people interested in the specific
> feature (FQDN in ICE candidates) participate in the discussion. So far this
> looks like this feature is going to be shipped regardless of what anybody
> thinks about it and without even attempting to discuss it in the group
> which is responsible for this functionality.
>
> My favorite examples are -msid (initial version May 2012, IESG evaluation
> June 2016); -sdp-simulcast (initial version April 2015, IESG evaluation May
> 2018); -bundle-negotiation (initial version October 2011, IESG evaluation
> February 2018).
>
> Each of these has its own history, but when a group is capable of
> discussing a draft for seven years before it is IESG-ready, I question the
> effectieness of moving drafts into that group.
>
>
> Best Regards,
> _____________
> Roman Shpount
>
>
>
> --
> Surveillance is pervasive. Go Dark.
>
>