Possible approaches to signal IPv 4 embedded IPv

  • Slides: 12
Download presentation
Possible approaches to signal IPv 4 embedded IPv 6 Multicast Address

Possible approaches to signal IPv 4 embedded IPv 6 Multicast Address

Agenda Ø IPv 4 -IPv 6 Mcast: Problem Statement Ø Possible Solutions. Ø Solution

Agenda Ø IPv 4 -IPv 6 Mcast: Problem Statement Ø Possible Solutions. Ø Solution Comparison Ø Q&A

IPv 4 -IPv 6 Mcast: Problem Statement • Scenarios identified by draft-ietf-mboned-v 4 v

IPv 4 -IPv 6 Mcast: Problem Statement • Scenarios identified by draft-ietf-mboned-v 4 v 6 -mcast-ps as part of IPv 4 to IPv 6 Multicast translation, q q q IPv 4 source and Receivers connected over IPv 6 -Only network (4 -6 -4) IPv 6 Receiver Connected to IPv 4 source via IPv 4 Access and IPv 6 network (6 -4 -6 -4) IPv 6 Receivers and Source connected via IPv 4 -Only network (6 -4 -6) IPv 6 Receivers and IPv 4 Source (6 -4) IPv 4 Receivers and IPv 6 Source (4 -6) • Scenarios involving IPv 4 as source are of top priority.

IPv 4 -IPv 6 Mcast: Problem Statement Contd. . • Raises below requirement, q.

IPv 4 -IPv 6 Mcast: Problem Statement Contd. . • Raises below requirement, q. Embed IPv 4 group address in IPv 6 group address. q. Procedure to signal any AFBR that IPv 4 group is embedded in IPv 6 group address.

Possible Solutions Designated bit/flag in IPv 6 Multicast Address A designated field of 4

Possible Solutions Designated bit/flag in IPv 6 Multicast Address A designated field of 4 bits are reserved as 64 IX for IPv 4 -IPv 6 interconnection. First bit “M” is reserved to signal that IPv 4 group is embedded. This is documented in draft-ietf-mboned-64 -multicast-address-format-02. Well known IPv 6 Multicast prefix An IPv 6 Multicast prefix dedicated for IPv 4 -IPv 6 translation usage. Using PIM Join Attribute & MLD Auxiliary Data New PIM Join Attribute or MLD Auxiliary Data with T flag to signal that IPv 4 is embedded. This is documented in draft-kumar-mboned-64 mcast-embedded-address. Manual Configuration on each border device Assigning a specific prefix for IPv 4 -IPv 6 translation usage and statically configure the prefix in each border device. Dynamic signaling of translation prefix using another protocol (e. g. BGP) Prefixes used for IPv 4 -IPv 6 translation can be advertised across domains.

Designated bit/flag in IPv 6 Multicast Address IPv 4 Receiver AFBR requires to embed

Designated bit/flag in IPv 6 Multicast Address IPv 4 Receiver AFBR requires to embed IPv 4 group with 64 XI bits. Transit Router doesn’t require to understand 64 XI bits IGMP 239. 1. 1. 1 IPv 4 Cloud PIMv 6 FF 3 x: 0: 64 IX: G: 239. 1. 1. 1 IPv 6 Receiver PIMv 6 IPv 6 Cloud MLD FF 3 x: 0: 64 IX: G: 239. 1. 1. 1 Ø No changes required on End Host Ø AFBR should understand 64 XI bits Ø Backward compatible issue. FF 3 x: 0: 64 IX: G: 239. 1. 1. 1 IPv 6 Cloud AFBR requires to understand 64 XI bits. IPv 4 Source PIMv 4 239. 1. 1. 1 IPv 4 Cloud 239. 1. 1. 1

Well Known IPv 6 Multicast Prefix Ø No changes required on End Host Ø

