1 / 4

AMT sourcing concerns

AMT sourcing concerns . Greg Shepherd shep@cisco.com. AMT objective. Allow non mcast -connected receivers(sources ) to connect to the multicast Internet Allow multicast connected sources and deployments to carry mcast native to the edge of the mcast/ucast domains

taylor
Download Presentation

AMT sourcing concerns

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. AMT sourcing concerns Greg Shepherd shep@cisco.com

  2. AMT objective • Allow non mcast-connected receivers(sources) to connect to the multicast Internet • Allow multicast connected sources and deployments to carry mcast native to the edge of the mcast/ucast domains • Allow for the efficiencies of mcast where ever it’s deployed

  3. Current draft sourcing solution • Current source address allocation mechanism does not provide for native mcast over the mcast networks. • Hand waving about tunnel-brokers (my text, sorry..) • But why not allow tunnel brokers to use AMT to source efficiently??

  4. Possible sourcing solution • Efficient mcast sourcing over AMT would require RPF to source over the mcasttopo to the relay where the source is connected • Suggestion – remove source address allocation mechanism from the draft • Ensure AMT provides for address request (and clear to send) but keep the address provisioning outside of the draft

More Related