Re: media casting cluster*

Michael Thomas <mike@mtcc.com> Fri, 26 March 2021 22:38 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 7D1353A12D0 for <ietf@ietfa.amsl.com>; Fri, 26 Mar 2021 15:38:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.748
X-Spam-Level:
X-Spam-Status: No, score=-1.748 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.25, 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 dDqQDXd_mxGK for <ietf@ietfa.amsl.com>; Fri, 26 Mar 2021 15:38:02 -0700 (PDT)
Received: from mail-pg1-x52a.google.com (mail-pg1-x52a.google.com [IPv6:2607:f8b0:4864:20::52a]) (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 B89CE3A12D4 for <ietf@ietf.org>; Fri, 26 Mar 2021 15:38:02 -0700 (PDT)
Received: by mail-pg1-x52a.google.com with SMTP id l76so5555427pga.6 for <ietf@ietf.org>; Fri, 26 Mar 2021 15:38:02 -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=RW864S6s/0OqqEmCg06hrKHOIQjggGCTcxaT0iEBogg=; b=mvEE7QWL6xz5GecEdLle7/nibtg5vauuW3WC5KT/y13DYD/LbsSu/gGZzLTzJo8DMG vOW9C6uSDf3+C3hI7XSvBUBElA/HRBX0+DM+LnlYJ2atLczainCzlEHK2kM3dZmmPO/o BTx5aOhQYSIK01/7Jaof8GtUTi9ni+zs2QGVWnMAAG2MDEjZljoTbE/BmjcD9gPz0QZY K7fZSNPfo6ykBrJVIKRDVXAZGnUka6fdqzbIRe2JjLQateBZGSjrY8BAco0sWuRVZgq7 H3rvP1Uyk3Sn/i1f5wbrPMjjMlp71M3tnRGSLAyCIe8Dv3IJzDHd9Cs6peNqv1+lPVV7 YoOA==
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=RW864S6s/0OqqEmCg06hrKHOIQjggGCTcxaT0iEBogg=; b=oVfUqT7L6FyuEWQ1I0zxHPdVv2B9kDPNvJe3YRdfsMTsgh1uiHC/g5y+O9IVFbKebE fraU5RPoGS1gqGvrPyJK+db8P920q/fPHaG8TYw4OO4q2Nx1SBn+rGixFN3/uohqOWDQ izxRd+KpAxe6sNblZeJYksR+hphkoHSJ1VsWI9jf63fB410NuVymt9zxFweQ4tWR4kNc 0HUHAlJn0HUMlAniofjUxVfV9B00WEB+J8IMbU1ERtkBPt2O7qtstVliL0g5nCZIMWkE tQkuv44Fb7SwQii8T5rnrX8hUt78OXNi7q3B4Ss/02GB6j9+itaFO+EgDcdB1BAzCTBP +yDA==
X-Gm-Message-State: AOAM532nIoCsZUMXlWfFCP/1rp9fsepsoPEDFfDU/f8Ho6D/s2I9sMg2 FYV4e6q60wuz3WxftFybWRufBQ==
X-Google-Smtp-Source: ABdhPJxU6uq4joxPww6tMP/wHkay6/TCTwwY1/Df9tBJGDa8wpOkEOdU6wR1ZtpCYwDiXgC8CeH7Nw==
X-Received: by 2002:a62:7708:0:b029:1ee:f656:51d5 with SMTP id s8-20020a6277080000b02901eef65651d5mr15156205pfc.59.1616798281353; Fri, 26 Mar 2021 15:38:01 -0700 (PDT)
Received: from mike-mac.lan (107-182-42-86.volcanocom.com. [107.182.42.86]) by smtp.gmail.com with ESMTPSA id w15sm9946511pfn.84.2021.03.26.15.38.00 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 26 Mar 2021 15:38:00 -0700 (PDT)
Subject: Re: media casting cluster*
To: Harald Alvestrand <harald@alvestrand.no>, ietf@ietf.org, Tim Cappalli <Tim.Cappalli@microsoft.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> <1C838557-BBA2-4D5C-BEB8-718FA914CEE6@alvestrand.no>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <f940ac6f-9c58-e055-ef67-bd58912a1e5c@mtcc.com>
Date: Fri, 26 Mar 2021 15:37:59 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.8.1
MIME-Version: 1.0
In-Reply-To: <1C838557-BBA2-4D5C-BEB8-718FA914CEE6@alvestrand.no>
Content-Type: multipart/alternative; boundary="------------F9487C1461BB80B5A67BBDD6"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/GbTryYxah54VM_IXVNnzphFmaAU>
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 22:38:08 -0000

On 3/26/21 2:23 PM, Harald Alvestrand wrote:
> Don't be too sure. The chrome part of the name may be because there is 
> a browser in it.


Ah, good point. Makes app upgrades easy too. It's amazing what you can 
get in a SoC these days...


Mike


>
> 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.