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

  • Published on
    26-Jan-2016

  • View
    28

  • Download
    2

Embed Size (px)

DESCRIPTION

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. Outline. Background Mesh multicast framework Scenarios IPv4-over-IPv6 scenario IPv6-over-IPv4 scenario - PowerPoint PPT Presentation

Transcript

<p>PowerPoint Presentation - One-to-one m</p> <p>Softwire Mesh Multicast</p> <p>draft-xu-softwire-mesh-multicast-00 Mingwei Xu, Yong Cui, Shu YangTsinghua UniversityChris Metz, Greg ShephardCisco</p> <p>IETF79 Meeting, BeijingNov 2010IETF791OutlineBackground</p> <p>Mesh multicast framework</p> <p>Scenarios</p> <p>IPv4-over-IPv6 scenario</p> <p>IPv6-over-IPv4 scenario</p> <p>Summary</p> <p>2BackgroundSoftwires Charter and RFC4925 state multicast is a requirementOperators have expressed requirements for multicast solutionSoftwire Mesh Unicast methods have been defined. Where is the Multicast?Is section 11 of RFC5565 sufficient?MVPN-like schemes can achieve many-to-one mappingOne-to-one mapping (Internet-style multicast) is neededMany-to one mapping may introduce redundancy3Mesh multicast frameworkI-IP Transit CoreE-IPAFBRAFBRAFBRE-IPE-IPAFBRE-IPSRRI-IP TreeE-IP Tree4ScenarioIPv4-over-IPv6 scenario</p> <p>IPv6-over-IPv4 scenarioRemember that IPv6 address is longer than IPv4 address, thus additional effort will be requiredAdditional efforts will be required for IPv6-over-IPv4 scenario5IPv4-over-IPv6</p> <p>(S,G)(p::S,p::G)(S,G)RPFRFC 54964-over-6: Emerging requirement as operator build large native IPv6 networkRPF mentioned in RFC 54966Group address mappingFFXY must be in accordance with the IPv6 multicast address format of [RFC2373]</p> <p>The next 10 octets are assigned by ISP</p> <p>FFXYISP assignedIPv4 address01696127draft-xu-softwire-mesh-multicast-00 have deleted IANA assigned octets7Actions performed by AFBRProcess E-IPv4 PIM messages</p> <p>Perform E-IPv4 PIM to I-IP PIMv6 message conversion</p> <p>Transmit and receive I-IP PIMv6 messages8IPv6-over-IPv4 - DifficultyBecause of larger space of IPv6 addressHard to map without collision</p> <p>I-IP IPv4 multicast address limitations: Not all IPv4 multicast addresses are available</p> <p>Possible SolutionsLimit IPv6 address spacePick up a portion of IPv6 addressesApproximate one-to-oneSelect a good hashing function to make collision happen occasionallyInter-AFBR signalingSignal each AFBR about mapping informationLimit IPv6 address spacePick up a portion of IPv6 address to achieve one to one mapping with IPv4 address</p> <p>10Limit IPv6 address spaceIPv4 spaceLimited v6 spaceIPv6 spaceMappingThe address is group address11Approximate one-to-oneIPv6 addressIPv4 addressNeed a proper hashing function12Inter-AFBR signaling </p> <p>(S,G)(S,G)?(S,G) G GSomething like mapping server or designated AFBR13SummaryOnly need changes on AFBR</p> <p>Reduce redundant traffic compared to MVPN-like schemes</p> <p>More details will be added</p> <p>141LSLUSLI-IPv6 Backbone</p> <p>Customernetwork</p> <p>Clientnetwork</p> <p>receiver</p> <p>receiver</p> <p>S</p> <p>Clientnetwork</p> <p>1LSLUSLI-IP Backbone</p> <p>Customernetwork</p> <p>Clientnetwork</p> <p>receiver</p> <p>receiver</p> <p>S</p> <p>Clientnetwork</p>