Re: [MBONED] [blink-dev] Intent to Prototype: Multicast Receive API

Gyan Mishra <hayabusagsm@gmail.com> Wed, 23 February 2022 16:46 UTC

Return-Path: <hayabusagsm@gmail.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C89543A1154 for <mboned@ietfa.amsl.com>; Wed, 23 Feb 2022 08:46:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 tagged_above=-999 required=5 tests=[AC_DIV_BONANZA=0.001, 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, RCVD_IN_DNSWL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7VziNACuiPqY for <mboned@ietfa.amsl.com>; Wed, 23 Feb 2022 08:46:25 -0800 (PST)
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 82F473A0C89 for <mboned@ietf.org>; Wed, 23 Feb 2022 08:46:25 -0800 (PST)
Received: by mail-pj1-x1031.google.com with SMTP id h17-20020a17090acf1100b001bc68ecce4aso2878291pju.4 for <mboned@ietf.org>; Wed, 23 Feb 2022 08:46:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=M+HfGPA5UMqVLxBkVZstMeMld7nD4C1bZKIVedFttUs=; b=HqgZwGRNJFcXzHbkOkSzqdj37JDzpCv4NjZXCJidEbQf0od8wBm4KRrnybA6s7+neN Tqlh6cF5EWeFy4AtY0EYIeSPzitGpL4SlxrhQugyhH0QQD3MXwEni8wMNczOp5szBm2H MnpNeacPWK9x7qvWUUuInpijlpU8K4TQea4K/Pu6yr+2V4fKaBvSqQYt/uA+6U8SzuR1 WmBtVVEMvPse+vpmoltAydAI0HirDQs0xaxD1EaZNKBhspVXk9T9ZOgYrI0ICMy75m4l l6ZBx86PqRkZXSdvW8YZII5+iKr0heWhTuBom2JY+IFV6qnxG6qWqxKhSAckpPcMJRby TsAw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=M+HfGPA5UMqVLxBkVZstMeMld7nD4C1bZKIVedFttUs=; b=3J1x2hpdjYXvmfCNRjEjux3xLM4/pwL+8c/JNXI2M40Z4tUMxxFSqO8pC67fHkquxF +p12HEF0bRyGCP4tcvbGYtZNUEV0pc2BvlaC766m+8KQuda0W0uKryJcEoQ+JvXyLD75 tmB812GGDS3ZGwIR5+BGHRQHfbxAW8u+/LiVc4ztQybNMcWMdULSIQWdu5BZUsQJKfOD vtJ2DVuj245NSSO3KpWktQ++AgGI9P7j8gStiRb4sUG0aB9GyOpScuZUz5yLIA/lj0Vq /d6Ee5zmaw0u3BTQf6VrmwjuUBOvcYfqDHHMc8VJjUblHbogCoDA+lNhFB9DlwX578Ok UXpg==
X-Gm-Message-State: AOAM533fyOsrksnQMHEmExj2kCvUXqWb2WwFXVPL3ilfIUq0ejJwxCUn fOXGJFPOH3CUek9ubsFF+7OyXkEjPwzxxG92Ct0=
X-Google-Smtp-Source: ABdhPJxB1cbUdWX+5GgenjtwZ2Utuk7N1/2e6C7XTEty7QClmRmkmChbqeqr2hTGPzoLbPLLgP4z0B1AMRGpugNd9UY=
X-Received: by 2002:a17:90a:a594:b0:1bc:5def:a652 with SMTP id b20-20020a17090aa59400b001bc5defa652mr181667pjq.167.1645634784327; Wed, 23 Feb 2022 08:46:24 -0800 (PST)
MIME-Version: 1.0
References: <CABNhwV2PPvp4r-tcAQpxRd2_Qe0ihm+KX68VeEKw8t1OPrCZGw@mail.gmail.com> <532FF57A-DB29-4CF7-890D-815CD1973039@akamai.com>
In-Reply-To: <532FF57A-DB29-4CF7-890D-815CD1973039@akamai.com>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Wed, 23 Feb 2022 11:46:13 -0500
Message-ID: <CABNhwV1ngNASEs+tUKB_q2Xg8M+iGDVA0vhpCZGOF30bwQ8HUQ@mail.gmail.com>
To: "Holland, Jake" <jholland@akamai.com>
Cc: MBONED WG <mboned@ietf.org>, Toerless Eckert <tte@cs.fau.de>
Content-Type: multipart/alternative; boundary="000000000000bffb5505d8b23434"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/BBpYoeiKEFxIojeAZLDkUNC84NA>
Subject: Re: [MBONED] [blink-dev] Intent to Prototype: Multicast Receive API
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Feb 2022 16:46:31 -0000

Excellent!

Questions in-line

Thanks

Gyan

On Wed, Feb 23, 2022 at 11:04 AM Holland, Jake <jholland@akamai.com> wrote:

> Hi Gyan,
>
>
>
> it’s not currently expected to make it into the upstream, as Google said
> they’re not interested.  However, an implementation is available for
> experimenting with.
>
>  Gyan>  Did google say why they are not interested?
>
> I’ve been maintaining a fork that implements the proposed api (but does
> not have the authentication functionality implemented):
>
> https://github.com/GrumpyOldTroll/chromium_fork
>
>  Gyan>  That’s great.   I will try testing it out
>
> I’ve been keeping it approximately up to date with chromium releases.
> There’s .deb binaries linked from the repo that you can experiment with,
> and there’s an example page that uses the api at
> https://grumpyoldtroll.github.io/wicg-multicast-receiver-api/demo-multicast-receive-api.html
> .
>
>  Gyan> Excellent
>
> I’m looking into alternatives that might have a better chance at moving
> forward and getting adoption based on the feedback we got so far, and as
> soon as one of those is operational I’ll probably stop maintaining that
> fork and put up a note to the new thing, but for now that’s what I’ve got.
>
> Gyan>  Alternative that might get adopted by Google so they can integrate
> natively into the browser?
>


>
> The primary discussion venue for this is the W3C multicast community
> group.  You can get a rough idea of what we’ve been thinking from the
> meeting logs and videos:
>
> https://github.com/w3c/multicast-cg/tree/main/meetings
>
>  Gyan> Thanks
>
> HTH,
>
> Jake
>
>
>
> *From: *Gyan Mishra <hayabusagsm@gmail.com>
> *Date: *Tue,2022-02-22 at 8:15 PM
> *To: *"Holland, Jake" <jholland@akamai.com>, MBONED WG <mboned@ietf.org>,
> Toerless Eckert <tte@cs.fau.de>
> *Subject: *Re: [blink-dev] Intent to Prototype: Multicast Receive API
>
>
>
>
>
> Dear Jake, Toerless and MBONED
>
>
>
> Does anyone know the status of this project to allow Chrome browser to
> play multicast natively.
>
>
>
> The issue was that NPAPI plug-in is not supported and so multicast cannot
> play natively.
>
>
>
> So some dev work was needed to get this fixed and working for MBONE
> community at large.
>
>
>
> https://groups.google.com/a/chromium.org/g/net-dev/c/TjbMyPKuRHs?pli=1
> <https://urldefense.com/v3/__https:/groups.google.com/a/chromium.org/g/net-dev/c/TjbMyPKuRHs?pli=1__;!!GjvTz_vk!DhNFIJSjLlBTt2ff1aIHLB55Hz9D_vR8WG3b2uPJ37dr9hNIU4dghgNFRnRSVq8$>
>
>
>
>
>
> Copy/paste from link above.
>
>
>
> Moving blink-dev@ to BCC and forwarding this to the net-dev@ mailing list.
>
>
>
> This work proposes adding support for new network protocols to Chromium,
> which has security and privacy consequences. net-dev@ is the mailing list
> where this conversation should start. From private communications with the
> proposers of this new API their primary goal at this stage of development
> is to land an experimental implementation within Chromium in order to
> facilitate iteration and evaluation of the technology.
>
> Reilly Grant | Software Engineer | rei...@chromium.org | Google Chrome
> <https://urldefense.com/v3/__https:/www.google.com/chrome__;!!GjvTz_vk!DhNFIJSjLlBTt2ff1aIHLB55Hz9D_vR8WG3b2uPJ37dr9hNIU4dghgNFJ2r6e6c$>
>
>
>
>
>
> On Thu, Feb 4, 2021 at 1:31 PM 'Holland, Jake' via blink-dev <
> blin...@chromium.org> wrote:
>
> Contact emails
>
> jhol...@akamai.com, bq...@akamai.com
>
>
> Explainer
>
>
>
> https://github.com/GrumpyOldTroll/wicg-multicast-receiver-api/blob/master/explainer.md
> <https://urldefense.com/v3/__https:/github.com/GrumpyOldTroll/wicg-multicast-receiver-api/blob/master/explainer.md__;!!GjvTz_vk!DhNFIJSjLlBTt2ff1aIHLB55Hz9D_vR8WG3b2uPJ37dr9hNIU4dghgNFmW_6mkM$>
>
>
> Specification
>
>
>
> TBD: API spec and design document (currently just entering Intent to
> Prototype).
>
> IETF standards-track docs (all presently works in progress):
>
> - draft-ietf-mboned-ambi
> <https://urldefense.com/v3/__http:/draft-ietf-mboned-ambi/__;!!GjvTz_vk!DhNFIJSjLlBTt2ff1aIHLB55Hz9D_vR8WG3b2uPJ37dr9hNIU4dghgNFhiTQ8xc$>
> - draft-ietf-mboned-dorms
> <https://urldefense.com/v3/__http:/draft-ietf-mboned-dorms/__;!!GjvTz_vk!DhNFIJSjLlBTt2ff1aIHLB55Hz9D_vR8WG3b2uPJ37dr9hNIU4dghgNFpBPIpck$>
>
> - draft-ietf-mboned-mnat
> <https://urldefense.com/v3/__http:/draft-ietf-mboned-mnat/__;!!GjvTz_vk!DhNFIJSjLlBTt2ff1aIHLB55Hz9D_vR8WG3b2uPJ37dr9hNIU4dghgNFEzNi_XI$>
> - draft-ietf-mboned-cbacc
> <https://urldefense.com/v3/__http:/draft-ietf-mboned-cbacc/__;!!GjvTz_vk!DhNFIJSjLlBTt2ff1aIHLB55Hz9D_vR8WG3b2uPJ37dr9hNIU4dghgNF9SrvDFo$>
>
> (There will be integrated components prototyped in the browser feature
> based an appropriate subset of the above specs before origin trials begin.)
>
>
>
>
> Summary
>
> Subscribe to source-specific multicast IP channels and receive UDP
> payloads in web applications.
>
> --
>
> [image: Image removed by sender.]
> <https://urldefense.com/v3/__http:/www.verizon.com/__;!!GjvTz_vk!DhNFIJSjLlBTt2ff1aIHLB55Hz9D_vR8WG3b2uPJ37dr9hNIU4dghgNFEOI0wLY$>
>
> *Gyan Mishra*
>
> *Network Solutions Architect *
>
> *Email gyan.s.mishra@verizon.com <gyan.s.mishra@verizon.com>*
>
> *M 301 502-1347*
>
>
>
-- 

<http://www.verizon.com/>

*Gyan Mishra*

*Network Solutions A**rchitect *

*Email gyan.s.mishra@verizon.com <gyan.s.mishra@verizon.com>*



*M 301 502-1347*