Re: [Rmt] small group replication service, application-level multicast etc.

Justin,

  Reading the article you pointed out, your P2P mechanism
  is very clever system to copy a immutable file from peer to
  peer. If one peer that provide some part of copy but have not
  enough up-link bandwidth to deliver, request side peer look for
  other peers who connect via broader up-link and can deliver
  more while receiving from first one. And to compile several
  part from several node, FEC is used.

  Is my understanding correct?

  It is very interesting idea because popular file will be
  duplicated on many hosts broadly on the Internet already,
  requester can ask several peers to send different part of
  files while encoding FEC.

  But your system seems to be focused on the goal different from
  ours. For real time datagram exchanging like VoIP and video
  meeting, source of original is only one node and it is not
  difficult, I think nearly impossible, for the listeners to
  require other several nodes to relay each part of real time
  streaming data depending of various unsettled bandwidth
  situation.

  For me, this looks the example of "There is no one-fits-all
  multicast transport protocol."
----
Yuji

From: Justin Chapweske <justin@chapweske.com>
Subject: Re: [Rmt] small group replication service, application-level multicast etc.
Date: Wed, 19 Mar 2003 13:29:47 -0600

> >>Actually, the Swarmcast system that we developed in late 1999 utilized
> >>Forward Error Correction combined with peer-to-peer (end-system)
> >>multicast to overcome the first-mile bottleneck in systems like this.
> >>
> >>I'd be happy to discuss this approach off-line with anyone that is
> >>interested.
> >>
> > 
> > 
> > Justin,  Thanks.  Can you provide a reference?
> > Rick
> 
> Swarmcast was a commercial endeavor, so no papers were published on it.
> 
> An old article at 
> (http://www.openp2p.com/pub/a/p2p/2001/05/24/swarmcast_beta.html) 
> provides an overview of the system and I'd be happy to answer any 
> questions about it off-line.
> 
> -- 
> Justin Chapweske, Onion Networks
> http://onionnetworks.com/
> 
> _______________________________________________
> Rmt mailing list
> Rmt@ietf.org
> https://www1.ietf.org/mailman/listinfo/rmt
> 
_______________________________________________
Rmt mailing list
Rmt@ietf.org
https://www1.ietf.org/mailman/listinfo/rmt