1 / 11

Softwire Mesh Multicast draft-xu-softwire-mesh-multicast-01

Softwire Mesh Multicast draft-xu-softwire-mesh-multicast-01. Mingwei Xu, Yong Cui, Shu Yang Tsinghua University Chris Metz, Greg Shephard Cisco IETF80 Meeting, Prague Mar 2011. Background. Softwires Charter and RFC4925 state multicast is a requirement

fritz
Download Presentation

Softwire Mesh Multicast draft-xu-softwire-mesh-multicast-01

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. Softwire Mesh Multicast draft-xu-softwire-mesh-multicast-01 Mingwei Xu, Yong Cui, Shu Yang Tsinghua University Chris Metz, Greg Shephard Cisco IETF80 Meeting, Prague Mar 2011

  2. Background • Softwires Charter and RFC4925 state multicast is a requirement • Softwire Mesh Unicast methods have been defined. Where is the Multicast? • MVPN-like schemes can achieve “many-to-one” mapping • “One-to-one” mapping (Internet-style multicast) is needed

  3. Update from last IETF • draft-xu-softwire-mesh-multicast-00 • Possible solutions discussion for IPv6-over-IPv4 • Limit IPv6 address space • Approximate “one-to-one” • Inter-AFBR signaling • draft-xu-softwire-mesh-multicast-01 • Give two solutions for IPv6-over-IPv4 • Limit IPv6 address space • Inter-AFBR signaling

  4. Mesh multicast framework E-IP E-IP S AFBR AFBR I-IP Transit Core AFBR AFBR E-IP E-IP R R I-IP Tree E-IP Tree

  5. IPv4-over-IPv6 (S,G) (p::S,p::G) RPF (S,G) RFC 5496

  6. Group address mapping • FFXY must be in accordance with the IPv6 multicast address format of [RFC2373] • The next 10 octets are assigned by ISP 0 16 96 127

  7. Actions performed by AFBR • Receiving a PIM message: • Downstream AFBR • If next-hop is IPv6: Perform PIM message conversion • Else: Just forwarding • Upstream AFBR • If the prefix is ISP assigned: Translate it back • Else: Just forwarding

  8. IPv6-over-IPv4 - Difficulty • Because of larger space of IPv6 address • I-IP IPv4 multicast address limitations: Not all IPv4 multicast addresses are available • Hard to map without collision

  9. Solution 1: Limit IPv6 address space • Pick up a portion of IPv6 addresses • Higher order bits should be fixed • “IPv4-Embedded IPv6 Multicast Address Format” (draft-boucadair-behave-64-multicast-address-format-01) provides a guideline • The lower bits are treated as Flow_ID

  10. Solution 2: Inter-AFBR signaling (S,G) ? (S’,G’) (S,G) S’ G G’ Upstream AFBR is given a signal for translating

  11. Summary • Only need changes on AFBR • Reduce redundant traffic compared to MVPN-like schemes • IPv4-over-IPv6 is mature, IPv6-over-IPv4 needs more details

More Related