Re: [Bier] WGLC: draft-ietf-bier-multicast-http-response

Gyan Mishra <> Wed, 22 December 2021 23:14 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 778BB3A0CF6; Wed, 22 Dec 2021 15:14:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.097
X-Spam-Status: No, score=-1.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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id u3SFcfNH7BxW; Wed, 22 Dec 2021 15:14:45 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4864:20::1032]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id A49393A0D8D; Wed, 22 Dec 2021 15:14:45 -0800 (PST)
Received: by with SMTP id f18-20020a17090aa79200b001ad9cb23022so3960918pjq.4; Wed, 22 Dec 2021 15:14:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=/CAvFRHo9dog/3TCsRm8RQjpQs7zXtYOgNJ/1pl/XU0=; b=TR4dGS9AL2R93imxTWphVzQBeJfW3tbeUpG3VxGCaaa1KGH2p3ivrEhBfANeQI3IcL wsi36IMnluSixPvbJkEgUrsrvSW706dOWrvSr+gFn1yeDvkTVfdDzFiDy2o9PYkeNyds pYcevMiet4zidr6ob19uQWRIBRiZ+VS3UQL7yIMMA06ffYSFxrWbwkescTZfBYvkOk5Y q55VyYyrBdYghgPc8XlCCXQdfdJIEI0PtkatsQUFuJPBvj5hLlRGVbPXUmNaw8aCeRLB UbHUUH1PJN/9jQqh9vauF3E2h+h6iKXvHdPOR/Wvp/So3GQ07WgcvioKmrSB6SdczEQU O6Dg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=/CAvFRHo9dog/3TCsRm8RQjpQs7zXtYOgNJ/1pl/XU0=; b=1cfWj8Be+PfyEjRdi4fKt6br2OwPmaJ55h7pqL+yVp2cQPD50iI19qhTEhGcIb4qVz fFZ9y1Yo7NYyHjr/gEIsfU79j0yZD1Z9Gt2QaI6RO/wfeg7ciFRwlccih4g85otAejkY 9qDJzv0Lr8wOLvKoLFvtglmH5LeXEAc0qsTpjA4WK/PxsQCcm6Mm+OfgaruVeT7ntAzX No7rErHQEM3pfBiuWsWn5PvkU8yDfV4Ae1EXBTos9ZJKc8l0bImqBJVhd4v7DjoliCVP /tAhuxHRfl6XahUZJ3j8eRVLJUoMc3ZAciyaR7XthGddMgRvRR/VMAJbwXGJPfvO9/+U QR1w==
X-Gm-Message-State: AOAM530a/CAkC6LrQ/e/gxBD7ZAprIgw8frq22sMJq3UxVglxqUb23Cp 0ZChYSoDSwOOIOrp+0uFtXacdjZfn8f8qyZjEwQ=
X-Google-Smtp-Source: ABdhPJxoAGIdTHobxpYktPrWbwOWa7Lh+TYgU98gU5FaIyEPteKdhYRMJRLdGXv/wekndO5V1KCDIRR+0dgcKxZbYlc=
X-Received: by 2002:a17:902:c948:b0:149:2dde:6157 with SMTP id i8-20020a170902c94800b001492dde6157mr4718381pla.58.1640214883773; Wed, 22 Dec 2021 15:14:43 -0800 (PST)
MIME-Version: 1.0
References: <> <> <> <>
In-Reply-To: <>
From: Gyan Mishra <>
Date: Wed, 22 Dec 2021 18:14:33 -0500
Message-ID: <>
To: Toerless Eckert <>
Cc: Alvaro Retana <>, BIER WG <>,
Content-Type: multipart/alternative; boundary="00000000000080b32305d3c4493a"
Archived-At: <>
Subject: Re: [Bier] WGLC: draft-ietf-bier-multicast-http-response
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "\"Bit Indexed Explicit Replication discussion list\"" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 22 Dec 2021 23:14:51 -0000


I support publication  of this informational draft which provides the
framework and basis of how stateless BIER infrastructure can eliminate
state and bandwidth usage with an aggregate http response when many client
join a stream.  I would be happy to collaborate on the draft.

I have some comments on the draft based on my experience working with
multicast video delivery:

Is the waste in transmission bandwidth due to PIM Assert and double stream
when multiple first hop routers are connected to the source?

Can you comment on the increase in signaling when there are a few
subscribers?  I assume you are referring to IGMP join last hop router

The goal of BIER is to eliminate state in the core for MVPN P-tree and
C-Tree tree building technologies and not the last hop router as that is on
the customer side signaling.

I read through this RFC related to IRTF ICN deployments scenario discussed
related to 80 nodes test, however not much detail is provided related to
the adaptive multicast streaming testing.

I read through this draft section 3.10 and it also does not provide details
into how multicast adaptive video delivery works without having a gateway
or server that does an ingest of the adaptive video to source the multicast
distribution stream over UDP transport.

The key point I am missing is how adaptive video is natively possible over
UDP transport.

Comments below are related to multicast and adaptive streaming.  The
problem with multicast is it uses UDP transport and is a one way stream and
not bidirectional so no feedback mechanism exists for adaptive rate
limiting.  I believe QUIC with sideband TCP channel  is a possibility which
I have investigated as an alternate transport to UDP.  PGM pragmatic
multicast is another possibility.

