Re: media casting cluster*

Michael Thomas <mike@mtcc.com> Fri, 09 April 2021 23:20 UTC

Return-Path: <mike@fresheez.com>
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 50CB53A1652 for <ietf@ietfa.amsl.com>; Fri, 9 Apr 2021 16:20:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.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 gWQl9fY4-5ld for <ietf@ietfa.amsl.com>; Fri, 9 Apr 2021 16:20:15 -0700 (PDT)
Received: from mail-pj1-x1031.google.com (mail-pj1-x1031.google.com [IPv6:2607:f8b0:4864:20::1031]) (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 860C43A1651 for <ietf@ietf.org>; Fri, 9 Apr 2021 16:20:15 -0700 (PDT)
Received: by mail-pj1-x1031.google.com with SMTP id ha17so3626908pjb.2 for <ietf@ietf.org>; Fri, 09 Apr 2021 16:20:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=LihR78gph/iQQUD37sTwNRliAVqjYreX7mPdJcrDgTg=; b=NT4btbOjjhFDWRZh7pIO+JLFoKn73LkQ8+cnqvhNwRuigneeTfr6dY+Zc5ExDNoU8m 8u5TyK2QEbCXglzdNtXIL651SWH8To0XWhNfd9f+GZ25Hjjvl/vEDUkFBLCkQ2THe79r VO/Zec51CJznHcM4gtAXN5wWar3nZPuP4TAcjRQasbq2Quu/jMtbyoJUAICswI9pzA+x bEYm2dWFvynvVzCpNigvyG+tkHGZf0ToAdFXc97EP1aPLhBTqZ7pUeRgTiY5KL4Gftqz 2JOf94Bh/k+dva6YdmhHtm5WXzfv7b5yoLVI0yvDs5INAT+eQpQrPNAZeWKUdxVpaL5j +EgA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=LihR78gph/iQQUD37sTwNRliAVqjYreX7mPdJcrDgTg=; b=I3WOhixK1pWpK9F1je0x2PgWz8HjdCJoYLIz+iWw/eXcws92op5JniXLtR3iNWkDDz Lc3DtVQdw3hAkPtKpcZ+Mi/Yck0eQ2b4jW4g4boBBeTb250PxLyl4fDDeBbtC6PBAwJd Yit31reI3I2Ul17HRYDP8qNtr6BXoGmBUaPbZF5JC6hIK8+XpZlJbvrYQBY9TPBSxZ7R CqWQZcadOmsKnyGR6qZ0lbN15i9devZ/siYrC9GCUoru5YaMvtQ5UuQLmtSbkhza3PYQ ORyvDMpCQuQ3/w/apVbOLV4rEGZXkeI3suit+cX30LCZLt0TSLNEXvoapYvck4BertbB N7Zw==
X-Gm-Message-State: AOAM531N9Fq2Zoz+wd2v6r0jeN69MHF0GGtfL5XZipidJsAtPaAVutgm eaM9Hi+YlzJg94TL9jspk6gG1IHiid6zFQ==
X-Google-Smtp-Source: ABdhPJxH1Fx4ZqxmW9YcVnq6aBp6Liarc04hgjD1gI7MA749Jdzc8PihpVTz62RU4ULX19aSvYL1DQ==
X-Received: by 2002:a17:902:9b8b:b029:e6:b027:2f96 with SMTP id y11-20020a1709029b8bb02900e6b0272f96mr15586452plp.28.1618010413888; Fri, 09 Apr 2021 16:20:13 -0700 (PDT)
Received: from mike-mac.lan (107-182-38-56.volcanocom.com. [107.182.38.56]) by smtp.gmail.com with ESMTPSA id l124sm3124632pfl.195.2021.04.09.16.20.12 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 09 Apr 2021 16:20:13 -0700 (PDT)
Subject: Re: media casting cluster*
To: Tim Cappalli <Tim.Cappalli@microsoft.com>, "ietf@ietf.org" <ietf@ietf.org>
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> <SJ0PR00MB1038BD76135FFE31379B25E195759@SJ0PR00MB1038.namprd00.prod.outlook.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <182fbaf3-2442-0bba-716d-92de784ceba7@mtcc.com>
Date: Fri, 9 Apr 2021 16:20:11 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.9.0
MIME-Version: 1.0
In-Reply-To: <SJ0PR00MB1038BD76135FFE31379B25E195759@SJ0PR00MB1038.namprd00.prod.outlook.com>
Content-Type: multipart/alternative; boundary="------------55306FEECD72BDD7AE35B152"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/AyBzo5e9fLNNi2HkQwnDYrlJQTE>
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, 09 Apr 2021 23:20:20 -0000

On 4/7/21 4:46 PM, Tim Cappalli wrote:
> openscreenprotocol/explainer.md at master ยท w3c/openscreenprotocol 
> (github.com) 
> <https://github.com/w3c/openscreenprotocol/blob/master/explainer.md#protocol-overview>


Does this have buy in from the usual suspects including Firefox? If so 
that would be fantastic.


Mike


> ------------------------------------------------------------------------
> *From:* Michael Thomas <mike@mtcc.com>
> *Sent:* Thursday, March 18, 2021 15:59
> *To:* Tim Cappalli <Tim.Cappalli@microsoft.com>om>; ietf@ietf.org 
> <ietf@ietf.org>
> *Subject:* Re: media casting cluster*
>
>
> 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> <mailto:mike@mtcc.com>
>> *Sent:* Tuesday, March 16, 2021 19:17
>> *To:* Tim Cappalli <Tim.Cappalli@microsoft.com> 
>> <mailto:Tim.Cappalli@microsoft.com>; ietf@ietf.org 
>> <mailto:ietf@ietf.org> <ietf@ietf.org> <mailto: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%7C492717640a29480d7b3908d8ea485d20%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637516943819588036%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=AI2Ms7%2F%2Ff2%2BdZFerCH9dnAD%2BqW%2Fgjc%2B7IXffMeAburA%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
>>>