1 / 4

Authors: Frank Brockners (fbrockne@cisco), Yiu L. Lee (yiu_lee@cablecast)

Multicast Considerations for Gateway Initiated Dual-Stack lite (draft-brockners-softwire-mcast-gi-ds-lite-00). Authors: Frank Brockners (fbrockne@cisco.com), Yiu L. Lee (yiu_lee@cable.comcast.com) IETF 79, Beijing. Overview Multicast in Subscriber Access Networks. Access Device.

avi
Download Presentation

Authors: Frank Brockners (fbrockne@cisco), Yiu L. Lee (yiu_lee@cablecast)

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. Multicast Considerations for Gateway Initiated Dual-Stack lite(draft-brockners-softwire-mcast-gi-ds-lite-00) Authors:Frank Brockners (fbrockne@cisco.com), Yiu L. Lee (yiu_lee@cable.comcast.com) IETF 79, Beijing

  2. OverviewMulticast in Subscriber Access Networks AccessDevice • Architectural Characteristics / Assumptions • Access Devices receive, but do not source IP-Multicast traffic • Gateway is first hop IP-Multicast router for Access Devices • Multicast and unicast forwarding paths in the access network (Access-Device to Gateway) can differ (e.g. due to use of “Multicast VLAN”) • Access network can contain IGMP proxies (to optimize Layer-2 multicast delivery) • Multicast NAT is not considered IGMPProxy IPv4-Multicast Source Gateway AccessDevice IPv4-MulticastNetwork IPv4-Multicast Source AccessDevice Deployment example

  3. IP-Multicast Deployment with GI-DS-lite OnlyIPv4-Unicast AccessDevice • GI-DS-lite only applies to IPv4-Unicast traffic: IPv4-Multicast forwarding does not change • If Gateway loses IPv4-Multicast connectivity while deploying GI-DS-lite: Establish a tunnel between Gateway and appropriate IP-Multicast router • Switching to AFTR as first-hop router (e.g. in case Gateway has only IPv6 connectivity)would change multicast forwarding on Gateway and challenge AFTR & network scalability • GI-DS-lite allows for overlapping IPv4 addresses on Access-Devices • Typically no additional considerations required, e.g. architectures like BBF TR-101 even contain IGMP proxies, where IGMP packets are sourced with 0.0.0.0. • For deployments with IGMPv3 and a requirement for explicit tracking, an identifier other than the Source-IPv4 address of the IGMP packets needs to be used (see also I-D.ietf-multimob-pmipv6-base-solution) IGMPProxy AFTR Gateway AccessDevice IP-Multicast Source IPv4-MulticastNetwork IP-Multicast Source AccessDevice Deployment example

  4. Next steps • More feedback is much appreciated • Adopt as a WG draft?

More Related