1 / 4

Multicast Source Notification Protocol: Efficient Source Notification System

The Multicast Source Notification of Interest Protocol (MSNIP) enables efficient signaling between applications and routers to notify source interest and receiver notifications in multicast scenarios, enhancing support for ASM and SSM. Application, host, and router interactions are streamlined, improving multicast efficiency. Application signals source status, and routers notify hosts of receiver interest. MSNIP enhances ASM support, introducing new IGMP messages for efficient communication. FHR learns source addresses directly from hosts, optimizing multicast routing.

naeva
Télécharger la présentation

Multicast Source Notification Protocol: Efficient Source Notification System

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. draft-ietf-magma-msnip-06 Multicast Source Notification of Interest Protocol (MSNIP)

  2. MSNIP overview • Application signals to stack that it is a potential source • And wants to receive notification of (receiver) interest • Host stack signals that it wants notifications to first hop router • First hop router sends notification when there are receivers • Host support needed • Application support best, but can work without • IGMP/MLD extensions • New IGMP messages • Host sends request to all igmp/mld routers address • Router unicasts notifications to the host

  3. SSM support • First hop router just learns source address from host • When FHR has interest for an (S,G), host is notified

  4. ASM support • Proposing extension to support ASM • Host signals (S,G) to FHR • If pim-sm FHR can send null-registers for (S,G) to eventually learn of (S,G) interest • This means native forwarding path available before the application starts sending • No need for pim-sm data registers? • If e.g. bidir, just pretend there is interest

More Related