Well Known IPv 6 Multicast Prefix Ø No changes required on End Host Ø AFBR should understand WKP Ø Permanent reservation for intermittent solution. IPv 4 Receiver AFBR requires to embed IPv 4 group with well-known prefix. Transit Router doesn’t require to understand Wellknown prefix IGMP 239. 1. 1. 1 IPv 4 Cloud PIMv 6 Prefix: 239. 1. 1. 1 AFBR requires to understand Wellknown prefix. IPv 6 Receiver IPv 4 Source IPv 6 Cloud MLD IPv 6 Cloud Prefix: : 239. 1. 1. 1 PIMv 6 Prefix: : 239. 1. 1. 1 PIMv 4 IPv 4 Cloud 239. 1. 1. 1

Using PIM Join Attribute & MLD Aux. Data Ø Changes required on End Host

Using PIM Join Attribute & MLD Aux. Data Ø Changes required on End Host Ø AFBR should understand Join Attribute & Aux. Data Ø Backward Compatible with no permanent reservation. IPv 4 Receiver AFBR requires to embed IPv 4 group with new Join Attribute. DR requires to understand new Auxiliary Data IGMP 239. 1. 1. 1 PIMv 6 IPv 4 Cloud Join-Attribute=T-flag AFBR requires to understand new Join Attribute. Any-Prefix: 239. 1. 1. 1 IPv 6 Receiver IPv 6 Cloud MLD PIMv 6 IPv 6 Cloud Auxiliary-Daya=T-flag Join-Attribute=T-flag Any-Prefix: : 239. 1. 1. 1 IPv 4 Source PIMv 4 IPv 4 Cloud 239. 1. 1. 1

Manual Configuration on each Border Devices Ø No changes required on End Host Ø

Manual Configuration on each Border Devices Ø No changes required on End Host Ø Manual configuration required on all AFBR. This is not scalable Ø Inter-AS – Not possible. IPv 4 Receiver Transit Router doesn’t require to understand ASLocal-prefix AFBR look into manual table and embed IPv 4 group with AS-localprefix. IGMP 239. 1. 1. 1 IPv 4 Cloud PIMv 6 AS-local-Prefix: 239. 1. 1. 1 AFBR look into manual table to identify AS-localprefix. IPv 6 Receiver IPv 4 Source IPv 6 Cloud MLD IPv 6 Cloud AS-local-Prefix: : 239. 1. 1. 1 PIMv 6 AS-local-Prefix: : 239. 1. 1. 1 PIMv 4 IPv 4 Cloud 239. 1. 1. 1

Dynamic Signaling of translation prefix Ø No changes required on End Host Ø Complex

Dynamic Signaling of translation prefix Ø No changes required on End Host Ø Complex approach. IPv 4 Receiver Transit Router doesn’t require to understand ASLocal-prefix AFBR look into BGP table and embed IPv 4 group with AS-localprefix. IGMP 239. 1. 1. 1 IPv 4 Cloud PIMv 6 AS-local-Prefix: 239. 1. 1. 1 AFBR look into BGP table to identify AS-localprefix. IPv 6 Receiver IPv 4 Source IPv 6 Cloud MLD IPv 6 Cloud AS-local-Prefix: : 239. 1. 1. 1 PIMv 6 AS-local-Prefix: : 239. 1. 1. 1 BGP-UPDATE PIMv 4 Prefix=AS-local-prefix: : IPv 4 Cloud 239. 1. 1. 1

Solution Comparison Solution Advantage Disadvantage Designated bit/flag in IPv 6 Multicast Address Ø Can

Solution Comparison Solution Advantage Disadvantage Designated bit/flag in IPv 6 Multicast Address Ø Can be signaled via existing devices Ø Changes to format. Backwards compatible issue if using existing flags Well known IPv 6 Multicast prefix Ø Backward compatible Ø Does not work with embedded-RP. Interdomain hard. Using PIM Join Attribute & MLD Auxiliary Data Ø No restrictions on group addresses Ø Requires some code changes Manual Configuration on each border devices Ø Simple to use Ø Not Scalable Ø Inter-domain communication is not possible Dynamic signaling of translation prefix using another protocol Ø Flexibility Ø Complexity

Q&A • Open for questions

Q&A • Open for questions