Re: media casting cluster*

Harald Alvestrand <harald@alvestrand.no> Fri, 26 March 2021 21:23 UTC

Return-Path: <harald@alvestrand.no>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA7D03A107E for <ietf@ietfa.amsl.com>; Fri, 26 Mar 2021 14:23:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 Lt09ZVqikbGq for <ietf@ietfa.amsl.com>; Fri, 26 Mar 2021 14:23:51 -0700 (PDT)
Received: from mork.alvestrand.no (mork.alvestrand.no [IPv6:2001:700:1:2::117]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 54A673A107C for <ietf@ietf.org>; Fri, 26 Mar 2021 14:23:50 -0700 (PDT)
Received: from Haralds-P4.lan (109.179.64.158.tmi.telenormobil.no [109.179.64.158]) by mork.alvestrand.no (Postfix) with ESMTPSA id 55BAA7C6B88; Fri, 26 Mar 2021 22:23:48 +0100 (CET)
Date: Fri, 26 Mar 2021 22:23:43 +0100
User-Agent: K-9 Mail for Android
In-Reply-To: <de2e1751-b75a-63bc-ac5f-bbc98e8d9d7c@mtcc.com>
References: <bd87e657-5030-1281-8467-3d0035deb8ae@mtcc.com> <SA0PR00MB103627113D806E995A1EA93F956B9@SA0PR00MB1036.namprd00.prod.outlook.com> <913e1183-2b0f-5561-517b-ece57b2c3cef@mtcc.com> <SA0PR00MB1036651D8A6F55F82DD9FF9F956B9@SA0PR00MB1036.namprd00.prod.outlook.com> <de2e1751-b75a-63bc-ac5f-bbc98e8d9d7c@mtcc.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----3RX8SUBX1V4PZLINMGM6X7FH3511TT"
Content-Transfer-Encoding: 7bit
Subject: Re: media casting cluster*
To: ietf@ietf.org, Michael Thomas <mike@mtcc.com>, Tim Cappalli <Tim.Cappalli@microsoft.com>, "ietf@ietf.org" <ietf@ietf.org>
From: Harald Alvestrand <harald@alvestrand.no>
Message-ID: <1C838557-BBA2-4D5C-BEB8-718FA914CEE6@alvestrand.no>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/IPQk_39Nv3SmWJtzrr7kRR72HTY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Mar 2021 21:23:56 -0000

Don't be too sure. The chrome part of the name may be because there is a browser in it.

Den 18. mars 2021 20:59:36 CET, skrev Michael Thomas <mike@mtcc.com>om>:
>
>On 3/16/21 4:18 PM, Tim Cappalli wrote:
>> Are you asking about content handoff (aka casting) or screen 
>> mirroring? They operate very differently.
>>
>> DIAL is used for content handoff.
>
>
>I'm talking about casting, but really both could use to be
>standardized. 
>I looked over that document (i could only see the first 7 pages for
>some 
>reason), and that kind of the way that Chromecast behaves but not 
>exactly. Chomecast doesn't launch specific apps itself, it just fetches
>
>the media. I saw a vague reference to a token which I'm guessing is
>some 
>sort of bearer token but didn't see how that works.
>
>
>The larger issue is that this entire area is a mess with tons of
>opacity 
>and lack of standardization. I can't, for example, use Firefox to drive
>
>Chromecast.
>
>
>Mike
>
>
>
>>
>------------------------------------------------------------------------
>> *From:* Michael Thomas <mike@mtcc.com>
>> *Sent:* Tuesday, March 16, 2021 19:17
>> *To:* Tim Cappalli <Tim.Cappalli@microsoft.com>om>; ietf@ietf.org 
>> <ietf@ietf.org>
>> *Subject:* Re: media casting cluster*
>>
>>
>> On 3/16/21 4:14 PM, Tim Cappalli wrote:
>>> The DIAL protocol, used by Chromecast, is at least publicly 
>>> documented: DIAL-2ndScreenProtocol-2.2.1.pdf (google.com) 
>>>
><https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.google.com%2Fviewer%3Fa%3Dv%26pid%3Dsites%26srcid%3DZGlhbC1tdWx0aXNjcmVlbi5vcmd8ZGlhbHxneDo1MWVmNzNhZDUyYTI0YTkz&data=04%7C01%7CTim.Cappalli%40microsoft.com%7Ca7253e10c6f1471f080908d8e8d1a42a%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637515334395551096%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=qxFW05hl3mEJLHcVK9vkuSb2RxfdO1HGxZiN%2FxVvIbM%3D&reserved=0>
>>
>> I've seen this before, and I'm pretty sure that it's not the whole 
>> story. Or maybe it's something more recent?
>>
>>
>> Mike
>>
>>
>>>
>------------------------------------------------------------------------
>>> *From:* ietf <ietf-bounces@ietf.org> <mailto:ietf-bounces@ietf.org> 
>>> on behalf of Michael Thomas <mike@mtcc.com> <mailto:mike@mtcc.com>
>>> *Sent:* Tuesday, March 16, 2021 16:55
>>> *To:* IETF Discussion Mailing List <ietf@ietf.org>
><mailto:ietf@ietf.org>
>>> *Subject:* media casting cluster*
>>>
>>> If we built such a thing would they come? It's extremely frustrating
>>> that Apple, Google and Amazon all have different proprietary
>protocols
>>> to cast media from your phone or laptop to a tv or whatever. they
>all
>>> have interoperability problems because their petty business fueds,
>and
>>> for users it is a complete nightmare to try to figure out what is
>going
>>> wrong which happens way too often. Worst of all, is that since it's
>>> proprietary we have no clue what is happening under the hood and
>>> especially what is going on the security front. For example, if I
>were
>>> to cast at a public venue would I potentially be opening myself up
>to
>>> some sort of attack? Nobody but them knows and they aren't telling.
>>>
>>> Mike
>>>

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.