-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sun, 10 Jun 2001, Michael Whisenant wrote:
On Sat, 9 Jun 2001, Tim Winders wrote:
AT&T has most/all of their backbone natively multicast enabled and will multicast enable customer access routers upon request. They do have a setup fee, but no monthly recurring fees.
Fundamentally is that not the way that it should be?
Yes, I agree.
I think that if I were an AT&T customer I am paying for the ability to flow bits at whatever speed my link or service contract was permitted. It should not depend if those bits are multicast bits or unicast bits. Then in my selection of a provider the provider that offered me more features for the same dollar would have a larger value and ultimately win my decision process.
Again, I agree. I am struggling with this issue right now.
UUnet has two levels of multicast capabilities. Their "Basic" package is receive only and is free. Their "Gold" package is full send/receive, but they charge a ton for it. The basic package seems pretty useless to me. To join a multicast group, you have to be able to send to it, right?
If you are wanting to receive multicast traffic of a live event for example, no you would not have to send to the multicast group. Your client would send an IGMP join request to the (*,Group) and then ultimately receive (host, Group) of data. Your clients and routes only need to know that there is a host registered to receive the data, then they will not PRUNE the flow.
Thanks, Michael. I had one other person inform me that JOIN requests are done with IGMP. I appreciate the correction. === Tim ********************************************** Tim Winders, MCSE, CNE, CCNA Associate Dean of Information Technology South Plains College Levelland, TX 79336 Phone: 806-894-9611 x 2369 FAX: 806-894-1549 Email: TWinders@SPC.cc.tx.us ********************************************** -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (OSF1) Comment: Made with pgp4pine 1.76 iEYEARECAAYFAjsjszEACgkQTPuHnIooYbxl5gCfX63Ol9hkl2AfFvos69jVZUpp HG8An3YusnPS+0NXFXBHLN5GU9SHeaAl =EUsG -----END PGP SIGNATURE-----