MVPN Revisiteddraft-mnapierala-mvpn-rev-00.ppt

MVPNRevisiteddraft-mnapierala-mvpn-rev-00IETF68March2007MariaNapierala1SummaryoftheProposalC-sourceisdiscoveredbasedon1stC-SpacketreceivedonC-sharedtree(PIM-SM)andon1st(C-S,C-G)Join(PIM-SSM)PIM-SMC-treesare(bydefault)automaticallytriggeredasSPTsbyallegressPEsbutthereisnointer-PERPT-to-SPTswitchoverinitiatedbyC-routersIfasourceC-SisreachableviaseveralPEs,downstreamPEwillchooseitsBGPbestinstalledroutetoreachC--hopsareinstalledthetiebreakeriseitherhighestIPaddresswhichisthedefaultRFPselectionmethod*PEjoinsonlythosetunnelsthatwereannouncedbyitsbestnexthoptoC-SInitialC-StrafficisdroppeduntiltheS-PMSIorUI-PMSIisbuilt*Orcouldbebasedonpermulticaststateloadsplittingbutthereisnostandardmethod2NewAdditionsTobeaddedinthenextversion(-01)ofthedraftSupportofC-SharedTreesSupportofC-BidirTreesSupportofAnycastC-RPs3MainRequirementsMulticastroutinginVRFshouldfollowitsunicastroutingpolicyDownstreamPEshouldjoinonlythosetunnelsthatwereannouncedbyitsbestnexthoptoC-SorC-RPatunneltobeusedforC-SshouldnotbecreatedeitherbeforeC-ativelyon(C-S,C-G)stateRPFneighbor(upstreamPE)forC-SshouldbeuniquepersetofVRFswiththesameunicastroutingpolicytowardstheC-SRPFneighborselectionshouldnotincludenotinstalledBGProutesbecausethismightaltertheexpectedtrafficflowsinMVPNSupportofmultipleRPFneighborsforAnycastC-RPisrequired4MainDifferencesfromOtherProposalC-MulticastRouting:Point-to-pointbasednotLAN-basedRPFneighborselection(noDRorDR-likeelectionprocedure)RPFneighborselectionincludesonlyBGPinstalledroutesRPFneighborisuniquetosetofVRFswiththesameunicastroutingpolicyPEjoinsonlythosetunnelsthatwereannouncedbyitsbestnexthoptoC-SorC-RPPIM-likesupportofAnycastC-RPs:anydownstreamPEonasingleC-RPTtoclosestC-RPC-SourceDiscoverydoesnotrequirePEstoparticipateinC-RPsourcediscoveryprocessdifferentSourceDiscoveryforPIM-SSMandPIM-SM5SourceDiscoveryinMVPNProposedsolutionconsistsinASM-likeC-sourcediscoverytechniqueandresultsinthesimplificationofinter-PEmulticasttrafficpatternsASMC-sourcediscoveryprocessis“interc