The general approach is to support multiple levels of overlay networks,
each of which extracts a subgraph from the overlay below it, until we
have selected the subgraph that the application expects. For end system
multicast, in particular, this happens in two stages: First we construct
a simple mesh overlay on top of the fully connected Internet, and then
we select a multicast tree within this mesh. The idea is illustrated in
Figure 9.22, again assuming the four end hosts A, B, C, and D. The first
step is the critical one: Once we have selected a suitable mesh overlay, we
simply run a standard multicast routing algorithm (e.g., DVMRP) on top
of it to build the multicast tree. We also have the luxury of ignoring the
scalability issue that Internet-wide multicast faces since the intermediate
mesh can be selected to include only those nodes that want to participate
in a particular multicast group.
The key to constructing the intermediate mesh overlay is to select a
topology that roughly corresponds to the physical topology of the underlying
Internet, but we have to do this without anyone telling us what the
underlying Internet actually looks like since we are running only on end
hosts and not routers. The general strategy is for the end hosts to measure
the roundtrip latency to other nodes and decide to add links to the mesh
only when they like what they see. This works as follows.
The general approach is to support multiple levels of overlay networks,each of which extracts a subgraph from the overlay below it, until wehave selected the subgraph that the application expects. For end systemmulticast, in particular, this happens in two stages: First we constructa simple mesh overlay on top of the fully connected Internet, and thenwe select a multicast tree within this mesh. The idea is illustrated inFigure 9.22, again assuming the four end hosts A, B, C, and D. The firststep is the critical one: Once we have selected a suitable mesh overlay, wesimply run a standard multicast routing algorithm (e.g., DVMRP) on topof it to build the multicast tree. We also have the luxury of ignoring thescalability issue that Internet-wide multicast faces since the intermediatemesh can be selected to include only those nodes that want to participatein a particular multicast group.The key to constructing the intermediate mesh overlay is to select atopology that roughly corresponds to the physical topology of the underlyingInternet, but we have to do this without anyone telling us what theunderlying Internet actually looks like since we are running only on endhosts and not routers. The general strategy is for the end hosts to measurethe roundtrip latency to other nodes and decide to add links to the meshonly when they like what they see. This works as follows.
การแปล กรุณารอสักครู่..
