1 / 10

mDNS (ICM3400)

mDNS (ICM3400). Proposal for Hierarchical Multicast Session Directory Architecture . Piyush Harsh & Richard Newman. Why do we need multicast?. No Universal Deployment? . Text. Text. Text. Text. Why do we need a multicast session directory?.

yoshi
Download Presentation

mDNS (ICM3400)

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. mDNS (ICM3400) Proposal for Hierarchical Multicast Session Directory Architecture Piyush Harsh & Richard Newman

  2. Why do we need multicast?

  3. No Universal Deployment? Text Text Text Text

  4. Why do we need a multicast session directory?

  5. mDNS – DNS Aware Multicast Session Directory Architecture

  6. mDNS - Architecture

  7. mDNS URL Design • In mDNS, sessions can be accessed directly if creator successfully registers keyword with it’s domain’s URS server. • mDNS URL syntax • <protocol>://<domain URL>/<URS Keyword> • Protocol could be http or any valid protocol type • Domain URL helps resolve MSD server located in the creator domain, it begins with mcast. • Example mDNS URL could be • http://mcast.cise.ufl.edu/gators • This would refer to multicast session hosted under cise domain with keyword ‘gators’ registered with cise URS server.

  8. mDNS Session Registration

  9. mDNS - Search

  10. mDNS Analysis TEXT TEXT TEXT TEXT

More Related