IETF Logo Mail Archive

Re: [rtcweb] Review of draft-ietf-rtcweb-mdns-ice-candidates

youenn fablet <youennf@gmail.com> Fri, 14 September 2018 19:49 UTC

Return-Path: <youennf@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 256A5130E6B for <rtcweb@ietfa.amsl.com>; Fri, 14 Sep 2018 12:49:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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_PASS=-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 qjvnrFG1wDJu for <rtcweb@ietfa.amsl.com>; Fri, 14 Sep 2018 12:49:15 -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 40EF5130E3A for <rtcweb@ietf.org>; Fri, 14 Sep 2018 12:49:15 -0700 (PDT)
Received: by mail-lj1-x22d.google.com with SMTP id y17-v6so8456321ljy.8 for <rtcweb@ietf.org>; Fri, 14 Sep 2018 12:49:15 -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=B0PcHXfVcUYLJyoo/GKv+wz6+S9cOcfE1GW4exjvm5o=; b=C6F0ikMiLAo8hFYqcRGqZS60/9GElgn/+eoh55Wsv19K3qsqi5EdgFM4g2j3knorGp iVAFRhcshu7K1MiX78fnzNOUCraTVn3Smmm92ipi/49oaL3tDIQ2MKxL0SbYmgDW/fjb eTbXMVtuOBFrUGCYZTd42wgYpABoNWC1Rz+qxdeX49l6D7wft0WLjQncT+JyTMOyFrnE XR76VHWYKUX5Rv3s9jCAwpT9UzFFvERkXpV6Ui8AEFe/Ub0vdl2fS9A4T/NvWGHViRjV Wqx5IpEUL9DcvIzeeVT0TryQKJceXE8zecYIuaW0lpYr69QGZC2/2f5y02FrkqR5J/gd f47A==
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=B0PcHXfVcUYLJyoo/GKv+wz6+S9cOcfE1GW4exjvm5o=; b=e0AYVNr3+iXhUEwLGBE9uqUHVGqfvbYCFGoU/LM/muH7ZLmidc7nweAFbqzZMpDWSs WYISWKjD45wjLQ1RD6IkoESm+BcCqzA3yIYg6RG9l8gesX09pFQomK0qVNGj61xV7+Rd PbQRHfngRqBuch2+zFbo+tHBumLVHP/KgGUvBVu0jKApCU5Q4wTt09BQ+VmAxk1M4fJI Yn2Gf1w8AP5N9ytTJwzCi7KJnfmuZt9CToviAqOkVimjrk4Aojvs813FC2+wPAsqNetp 5wUd5KyUgiC1gSBIssw3XOQylwDVfh5OsiLJU2vEQ8xThkP0e3k8Tl1Da/W14j/vEO7Z VtfA==
X-Gm-Message-State: APzg51Bb3QmKzFz3Rt2dFSYVSvzg+Rp88eUPxMjXzNFBvJaw0cCN73Ly b7AXBGcLEBcq9/c2Bb1XSAg/sEqXE8rziQROk38=
X-Google-Smtp-Source: ANB0VdaGmlKGNieoi/NyH1JYkseq4Nzo4RmaCrukQJLs2FoI1tG0nKI0jhursFwPBELhxxsI10nd4DbmcAto98+rTL0=
X-Received: by 2002:a2e:8188:: with SMTP id e8-v6mr8645190ljg.138.1536954553392; Fri, 14 Sep 2018 12:49:13 -0700 (PDT)
MIME-Version: 1.0
References: <CAOW+2dtkNjzS0DkD37SD=POtC2Nd6Xe=upyjvVoyBnnMw7qwbQ@mail.gmail.com> <E33840DD-0E89-40C2-9CFF-E1A798007C7B@westhawk.co.uk> <84F2BA5D-3B55-4B75-A8BE-C36852BA251C@gmail.com>
In-Reply-To: <84F2BA5D-3B55-4B75-A8BE-C36852BA251C@gmail.com>
From: youenn fablet <youennf@gmail.com>
Date: Fri, 14 Sep 2018 12:49:01 -0700
Message-ID: <CANN+akYPTyA2tQrPRAKGd=DV4f8DWCFQknMJ8OnywoTdyZtn_Q@mail.gmail.com>
To: Bernard Aboba <bernard.aboba@gmail.com>
Cc: westhawk <thp@westhawk.co.uk>, RTCWeb IETF <rtcweb@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000030e2e30575da1e5b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/X3WCq5Co10hwoHq5oymhllKmZro>
Subject: Re: [rtcweb] Review of 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: Fri, 14 Sep 2018 19:49:19 -0000

Le ven. 14 sept. 2018 à 11:56, Bernard Aboba <bernard.aboba@gmail.com> a
écrit :

> Good point. In that scenario (where getUserMedia isn’t called) the current
> permissions model wouldn’t even allow presentation of alternative output
> audio devices (e.g. speaker or headphones).
>

Is that an issue though? How is it different than viewing regular DASH/HLS
content?
I would hope that the browser makes a good job at selecting the right
output in such case.
If it does not do so, maybe that is a browser bug. Or maybe the page could
provide hints so that the browser does the right selection.

To return to the initial question, in the sendonly/town-hall meeting
scenario, what is the configuration that mandates exposing host candidates?
How common is it?


> > On Sep 14, 2018, at 10:47 AM, westhawk <thp@westhawk.co.uk> wrote:
> >
> > I’d argue  that sendonly video is also impacted - things like town-hall
> meetings etc
> > T.
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>

v2.23.0 | Report a Bug | By Email