IETF Logo Mail Archive

Google, etc, and their proprietary protocols

Michael Thomas <mike@mtcc.com> Thu, 26 November 2020 20:34 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 7235D3A0D09 for <ietf@ietfa.amsl.com>; Thu, 26 Nov 2020 12:34:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.65
X-Spam-Level:
X-Spam-Status: No, score=-1.65 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc-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 hSJ0YYFUYv1Y for <ietf@ietfa.amsl.com>; Thu, 26 Nov 2020 12:34:00 -0800 (PST)
Received: from mail-pf1-x42c.google.com (mail-pf1-x42c.google.com [IPv6:2607:f8b0:4864:20::42c]) (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 ADFC93A0D03 for <ietf@ietf.org>; Thu, 26 Nov 2020 12:34:00 -0800 (PST)
Received: by mail-pf1-x42c.google.com with SMTP id 131so2544621pfb.9 for <ietf@ietf.org>; Thu, 26 Nov 2020 12:34:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc-com.20150623.gappssmtp.com; s=20150623; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding:content-language; bh=al+0g3MlgxYsvwh0FNPmYPsCMLxs3f2xzbDSmeedp9Y=; b=LIlYTFASFl6G83ayR2qRUe6thq8VKBA0iDjUxf8wCD491sgvPoLcB9KpsrKqYaBwr6 Ea3ZVoiHaLsX3i1xaQBitj66SuyQFt8RdUNan3hDdQYlrTxhNfQeTPg/Zws34VNRlys/ nriBCc5tsrF7FucIIs042PWywGWQIPLutGSa8gpbdm6i+E1AIWYtnJWBp1sshf5BDnVn uUNa0Pwj+qwP9gOGhwaps50JeiUpbJEHqfvriFw4nqRYDpu6jcWPu/eimsGusW2k1qoW w9F+UZB+Z+DqAEBsEbkOdTObdqpuoGCv0TM5caAWC/4AUTUyKFmJTUhjhb0uy88BZxKz CShQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding:content-language; bh=al+0g3MlgxYsvwh0FNPmYPsCMLxs3f2xzbDSmeedp9Y=; b=jdSlTH5NgtJzWHNaLzdqzLodkcoegFoWnHNmF9jCsEKHwYeuBmYOTQxd8CbVDVcc6J 1Nm7XEA50cUCEigLEkLxwMyuT86vOSeijnGtoUtLL9qf6C6WI7ue3ZO6D8XQVGumv0P8 Zoo2DJGiY8oTaaMj8s4th01ebdBFQZ7SRefT8oerDl/YIiN+kCsv9xH67bvizWGgIQn7 Fe3gtUsshZqlrayNXGOtrc5jHGWRAW4aVMW6VkQwqUb9DnGrOmSEuEG2n3ANpaiSokeO AH3s7OlYMD5l9HXVisdsFU2QHI6s+NwK1/x5hbXg24e9yzRAu2HUvj3tyggjYHlu2Tsj xGBw==
X-Gm-Message-State: AOAM532yBp6bJjt5Bd8Kk+A09ll0Gi1fqspbjJTwU5dHSIYcV15mHwjl 9a0FUvJq9ONmuAszUa2oZ35Ty4ew0b9z6g==
X-Google-Smtp-Source: ABdhPJz7EQYWpyUIKS03zRYGj3QY3CNetlM5nND95maA0TXih04jn2g5Dh6+Rtu4KUYkpXJDJe+XzQ==
X-Received: by 2002:a63:c43:: with SMTP id 3mr3859138pgm.222.1606422839609; Thu, 26 Nov 2020 12:33:59 -0800 (PST)
Received: from mike-mac.lan (107-182-37-5.volcanocom.com. [107.182.37.5]) by smtp.gmail.com with ESMTPSA id d24sm6058954pjv.44.2020.11.26.12.33.58 for <ietf@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 26 Nov 2020 12:33:58 -0800 (PST)
To: IETF Discussion Mailing List <ietf@ietf.org>
From: Michael Thomas <mike@mtcc.com>
Subject: Google, etc, and their proprietary protocols
Message-ID: <d00258b3-ef73-ee93-a47d-2831738d32d1@mtcc.com>
Date: Thu, 26 Nov 2020 12:33:57 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.5.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jBJipNfkIZmfG4PGhXBiG32Xzwc>
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: Thu, 26 Nov 2020 20:34:02 -0000

I know there are a whole lot of things that Google is doing for 
configuration, casting of urls (cf chromecast), etc which use 
proprietary protocols. Lots of other vendors are inventing the same or 
similar wheels. Can anybody tell me why these haven't been standardized? 
Is it politics? It sure is a PITA to not be able to send a URL to Apple 
Device or cast from Firefox onto my chromecast. I assume that this 
tangle applies for every other ecosystem like Apple and Amazon.

Does anybody know the history and/or why we suffer this mess? I mean, 
the base level mechanisms seem pretty well understood.

Mike, cheers and happy T-day for those who celebrate it :)

v2.23.0 | Report a Bug | By Email