My understanding and experience with HLS and DASH adaptive streaming which
uses chunks and segments natively both video delivery methods only support
Unicast video delivery.  Does not support native delivery via multicast.

Most all modern web browsers Chrome, Firefox and Safari etc do not support
NPAPI plug in and thus cannot play multicast natively.  That is a major
industry wide problem.

There are standard solutions that exist that involve a UDP wrapper at the
source multicast gateway that ingests unicast and distributes  multicast.

Ramp is one vendor that provides such a solution.
Ramp uses a source sender that ingests HLS or DASH unicast stream and
packages in UDP envelope and at the host receiver endpoint Window or Mac it
strips UDP encapsulation and plays out HLS or DASH video natively on

Wowza is another vendor that does support multicast streaming but requires
ingest as well of adaptive steam and then sources multicast distribution

There has been development work done with WebRTC messaging that has the
ability to provide a similar solution to natively play out multicast in a
web browser.

This is the only link below I could find on DASH multicast.

Some history on DVB:

DVB is basically MPEG video delivery over an IP network.  There was a DVB
IETF WG which concluded decades ago and since had been a standards forum
for digital video delivery.

This document was published in 2018 and talks about adaptive streaming over
IP multicast.

This document talks about how ingest occurs if adaptive video source stream
done by a multicast server which encapsulated and delivers the multicast
over the network.

3GPP 5G to support MBS Multicast and Broadcast Services with release 17
adaptive video delivery MPEG DASH

This solution to use BIER could apply to any network that utilizes adaptive
video on FBB, MBB as well as an other network so  could have ubiquitous use

I can provide a further review of the draft and input to help advance the

Many Thanks!


On Mon, Dec 20, 2021 at 3:13 PM Toerless Eckert <> wrote:

> Dear BIER WG-chairs
> a) As authors, we are pinging other WG members to ask for more reviews
> within BIER-WG.
> b) Picking up on Alvaros suggestion (thanks a lot), i would like to request
>   on behalf of the authors a TSVART (Transport Area Review Team).
> (we will ask for Application Area review later.. working ourselves up the
> stack).
> Here is the suggested text for the datatracker form through which
> you WG chairs could reques
> Deadline:
>   02-15-2022
> Document revision:
>   draft-ietf-bier-multicast-http-response-06
> Requester's comments and instructions
>   The authors are requesting early review of the document from transport
> area.
>   The following is a motivational summary of the purpose of this document:
>   Adaptive bitrate streaming (such as today DASH) for live-streaming or
> short-tail can
>   use Multicast to improve network efficiency by eliminating duplicate
> transmission
>   of the same data segments to multiple users requiring the same bitrate.
> This
>   was shown and used in products as early as 200x (e.g.: Digital
> Fountain).
>   These solutions never proliferated because of the intrinsic signaling
> problems
>   of IP Multicast causing severe performance/scale/operational issues.
>   These IP Multicast limitations can today be overcome with the novel BIER
>   multicast mechanism. This document describes an application solution
> layer
>   architecture in which BIER is used as the multicast mechanism for HTTP
>   adaptive bitrate streaming including the use of BIER-TE for including
>   path steering optimizations into the solution. This document is solely
>   informational and does not intend to establish any standards for the
> Thank you so much
>     Toerless (for the authors)
> On Fri, Dec 17, 2021 at 05:09:36AM -0800, Alvaro Retana wrote:
> > Greg:
> >
> > Hi!
> >
> > It is important in light of rfc8789, which requires that all IETF
> documents
> > reach consensus, to demonstrate that the WG cares and has reviewed,
> > commented, etc.  Silence is not a good indicator of consensus. Thanks for
> > following up on this!
> >
> > If there is interest in the WG, and given that this document deals with
> > HTTP level multicast, please request an early review from both the ART
> and
> > Transport areas review teams before sending it off for publication.
> >
> >
> > A couple of quick comments for the authors.  Please use the rfc8174
> > template (not rfc2119).  I am surprised that there are no Normative
> > references (
> >
> > ).
> >
> > Thanks!
> >
> > Alvaro.
> >
> > On December 9, 2021 at 12:19:05 PM, Greg Shepherd (
> wrote:
> >
> > Zero response for this WGLC, not even from the authors. Is this work
> still
> > of interest to anyone in the WG?
> >
> > - Shep
> >
> > On Mon, Nov 22, 2021 at 8:45 AM Greg Shepherd <> wrote:
> >
> > > This email starts a 2 week WGLC timer for
> > > draft-ietf-bier-multicast-http-response. Please read and review:
> > >
> > >
> > >
> > > We also need a doc Shepherd before we can progress this work. Can
> someone
> > > please step up to help.
> > >
> > > Thanks,
> > > - Shep
> > > (Chairs)
> > >
> > _______________________________________________
> > BIER mailing list
> >
> >
> > _______________________________________________
> > BIER mailing list
> >
> >
> --
> ---
> _______________________________________________
> BIER mailing list


*Gyan Mishra*

*Network Solutions A**rchitect *

*Email <>*

*M 301 502-1347*