Re: [mpls] [spring] Query related to SR Architecture

Thanks Stefano,
Although PIM based IP multicast or draft-rosen is an option for an MPLS based carrier to continue to provide mutlicast without it being label switched multicast, my understanding is that BIER introduces a bit indexed method of replication without needing intermediate routers to participate in the state.

The obvious question then would be, if a carrier decided to use SR (alongwith BIER), e.g. can BIER coexisting with SPRING/SR provide the same level of convergence/SLA for multicast traffic in existing MPLS-based core networks that a carrier would otherwise achieve using P2MP-TE (with node/link FRR)?
In other words, would potentially TI-FRR (using SR) be applicable to BIER based multicast as well ?

RegardsUsman

      From: Stefano Previdi (sprevidi) <sprevidi@cisco.com>
 To: Usman Latif <osmankh@yahoo.com> 
Cc: "spring@ietf.org" <spring@ietf.org>; "mpls@ietf.org" <mpls@ietf.org> 
 Sent: Tuesday, 15 September 2015, 19:02
 Subject: Re: [spring] Query related to SR Architecture

Hi,

if you're an operator (SP, content, etc) and looking for a multicast solution, maybe you should have a look at BIER WG.

Thanks.

s.

On Sep 15, 2015, at 9:44 AM, Usman Latif <osmankh@yahoo.com> wrote:

> Hi,
> 
> I have a basic question around SPRING/SR.
> 
> How can an IP/MPLS carrier in the market today deploy SPRING in their core network without SR being able to support efficient multicast routing in the network?
> Are we not restricting carriers by proposing the SPRING/SR architecture when we know it does not efficiently support routing of multicast traffic?
> 
> I would like get some feedback on this point
> 
> 
> thanks,
> Usman
> _______________________________________________
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring