1 / 14

Softwire Mesh Multicast: A Comprehensive Framework for IPv4 and IPv6 Scenarios

This document outlines the Softwire Mesh Multicast framework presented at the IETF79 meeting in Beijing. It highlights the background on multicast requirements, the need for various mapping methods, and scenarios involving both IPv4-over-IPv6 and IPv6-over-IPv4 configurations. It discusses challenges related to address space limits and signaling, emphasizing the necessity for "one-to-one" mapping in mesh multicast operations. The proposed solutions aim to optimize multicast traffic, reduce redundancy, and facilitate inter-AFBR signaling for better address handling in multicast communications.

shadow
Télécharger la présentation

Softwire Mesh Multicast: A Comprehensive Framework for IPv4 and IPv6 Scenarios

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-00 Mingwei Xu, Yong Cui, Shu Yang Tsinghua University Chris Metz, Greg Shephard Cisco IETF79 Meeting, Beijing Nov 2010

  2. Outline • Background • Mesh multicast framework • Scenarios • IPv4-over-IPv6 scenario • IPv6-over-IPv4 scenario • Summary

  3. Background • Softwires Charter and RFC4925 state multicast is a requirement • Operators have expressed requirements for multicast solution • Softwire Mesh Unicast methods have been defined. Where is the Multicast? • Is section 11 of RFC5565 sufficient? • MVPN-like schemes can achieve “many-to-one” mapping • “One-to-one” mapping (Internet-style multicast) is needed

  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. Scenario • IPv4-over-IPv6 scenario • IPv6-over-IPv4 scenario • Remember that IPv6 address is longer than IPv4 address, thus additional effort will be required

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

  7. 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

  8. Actions performed by AFBR • Process E-IPv4 PIM messages • Perform E-IPv4 PIM to I-IP PIMv6 message conversion • Transmit and receive I-IP PIMv6 messages

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

  10. Possible Solutions • Limit IPv6 address space • Pick up a portion of IPv6 addresses • Approximate “one-to-one” • Select a good hashing function to make collision happen occasionally • Inter-AFBR signaling • Signal each AFBR about mapping information

  11. Limit IPv6 address space IPv6 space Limited v6 space IPv4 space Mapping

  12. Approximate “one-to-one” IPv6 address IPv4 address

  13. Inter-AFBR signaling G G’ (S,G) ? (S’,G’) (S,G)

  14. Summary • Only need changes on AFBR • Reduce redundant traffic compared to MVPN-like schemes • More details will be added

More Related