Re: [Bier] FW: I-D Action: draft-kumar-bier-use-cases-01.txt

Hi guys - i wonder if it would be worth extending the IPTV section to
embrace content pre-placement in not only IPTV, but OTT and even
big-software update and other such CDN activity: I stay close to IP
Multicast specifically for this use case, and I always think it is
interesting that while live/linear is an obvious Multicast candidate,
pre-placing content in many caches that is known to be 'about to be heavily
requested' is actually an extremely valuable capability - even if it is not
live....

Just a thought.

While i am a n00b to the formality of an IETF draft, if you like i would be
happy to try to extend that IPTV paragraph to try to explain that 'CDN'
focussed use case...?

Let me know - ill try to contribute before the start of next week....

Kind regards

Dom

On 30 January 2015 at 21:34, Nagendra Kumar Nainar (naikumar) <
naikumar@cisco.com> wrote:

> Hi,
>
> Below is the updated version of BIER use case draft.
>
> Please read and share your comments.
>
> Regards,
> Nagendra
>
>
>
> On 1/30/15, 3:40 PM, "internet-drafts@ietf.org" <internet-drafts@ietf.org>
> wrote:
>
> >
> >A New Internet-Draft is available from the on-line Internet-Drafts
> >directories.
> >
> >
> >        Title           : BIER Use Cases
> >        Authors         : Nagendra Kumar
> >                          Rajiv Asati
> >                          Mach(Guoyi) Chen
> >                          Xiaohu Xu
> >                          Andrew Dolganow
> >                          Tony Przygienda
> >                          Arkadiy Gulko
> >       Filename        : draft-kumar-bier-use-cases-01.txt
> >       Pages           : 11
> >       Date            : 2015-01-30
> >
> >Abstract:
> >   Bit Index Explicit Replication (BIER) is an architecture that
> >   provides optimal multicast forwarding through a "BIER domain" without
> >   requiring intermediate routers to maintain any multicast related per-
> >   flow state.  BIER also does not require any explicit tree-building
> >   protocol for its operation.  A multicast data packet enters a BIER
> >   domain at a "Bit-Forwarding Ingress Router" (BFIR), and leaves the
> >   BIER domain at one or more "Bit-Forwarding Egress Routers" (BFERs).
> >   The BFIR router adds a BIER header to the packet.  The BIER header
> >   contains a bit-string in which each bit represents exactly one BFER
> >   to forward the packet to.  The set of BFERs to which the multicast
> >   packet needs to be forwarded is expressed by setting the bits that
> >   correspond to those routers in the BIER header.
> >
> >   This document describes some of the use-cases for BIER.
> >
> >
> >The IETF datatracker status page for this draft is:
> >https://datatracker.ietf.org/doc/draft-kumar-bier-use-cases/
> >
> >There's also a htmlized version available at:
> >http://tools.ietf.org/html/draft-kumar-bier-use-cases-01
> >
> >A diff from the previous version is available at:
> >http://www.ietf.org/rfcdiff?url2=draft-kumar-bier-use-cases-01
> >
> >
> >Please note that it may take a couple of minutes from the time of
> >submission
> >until the htmlized version and diff are available at tools.ietf.org.
> >
> >Internet-Drafts are also available by anonymous FTP at:
> >ftp://ftp.ietf.org/internet-drafts/
> >
> >_______________________________________________
> >I-D-Announce mailing list
> >I-D-Announce@ietf.org
> >https://www.ietf.org/mailman/listinfo/i-d-announce
> >Internet-Draft directories: http://www.ietf.org/shadow.html
> >or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
> _______________________________________________
> BIER mailing list
> BIER@ietf.org
> https://www.ietf.org/mailman/listinfo/bier
>

-- 
Dom Robinson
Co-Founder, Director and Creative Firestarter @ id3as-company ltd
Innovation, Development, Architecture, Strategy
for IT, Cloud and StreamingMedia Projects
uk.linkedin.com/in/domrobinson

Also Contributing Editor for www.StreamingMedia.com
http://www.streamingmediaglobal.com/Authors/4268-Dom-Robinson.htm