Re: [MBONED] FW: [Secdispatch] Requesting agenda time for draft-krose-multicast-security"

Gyan Mishra <hayabusagsm@gmail.com> Wed, 06 April 2022 04:01 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 DAB563A0B70 for <mboned@ietfa.amsl.com>; Tue, 5 Apr 2022 21:01:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, T_SCC_BODY_TEXT_LINE=-0.01, 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 n-tmR28AaecE for <mboned@ietfa.amsl.com>; Tue, 5 Apr 2022 21:01:45 -0700 (PDT)
Received: from mail-pl1-x62a.google.com (mail-pl1-x62a.google.com [IPv6:2607:f8b0:4864:20::62a]) (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 048193A0B6C for <mboned@ietf.org>; Tue, 5 Apr 2022 21:01:44 -0700 (PDT)
Received: by mail-pl1-x62a.google.com with SMTP id d15so883475pll.10 for <mboned@ietf.org>; Tue, 05 Apr 2022 21:01:44 -0700 (PDT)
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=beCxNyVjX7G59XZA11T0t+C9C3a5x44K1t1l5PQ1NMY=; b=SwvaLcTfeg40AnEzzsRxpgSyYrQfzHRnw8vDWzNLaAqk052GnAOmYUrnotmTIll2LK i6Sguy6Bn+5BdQIffcNXkcyZYl6kYf+7JahdsUepTYWx1niW75fucR8vDCqKuRb4AK+k 3JFjXy9z85PcpiGUTWPMhqbdGkOd9K/sE0P0jAsTdcuvDhCbvFi/okeNoHpm/i7xcE75 SMOwj/hn6f9NJSa7nTonC0fWBhVxC42a0UOJZSm6xLkb7H+MlASsfyA+I2XdiC+UJQ8E 5LLJfrwYqPlLrmDoqqXzHPSGDOU9AaGNEg14aoTU0tvQwn4JrO9o49eauVERnGUu90of ikOw==
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=beCxNyVjX7G59XZA11T0t+C9C3a5x44K1t1l5PQ1NMY=; b=jqJG2JZleQoGOgOZ/Az1Yuma5xI/zzWJ+FstsEYcY6Q9iiznweeFmiJKfVzv5s4Qdd Yi0LXM5Xva/GB+ws9Kj6+e9OBRZpjHdsX4gfNrDh2LemT7bUAqZaeL44RwHAp3QaPY3L CPAdUYtHGjLWhZUhr4/jiFl4KxdnNPlJJ9K9ULTtmtrHnwa1voD4/9a6eA4i40bD/3uQ mREpj+rlS1F0RuAzsDziazPE4Qwfja/u0cDwrvHmt9lJkLZRMYmYaGJKdMdMOjZpr11L 3bKv0KQ7KiutY4DYtzziPbXoiKqkbp4HypaxT+anIMuyLa0YMwnV2AFCos12lF4n4wNI 936g==
X-Gm-Message-State: AOAM533+2EKfl7boLY6dpPzJR1T5sNYEYOopfinJjWnl04FoK1xmekBS jfkuHAl+w1nYdUy32qFqfZHFm5RMOcmKHoSVE+iymfE4
X-Google-Smtp-Source: ABdhPJy74WLSoP+HIpB5Kw5cyV+AYSUVsMdXSrhRH7qulAjmh2NSPU9OU4HfJVwHzz2IwylHq5+en2BbZ28IbDzPHJA=
X-Received: by 2002:a17:90b:3849:b0:1ca:95b3:599 with SMTP id nl9-20020a17090b384900b001ca95b30599mr7746686pjb.167.1649217703859; Tue, 05 Apr 2022 21:01:43 -0700 (PDT)
MIME-Version: 1.0
References: <DB9PR08MB660213814FDC862382AD21CBFD879@DB9PR08MB6602.eurprd08.prod.outlook.com> <886CCDF8-282A-4137-83B1-ED04C7EF6200@akamai.com> <CABNhwV39TBNmsO+JVSSuMMCbSA3yMqzz6JT=tseU+x5TtOP1BA@mail.gmail.com> <8C4362E7-5601-486A-8610-4BB0AC047902@akamai.com>
In-Reply-To: <8C4362E7-5601-486A-8610-4BB0AC047902@akamai.com>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Wed, 06 Apr 2022 00:01:33 -0400
Message-ID: <CABNhwV0KXNX_uXM2DKgRPh0ABQoSVL4Y-2rTWxWRRbMEMbiH2w@mail.gmail.com>
To: "Holland, Jake" <jholland@akamai.com>
Cc: MBONED WG <mboned@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000655c4005dbf46b5f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/OBDJ25ejfOLYR55bLv1wVLoVUys>
Subject: Re: [MBONED] FW: [Secdispatch] Requesting agenda time for draft-krose-multicast-security"
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, 06 Apr 2022 04:01:50 -0000

Thanks Jake for the clarification and additional MABR links.

Kind Regards

Gyan

On Tue, Apr 5, 2022 at 8:49 PM Holland, Jake <jholland@akamai.com> wrote:

> Hi Gyan,
>
> From: Gyan Mishra <hayabusagsm@gmail.com>
> > Date: Sun,2022-04-03 at 11:25 AM
> > Hi Jake
> >
> > I agree that Multicast ABR standardization is valuable for operators as
> customers start shifting to OTT streaming services which we are seeing
> already from the pandemic.
> >
> > Does MBONE have MABR drafts already in progress?
>
> I don't think so.  The active doc list is in the datatracker:
> https://datatracker.ietf.org/wg/mboned/documents/
>
> Although I would love to see more forward progress specifically on
> MABR, I think work on MABR-specific protocols would probably be out
> of scope for mboned.  The main reasons I wanted to point the note
> out to MBONED were:
>
> 1. it might wind up leading to a report about deployment status of
>    multicast, which is one of the things mentioned in the mboned charter
> 2. the reported improvements that were observed in practice by enabling
>    the use of multicast are also especially noteworthy
>
> Anyway, if MABR work happens at IETF, I'd expect that to fall under
> the ART area (and possibly somewhere in TSV if it's trying to use a
> new transport protocol), with hopefully some updates given to MBONED
> especially about deployment status.
>
> But I wouldn't expect to see such work adopted here, and I didn't intend
> to suggest we do so (though I would be interested to know if there's any
> work I'm not aware of yet, and I think some kind of list to track that
> might perhaps be in scope here as well as mops?)  Anyway, sorry if that
> caused any confusion.
>
> > I did a google search on MABR as far a standardization across SDOs and
> ITU came up.
> > https://www.itu.int/md/T17-SG09-C-0197/en
> >
> > DVB has a presentation on MABR
> >
> https://thebroadcastknowledge.com/2020/10/27/video-making-a-case-for-dvb-mabr/
> >
> > Another link about OTT and MABR
> >
> https://www.tvtechnology.com/news/smpte2020-finding-the-middle-ground-for-live-content-over-ott
>
> I would add at least a few more items to your list, namely a few of
> CableLabs' technical reports, as well as the MABR spec developed at
> DVB and the ROUTE/DASH work for ATSC 3.0:
>
> - IP Multicast Adaptive Bit Rate Architecture Technical Report
> (CableLabs OC-TR-IP-MULTI-ARCH-V01-141112)
>
> https://community.cablelabs.com/wiki/plugins/servlet/cablelabs/alfresco/download?id=51b3c11a-3ba4-40ab-b234-42700e0d4669
>
> - IP Multicast Controller-Server Interface Specification
> (CableLabs OC-TR-IP-MULTI-ARCH-C01-161026)
>
> https://community.cablelabs.com/wiki/plugins/servlet/cablelabs/alfresco/download?id=7102f5ad-f08e-42dc-8603-b4c2477e334e
>
> - IP Multicast Controller-Client Interface Specification
> (CableLabs OC-SP-MC-EMCI-I02-160923)
>
> https://community.cablelabs.com/wiki/plugins/servlet/cablelabs/alfresco/download?id=77eb9e28-c7ed-491a-98ba-f20507eb223e
>
> - Digital Video Broadcasting (DVB);
> Adaptive media streaming over IP multicast
> (ETSI TS 103 769 V1.1.1 (2020-11))
>
> https://www.etsi.org/deliver/etsi_ts/103700_103799/103769/01.01.01_60/ts_103769v010101p.pdf
>
> - Signaling, Delivery, Synchronization, and Error Protection
> (ATSC A/331:2022-03)
>
> https://muygs2x2vhb2pjk6g160f1s8-wpengine.netdna-ssl.com/wp-content/uploads/2022/04/A331-2022-03-Signaling-Delivery-Sync-FEC.pdf
> (Defines use of "Real-time Object delivery over Unidirectional Transport"
> for digital TV)
>
> HTH.
>
> -Jake
>
>
> --

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