[pim] Verizon worldwide deployment - question on Chromebook

Gyan Mishra <hayabusagsm@gmail.com> Wed, 22 April 2020 15:15 UTC

Return-Path: <hayabusagsm@gmail.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id CDF6D3A0E65; Wed, 22 Apr 2020 08:15:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id idgal2YJxPmv; Wed, 22 Apr 2020 08:15:03 -0700 (PDT)
Received: from mail-il1-x12f.google.com (mail-il1-x12f.google.com [IPv6:2607:f8b0:4864:20::12f]) (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 C4CE03A0DBA; Wed, 22 Apr 2020 08:15:03 -0700 (PDT)
Received: by mail-il1-x12f.google.com with SMTP id f82so2223819ilh.8; Wed, 22 Apr 2020 08:15:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=l8FBTQDF4sEXrOhwVf51anLqIEp/2FC0tgilOWCiW+w=; b=iarMxrWEaRaapqLZNOmmvUk2AwGEcMbLmeuidEZcZ4gZxMptB3H2u3sKZnCW42Guvy A0XWDGs8ig1CfwGsihyQ+07XaN1Zwea9HvOiiW3Re5U50XZqCYKpWnHAR3DzvxxtDqOr gKUS5zmARU9RDkGcrdi58sebzn2oAt8H0I4B5kIX30IHyqMvegGdPFs2D23WddZTIvrA XpLo+W0UvSYNXLN2LSWUYuEmgvrWX7sxbZn6T0saXRVqAiU6WoGWI9PWkN0bm0CxJ5JM moWzd/lwP931IP5dwRCtSadj6WcYioOvJzHuo+ZXbJiIyDyDtenA3/4sJ0UH6He2myom 1YYg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=l8FBTQDF4sEXrOhwVf51anLqIEp/2FC0tgilOWCiW+w=; b=Vna1I+1CXu8laV/8nyx/Ujt57YDQ8DZ3+FhuWHHhPhfqtmHdbWFdw42dM7nxJx+8ov XFRIUsFX8FVkE0TmtiGzVJKKy+3UCRbtTXTSOwjxaVBzOXPp2kIAqJrAHXHmY/OB8v0M nwrV0t2ZC8CKzY0CyMGSp4erD2MnwQp1uxwpTNVG5njf++/vRaTp38xTtAOYRIbFvh6Z xUmt0zkS6Y7zPJJQz1HMJTtILwGvfpxIjIvV8pVqn9LAQsaRMzthT8iDIRPrbrFQjaOk DMqzE7fbXAOG2w02P+sZwp1uWYzUJG7R2vuzJ2037swz7UhMV/9m925Kgb+lgKQx6VPV Wcjw==
X-Gm-Message-State: AGi0PubdZl3l+Cjf+nwpDv743NwNeZgx8iqWXZurY8dxkDrIPn1xe3SQ S+wsFzYYs/fJtf4FW63Z8b0wKW/XHcq4HIETbdSoXY5iM5Y=
X-Google-Smtp-Source: APiQypL0oHaRA1CvnJAo9QkJdfS2nXe/mu8U/TeHN0rwnSq45mTSEVXVSq35keyiTfsJIvP27HgfO6m8mxIDO6BB2T4=
X-Received: by 2002:a05:6e02:4cd:: with SMTP id f13mr16609597ils.300.1587568502845; Wed, 22 Apr 2020 08:15:02 -0700 (PDT)
MIME-Version: 1.0
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Wed, 22 Apr 2020 11:14:35 -0400
Message-ID: <CABNhwV11snfhSg8v9mo+5OwMDH8odgWpGX19n4b6PSpAeVFQYg@mail.gmail.com>
To: Toerless Eckert <tte@cs.fau.de>, "mboned@ietf.org" <mboned@ietf.org>, "pim@ietf.org" <pim@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ab35c805a3e298fb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/pK1U3Mx33nlDtAbWdP3CR4_iGr8>
Subject: [pim] Verizon worldwide deployment - question on Chromebook
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Apr 2020 15:15:06 -0000

Toerless / All

I just remembered after the interim meeting yesterday the reason why
Chromebook does not support multicast.

Since Chromebooks use Chrome browser as the GUI user interface it has the
same issue with not supporting NPAPI plugin.  So is unable to play
multicast natively just as with a standalone chrome browser on a pc.
Verizon has discussions with Google developers related to using Web-RTC
messaging to do the translation from multicast to unicast and we had an
engagement where me representing Verizon acted as liaison go between with
Ramp and Chromebook to see if the agent could work on Chromebook as it does
on Microsoft Windows and Mac.  There was some completely as Google places
both the development of Chromebook and Android OS mobile phone in one
bucket development platform container so that created many challenges.  I
have to dig up my notes but from what I remember we got to the point where
it was possible but Google did not see the urgency to make it happen to
support multicast.  That was disappointing for Verizon.  I will try to
follow up again to see if we can still make traction on that end as I see
multicast should be a standard capability for all platforms including all
mobile devices.  With that thread with Google will bring up Android OS and
ask about multicast support for Android if that can happen and business
necessity and that it could potentially be a marketing strategy for Android
over Apple.

At the end of the call mobile device multicast was discussed and I agree
that could be very powerful almost like bit torrent peer to peer
multicast.  On the 5G infrastructure side the RAN radio network cell tower
backhaul am guessing for peer to peer multicast would have to support pim
bidir MVPN MP2MP MDTs using any of the p-tunnel tunnel encapsulations.  I
can see that being very powerful and of course the massive bandwidth
savings for providers using multicast over unicast steaming.

At the end of call was also discussed MBONED access via any modern browser
with does not support NPAPI and finding a solution for this issue.

This is a critical industry wide issue with multicast for all enterprises
and service providers related to source or receiver endpoints not being
able to support multicast playback via web browser.

I did some extensive research on this issue a few years back before we
migrated to SSM and was only able to find 2 companies that supported an
agent based solution which was Ramp I mentioned in the presentation and
cisco vBrick.  All other methods required some extensive development and
Verizon investigated that option of possible solution with WebRTC but due
to support issues ongoing with in house we decided on off the shelf product.

I just joined MBONED yesterday and look forward to be part of the many
multicast discussions.

Kind regards


Gyan  Mishra

Network Engineering & Technology


Silver Spring, MD 20904

Phone: 301 502-1347

Email: gyan.s.mishra@verizon.com