1 / 12

Thomas C. Schmidt t.schmidt@ieee HAW Hamburg

Mobile Multicast Sender Support in PMIPv6 Domains with Base Multicast Deployment draft-ietf-multimob-pmipv6-source-00. Thomas C. Schmidt t.schmidt@ieee.org HAW Hamburg. Objective of the Draft. Define Multicast Source Mobility for PMIP Three Basic Multicast Scenarios:

garret
Télécharger la présentation

Thomas C. Schmidt t.schmidt@ieee HAW Hamburg

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. Mobile Multicast Sender Support in PMIPv6 Domains with Base Multicast Deploymentdraft-ietf-multimob-pmipv6-source-00 Thomas C. Schmidt t.schmidt@ieee.org HAW Hamburg

  2. Objective of the Draft • Define Multicast Source Mobility for PMIP • Three Basic Multicast Scenarios: • Pragmatic base-line approach as for listeners: • Suboptimal routes are price for simplicity • Direct Multicast • Based on Proxies, PIM-S(S)M or BIDIR PIM • Optimized Source Mobility • Extended Proxies for traffic optimization 2

  3. DocumentHistory • Two initial approaches • Base solution for sourcesdraft-schmidt-multimob-pmipv6-base-source-01 • Multiple upstream proxy for sourcesdraft-zhang-multimob-msm-03.txt • Merged to • Mobile Multicast Sender Support in PMIPv6 Domains draft-schmidt-multimob-pmipv6-source-00 • Now draft-ietf-multimob-pmipv6-source-00 3

  4. 1. Base Solution • Deployment as of RFC 6224 • MLD Proxy at MAG (one instance per LMA-uplink) • Multicast router (or another proxy) a LMA • At MAG multicast data from MN is forwarded • to all downstream interfaces with subscriptions • to the upstream LMA • Transparent to ASM and SSM • Supports IPv4 access/bindings (plain GRE tunneling) • Caveat: Proxy should check subscriptions prior to forward downstream 4

  5. DR or MLD Proxy MLD Proxy forwards locally and per Uplink Multicast Base Deployment with Mobile Source +-------------+ | Multicast | | Receivers | +-------------+ / \ +----+ +----+ |LMA1| |LMA2| Multicast Anchor +----+ +----+ LMAA1 | | LMAA2 | | \\ //\\ \\ // \\ \\ // \\ Unicast Tunnel \\ // \\ \\ // \\ \\ // \\ Proxy-CoA1 || || Proxy-CoA2 +----+ +----+ |MAG1| |MAG2| MLD Proxy +----+ +----+ | | | MN-HNP1 | | MN-HNP2 | MN-HNP3 MN1 MN2 MN3 Multicast Senders & Receivers 5

  6. PIM-SM: Direct Connect Problem Issue for LMAs running PIM-SM: • PIM-SM requires sources to be directly connected • Generic problem for Proxy-augmented PIM domains (proxy is intermediate router) • Solution:Configure tunnel interface with Border bit that ends PIM domain  eliminates constraint 6

  7. Efficiency Issues • Routing is optimal for receivers at the sender’s MAG that belong to the same LMA, and for the fixed Internet • Routing detours via LMAs, whenever • Mobile listener is attached to another MAG • Mobile listener is associated with a different LMA • No way to suppress the forwarding uplink to LMA • Admission control/rate limiting may be desirable to prevent flooding LMAs 7

  8. 2. Direct Multicast Routing 8

  9. Alternative Approaches • MLD Proxies connect MAGs to multicast cloud • Single instance uplinked (tunneled) to multicast domain • PIM-SM deployed at MAGs • Problem: Use meaningful MRIB independent of PMIP unicast • Keep access network flat to avoid tardy re-routing • BIDIR-PIM deployed at MAGs • Source mobility agnostic • Simplest, most transparent approach 9

  10. 3. Optimized Source Mobility • Scenario: Proxies at MAGs • Objective: avoid re-routing, when traffic is at local MAG (at different instances) • Multiple upstream proxy for sources (MUIMP) • Traffic forwarded to multiple LMAs • Proxy-Instance Interconnect (PII) • Traffic exchange between proxy instances • SSM: Route to source-specific instance (routing table at interface needed) • ASM: Distribute according to address ranges 10

  11. Summary & Outcome • This draft defines source mobility in the basic scenarios • In easy deployments traffic flows/aggregation may be optimal, but need not be • Direct routing and extended Proxy functions to optimize traffic flows 11

  12. Questions? 12

More Related