Nov 7, 1999 2:00 AM
`
`2/9/2017
`Google Groups
`
`Seminar - Francis - Nov 9 10am - Y'allcast architecture - Google Groups
`
`Seminar Francis Nov 9 10am Y'allcast architecture
`
`b...@isi.edu
`Posted in group: la.seminars
`
`From: Clifford Neuman <b...@ISI.EDU>
`
` USC/ISI Networking Seminar Series
`
` Yallcast: Extending the Internet Multicast Architecture
`
` Dr. Paul Francis
` Tuesday, Nov 9th, 1999 at 10am
` Hosted by: Dr. Deborah Estrin
`
` 11th floor Large Conference Room
` USC/Information Sciences Institute
` 4676 Admiralty Way
` Marina del Rey, CA
`
` http://www.isi.edu for directions
`
`If we take a broad view of the term ``multicast'' to mean any
`distribution of content to more than one machine, we find that
`multicast is proceeding along two distinct architectural tracks. On
`one track is IP multicast, which mainly targets realtime nonreliable
`applications, but for which hopes run high for reliable applications
`as well. On the other are a plethora of open or proprietary host or
`serverbased approaches, each typically targeting a specific
`application or product line.
`
`IP multicast suffers from a number of technical problems, lacks
`applications, and in general is having trouble reaching critical mass,
`especially regarding anything resembling a global infrastructure.
`Serverbased approaches are valuable and widespread, but there is no
`synergy in terms of multiple distinct groups working within the same
`architecture. As a result, progress is not as fast as it could be, and
`consumers are strapped with multiple applicationspecific
`infrastructures to deal with.
`
`This talk presents an architecture, called yallcast, that aims to
`unify both tracks under a single umbrella architecture. Yallcast
`attempts to take the best from both tracksreliable and asynchronous
`distribution from the serverbased track, and dynamic
`autoconfiguration via a simple API from the IP multicast track.
`
`A key component of yallcast is that it allows a group of endhosts (the
`hosts where the contentconsuming application resides) to
`autoconfigure themselves into a tunneled topology for the purpose of
`content distribution. Yallcast can run over IP multicast, but does
`not require it. This allows application developers to bundle yallcast
`into their applications, giving their applications robust and scalable
`configurationfree outofthebox multicast. This is key to the
`initial acceptance of yallcast and for allowing it to reach critical
`mass.
`
`https://groups.google.com/forum/print/msg/la.seminars/R9rUO8QVhT8/4fDFDJ1HGr4J?ctz=3739572_80_80_104160_76_446820
`
`1/2
`
`BUNGIE - EXHIBIT 1014
`
`
`
`Seminar - Francis - Nov 9 10am - Y'allcast architecture - Google Groups
`2/9/2017
`Yallcast is not limited, however, to endhostbased distribution. It
`can also work in infrastructure servers (boxes that receive,
`replicate, and forward content but that are not consumers of the
`content). This allows improved performance for applications that
`require it. It can also provide other benefits such as better
`security. The endhost and serverbased modes of operation taken
`together, along with yallcast's ability to utilize local islands of IP
`multicast, allow yallcast to support the broadest possible range of
`applications.
`
`
`
`Online information about the ISI Network Seminars is available at
`
`http://www.isi.edu/divisions/div7/networking_seminar.html
`
`https://groups.google.com/forum/print/msg/la.seminars/R9rUO8QVhT8/4fDFDJ1HGr4J?ctz=3739572_80_80_104160_76_446820
`
`2/2
`
`
