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

[Toerless Eckert <[e-mail]>]

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 IETF.
  
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 (
> https://www.ietf.org/about/groups/iesg/statements/normative-informative-references/
> ).
> 
> Thanks!
> 
> Alvaro.
> 
> On December 9, 2021 at 12:19:05 PM, Greg Shepherd ([e-mail]) 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 <[e-mail]> wrote:
> 
> > This email starts a 2 week WGLC timer for
> > draft-ietf-bier-multicast-http-response. Please read and review:
> >
> > https://datatracker.ietf.org/doc/draft-ietf-bier-multicast-http-response/
> >
> > 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
> [e-mail]
> https://www.ietf.org/mailman/listinfo/bier

> _______________________________________________
> BIER mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/bier


-- 
---
[e-mail]