In einer eMail vom 28.11.2009 20:50:31 Westeuropäische Normalzeit schreibt [email protected]:
Well if multicast proper is not on the requirements for scaling the routing architecture, how can we set our sights higher? Do you expect multicast route scaling to be solved in some other forum like perhaps SAMRG? Dino Next to IP-Mobility, scalable multicast to multiple millions of receivers should be on the radar screen, too. All multicast holy cows should be tabled: E.g. the multicast address as such. A different protocol type plus the sender's source address may entirely replace it (and free a lot of IPv4-addresses). Cascade tree routing could be used for p2mp (=multicast) as well as mp2mp. Because it can even be combined with today's BGP, I do not see an impact on any model for a future scalable routing architecture.Multicast itself has to change, imho. I have gone over the AMT-draft roughly. I know that the authors are able to adapt its basic idea to pim-ssm. Neither here nor with my Cascade Tree Routing branching/relaying can be done at the receiver devices (uploading takes more time than downloading due to the asynchron DSL). So I see shared problems, which btw can be worked out by others than me much better. Heiner
_______________________________________________ rrg mailing list [email protected] http://www.irtf.org/mailman/listinfo/rrg
