should be multicast enabled. This is an important decision because it directly
affects many aspects of multicast implementation. To strategically place the
rendezvous points (RPs), you must know where all of the multicast leaf rout-
ers will be. Knowing an approximate number of potential multicast sub-
scribers can have an impact on which protocols are run in the network to
allow efficient multicast forwarding and routing.
enabling multicast for a corporate application, you would need to enable
multicast on every interface on every router throughout the enterprise. How-
ever, if you need to provide access to only the MBONE for the engineering
department, or some other department within the organization, perhaps the
most efficient method would not include end-to-end configuration and
deployment.
access. Before jumping on the project and planning for just that department,
consider that in the near future, it is likely that other departments will also
request access. Applications that will require end-to-end multicast capability
may be purchased or integrated into the enterprise. It is far better to plan an
end-to-end deployment and initially activate only the routers and interfaces
that are needed than to plan your implementation on a limited initial activa-
tion. It will be easier to "build it right the first time" than to try to come back
and work around or rebuild a poor IP multicast deployment.
important that you have previously prepared and planned for the actual con-
figuration. It isn't something that you can just sit down and throw together
(not without a lot of problems anyway).